Viper Update Problem

I've bought Viper Racing (again,lost my old one). This time it was part of a 4 CD ValueSoft bundle for �9.99. It installs and plays ok, but it won't let me install the viper11.exe update. It gets to 44% and stops with an error message relating to the race.bin file. Any idea's ? Also, it won't let me import or export files from the paint shop.

"redTed" <[email hidden]> wrote in news:9lrsev$b4kdm$[email hidden]:

Quoted text (9 lines)

> I've bought Viper Racing (again,lost my old one). This time it was part > of a 4 CD ValueSoft bundle for �9.99. > It installs and plays ok, but it won't let me install the viper11.exe > update. It gets to 44% and stops with an error message relating to the > race.bin file. Any idea's ? > Also, it won't let me import or export files from the paint shop. > > >

I have exactly the same problem with patching. I'm running under Windows ME, and it was the Sierra Originals budget package. Import and export works fine for me. Note that the game doesn't indicate what is going on, or throws up a file selection box or anything like that - - only reads from and writes to the paint.tga file in the Config\Paint subdirectory. -- "Hamsters - more fun for less money" Per Thulin Spamblock in operation - remove the obvious to reply by mail.

It's possible that the patch may not run because you already have the latest version. My memory is foggy on this, but I recall that we may have used a patch program that would only patch from 1.0 to 1.1... you can tell which version you have by going to the Options screen in Viper and seeing if there's a little "v1.1" in the lower right-hand corner of the screen, just above the bottom bar--the unpatched version would say either "1.0" or have nothing there. I don't know how Sierra repackaged the game for the budget version, but it's quite likely they shipped a "pre-patched" version. If that was the case, then obviously the patch program is not giving a very informative error message (blame Sierra for this one--they wrote the patch installer ;)! There also was a bug (ours, of course, and one that may not have been fixed in the patch) where if you never actually "saved" a paint job in the paintkit, you couldn't export (because saving would create a subdirectory in the Config folder for custom paint jobs, and export would try to save there even if it didn't exist). Also, of course, our import/export was as you say relatively cryptic in its operation. Life goes on. -Dave Pollatsek MGI "Per Thulin" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (18 lines)

> "redTed" <[email hidden]> wrote in > news:9lrsev$b4kdm$[email hidden]: > > > I've bought Viper Racing (again,lost my old one). This time it was part > > of a 4 CD ValueSoft bundle for �9.99. > > It installs and plays ok, but it won't let me install the viper11.exe > > update. It gets to 44% and stops with an error message relating to the > > race.bin file. Any idea's ? > > Also, it won't let me import or export files from the paint shop. > > > > > > > > I have exactly the same problem with patching. I'm running under Windows > ME, and it was the Sierra Originals budget package. > > Import and export works fine for me. Note that the game doesn't indicate > what is going on, or throws up a file selection box or anything like

that -

Quoted text (9 lines)

> - only reads from and writes to the paint.tga file in the Config\Paint > subdirectory. > > -- > "Hamsters - more fun for less money" > > Per Thulin > > Spamblock in operation - remove the obvious to reply by mail.

Dave Pollatsek wrote:

Quoted text (17 lines)

> There also was a bug (ours, of course, and one that may not have been > fixed > in the patch) where if you never actually "saved" a paint job in the > paintkit, you couldn't export (because saving would create a > subdirectory in > the Config folder for custom paint jobs, and export would try to save > there > even if it didn't exist). > Also, of course, our import/export was as you say relatively cryptic > in its > operation. > > Life goes on. > > -Dave Pollatsek > MGI >

Nice to here from someone from MGI again. So when are we gonna see Viper 2 for the PS2? :-) P.S. I rented Heat 2002 for the PS2 and thought it was pretty damned good, and this is coming from someone who hates NASCAR! -- Stuff You Gotta Have software for BeOS and PalmOS http://www.stuffyougottahave.com/

> It's possible that the patch may not run because you already have thelatest

Quoted text (8 lines)

> version. My memory is foggy on this, but I recall that we may have used a > patch program that would only patch from 1.0 to 1.1... you can tell which > version you have by going to the Options screen in Viper and seeing if > there's a little "v1.1" in the lower right-hand corner of the screen, just > above the bottom bar--the unpatched version would say either "1.0" or have > nothing there. > > I don't know how Sierra repackaged the game for the budget version, but

