Aaron

'nuff said.

Sedative has a voodoo doll!

This might have something to do with it: FactoryMode = YES I've never heard of this command. As for when you tested your batch scripts and the window disappeared quickly - this could be because the paths specified in the batch files don't exist.

Ok I'll give that a go. There's no side effects from running FixMBR is there? Because this might be the first time I've actually gonna use it.

Now that you mention it, I created a small FAT32 partition yesterday on the same hard drive so I could backup my ghost images to it. And that partition was created with PM8, I guess I'll have to reinstall that and see what's wrong Edit: Looks like I can't check it for errors and it suggests to use the Operating System's check utility. But chkdsk never fixes it.

And me!

How he managed to eat all that while drinking coke is astonishing! I never drink coke with my meals as it tends to fill you up too quickly.

I noticed your /s switch isn't uppercase, some switches are case-sensitive.

Go to Start > Run and type CMD then when the command prompt window appears, type only: chkdsk c: (change drive letter to where your OS resides if different from c:\) Do you get the following messages? Correcting errors in the Volume Bitmap. Windows found problems with the file system. Run CHKDSK with the /F (fix) option to correct these. I got this on my maxtor 60gb, thinking it was a bad hard drive, despite running a full chkdsk scan with /F and formatting & reinstalling XP, but I still got that message. I swapped over to a working 120gb Western Digital and I'm still getting the same message. If you get the same message when you try chkdsk, then its obviously normal behaviour. (I just want to put my mind at peace )

What has Tomb Raider 2 got to do with an Unattended XP CD? Please use the Private Messaging feature in future please.

I'm not sure if its possible, but disable emulation of networks in Virtual PC as this looks like where Setup is hanging.

Add UnattendSwitch="yes" to [unattended] to bypass the Welcome to Windows XP section of Setup.

My CAS Latency is at 2.5 at the moment, I might change this to 2 as I've read that some 400mhz ram modules can support this.

Thanks, posted

my Abit mobo has a softmenu in the bios, I think it does CPU/PCI/AGP and I just raise it or lower it. It can go up to 6Ghz (no way I'm ever gonna try that!)

Thanks for the help everyone! I've ordered a Vantec Aeroflow HSF, Artic Silver 3 compound and a heatsink lapping kit. For now, I've underclocked my 3.0GHz to 2.0Ghz and the temp is steady at 39C until the parts arrive.

I'm on Freeserve 56k and I don't tweak the MRU settings or anything of the like. Top speed I get on it is 6kb/sec Using Mozilla Firebird will speed up web browsing noticably (has a far better cache system than IE) but I hate the browser!

Dunno, it hasn't got a name on it. But then I don't need it on do I as the heatsink fits on perfectly without moving about. Edit: How does thermal compound make all the difference? Its only some sort of glue isn't it? Anyway, I've ordered some artic silver, need to find out a good quiet HSF though.

I think airflow is ok, as case temp is steady at 38ºC

Pskill can be copied to c:\windows\system32 to allow the pskill file to execute no matter what directory you're currently in

You will have to expand it again to edit the dll

I think what he's trying to say, is that the screen asking you if you want to repair, or create a new installation of windows doesn't appear when using an unattended CD.

I can see you don't quite fully understand the concept of these $OEM$ folders. To put it simply, the naming of these folders instruct Setup where they should be copied to. Everything in $OEM$\$1 will be copied to C:\ (or the systemdrive the OS is installed on). Everything in $OEM$\$$ is copied to C:\Windows So, $OEM$\$1\install will become C:\install This will only work when OemPreinstall=Yes is specified in winnt.sif

I've got a P4 3.0GHz CPU, and have monitored its temperatures over the last few days. It averages at around 65ºC (148ºF), and can go up to 73ºC. Is this too high for a P4 to run at? By the way, some of that thermal stuff came with the P4, was I supposed to put this on? I wasn't sure cos the HSF mounted and locked in perfectly.

It should be able to be done the same way as any other driver is installed during windows setup. Extract the nforce drivers check which folders contain the INFs and use a correct path to them in winnt.sif (Bear in mind I haven't used nforce drivers, but I'm sure its similar to the way VIA chipset or nvidia gfx drivers are installed)