hal.dll and ghosting

[Guest]

Hi,


I downloaded article 309283 for getting more information about hal.dll and
restoring ghost images in different PCs, and I still cannot get clear one
thing:

I have a standard ghost image where a standard pre-PIV hal.dll file is
installed, this means that this image can run in any Intel Pentium III
chipset and motherboard.

However, if I install this image in a PIV (with for example hyperhtreading),
it is impossible to get the hyperhreading run and change the hal.dll file!

How can I do this? The idea would be to start with a 'simple' image, and
update the hal.dll so the performance gets better in PIV motherboards.

WOuld a Windows XP Restore (using the installation CD) could help?


Thanks for your help.

 

[Walter Clayton]

Hi,


I downloaded article 309283 for getting more information about hal.dll and
restoring ghost images in different PCs, and I still cannot get clear one
thing:

I have a standard ghost image where a standard pre-PIV hal.dll file is
installed, this means that this image can run in any Intel Pentium III
chipset and motherboard.

Not quite. There's quite a bit of difference betweena VIA, SiS and Intel
chipset. Same processor though, but the hardware and BIOS is just a wee bit
different. Same applies between chipsets with a different BIOS.

However, if I install this image in a PIV (with for example
hyperhtreading), it is impossible to get the hyperhreading run and change
the hal.dll file!

This is true. hal.dll isn't the sole problem. Chipset is the biggest issue.

How can I do this? The idea would be to start with a 'simple' image, and
update the hal.dll so the performance gets better in PIV motherboards.

WOuld a Windows XP Restore (using the installation CD) could help?

You mean repair reinstall. The answer is yes. If you want to take advantage
of those instances where HT benefits performance, then do a repair
reinstall.

 

[Guest]

Thanks walter for your answer.

So, if I had the same chipset (Intel) in the 'old' and 'new' motherboards,
could it be possible to ghost an old image into a 'new' motherboard (with
PIV and Intel Chipset) and change hal.dll so it could benefit from
hyperthreading, etc?

 

[Guest]

If you have a standard image of XP, it should go on the 'Standard
Configuration' PC. That is to say, in order for it to be able to be
'ghosted' back to a HDD and that particular PC be able to startup and run,
immediately: it must have identical configuration to the 'master' PC from
which the image was created.

If the destination PC has a differnet Mobo, CPU or Hard Drive [make, model,
capacity], then it will be necessary to perform a REPAIR installation of XP
in order for the Operating SYstem to boot. Just part of the copyright
protection built into XP.

Given that oyu may have all XP, applications and other items 'customised'
for your office, then it is still quicker to Repair Install than 'build'
every system environment from scratch.

 

[Walter Clayton]

No. Intel isn't the chipset. They're simply a vendor. There's a ton of
difference between a 430VX and 915G although they're both made by Intel. The
difference is at least as large as that between a VIA MVP3 AGP and 430VX and
they, at least, were of the same era and accepted the same processors.

Repair reinstall is your only option.

 

[Guest]

Hi Bar,

I'm sorry but I disagree. Lots of things can be different, from HD to
screen, Xp detects lots of them.

The only thing I have found is really a problem since it can even make the
system to be unable to boot, is the combination chipset/processor type.

Never install a ghost image created in a via motherboard onto a Intel
Chipset, etc...

And there are known problems between ACPI processors and non acpi...

And, as I was asking here, I have problems for upgrading a hyperthreading
processor in a 'no chyperthreading' ghosted OS...

If you have a standard image of XP, it should go on the 'Standard
Configuration' PC. That is to say, in order for it to be able to be
'ghosted' back to a HDD and that particular PC be able to startup and run,
immediately: it must have identical configuration to the 'master' PC from
which the image was created.

If the destination PC has a differnet Mobo, CPU or Hard Drive [make,
model,
capacity], then it will be necessary to perform a REPAIR installation of
XP
in order for the Operating SYstem to boot. Just part of the copyright
protection built into XP.

Given that oyu may have all XP, applications and other items 'customised'
for your office, then it is still quicker to Repair Install than 'build'
every system environment from scratch.

Not quite. There's quite a bit of difference betweena VIA, SiS and Intel
chipset. Same processor though, but the hardware and BIOS is just a wee
bit
different. Same applies between chipsets with a different BIOS.


This is true. hal.dll isn't the sole problem. Chipset is the biggest
issue.


You mean repair reinstall. The answer is yes. If you want to take
advantage
of those instances where HT benefits performance, then do a repair
reinstall.