it's > quite likely they shipped a "pre-patched" version. If that was the case, > then obviously the patch program is not giving a very informative error > message (blame Sierra for this one--they wrote the patch installer ;)! > > There also was a bug (ours, of course, and one that may not have beenfixed > in the patch) where if you never actually "saved" a paint job in the > paintkit, you couldn't export (because saving would create a subdirectoryin > the Config folder for custom paint jobs, and export would try to savethere > even if it didn't exist). > Also, of course, our import/export was as you say relatively cryptic inits > operation. > > Life goes on. > > -Dave Pollatsek > MGI Thanks for the info. Just FYI the version number does say 1.0 in game. I think this IS the patched version though because of the race.bin error message. That would be the only reason why the installer doesn't run to it's completion. The paint export problem is related to my Photoshop 6, I believe. I'll sort that out later. I also echo the thoughts of Galley_SimRacer when he asked about a Viper2 game. It would be very nice. Cheers.

Glad you liked PS2 Heat... although I think our upcoming Xbox version will blow its doors off graphically--we're submitting a release candidate to Microsoft in a few weeks, I guess we'll see how anal Microsoft will be on their design requirements; all that fun stuff like "Rule 12, codecil J, when you refer to the X button, you must use at least a 12-pixel font and use the subjunctive mood blah blah blah". Unfortunately, the Xbox as of right now had no force-feedback standard for steering wheels, so we can't support them like we did the logitech wheel on the PS2... although gaining 5.1 surround sound and link play is a nice trade. A popular topic at work is what type of vehicle-based game to choose if we were to do another non-NASCAR title... a reworked sports car racing game would definitely be pretty fun to work on, especially now that we have more than just one track artist on our team! Especially if they gave us more than just one car license this time (Historical note: we switched from "Rivals Racing", a Need-for-Speed "killer" to "Viper Racing" at the last minute when all the licensing was falling through, poor Troy had to throw out all the other car models he made. Luckily we had zero advance press or hype, so nobody had to know we didn't plan to do it that way. I'd give my left <insert body part here> for access to the Sony/Polyphony licensing team...) Of course, I'm not sure if Sierra would want us to work for them again while we're competing with their NASCAR franchise for the "other French-owned mega corporation"... ;) "Galley_SimRacer" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (31 lines)

> Dave Pollatsek wrote: > > > > There also was a bug (ours, of course, and one that may not have been > > fixed > > in the patch) where if you never actually "saved" a paint job in the > > paintkit, you couldn't export (because saving would create a > > subdirectory in > > the Config folder for custom paint jobs, and export would try to save > > there > > even if it didn't exist). > > Also, of course, our import/export was as you say relatively cryptic > > in its > > operation. > > > > Life goes on. > > > > -Dave Pollatsek > > MGI > > > > Nice to here from someone from MGI again. So when are we gonna see > Viper 2 for the PS2? :-) > > P.S. I rented Heat 2002 for the PS2 and thought it was pretty damned > good, and this is coming from someone who hates NASCAR! > > -- > Stuff You Gotta Have > software for BeOS and PalmOS > http://www.stuffyougottahave.com/

"redTed" <[email hidden]> wrote in news:9lu3h2$b8vrd$[email hidden]:

Quoted text (40 lines)

> >> It's possible that the patch may not run because you already have the >> latest version. My memory is foggy on this, but I recall that we may >> have used a patch program that would only patch from 1.0 to 1.1... you >> can tell which version you have by going to the Options screen in >> Viper and seeing if there's a little "v1.1" in the lower right-hand >> corner of the screen, just above the bottom bar--the unpatched version >> would say either "1.0" or have nothing there. >> >> I don't know how Sierra repackaged the game for the budget version, >> but it's quite likely they shipped a "pre-patched" version. If that >> was the case, then obviously the patch program is not giving a very >> informative error message (blame Sierra for this one--they wrote the >> patch installer ;)! >> >> There also was a bug (ours, of course, and one that may not have been >> fixed in the patch) where if you never actually "saved" a paint job in >> the paintkit, you couldn't export (because saving would create a >> subdirectory in the Config folder for custom paint jobs, and export >> would try to save there even if it didn't exist). >> Also, of course, our import/export was as you say relatively cryptic >> in its operation. >> >> Life goes on. >> >> -Dave Pollatsek >> MGI > > Thanks for the info. Just FYI the version number does say 1.0 in game. > I think this IS the patched version though because of the race.bin > error message. That would be the only reason why the installer doesn't > run to it's completion. > The paint export problem is related to my Photoshop 6, I believe. I'll > sort that out later. > I also echo the thoughts of Galley_SimRacer when he asked about a > Viper2 game. It would be very nice. > Cheers. > > >

Yeah, mine says 1.0 also. I haven't really experienced any serious problems, but the rear view mirror does look VERY small in 1024x768, which is one of the probs supposedly fixed by 1.1 ... -- "Hamsters - more fun for less money" Per Thulin Spamblock in operation - remove the obvious to reply by mail.

In article <3b81a54b$0$329$[email hidden]>, [email hidden] says...

Quoted text (25 lines)

> It's possible that the patch may not run because you already have the latest > version. My memory is foggy on this, but I recall that we may have used a > patch program that would only patch from 1.0 to 1.1... you can tell which > version you have by going to the Options screen in Viper and seeing if > there's a little "v1.1" in the lower right-hand corner of the screen, just > above the bottom bar--the unpatched version would say either "1.0" or have > nothing there. > > I don't know how Sierra repackaged the game for the budget version, but it's > quite likely they shipped a "pre-patched" version. If that was the case, > then obviously the patch program is not giving a very informative error > message (blame Sierra for this one--they wrote the patch installer ;)! > > There also was a bug (ours, of course, and one that may not have been fixed > in the patch) where if you never actually "saved" a paint job in the > paintkit, you couldn't export (because saving would create a subdirectory in > the Config folder for custom paint jobs, and export would try to save there > even if it didn't exist). > Also, of course, our import/export was as you say relatively cryptic in its > operation. > > Life goes on. > > -Dave Pollatsek > MGI

