Forums » Windows
A rather odd Updater bug...
First things first:
2.4Ghz Athlon CPU
512 MB RAM
NVIDIA GeForce FX5500
VIA Rhine II Fast Ethernet Adapter (it's an on-board)
C-Media Wave Audio (another on-board)
Windows 98SE
And yes, this has changed since I was last able to run VO several years ago. And no, I can't return to my old setup because the method of change was FIRE. Shooting out the power supply. Rather nasty.
Anyway, after an all-to-long long hiatus, I decided to try jumping back in to VO and promptly smacked my head into a very solid error regarding the updater. The first time I run it, it works just fine, patches the .rlb to the latest version, and lets me play (or would, but there's a different error entirely at that point, and one I can't adequately investigate because of this Updater error).
However, on all subsequent attempts to run the updater, it fails. Here's the text it leaves:
"Checking update program...
Version is current; verifying files...
Update program is up to date. Checking Vendetta...
Unable to connect to the Vendetta Online
For more information on using Vendetta Online with
", with "Connection failed!" in the status line.
This all pops up in under a second- the Updater isn't waiting for a response from the server at all. I've checked my firewall logs, and it IS getting a response from the server. Several, in fact. It's just that it's already errored out and canceled its attempt before they could reach it. Furthermore, the error message looks suspiciously incomplete, as if it's missing the name of some device or program. I've tried canceling the updater after it updates without running the game, but it just acts like this on all future run attempts anyway, wasting my only chance to actually click on play.
I've found that re-installing allows me another single shot at running the game, but I'm fairly sure that you poor fellows wouldn't like me sucking up an update every time I try and run it, and I certainly don't like waiting about four minutes for *anything* to load, especially when I'm still trying to configure said program so it'll run. On a hunch, I tried copying the install version of Vendetta.exe to another folder, running the original and letting it patch, then copying back the install version. I was hoping it would limit the update to just vendetta.exe, as a mere 240kb update was something workable. Unfortunately, that just produced a page fault error.
So gentlemen, any ideas?
2.4Ghz Athlon CPU
512 MB RAM
NVIDIA GeForce FX5500
VIA Rhine II Fast Ethernet Adapter (it's an on-board)
C-Media Wave Audio (another on-board)
Windows 98SE
And yes, this has changed since I was last able to run VO several years ago. And no, I can't return to my old setup because the method of change was FIRE. Shooting out the power supply. Rather nasty.
Anyway, after an all-to-long long hiatus, I decided to try jumping back in to VO and promptly smacked my head into a very solid error regarding the updater. The first time I run it, it works just fine, patches the .rlb to the latest version, and lets me play (or would, but there's a different error entirely at that point, and one I can't adequately investigate because of this Updater error).
However, on all subsequent attempts to run the updater, it fails. Here's the text it leaves:
"Checking update program...
Version is current; verifying files...
Update program is up to date. Checking Vendetta...
Unable to connect to the Vendetta Online
For more information on using Vendetta Online with
", with "Connection failed!" in the status line.
This all pops up in under a second- the Updater isn't waiting for a response from the server at all. I've checked my firewall logs, and it IS getting a response from the server. Several, in fact. It's just that it's already errored out and canceled its attempt before they could reach it. Furthermore, the error message looks suspiciously incomplete, as if it's missing the name of some device or program. I've tried canceling the updater after it updates without running the game, but it just acts like this on all future run attempts anyway, wasting my only chance to actually click on play.
I've found that re-installing allows me another single shot at running the game, but I'm fairly sure that you poor fellows wouldn't like me sucking up an update every time I try and run it, and I certainly don't like waiting about four minutes for *anything* to load, especially when I'm still trying to configure said program so it'll run. On a hunch, I tried copying the install version of Vendetta.exe to another folder, running the original and letting it patch, then copying back the install version. I was hoping it would limit the update to just vendetta.exe, as a mere 240kb update was something workable. Unfortunately, that just produced a page fault error.
So gentlemen, any ideas?
When you said you reinstalled, you reinstalled with the latest installer from the web site?
First, make sure you have about 200 megs free on your harddrive.
Next, see if your harddrive has any bad sectors.
Last, you can get around using the updater once the game is updated
by renaming the vendetta.rlb file to something like vo.exe and run that directly.
Is that computer setup you listed your current computer or was it your previous computer?
First, make sure you have about 200 megs free on your harddrive.
Next, see if your harddrive has any bad sectors.
Last, you can get around using the updater once the game is updated
by renaming the vendetta.rlb file to something like vo.exe and run that directly.
Is that computer setup you listed your current computer or was it your previous computer?
"When you said you reinstalled, you reinstalled with the latest installer from the web site?"
I've just kept the same installer file since I downloaded it off of one of the official hosts on March 27th, 2008, and re-ran that to revert to the old version. I haven't checked to see if the installer has changed since.
"First, make sure you have about 200 megs free on your harddrive.
Next, see if your harddrive has any bad sectors."
11 GB free. I'll do a deep scan overnight since I can't do anything besides let it scan while it's running.
"Last, you can get around using the updater once the game is updated by renaming the vendetta.rlb file to something like vo.exe and run that directly."
This actually worked quite well! It also let me track down and get rid of the other bug- turned out that my system doesn't like Wave output even though it never reported an error in waverror.log, so a quick addition of
[wavsound]
use_dsound=1
to my config.ini fixed things nicely.
"Is that computer setup you listed your current computer or was it your previous computer?"
It's my current. My prior setup was fairly similar, except with slightly less CPU speed, slightly more memory, a real soundcard, and slightly more flammability.
Now that that's done...
I'm currently at the title screen, admiring the spinning station and grooving to the music. I suppose this counts as a near-full success, since a connect attempt from there correctly referred me to go renew my subscription. Time to renew, load up my wgaf with bloated bindings, and play busball until I regain my high-speed docking knack.
EDIT: Whoops! Not quite hunky-dory yet. The updated Updater won't patch VO to the latest version (yes, even accounting for the copied & renamed vendetta.rlb), so I still need to do the reinstall/full update to get the latest patch. "Once per patch" is still immeasurably better than "every time", so I can live with it.
I've just kept the same installer file since I downloaded it off of one of the official hosts on March 27th, 2008, and re-ran that to revert to the old version. I haven't checked to see if the installer has changed since.
"First, make sure you have about 200 megs free on your harddrive.
Next, see if your harddrive has any bad sectors."
11 GB free. I'll do a deep scan overnight since I can't do anything besides let it scan while it's running.
"Last, you can get around using the updater once the game is updated by renaming the vendetta.rlb file to something like vo.exe and run that directly."
This actually worked quite well! It also let me track down and get rid of the other bug- turned out that my system doesn't like Wave output even though it never reported an error in waverror.log, so a quick addition of
[wavsound]
use_dsound=1
to my config.ini fixed things nicely.
"Is that computer setup you listed your current computer or was it your previous computer?"
It's my current. My prior setup was fairly similar, except with slightly less CPU speed, slightly more memory, a real soundcard, and slightly more flammability.
Now that that's done...
I'm currently at the title screen, admiring the spinning station and grooving to the music. I suppose this counts as a near-full success, since a connect attempt from there correctly referred me to go renew my subscription. Time to renew, load up my wgaf with bloated bindings, and play busball until I regain my high-speed docking knack.
EDIT: Whoops! Not quite hunky-dory yet. The updated Updater won't patch VO to the latest version (yes, even accounting for the copied & renamed vendetta.rlb), so I still need to do the reinstall/full update to get the latest patch. "Once per patch" is still immeasurably better than "every time", so I can live with it.
Windows 98SE? o.O
Yes, Windows 98 Second Edition, "The Happiest Operating System on Earth!"™.
But all hyperbole aside, it works for everything I've tried it with, so I've never felt the need to change it. When I do finally need to built a new computer, it'll have to change as it's not workable on a 64 bit architecture. However, that will only happen once I come across something I need but can't run (or my current system is again cleansed by The Emperor's Holy Promethium, and 32 bit parts are unavailable).
But all hyperbole aside, it works for everything I've tried it with, so I've never felt the need to change it. When I do finally need to built a new computer, it'll have to change as it's not workable on a 64 bit architecture. However, that will only happen once I come across something I need but can't run (or my current system is again cleansed by The Emperor's Holy Promethium, and 32 bit parts are unavailable).
Nono, I think the devs also need to look into dropping Windows 98 ME and Windows 2000 support.
Honestly, use Linux if you are that stubborn.
I can reproduce this bug on 2 Windows 98 machines. I really think focus should be on Microsoft's new crock o shite.
Honestly, use Linux if you are that stubborn.
I can reproduce this bug on 2 Windows 98 machines. I really think focus should be on Microsoft's new crock o shite.
strange.
Just make Vendetta require DX9 to be installed... 9x problem solved, I s'pose...
Actually, you need to require DX10 to knock out Win 98. MS supported it up to DX9.0c before figuring out people weren't upgrading because there wasn't a critical need to upgrade. Unfortunately, requiring DX10 would knock out everyone not using Vista, and require the devs to create yet another video driver.
Thus, Apathy, Procrastination, and Not Being Evil are all on my side. With that force in my group, I'll just bring a 'moth XC loaded with the most expensive trade goods I can find, and start doing victory rolls before I even send the duel request :P
Thus, Apathy, Procrastination, and Not Being Evil are all on my side. With that force in my group, I'll just bring a 'moth XC loaded with the most expensive trade goods I can find, and start doing victory rolls before I even send the duel request :P
So MS released DX9 for Windows 9x? O.o
Well I was sure the highest version you could install on 98 was 8.1a...
Then the only way is to drop support for Windows 98/ME, I'd leave 2000 'cause it is not that different from XP.
Well I was sure the highest version you could install on 98 was 8.1a...
Then the only way is to drop support for Windows 98/ME, I'd leave 2000 'cause it is not that different from XP.
As of VO Update 1.8.34, I no longer experience this problem. It fails on the first server, but the second catches it and preforms the update routine every time.
Mission Accomplished!
Mission Accomplished!
Cool. Thanks for the update, IRS.