> To rebuild the HAL. What?
The HAL is not "built" by a user. It's a specific hardware-dependent file. What's more, it has nothing to do with the rest of the drivers in a system. While the shotgun approach of nuking _EVERY_ driver in the system might solve the _SPECIFIC_ issue of this being a boot device access issue, it's: 1) Gross overkill, 2) more difficult than necessary, and 3) completely unrelated to the HAL. -sc -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Chenault Sent: Thursday, August 28, 2014 2:35 AM To: [email protected] Subject: Re: [NTSysADM] move hdd with windows 7 on it *shrug* I've done it many times says the guy who owned a shop and did this regularly as part of upgrades. Doesn't always work though, especially AMD<->Intel (not relevant here). When it doesn't work a re-install is in order. To rebuild the HAL. It's usually the chipset; if the driver is for a family the same, or close, the chipset there's hope. Removing all drivers uses generic windows drivers. That's usually enough to get basic functionality, enough to get the correct ones in place. As for Pentium vs. i5. Maybe; close enough in basic functionality. >> On Aug 27, 2014, at 20:15, "Ben Scott" <[email protected]> wrote: >> >> On Wed, Aug 27, 2014 at 10:35 PM, Daniel Chenault <[email protected]> wrote: >> It's a little more complex than that. Basically the HAL is wrong. > > I believe a multicore Pentium and a multicore i5 will use the same HAL. > >> You *might* be able to fix it by booting in safe mode and (assuming >> it boots at >> all) removing ALL device drivers, then reboot and have it prompt you. > > I don't believe removing all device drivers (a) is possible[1], nor > (b) will change the HAL. > > -- Ben > > [1] Well, I suppose you could go in and nuke the entire > HKLM\System\CCS\Services branch in the registry, but that's not going > to leave you a functioning system. > >
