s bot

ich kann da nix drauf erkennen.
mach das bild mal größer bitte^^

edit: also ich hab mal versuch zu erahnen was da stehen soll. wenn das ein fatal error is dann probier mal das hier:

Zitat

Spoiler anzeigen

Over the past year, I have seen time after time people posting of an error where sbot is unable to start clients and it just waits for a while and gives the "fatal" error. In all those topics, I post as much as I am in the mood for typing that day due to often having to deal with it as many as 3 times in a week, and no one else, mod or otherwise, seems to be familiar with the fix or even the fact that so many topics exist, so I figure making a post should make it officially inexcusable to post more topics about this issue and therefore doing so will be in violation. Any and all discussion of this topic must be done in HERE. Anyways, here's all the information about this bug that you need to know.

Origin of this Bug

This bug, as many sro_client.exe related bugs are, is actually not a sbot bug; it is in fact a bug with silkroad itself. Well, technically, it's not really a legitimate bug because it cannot happen on an unaltered client. As far as hacking tools go though, any hack that uses multiclient could potentially encounter this bug. Basically, to put it in as non-technical terms as possible, the this bug happens is when a client will fail to start up due to some problem (most commonly due to multiple clients starting simultaneously or massive lagg), and therefore the files in said directory are therefore "stuck" in the process of starting up a client until all open process from those files are closed. As a result, after this bug has occurred, no clients started from ANY multiclient tool will open successfully from that location unless you close all open clients.

Fixing This Bug

The most basic way to fix this bug is to close all open clients, either by closing all open sbot windows then making sure no sro_client are left in "Processes" in Task manager or restarting the pc. However, especially when traffic exists, doing so is not only annoying but incredibly inconvenient and causes tons of potentially lost bot time. So, when I was having troubles with this bug about a year ago, I experimented until I found a method to start clients after this bug occurs without closing existing clients.

Since it is simply the files that are preventing you from starting another client, the easiest fix to this problem is to simply make another set of files from which you can start clients.

Doing so is not very difficult, the easiest way to do it is to copy your silkroad directory next time all clients are closed (such as inspection) and paste it in the same location as the normal directory but with a slightly different name. For example, you can make it so silkroad exists in:
1 - c:\Program Files\Silkroad
2 - c:\Program Files\Silkroad II
* make sure to make shortcuts to Silkroad.exe of both for easy updating

Now, once you have your 2 silkroad locations, have it so all sbots are designated to one of those directories. If and when this bug occurs, simply switch all of your sbots to the secondary location (in case the open ones have to relog) and manually start up those that got the fatal error. As long as this doesn't happen to you twice in 1 week (which it shouldn't), you shouldn't have problems. And even if it does, provided all the clients originally started from your 1st directory had dced by then, you can simply switch back to the 1st. Also, you can do a 3rd but I wouldn't call that necessary.

Preventing This Bug

The most common thing that causes this bug to happen is that 2 clients start up at the same time and 1 fails. A good way to prevent this is to give all of your characters different restart delays, and give no one 0. For example, if you run 4 chars...
Char A - 1 minute
Char B - 2 minutes
Char C - 3 minutes
Char D - 4 minutes
Doing this makes the probability of this bug occurring reduce to almost nothing.
* if your PC is very slow and sro takes a long time to start up, make all delays x2

The less common thing that causes this bug is lagg, because it has to be extremely laggy for this bug to actually occur as a result of it. However, do run your characters on all minimum graphic settings on 800x600 windowed mode to make potential for massive lagg not as high, and if you are running as many clients as your computer can possibly manage (i.e. your computer can't function if you open another client/program) consider running 1 less.

If you have any questions/comments/need of clarification, post HERE and nowhere else on the forum.

Alles anzeigen

[quelle]http://www.bot-cave.net[/quelle]

ansonsten würd ich mal nen komplett neuen ordner machen. oder einfach pc+inet neustarten und sicher gehen das antivirus+firewall+benutzerkontensteuerung nix blocken

Er sagt:

*** FATAL: Couldn't get handle information from process (Timeout)...
* Starting of sro_client.exe failed!"

Liegt vermutlich daran, dass irgendein (AntiVirus-) Programm SRO nicht richtig ausführen lässt.
Schalte mal alles ab bzw. füge die sro_client.exe als Ausnahme hinzu.

Frage:
Startet SRO denn ohne SBot?

EDIT: zu spät... -.-

dann wird sbot geblockt.
probier sonst auch nochmal das ausführen als admin

Beim nächsten Fehler weisste dann worauf du als erstes achtest^^

Closed