DosFreak

You could try setting your desktop res to different color depths. If 32bit (does Rage support 32bit? It's been 6 years since I tried gaming on a rage128...and half-life ran like crap), seen alot of Rage chips in servers tho....they do 2D fine. Also search the net for unofficial Rage drivers...there was a site where a guy put together Rage drivers because ATI was too pathetic to create proper drivers themselves...but I can remember his name even tho I should because he's pretty well known for helping out poor pre-radeon video card users. ( ATI radeon drivers are a million times better nowadays but their OGL support is still sorry compared to Nvidia).

This is a joke thread right? Good one!

I don't have the game but if it has a sound configuration program and the game uses a Soundblaster card then your need to configure the game for Port: 220 IRQ: 7 and either DMA 1 (8 bit) or DMA 5 (16bit).

Odd, MM6-7-8 run fine for me under 2000/XP/2003. Always have. MM6 has never given me any problems MM7 v1.1 Windows 2000 Set video to "Hardware Accelerated 3D". Set audio to "Disable Accelerated 3D Audio" (Haven't bothered to try an updated mss32.dll yet, also remember that you need to use the same "family" of bink version. For instance if a game uses v1.x of mss32.dll then you'll need to use a v1.x dll....you cannot use a v7.x dll".) Run MM7.exe in Windows 95 Compatibility mode. Game works. Windows XP Run the game in Windows 95 Compatibility Mode. MM8 v1.0 Windows 2000 Instructions the same as MM7 except disable all sound acceleration in DXDIAG. Windows XP Run the game in Windows 95 Compatibility mode.

Don't bother with that. It doesn't work well. Your only solution is to use Bochs/Vmware v4/Vmware v5.1 and then run Windows 9x which IIRC will offer limited direct3d software emulation. So think really old games from like 1997/1998.

Grab a NOTCD patch from www.gamecopyworld.com

Hmmmm, need to get my hands on MCE. Since the hardware limitation is still there and since your EMS worked fine in XP....and since MCE is further updated than plain ol' XP it's likely that an XP update (already included in MCE)had this effect.

Hmm, so your saying that your EMS worked fine in XP but doesn't under XP MCE on the SAME SYSTEM? Can you confirm this? This goes against the testing that I and others have done. So far it's been no EMS available on NT4/2K/XP/2003 and the only fix was to disable the devices in the motherboard bios......because you can't reassign the block of memory that NT uses for EMS. (Your supposed to be able to in Config.NT but it doesn't work).

Either disable integrated devices in your motherboard (USB/Sound/IDE/SCSI/Whatever) to free up the memory or use a program like DosBox http://dosbox.sourceforge.net.

Try without the 3.03 patch and just the updated thipx32.dll and see if that helps with stability.

If you receive the "system" is missing or corrupt message just boot into the Recovery Console or BartPE and copy "system" from c:\windows\repair to c:\windows\system32\config IIRC, a more updated version is in your "System Volume Information" Folder but you probably won't be able to get into it from the recovery console.

Never experienced this issue before. Are you using any patches for the game? Have you tried running the game under DosBox? Might want to do so and see if that fixes the issue,

I've tested 2000+ games in Windows and DX9 works fine for all old DX games from DX1-DX8....it's not necessary to go back to or alternate to an older version. (This might be necessary with DX10 but we won't know until it's released next year) Could you list these "old" games?

So does Doom 3 run at all? Does it sometime run and sometimes not run? When it doesn't run what error message do you receive? The SB Live! is a pretty old card but since the Audigy is basically thr same card there shouldn't be any problems. With that said I don't really keep up with Intel Motherboards (Last Live! I owned was like in 2001 or 2002 or something and last Intel processor was a dual P3 back in 2002). So there possibly could be an incompatibility there. How old are the sound drivers for the Live!? Every so often I get fed up with Creative's drivers and use the KX drivers which are much better (although no EAX). As for FAKK2, you have to manually decompress the patch files. Didn't you start a thread about this before?

You need to download the patch from the Westwood website....

Another person had a problem with this game that I was able to replicate. Basically you will be unable to go past a certain mission. His only fix was to play the game under Windows 9x where it works fine. Still don't have a fix for it yet. Of course this doesn't concern your issue but if you do get this issue fixed then you'll undoubtedly encounter the issue I mentioned....so it's best to run the game under 9x for now.

http://www.av-comparatives.org/ This is the one I always use.

Do people actually set their browser to homepages? Weird.

Well if Tie Fighter is a DOS games then you can use DosBox which support USB joysticks.

Wow. That's really weird. I'll have to load up Vmware with my different OS installs and test installation/uninstallation of Kaspersky. So far I haven't had any trouble with it....but I don't remember the last time I ever uninstalled it.

Kaspersky is the best for detection. Symantec second. Haven't used Symantec 10 but I doubt the interface has changed much. Kaspersky is probably superior interface wise. I'm referring to the corporate ver of Symantec of course.

Looks like it's not able to find the CD. This also happens if yout MW2: Mercs CD doesn't have CD audio tracked. To verify this try to see if Windows Media Player can see the CD tracks. If it can then that's not your problem. If it can't then you won't be able to get it work.

The original NFS is a DOS game and has nothing to do with DX. If it's asking for DX7 it was probably produce around the 1999-2000 time frame....probably NFS3-4?

jmmijo already stated the problem. It's the graphics card....(if that's what you want to call the POS devices they stick in their mobos to output video.....) I'm tired of dealing with Sims 2 problems but if the person above wants to get it working all they have to do is go to the nearest computer hardware store, show the Sims 2 system requirements to a rep, rep reads requirements, picks out video card and or installs video card in customers PC. Of course if that is really the MHZ amount of that PC/memory amount of that machine running Sims 2 on it isn't going to be a great experience..... Maxis really should have put on the boxes a big sticker stating that the Sims 2 is not Sims 1....ie it's a totally different beast and requires people to actually read and follow the system requirements. I know I know...totally unrealistic.

The %SYSTEMDRIVE% variable is standard on all NT systems and will always be the partition of the Windows that you are currently using. So on a dual-boot system if 9x was C: and NT was D: then %SYSTEMDRIVE% would be D. You can verify this by going into the command prompt and typing: "SET" I did this because I'm used to using variables, instead of hardcoding paths. It's more reliable this way. It's been a long, long time since I last used Windows 9x so I'm unsure what the variable for 9x would be, if there is none then simply go back to C:\. This shouldn't affect anything. As for determining the CDROM drive that the .bat is being run from...that shouldn't be necessary. When you run the setup.bat from the CD...then you are running the .bat from the CD. You can verify this by placing a PAUSE statement in your batch file and checking the prompt. It should be the CD drive letter that your running it from. I suppose you could create a variable for all drive letters with \website....but that shouldn't be necessary since it sounds like your batch file finds the files, just that sometimes it copies to the desktop? Can you reproduce this?