Hey Dave, do you suppose you could tell us a way to get Viper Racing to run under Win 2K? Or is it just not possible? Bob

We have ran it on Win2K in our office, and I recall it ran ok, but we haven't tested it on many types of machine. I think the problem is the launcher will detect NT (i.e., Win2K) and prevent you from running (at the time we shipped Viper, NT 5.0--A.K.A Win2K--had so many problems running DirectX without crashing that we wanted to make sure Sierra tech support wouldn't be bombarded with complaints) As Win2K is obviously a lot more stable these days, I keep intending to recompile the launcher with that check disabled (I've still got the source-code on my work machine, luckily). Probably we'd have to sneak it out as a "beta" patch or something so we don't step on Sierra's toes--I don't think anyone who was involved with Viper at Sierra is still working there... if I get the time to do that, I'll post here. (Oh, and for you guys having problems getting the patch program to work, all you need to do is get the "race.bin" file from someone with the patch installed and copy it over yourself.) "R.D.S" <[email hidden]> wrote in message news:[email hidden]... > In article <3b81a54b$0$329$[email hidden]>, > [email hidden] says... > > It's possible that the patch may not run because you already have thelatest > > version. My memory is foggy on this, but I recall that we may have useda > > patch program that would only patch from 1.0 to 1.1... you can tellwhich > > version you have by going to the Options screen in Viper and seeing if > > there's a little "v1.1" in the lower right-hand corner of the screen,just > > above the bottom bar--the unpatched version would say either "1.0" orhave > > nothing there. > > > > I don't know how Sierra repackaged the game for the budget version, butit's > > quite likely they shipped a "pre-patched" version. If that was thecase, > > then obviously the patch program is not giving a very informative error > > message (blame Sierra for this one--they wrote the patch installer ;)! > > > > There also was a bug (ours, of course, and one that may not have beenfixed > > in the patch) where if you never actually "saved" a paint job in the > > paintkit, you couldn't export (because saving would create asubdirectory in > > the Config folder for custom paint jobs, and export would try to savethere > > even if it didn't exist). > > Also, of course, our import/export was as you say relatively cryptic inits

Quoted text (10 lines)

> > operation. > > > > Life goes on. > > > > -Dave Pollatsek > > MGI > Hey Dave, do you suppose you could tell us a way to get Viper Racing to > run under Win 2K? Or is it just not possible? > > Bob

In article <3b8597a9$0$322$[email hidden]>, [email hidden] says... > We have ran it on Win2K in our office, and I recall it ran ok, but we > haven't tested it on many types of machine.............. Thanks for the reply Dave, any chance the launcher can be hacked to get around this? Viper is still one of my favorites and I hate to lose it. It's the only game I had on my machine when I switched from 98 to 2K that wouldn't run (figures eh?) Thanks again, Bob

"Dave Pollatsek" <[email hidden]> wrote in message news:3b8597a9$0$322$[email hidden]... > > (Oh, and for you guys having problems getting the patch program to work,all > you need to do is get the "race.bin" file from someone with the patch > installed and copy it over yourself.) > I had the same problem patching. Found a file called viperracing111.zip at http://www.3stoutsracing.com/viperutil.htm Listed as a MGI patch stating version 1.11 and it contained the race.bin file. Changed it and now at least the software says version 1.1 It was listed as a patch for Voodo cards and 1024 x 768 resolution. ivar

Quoted text (7 lines)

> "R.D.S" <[email hidden]> wrote in message > news:[email hidden]... > > In article <3b81a54b$0$329$[email hidden]>, > > [email hidden] says... > > > It's possible that the patch may not run because you already have the > latest > > > version. My memory is foggy on this, but I recall that we may have

used

Quoted text (11 lines)

> a > > > patch program that would only patch from 1.0 to 1.1... you can tell > which > > > version you have by going to the Options screen in Viper and seeing if > > > there's a little "v1.1" in the lower right-hand corner of the screen, > just > > > above the bottom bar--the unpatched version would say either "1.0" or > have > > > nothing there. > > > > > > I don't know how Sierra repackaged the game for the budget version,

but > it's > > > quite likely they shipped a "pre-patched" version. If that was the > case, > > > then obviously the patch program is not giving a very informativeerror

Quoted text (11 lines)

> > > message (blame Sierra for this one--they wrote the patch installer ;)! > > > > > > There also was a bug (ours, of course, and one that may not have been > fixed > > > in the patch) where if you never actually "saved" a paint job in the > > > paintkit, you couldn't export (because saving would create a > subdirectory in > > > the Config folder for custom paint jobs, and export would try to save > there > > > even if it didn't exist). > > > Also, of course, our import/export was as you say relatively cryptic

in

Quoted text (13 lines)

> its > > > operation. > > > > > > Life goes on. > > > > > > -Dave Pollatsek > > > MGI > > Hey Dave, do you suppose you could tell us a way to get Viper Racing to > > run under Win 2K? Or is it just not possible? > > > > Bob > >