now I've renamed AGP440.SYS (but you WERE right on both counts) and rebooted.
#Remove hauppauge drivers windows 7 driver#
anyway, when I previously attempted to resolve by booting into Safe Mode, I noticed the AGP driver file and wondered. I upgraded from a P4 to an i7, so I'm (still) running Intel, but I'm no longer using AGP. And since I won't have a 64-bit disc for another day or so, I have time to play. The failure was unexpected although I am backed up (both system and specific files/folders), I would like to resolve /address a couple of issues before doing a reinstall of a new OS. but what? Search for NVidia (my previous video card) in the registry, and remove all occurrences, then rename the existing NVidia folders? Open for suggestions.
So, ShadowHunterNV, the short answer is that merely moving (never delete) the INF and PNF files is insufficient.
I can see the drives previously available (HKLM\SYSTEM\MountedDevices), in which both a drive letter and a volume ID are listed, so I removed what used to be drive A. Obviously, there's no CurrentControlSet, but there are ControlSet001 and ControlSet002 (previously successful boot attempts). Browsing through here, I see evidence that it recognizes the new CPU, mobo and BIOS (all identified conveniently HKLM\HARDWARE). Now, my boot CD provides a remote registry option that permits me to select C:\Windows. And although it may be possible to remove driver files from C:\Windows\System32\Drivers, I'm not certain that will get me anywhere. PNF files to another folder on the drive (never delete) and tried to use the repair function but was told again that it's irrepairable. Then, following the advice in here, I moved the OEM#.INF and. I first tried to perform an in-place repair using the DVD but was told that it could not be repaired (Windows cannot repair this computer automatically). Ultimately, this will receive a new 64-bit OS (particularly since Win7 RC1 will start shutting itself down every two hours starting in March 2010), but it's an interesting exercise.
Attempting to boot the system as is (post rebuild) simply blue screens with a STOP error (re: drivers). Since it was past time to upgrade, I took the plunge and replaced the hardware (case, CPU/cooler/mobo, video, memory) but the HDs seem OK (accessible via a WinPE-based boot CD and in an external drive case). Similar problem here: my box (running Win7 RC1) toasted itself. Do you still think renaming/deleting the inf and pnf files will force 7 to a stock configuration, load a GUI and ask for the chipset drivers?
The newer version mainboard has a different chipset and I suspect this is the reason 7 won't load, not even in safe mode. The version of mainboard that came with the system has been replaced by this newer version and the original version board is no longer available. It was cheaper to get a replacement mainboard than to get a PCI-e video card and I assumed that I'd be able to get safe mode to remove the original drivers. This computer is a customer machine who's little kid pulled the video cable off the back without unscrewing the connections, thereby ripping the onboard video port from the mainboard. I obviously can't load Device Manager to remove anything because I can't load the GUI.
#Remove hauppauge drivers windows 7 upgrade#
I've always been able to load safe mode in the past to upgrade the drivers in situations like this, however Windows 7 is apparently different enough that this option does not work. Problem is that the mainboard has been replaced so those drivers no longer apply. This system is an HP pre-built system and the only option is to do a "System Recovery" (reload factory configuration) which then re-installs all the original drivers.
0 kommentar(er)
