|
Answer» Installing windows 7 RC (7100) 32-Bit on a blank HDD Toshiba Satellite M40 (Intel Centrino, NVIDIA Graphics) laptop is not going well.
First part of the install runs fine, then it RESTARTS, then it says "completing installation", which is fine, then it restarts again, then it hangs at "Starting Windows". Booting in safe mode it stops at "CLASSPNP.SYS"
Any ideas? I did some googling and it says Classpnp is something to do with video drivers? I don't really understand what i've found.
Thanks for any suggestions.It is possible that during the automatic harwdare detection, it mis-detected the GPU ( Video CPU ) of your system and the driver it is trying to run is not compatible.
For DESKTOP systems this can be fixed by placing a video card in place of the integrated GPU, but on a laptop there is no alternative usually. Only other suggestion i can think of is that at the initial install where it gives you the short prompt to press I think its F6 to install drivers, you might be able to use that for installing video support, however I have only used that for installing RAID drivers for adaptec cards and never used that as a way to change any other drivers.Hooray! I found a fix for this on Sevenforums.
Use setup disk/repair computer/go through all the rubbish as it says that it doesn't know what to do/advanced options/command prompt/navigate to windows|system32|Drivers/ type "Ren pcmcia.sys pcmcia.bak"
Bones92
You, Sir are my personal hero. When installing Windows 7 Pro on an old Toshiba Satellite M40-129 (PSM40E), it alsways hung at classpnp.sys.
When finally renaming the PCMCIA.sys so it COULD not be loaded any more, the laptop finally started Windows 7 Pro for the first time ever. Thank you very much. I hope this will be found by the search ENGINES so people can use our advise and solve their problems the same way.
Quote from: Bones92 on June 23, 2009, 11:00:56 PM type "Ren pcmcia.sys pcmcia.bak"
WOW! Finally, the ONLY permanent solution to this annoying classpnp.sys problem that has plagued Microsoft Windows since Windows Vista! Thank you so very much.Remember that renaming classpnp will prevent access to SCSI-based devices on that machine in the future, and the issues preventing it from working properly are more than likely not something that will just "go away" by renaming a file.Hi from Greece,
I found the solution MOST helpfull, after spending an entire workday searching for what could be wrong. It worked like a charm, BUT the problem returned as soon as I installed updates! I had to rerun the cure and then use AutoRuns from Sysinternals Suite to disable the specific driver. So far, after two more update sets, all work well! Thank you all for your help!
|