Gunner
2014-06-10 04:33:20
timeforthe - A fellow SRL user I met on Powerbot. I do not know his SRL name. If he pops in, I will be sure to update this with his proper name. He came up with this brilliant idea. He deserves all the credit for the process. His Powerbot profile - timeforthe
[spoiler="The Problem"]
Running more than 4 SMART clients, or even official RS clients results in #5 and beyond being loaded in Safe Mode. This is obviously a problem because Simba is not designed to run in Safe Mode. This has to do with the jagexcache folders and the preferences.dat and preferences2.dat files. These files are what store your graphics settings, among other things. The .dat files exist in the jagexcache, and for each new client you open, either official or otherwise, it will create a new jagexcache folder, up to a maximum of 4, and they will be named respectively. Trying to open a 5th client will not create a new folder, but will instead attempt to use the .dat files of jagexcache3 (which is actually folder #4.) Since these files are already being utilized by client #4, it will fail to load the proper graphics settings and will lock that client into Safe Mode, and thus, render it useless to Simba. I don't know whether this is intentional on the part of Jagex to prevent goldfarming, or if it simply a limitation of the system itself.[/spoiler]
[spoiler="The Solution"]
We can beat this problem in one of 2 ways.
1: Utilize multiple PC's and VPS' with Teamviewer and Remote Desktop. (A very cumbersome process that I have been using for the past 2 months.)
2: Utilize batch files to load our clients from different user accounts on the same PC. We will be learning this option here. The benefits of this solution are two fold. It solves the problem of the preferences.dat files, and it greatly reduces the system resources used by SMART and Simba. As far as I can tell already, by at least 50%. That is HUGE!
While there are no theoretical limits to how many Windows user accounts you can create, there are practical ones. Hard drive size, database functionality all play a part in where your limit is, but rest assured, you WILL run out of system resources for your SMART clients long before you run out of user accounts. So for the purpose of this tutorial, we're going to assume that a user account limit does not exist.[/spoiler]
This is going to cover the process for creating new user accounts in Win7. If you are using a different version of Windows, :google:
IMPORTANT NOTE: You will never actually be logging on to this account!
[spoiler="Creating User Accounts (Win7)"]
Step 1:
Click Start and type in "create an account", press enter. This will bring you to the account creation window.
[ATTACH=CONFIG]23377[/ATTACH]
Step 2:
Type in what you want the new account to be named. EXAMPLE: "Simba" and tick the Standard User option. Click Create Account. This will create the account, and drop you into the Manage Accounts window.
[ATTACH=CONFIG]23378[/ATTACH]
[ATTACH=CONFIG]23379[/ATTACH]
Step 3:
Click on the newly created account and select the option to Create a password. Set this to anything you like. You may also fill out the Password Hint field, but this is purely optional. As stated, you will never actually be logging on to this account, but you will need to remember the name, and password at least once.[/spoiler]
Here we will be covering the process of creating the batch files that connect our main user account to the file storage of the newly created user accounts. This will allow us to run programs on our account as other users without having to actually log on to those accounts.
[spoiler="Creating the batch files"]
Step 1:
We will need to download a piece of software first. The software is called CPAU, and it replaces the runas CMD command.
Download it here
Step 2:
Once that has finished downloading, we need to move it to the systemroot folder. Click Start again and paste this in the search bar:
%systemroot%\system32
Open that folder, and place your newly downloaded CPAU.exe file in it.
[ATTACH=CONFIG]23380[/ATTACH]
Step 3:
Open Notepad.
Step 4:
Paste this into Notepad:
cpau -u newly_created_account_name -p password -ex "simba.exe" -lwp
NOTE: Be sure to change "newly_created_account_name" to the name of the account you just created, and change "password" to the password of the account you just created.
Step 5:
Still in Notepad - File > Save As > simba.bat
This does NOT have to be named simba, it can be named anything you want, but it MUST be .bat
After being saved, move your new simba.bat file into your Simba folder. If you named it simba.bat it should land directly above Simba.exe.
[ATTACH=CONFIG]23381[/ATTACH]
Step 6:
Right click on the newly created .bat file, and create a Desktop shortcut.
[/spoiler]
Congratulations! You're now ready to run bots on top of bots on top of bots! There is no limit to the amount of users you can create, or the amount of SMARTS you can now run. The "limits" will be discovered when your scripts start to fail from lack of processing power. As stated above, this process lowers CPU usage by around 50%, but it will be up to your particular CPU/RAM/GPU as to how many clients you can run without your scripts failing.
To make use of your newly created bots, all you have to do is double-click on the .bat file and it will open Simba and it will be ready for use! You can open this same batch file up to 4 times per user account. If you need more bots, simply start again at step 1 and create more users and batch files!
Possible additional requirement: If you have never entered security credentials into the Windows command prompt before, you will need to enter the password for the newly created user account now.
To verify that you are indeed running your new bots as separate user accounts, open the task manager and verify.
So that's that. Good luck to all my fellow botters out there! Bot safe, Bot SMART, and Bot often!
