This should be very easy: If you have WINXP with Service Pack 2[or SP1?] The driver's in C:\Windows\System32\Drivers\INTELPPM.SYS Can someone EM me,or post, the INTELPPM.SYS CPU driver,that apparently came as a new driver with WINXP Service Pack 2[& also maybe in SP1] ? daydavid9@hotmail.com --------------- It's [obviously] not on my install CD. I'm trying to get 2 HD's,with a similar problem, to boot: Both stop loading at the MUP.SYS driver. INTELPPM.SYS would be the next driver that should install. I have succeeded in replacing 2 drivers: pci.sys & mup.sys & so allowing the boot process to continue further each time... I'm starting to think this approach may be too time-consuming,but it is cautious. Are WINXP drivers available in general & in particular SP2 drivers?

On it's way Roark... Daniel Morcombe... Missing Since December 7th, 2003

Research on google implies mup.sys is a file needed by novell. 2 things were brought up. #1-boot from the xp cd and go to the recovery console and type "disable mup.exe" #2-remove any usb 2 cards on the boot.

Thanks to Wombat/Don W!--Got it! -------------------------- Thanks,Per: Yes,I have also found some of the same suggestions you cite [searching for last 6 weeks]: I've no USB cards--I guess the MOBO provides the USB--but I have removed the USB Printer--& all other devices--to allow booting. I believe Mup.Sys has already loaded & so is not a problem...? [per some sources whom I tend to agree with.] I'll try disabling Mup.Sys anyway,tho! I have disabled intelppm.sys-- but it didn't help. ____________________________ My THEORY: The REASON SO MANY PC's HANG at MUP.SYS[with so many different solutions] may be twofold: 1]The next driver to be loaded after Mup.Sys varies & the problem may be related to that next driver [which driver may be corrupted or there is a hardware/software conflict with that device.] -------- 2]The "System" group of drivers is just about to be loaded right after Mup.Sys,which is the last of the "Boot" group of drivers. The "System" group seems to have a different [& more complex?]loading mechanism--which has been corrupted. Mup.Sys is the last of the "service_BOOT_start" group. So named by the enable/disable commands in Recovery Console. [Mup.Sys is the last to be loaded for me & many others-but this varies.] The 2nd group is the "service_SYSTEM_start" group which begins with intelppm.sys in my case. I also notice: the boot log for my [then working] PC lists the full path for all the drivers of the 2nd group [of about 100],but not for the 1st group [of about 25] --there is clearly some difference in the way these 2 groups are loaded by Windows!

The new intelppm.sys driver did not help me boot-- I would guess, as I said above, that in my case: The "System" group seems to have a different [& more complex?]loading mechanism--which has been corrupted.