HN

As subject. I simply can't get Pro Rally 2001 to work under either Windows 2000 or XP. The game freezes at startup. I think it's some kind of intro it wants to play. It's weird because the company says it Windows 2000 compatible on the back of the CD ;( I've tried to run the game in Windows 98 compatibility mode, with no luck. Any suggestions?

Hei everybody I simply can't get Baldur's Gate to run properly under Windows 2000. The game is running very jerky like my machine is to slow for game. When I click at a point where I would like my characters to go it seems like they are "jumping" to that place... I've installed the newest patch for the game from Interplay (1.3.5521). Anyone have any suggestions? I'm running W2000 SP3/DX9a/P4 2,4/GF 4/1024 MB RAM and no overclock whatsoever.

Nobody have any ideas?

Can you run Baldur's Gate & TotSC in OpenGL? I didn't know - please tell me how.

No, I've looked for myself but it's very hard to find these days maybe http://www.voodoofiles.com/ has it. I can send it to you on e-mail if necessary. The name of the driver is: v2-w2k-1.00.00-beta From the Readme-file: Quote: ======================================================================= Additional ======================================================================= Voodoo2 runs on Windows 2000 Professional as a secondary display adapter only and not as a multimedia device. Microsoft did not get "detached device" support into the kernel in time to get it fully tested prior to the final Windows 2000 Professional release. Detached device support is required to run Voodoo2 as a 3D only board. This means that Voodoo2 can only run attached to a multi-monitor desktop. 3dfx has developed a driver capable of this, but there are few caveats. 1) The SLI configuration is not supported. This limits the maximum 3D resolution to 800x600. The 1024x768x16 resolution is supported for the desktop only. The Voodoo2 driver will not accelerate any DirectX operations at the 1024x768 resolution. This is because there is not enough frame buffer memory on a single Voodoo2 to practically accelerate 3D applications at this resolution. 2) Voodoo2 is only supported in Multi-monitor mode (this requires users to have an extra monitor to run their Voodoo2 card). 3) Video pass-thru is not supported. Apparently, this is the primary reason for Microsoft deciding not to put this Voodoo2 driver on the Beta3 CDs. They concluded that many users would simply ignore the readme file (that explained the caveats) and try to install and use the Voodoo2 just like they did on W9x. 4) 2D corruption on desktop. This only happens with GDI calls and it is caused by the lack of byte enabled hardware on Voodoo2. 5) No support for Glide or OpenGL. Note: DO NOT ATTEMPT TO INSTALL THE WINDOWS NT 4.0 VOODOO2 GLIDE DRIVER. I'm not sure it's worth the trouble... BTW: Is it necessary to run Windows 2000 ;( Your setup Asus P5A-B/AMD 500 Mhz/ATI 3D Rage II and Voodoo 2 is screaming for WINDOWS NT 4.0 SP6a - ATI has some good Direct3D/OpenGL NT4.0 Drivers for download on their website. - The Voodoo2 NT 4.0 Drivers works perfectly with both Direct3D/Glide. - Windows NT would run much better on your box than W2K because lets face it an AMD 500 Mhz isn't the leader of the pack anymore - And how much RAM do you have? - Etc.

Quote: I can see Voodoo 2 in System Properties and it seems to work OK. In Display Properties there is also Voodoo 2 3DFX V2-1000. BUT there is only GLIDE-alternative! That's because it's a hacked NT4.0 Driver and it's Glide only. There is an alternative Direct3D driver (no Glide!) for those who like to use the V2 as a standalone card. Quote: Testprogram Dxdiag finds only ATI and informs it´s OK (although I can´t choose Enable in 3D Acceleratorion, because button it´s not available). Dxdiag can´t find Voodoo 2 at all!!!! I'm not sure but I think the reason you can't enable 3D acceleration is because your ATI card is mostly 2D and doesn't support todays 3D acceleration features. DXdiag can't find your V2 for the obvious reason described above - it's Glide only and DXdiag is a Direct3D test. Quote: So what I can do that I can use Direct3D programs and help Dxdiag to find Voodoo 2? I think you can use Direct3D programs but it's gonna be slow with the CPU doing most of the job. Which programs have you tried that doesn't work?

