Win Xp HAL MisMatch

Status
Not open for further replies.
harmandeep

harmandeep

VirTuaLiZaTioN Freak
Contributor
Hi ,

i had cloned a Win Xp prof sp2 image which was installed on a
Celeron 500 MMX machine ( NON ACPI Compliant - Standard PC )
to a VMware Guest Machine which is a ACPI Uniprocessor Compliant.
Using VMware Workstation 6 Eval.
Guest machine is configured 2 use a single System Processor
as HAL is mismatched recieved a BSOD

http://img241.imageshack.us/img241/8294/fbgtz9.jpg

i had messed up with replacing HAL,s nd ntoskrnl,s using SET command in Recovery Console .
Reading various MS Kb,s nd Vkb,s ... but all in VAIN.

one simple solution 2 repair it is to
Boot from XpCdrom
Enter
F8 nd
Press R ( for automatic Repairing ) whichs takes time.
It does its Jobs quite well but i thinking 2 do this manually

anyway 2 workout this Manually
:ohyeah: :tongue:
 
Probably better to do the auto route. The reason I suggest that is because there are several things you have to replace - the HAL, and several registry entries.

If you want to figure out what registry entries change, get one of those tools that lets you do a diff on registries, then compare the new registry (after importing into VMWare and fixing) with the old one (before fixing). You'd have to dump the registry hives for that I'd guess.
 
What terminal?

Anyway, I've done the steps above once and I managed.

But that was not the point I was making. What I was saying is:

1. Before you clone the machine, export HKEY_LOCAL_MACHINE to a .reg file (let us call it first.reg).

2. Clone the machine. Fix it up using the repair tools on the Windows CD. Then immediately on starting the VM, export HKEY_LOCAL_MACHINE (in the VM) to another .reg file (let us call it second.reg).

3. Copy the second.reg file out of the VM (or copy first.reg into the VM). Basically, get first.reg and second.reg side by side somewhere....

4. Run Windiff on the two .reg files. It will tell you all the differences between them.

There may be a lot of extraneous changes, but this method will tell you whatever has changed...
 
@ terminal i mean we cud share the Desktop screen ( console ) via terminal services in windows or a third party soft solution .

nd secondly A default installation of windows already creates a Backup of every hive After First installation Successful booting as Mentioned by MS in above link.

nd most importantly

i m not able 2 Fix up the machine using recovery console so that it can Be Booted ...
 
Why do these BSOD's originate ?

Images of computers running Microsoft Windows cannot simply be restored to different hardware as Windows will typically fail at boot time with a STOP: 0x0000007B error screen

Blue_Screen_of_Death Blue_Screen_of_Deathif the proper Microsoft Hardware Abstraction Layer

Hardware_Abstraction_Layer Hardware_Abstraction_Layer (HAL) and/or storage drivers are not installed in the

operating system OS OS at boot time

source : http://en.wikipedia.org/wiki/Acronis_True_Image

Solution 1 : Acronis Universal Restore is designed to overcome this problem. Universal Restoreis an add-on utility for True Image Echo versions running under Windows, and is designed to replace the HAL and inject updated storage drivers embedded within the image during the recovery process, allowing an image of a machine to be restored to different hardware.

Solution 2 : Using scripts via Norton Ghost to inject the proper generic storage controller drivers and app HAL as need.

http://www.symantec.com/connect/arti...winpe-16-or-2x

Solution 3 : Use any Bart PE Plugin , if available

Solution 4 : ubcd4win ... downloading FTW

Solution 5 : StorageCraft Server / Desktop ... downloading FTW

Also there is VMFixScsi plugin available for BART PE ... for V2P deployments to inject proper Storage contoller drivers ... which wud leave us only with replacing HAL ...

so ... it goes ... that we are targetting ... Hardware Independent Windows OS cloning ... :ohyeah:

Sysprep does the job ... but i wanna leave it as exception ...:tongue:

Testing Method ...

As mentioned

Wud be cloning source image with hardware as

Celeron 500 MMX , Standard-PC windows HAL , 810e intel chipset ,

to VMware Guest machine ... with intel IDE controller , with One and Two Logical Processors Respectively

normally . we wud recieve the same BSOD as shown in Screenshot and mentioned here ... the Counterpart is to change this ...

wud test out and report back ...:cool2:
 
Solution 1 : It worked nicely ... played only with Windows Xp , Server 2003 and FLP ...

windows v6 OSes left ...

This option also marks the easiet , best ,and only possible ( atleast for me ) method to inject windows device drivers and low level critical drivers ( such as ur I/O Controller driver... just browse to any appropriate driver and select it to clone directly using Universal Restore Addin )

Rest of the solutions wud require manually editing , alot , for proper injection , and Rest of them deals with Generic drivers --- (Leaving Solution 2) ...

Rest still to try ...
 
Solution 3 : Worked using FIXVMSCSI BartPE Plugin Designed for V2P and P2V conversions ... we had selected ... " Install Native IDE Drivers " option ... this option justb installed the right generic drivers ... in this case ... HAL was'nt edited ... on the storage controller part was edited ( using FIXVMSCSI )

played only with Windows Xp , Server 2003 and FLP ...

windows v6 OSes left ...
 
Solution 4 : Worked , after slipstreaming ... making ISO bootable and selecting " Fix HDC " under Registry tools ...

played only with Windows Xp , Server 2003 and FLP ...

windows v6 OSes left ...
 
Status
Not open for further replies.
Top Bottom