Half-Life+Windows XP Problem

[FadingTheory]

I recently acquired the game Half-Life, and all its expansion. However, I failed to read the box. Apperently, it will work with all Windows, excluding XP.

My question is: Can I trick it to play on XP? Everytime I try to install it, it gives me an error.

'C:/Windows\System32\Autoexec.NT. The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application'. I asume this means theres a problem with XP being an exclusivelly 32 bit program, while half-life runs 16 bit routines.

Its not a problem, I can put 98 on my computer as well in a dual boot, I just dont want to. Is there any other way?

 

[Nubius]

wow lol, stupid me thought for a split second you were talking about HL2.....forgot people still like the original hehe....

That's pretty weird though. I didn't know that would happen honestly.

 

[Simon]

It works with XP fine for me and all my friends, yes original HL

 

[FadingTheory]

I bought the collection pack deally, the one that comes with all the expansions.

Curses! Guess 98 will eat some Linux partition...

 

[NeoExtreme]

XP SP2 moved the autoexe.nt file that is why you are getting that error or if you are running SP1 it is possible that it is missing or damaged.Try this link and let me know how it works for you.

http://support.microsoft.com/default.aspx?scid=kb;en-us;324767

 

[FadingTheory]

Okay, I'll post that and see how it works.

 

[DJ-CHRIS]

Just to let you know it does work with XP

 

[FadingTheory]

Mine dosn't

Okay, I tried the first step, but that didnt work. All it did was try to execute the first file in the command line- which failed miserably. I assumed they meant copy, so I performed that through the command prompt (just throw copy in front of the comand line). That worked, and I found that my computer was actually missing the autoexec.bat in that folder.

Now, its giving the same error, just instead of the Autoexec.bat, its giving me one about the config file. I'm going to mess with it more tonight, and try some of there other suggestions, if Microsoft didn't botch those up as well.