I've applied the latest official patch (12.17.99) and I'm able to run the game/videos in windowed mode but not in fullscreen. I've already searched for some suggestions both here and on the net and I think the following is the solution (taken from another post): "To make the video clips work in full-screen mode in Windows 2000, get the TOMB4.EXE patch from Dec 17th (790,528 bytes) and change the byte at offset 0x93C23 from 0x74 to 0xEB. Additionally, playing the videos at 32bpp instead of 16bpp gives slightly better quality. Change the bytes at offsets 0x9C4F7 and 0x9C53C from 0x10 to 0x20 to achieve this." I can't find the suggested values when I open the file in UltraEdit but on the other hand I haven't used an hexeditor before so I would really appreciate some help with this.

Why don't you try this little free utility: http://www.sysinternals.com/ntw2k/freeware/psshutdown.shtml

So when you write "...er the glide2x, glide3x, 3dfxogl DLL other then that DirectX is mess up big in both Win9x & Win2k drivers & ...with 1.04.00 in both set of drv BooHoo hehehe." you ONLY meant the Windows 2000 drivers...ooops, I'm sorry :-)

HN just saved Alan Harris-Reid from spending money on a program he already owns, clap-clap-clap :-)

So if you follow the link (to 3dfx.com!) and look at the 3rd driver to download from the top of the page in the Windows 9x/ME-section that is NOT the v1.04.01 driver ??? (it even has a .doc with 3dfx Beta Release Notes for the Voodoo Series Windows 9x - Kit Version: 1.04.01). But I could be wrong...

Galiley The Voodoo5 card is NOT slower in Windows 2000 than Windows 98/ME. That was the situation with the first couple of drivers but with the newest v1.04.00 WHQL the situation is just the opposite for me. I'm running Q3A 3% faster in Windows 2000.

JUST DON'T BUY A CREATIVE DVD-DRIVE!!! I had their 6x/32 IDE-Drive - it was terrible. Currently I have a 10x Pioneer Slot-in which works flawlessly.

If only nVidia would offer that kind of support for my Voodoo5... :-)

Areid Adaptec/Roxio is still offering support...in german...(HA-HA) They have supplied DirectCD v3.01E (works perfect with Windows 2000) for us Windows 2000 users with WinOnCD 3.7 (it checks for WinOnCD) Link: http://www.roxio.de/german/support/list_servicepacks_g.html

Win2000 Launcher http://www.gameroffice.com/

SHS 3dfx did in fact release v1.04.01 beta drivers: http://www.3dfx.com/downloads.htm (3rd from the top)

Certainly, Microsoft has (not!) released a patch. Read: http://support.microsoft.com/support/kb/...amp;SPR=WIN2000 You can download the patch from different sources on the internet but I would wait for the "Service Pack 2" for Windows 2000 sceduled for release in February which will correct the issue.

I'm running the WHQL-drivers (same version as you) and would have tried them out tonight - thanks for the warning. You seem to be running Delta Force - Landwarrior on Windows 2000. I have considerd it as my next game-purchase and would really like to know if it runs fine (we seem to have same config/setup).

Are you running on a Pentium III? Edit config.dat (using Notepad in the install directory) and add the following line at the end of the file: Pentiumiii=0 Download the "Windows 2000 Application Compatibility Toolkit" from http://msdn.microsoft.com/compatibility/ Install and run "QFixApp". Tick the "IgnoreException.dll" and run the game. That should do the trick.

The protection issued by Microsoft shouldn't crash your program. What it does is quitting the program immediately after startup (which is off course annoying). What the new "Service Release 1" update does is checking if you're using one of the serialnumbers which has been around on the internet for a while & then disable all your Office programs. There is a way around this but I won't tell you :-)

Did you remember to disable "Fast Initialization" in the mouse properties hardware tab before using the program?