My list of NTCompatible games
This is an excel spreadsheet of all of the games that I own. Each game has been tested by me so you can be sure that the results are accurate Currently the list does not include any results for any 3rd party programs.
This is an excel spreadsheet of all of the games that I own.
Each game has been tested by me so you can be sure that the results are accurate
Currently the list does not include any results for any 3rd party programs.
The list has only been tested with the latest updates applied to the
operating system and the latest patch for the game.
For instance, if you see a DOS game with a status of "green" then this
simply means that the game works but it will of course not have any
sound in NT without using a 3rd party prog such as VDMSound.
I have kept 3rd party programs off of the main list and created a
seperate worksheet for them for a simple reason. This unclutters the
results and provides a very readable format without confusion. Also due
to the constant changes to 3rd party progs and the fact that it is in
most cases desirable to just get the games working without downloading
anything.
Currently my list has it's home here:
http://vogons.zetafleet.com/showthread.php?s=&postid=4046#post4046
Each game has been tested by me so you can be sure that the results are accurate
Currently the list does not include any results for any 3rd party programs.
The list has only been tested with the latest updates applied to the
operating system and the latest patch for the game.
For instance, if you see a DOS game with a status of "green" then this
simply means that the game works but it will of course not have any
sound in NT without using a 3rd party prog such as VDMSound.
I have kept 3rd party programs off of the main list and created a
seperate worksheet for them for a simple reason. This unclutters the
results and provides a very readable format without confusion. Also due
to the constant changes to 3rd party progs and the fact that it is in
most cases desirable to just get the games working without downloading
anything.
Currently my list has it's home here:
http://vogons.zetafleet.com/showthread.php?s=&postid=4046#post4046
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
DosFreak well i cant wait till windows xp come out so i can play maybe some of ym ea sports game they never would work. Like Nascar Revoultion , Sim theme park , Sims livin large , etc
But if they dont work ever then thats fine i can live without them because win2k is a good enough OS to give those games up forever.
I am happy i will beable to use all kind of windows xp drivers in win2k that will be a nice thing. Cant wait!!
But if they dont work ever then thats fine i can live without them because win2k is a good enough OS to give those games up forever.
I am happy i will beable to use all kind of windows xp drivers in win2k that will be a nice thing. Cant wait!!
DosFreak.........
Have you ever felt like a putz? Well I do right now! Simply put, something just didn't seem "right" about the post where you said,
".....I....found out that I didn't have Warzone 2000. Only Warzone 2100....."
......so I went back an re-read it! Well (and you don't know how embarassed I am to say this), I found that I've been repeatedly mis-typing Warzone 2000, when I should have been typing Warzone 2100 by EIDOS. Once again, I apologize for the curveball.
Now that we know we're both working with the same program, does that portion of your prior post where you say.....
".....Only Warzone 2100.....worked fine."
....now have more significance relative to my original question about screen movement lagging behing cursor movement? During play under Win98SE, mouse movement and screen-scroll were virtually identical.
Once again, sorry about the recurring typo!
SnapperOne
Have you ever felt like a putz? Well I do right now! Simply put, something just didn't seem "right" about the post where you said,
".....I....found out that I didn't have Warzone 2000. Only Warzone 2100....."
......so I went back an re-read it! Well (and you don't know how embarassed I am to say this), I found that I've been repeatedly mis-typing Warzone 2000, when I should have been typing Warzone 2100 by EIDOS. Once again, I apologize for the curveball.
Now that we know we're both working with the same program, does that portion of your prior post where you say.....
".....Only Warzone 2100.....worked fine."
....now have more significance relative to my original question about screen movement lagging behing cursor movement? During play under Win98SE, mouse movement and screen-scroll were virtually identical.
Once again, sorry about the recurring typo!
SnapperOne
DosFreak BTW how did you get 305 games work in Windows 2000 now?
with win2k 1.5 compat update or windows xp compat update from beta 2 ?
or just the normal windows compat. from windows update?
DosFreak and do you have compat update for win2k that uses RC1 compat mode or no? Like the same files and such or windows 2k 1.5 compat. update MS just released is just as good?
Thanks
with win2k 1.5 compat update or windows xp compat update from beta 2 ?
or just the normal windows compat. from windows update?
DosFreak and do you have compat update for win2k that uses RC1 compat mode or no? Like the same files and such or windows 2k 1.5 compat. update MS just released is just as good?
Thanks
For now forget about using the XP Compatibility toolkit in 2K. The 2000 1.5 App kit has all of the fixes that the XP Compatibility toolkit does. XP MIGHT have a few more game fixes right now (It definetly will have more on retail release) but anyways if you can't fix your games using the Windows 2000 1.5 App Kit then just give up for now.
Ok as far as Warzone 2100 is concerned....I made a Windows 2000 Game Demo Compatibility list which includes 800+ games. I checked that when I went home and noticed that Warzone 2100 worked fine. I know that if I put it in there that it works but I will check it again when I go home (I compiled that list like 3 months ago.).
It's highly likely tho that it is your video card. Can you borrow a newer video card to test it out? If your planning on gamming in Windows 2000 anyways you might as well fork out the money and get a GF2/3/Radeon/Kyro.
Nvidia has the best 2000 drivers at the moment but the TNT hasn't been the focus in Nvidia's drivers for a loooonnngg time.
Ok as far as Warzone 2100 is concerned....I made a Windows 2000 Game Demo Compatibility list which includes 800+ games. I checked that when I went home and noticed that Warzone 2100 worked fine. I know that if I put it in there that it works but I will check it again when I go home (I compiled that list like 3 months ago.).
It's highly likely tho that it is your video card. Can you borrow a newer video card to test it out? If your planning on gamming in Windows 2000 anyways you might as well fork out the money and get a GF2/3/Radeon/Kyro.
Nvidia has the best 2000 drivers at the moment but the TNT hasn't been the focus in Nvidia's drivers for a loooonnngg time.
DosFreak........
Already tried WarZone2100 (Hurray! Finally typed it correctly!) onto another PC here at home that is virtually identical to my PC. This second PC also runs Win2KPro, but with a slightly newer (and I mean slightly newer) video card (a Viper770 w/32Mb) and a PIII-667 vs. a PIII-533 processor.
Same results w/ explosions looking like white squares of varying sizes and screen movement lagging behind cursor movement.
With regard to your suggestion about biting the bullit and upgrading video, having just built both of these machines, so I guess I'm trying to squeeze my nickles a bit to hard. Right now I've narrowed my video card search to a Hercules GF2MX 32MB AGP or a GF2 GTS (Pro? $$$$$) 64MB from somebody. I was looking seriously at a Radeon, but I just kept reading about people having driver issues.
SnapperOne
Already tried WarZone2100 (Hurray! Finally typed it correctly!) onto another PC here at home that is virtually identical to my PC. This second PC also runs Win2KPro, but with a slightly newer (and I mean slightly newer) video card (a Viper770 w/32Mb) and a PIII-667 vs. a PIII-533 processor.
Same results w/ explosions looking like white squares of varying sizes and screen movement lagging behind cursor movement.
With regard to your suggestion about biting the bullit and upgrading video, having just built both of these machines, so I guess I'm trying to squeeze my nickles a bit to hard. Right now I've narrowed my video card search to a Hercules GF2MX 32MB AGP or a GF2 GTS (Pro? $$$$$) 64MB from somebody. I was looking seriously at a Radeon, but I just kept reading about people having driver issues.
SnapperOne
DosFreak........
Since I couldn't figure out the step-by-step procedure for installing new video drivers over older ones, a friend did it for me. Still don't know how he did it though.
Nonetheless, he loaded Detonator 12.20 drivers with no improvement. Didn't make it worse, but it didn't make it better either.
Further, since he was moving and wasn't going to be around to help with any unforeseen problems with the 12.20 driver, I had him uninstalled the 12.20 drivers, remove and reinstall the Viper550, and let Win2KPro install the MS drivers the OS spec'd for the Viper.
I can hear everyone moaning now, "How could you go back to the MS drivers". Well, since I don't fully understand the driver replacement procedure and therefore can't back my way out of a problem, I opted to go back to what I knew would work without a hitch......except for games.
SnapperOne
Since I couldn't figure out the step-by-step procedure for installing new video drivers over older ones, a friend did it for me. Still don't know how he did it though.
Nonetheless, he loaded Detonator 12.20 drivers with no improvement. Didn't make it worse, but it didn't make it better either.
Further, since he was moving and wasn't going to be around to help with any unforeseen problems with the 12.20 driver, I had him uninstalled the 12.20 drivers, remove and reinstall the Viper550, and let Win2KPro install the MS drivers the OS spec'd for the Viper.
I can hear everyone moaning now, "How could you go back to the MS drivers". Well, since I don't fully understand the driver replacement procedure and therefore can't back my way out of a problem, I opted to go back to what I knew would work without a hitch......except for games.
SnapperOne
try the 8.03 drivers they work great for TNT 2
Four and Twenty........
imtim83................
DosFreak...............
Got a post from someone who had the exact same problem on similar equipment. Says he/she found the problem was related to DirectX, and that I should make certain I am using 8.0a and not 9.0. But, since he/she couldn't tell me how to determine what DirectX I was using currently, it was suggested that I simply download 8.0a from download.com and reload it over whatever version I am using now.
Make any sense to you?
DosFreak................
"....something wrong with your config." Game config? PC config? Any best guess would be appreciated.
SnapperOne
imtim83................
DosFreak...............
Got a post from someone who had the exact same problem on similar equipment. Says he/she found the problem was related to DirectX, and that I should make certain I am using 8.0a and not 9.0. But, since he/she couldn't tell me how to determine what DirectX I was using currently, it was suggested that I simply download 8.0a from download.com and reload it over whatever version I am using now.
Make any sense to you?
DosFreak................
"....something wrong with your config." Game config? PC config? Any best guess would be appreciated.
SnapperOne
DosFreak.........
Yep! Guess you are right. Looks like we have arrived at the "what the heck" part of this pesky problem. Sooooooo, I've decided to first download NVidia drivers 6.34, then 6.50, then 7.58 to see if any of these solve the problem. Already know 12.20 didn't. Then, if no improvement, I'll load the newer DirectX version.
Catch you again sometime.
SnapperOne
Yep! Guess you are right. Looks like we have arrived at the "what the heck" part of this pesky problem. Sooooooo, I've decided to first download NVidia drivers 6.34, then 6.50, then 7.58 to see if any of these solve the problem. Already know 12.20 didn't. Then, if no improvement, I'll load the newer DirectX version.
Catch you again sometime.
SnapperOne
