Help please, I am unable to run VGcraftbot because it takes so long to patch.

Z

Zale00

Active Member
Recently I upgraded my computer and I also installed windows 64bit on it. On my old PC VGcraftbot worked fine, but now it seems like it takes absolutely forever to patch. Whenever I type in "runscript vgcraftbot" or "runscript vgcraftbot 1" It gets stuck at this...

ISXVG Subscription Active. Thank you!
...Please hold while the ISXVG patcher checks for updates...

isxGamesPatcher: Starting (Ver. 20070311.08 by CyberTech/Amadeus)

It just gets stuck there and I am unable to start VGcraftbot, it really sucks. Does anybody think they might have a solution to my woes? Any help would be most appreciated.

Thanks
 
Z

Zale00

Active Member
Lol I disabled my firewall, but the problem kinda changed now. It takes me about an hour to get it working each time I start it up. Most of the time when its trying to update it will give me the "120 seconds have passed" cancel message. So it ends up canceling the start up process whenever I try to start craftbot.

It looks like the problem is that Im updating so incredibly slowly. Before I updated this PC it was working fine, but now I'm getting this.

Any idea as to why I update so slowly? I dont think its my firewall, I disabled it and I also have a broadband connection.
 
Z

Zale00

Active Member
Any other ideas? I've disabled my firewall so it cant be that.

Earlier I was having a issue with innerspace always telling me that I required a direct x update even though I had the latest update. The way I managed to fix is was by copy and pasting the d3dx9_30.dll file into my innerspace directory.

I dont know if that helps any, but maybe there is something like that I need to do in order to fix this issue.
 
Amadeus

Amadeus

The Maestro
Staff member
My products are not designed for 64 bit systems.

Frankly, I don't think anyone should run 64 bit operating systems. I run 32 bit Vista with 4 megs of RAM ..and have yet to go over 45% memory usage. Moreover, I have a dual pentium cpu and my cpu is barely running at 30-40% (total) even when I'm doing the most on my computer.

In other words, there is no reason to run 64 bit windows. The statistics can say what they want, but in REALITY I doubt you could max out your system if you had good gear with a 32 bit OS.

So, uninstall 64 bit operating system, install 32 bit operating system, then come back if you still have problems.
 
A

axion

Active Member
Amadeus said:
. I run 32 bit Vista with 4 megs of RAM ..and have yet to go over 45% memory usage.
Click to expand...
You are aware that Vista 32bit can't fully utilize 4gb right? At the most, it will use 3gb.
 
Amadeus

Amadeus

The Maestro
Staff member
Yes, it's 4 gigs, and yes I know that.

However, with vista 32 and 4 gigs I still have not managed to get my memory usage over 50% even running multiple games, multiple instances of visual studio, multiple instances of IDA ...all at the same time.

It's a tired argument for using a 64 bit OS. The truth of the matter is that it's a waste of energy and time. If everyone was using it, fine ..but since a majority of the population is using 32 bit OS and developers simply don't the time or inclination to worry with giving adequate support for the 64 bit OS ....it's just not worth it.

I'm not even convinced that two identical computers sitting next to each other ...top of the line ...one running 32 bit Windows and the other running 64 bit Windows if a HUMAN could tell the difference. Perhaps if you're a graphic artist and rendering 3d scenes or something of that nature..but that's about the only time I think it'd be worth it.
 
Zeek

Zeek

Active Member
I run 64-bit Vista and have no issues with any of the patchers.

I run craftbot just fine without issue.

It's not a 64-bit issue.
 
B

bohicaseti

Active Member
I had this issue for a while as well. I have 2 different LAN ports on my motherboard and after doing the things you've already done, I just swapped LAN ports and everything worked just fine after that. This was a while ago (2 months or so) and I think at the time I might have been running WinXP 64bit also. I have such a frequent crashing rate (around once an hour) that I've tried every driver / OS combo I can think of and remember your scenario as one I was able to fix. So if you don't have another LAN port to switch to, maybe try looking for a different driver or do what I did and what Amadeus suggested and load WinXP 32bit back up. Maybe a dual boot if you have to have 64bit for your 3D proggies.
 
A

axion

Active Member
Having the same problem, and its not limited to 64bit os's. Sometimes its just fine sometimes it real slow and times out. Same issue on all the follow OS, Vista 64, Vista 32, XP 32, XP 64.

Maybe its just an over burdened patch server?
 
Amadeus

Amadeus

The Maestro
Staff member
Nope.

I've noticed it's slower with isxeq2 than with isxvg, and I'm not sure why. But, eventually, it will go through.

Maybe I'll ask cybertech to look into it if he has time.
 
Amadeus

Amadeus

The Maestro
Staff member
I made a change to the extension yesterday that I hope makes it run the patcher faster than it did previously. I believe it was a 'threading' issue.
 
Z

Zale00

Active Member
Its still booting up slow as molasses, takes me about 30-60 mins to get it workin. Then I crash....then its hell all over again.

It might be a threading issue though, because before I upgraded I had a dual core cpu, now im running a quad core.
 
Z

ZExit

Active Member
I'm running a quad core as well. Just installed vista64 and started encountering slow connection times as described here. What worked for me is in the task manager, right click the vgclient.exe, select 'select affinity' and deselect all but cpu 0. After that it connects instantly again.
 
A

axion

Active Member
ZExit said:
I'm running a quad core as well. Just installed vista64 and started encountering slow connection times as described here. What worked for me is in the task manager, right click the vgclient.exe, select 'select affinity' and deselect all but cpu 0. After that it connects instantly again.
Click to expand...
This does fix the issue, but a better solution I've found is launch InnerSpace, then set its Affinity to CPU0. As long as you don't close Innerspace down each time your load Vanguard, it will automatically be bound to CPU0.
 
You must log in or register to reply here.
Top Bottom