There is the possibility, though. Just rare exceptions. I think if you're not satisifed with the state of the game they would do it. And if you do demand a refund, that may prevent future buggy releases like this. :(

Thanks for that ATI fix
Works great.
Here is a link to ATIUMDAG.DLL from Catalyst 9.5. Seems to work well so far
This is for the Windows 7 x64 version of the driver so not sure if it'll work for others
Download Here

Thanks a lot all of you! With dgVoodoo and the 9.5 Catalyst dll the game works amazing in Glide!

I'd rather not. I had tons of blue screens due to the newer ATi drivers.
Hey out of interest is this working for people who have 64 bit operating systems? I have a 32-bit Vista.

Not just you, but everyone who contributed this fix is awesome.
I'm using Windows 7 64-bit with ATI4850 using dgvoodoo. Everything is running great. When selecting options from the main menu, I have some weird pink colors, but I don't care. :-)

This is really weird. I just tried using the 64-bit driver .dll and it works on glide perfectly with dgvoodoo even though I though I have Vista 32-bit. It looks like that is the answer.
edit: whoops, I was wrong. While Taurus doesn't freak out all the time he does it completely randomly. He drove perfectly fine and until the farm but afterwards he starts freaking out again. Damn.

Updated the OP with information about the ATi fix. Great work Zamfear and ManfromX! You've helped several folks get their groove on! :D
The 'Taurus Freakout' bug seems to be more linked to the framerate at which the game runs, and less linked to which render you're using. You'll certainly see that bug even in software rendering mode, even without any drivers loaded for your Glide wrapper. It's still touch and go about how to best limit the game's framerate, because apparently the 'ideal' setting for the game would be about 25 - 30 FPS. VSync is pretty much going to keep people in the 60-70 FPS range, depending on monitor, which seems to fix Taurus and the AI to some degree, but still breaks flamethrowers and mortars.

Has anyone tried the program FPS Limiter? It's supposed to limit the frame rates on D8, D9 and OGL games.
I cannot get it to accept shortcut switches (like -d3d) to see if it even works at all.
Maybe, someone can figure out how to get it running with I76.

Zamfear deserves most the credit :D
I fixed Taurus' driving with that CPUGrab util mentioned above.
I'm running Core2Duo @ 3.8ghz and I had to cpu limit at around 80%
It's got a nice little slider though. So if Taurus is still acting weird then bring up the options menu, alt-tab out of the game, crank the CPU usage up a little more, alt-tab back in (hit ESC a few times if the screen stays black and see how he drives. How many cycles you have to eat up is going to be different for everyone.
CPUgrab util download here

Does CPUgrab fix the mortar / flamethrower issue, as well?

I'm assuming this is the issue where it doesn't grow ?
It does once you hit a certain breaking point
Just keep increasing how much CPU time you're eating up until it behaves. Mine is around 80% like I said. You may or may not have to go that high.

YES!
CpuGRAB does fix the flamer/mortar issue. It introduces a tiny bit of jerkyness to the game for me, but there is a sweet spot where the game is quite playable with flamethrowers and mortars. Mine is about 85 percent.
Worth noting that once this is set up, you can turn off vsync, as the framerate is no longer an issue. Mine is running at 1650x1050. Menu colors are a bit wonky, but I don't care.
Note: for multicore users, set the affinity of CpuGRAB to the same processor that I76 is running in.

Tomorrow night, I will try this.
Hopefully, GoG team will try to make some "official fixes." In the mean time, I hope everyone can get this awesome game almost completely playable.
EDIT: I used 79%. The front wheel on the car still looks funny, but no cars are bouncing anymore. I could go further, but I think at 79~85% looks to be about right.

I just wanted to say thanks to you guys working on getting this fine game running for everybody - the .dll download was what finally got Glide working for me on my Radeon 4670 (also Windows Vista 32, fyi). I couldn't believe my eyes when it actually worked! I've had the game for years and NEVER got it to work until now - this fully made up for my disappointment with Gog not making the fixes themselves, as it was the reason I repurchased it. Oh well, at least the community is on the ball.
CPU Grab also slowed the game down into a fully playable, stable state. Awesome. This debacle actually ended up being slightly LESS complicated than installing Fallout 3 and making it stable, and for that I owe you THANKS, ha ha.
Also - for those using CPU Grab, if you have a dual core, you need to go into your Task Manager/Processes and set the CPU Grab affinity for 'core 0'. Tread carefully and read up on how to do this if you are confused!

This game is awesome once these fixes are in.
I never did get to play in Glide mode back in the day nor did I own Nitro.
Too bad about multiplayer atm but I'm content for now ;).
Any word if Mechwarrior 2 is a possibility ?