Re: Rolling back Computer device in device manager (hal.dll) after installing SP2 gives BSOD after restarting?

Large scale roll outs in managed environments do *not* happen via image cloning. ;-)

Again, arbitrarily swapping the HAL without forcing a full blown device reenumeration is a recipe for disaster. Always has been and always will be. You don't drop an image created for a VIA chipset on a SIS chipset and expect things to run. Just as you can not drop an Intel 915G on a 440BX and expect the thing to run. You don't drop an image created on a chipset with APIC (yes, that APIC, not ACPI), on a chipset that doesn't support APIC and expect things to run.

You can not change the abstraction layer and expect to have no issues unless the hardware is redetected, or the chipset is identical, including rev level. It's not going to happen. There is some margin for play, but any one that expects to be able to arbitrarily change the HAL without doing a repair reinstall in association is simply begging for trouble.

Setting aside the larger issue of the appropriate and correct way to change the HAL, considering carefully exactly what you're specifically requesting.

You want pre-SP2 kernel code to run with SP2 code. Why do you think that should be possible?

--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.


<cuentanewslabogel@xxxxxxxxxxxxxx> wrote in message news:OWRJxbFVFHA.2616@xxxxxxxxxxxxxxxxxxxxxxx
Well, Microsoft can continue to claim that this is a problem related to cloning, but everyday this will be an issue that will need to be solved. In fact, Microsoft published article 309283, I imagine that forced because of the fact that in WinXP it is even easier to change Halls...

Anyway, doing something using the Windows XP GUI (Device manager) that works without installing a service pack, and DOESNT WORK after installing a service pack... doesn't seem to me a wrong way of doing things...

In a corporate environment, where cloning workstations is needed everyday, IT Admins must solve this kind of problems. Microsoft should be aware of this, and not forwarding incidences related to this kind of problems to the cloning software manufacturers.




"Walter Clayton" <w-claytonNO@xxxxxxxxxxxx> escribió en el mensaje news:uRcBEcxUFHA.2700@xxxxxxxxxxxxxxxxxxxxxxx
Not a bug. It's an issue of doing things wrong to begin with and only getting away with it by sheer luck.

Changing hals should be accompanied with a repair reinstall. Always has been that way and always will. Actually you should change the hal via the reinstall.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.


<cuentanewslabogel@xxxxxxxxxxxxxx> wrote in message news:eMSLYmKUFHA.544@xxxxxxxxxxxxxxxxxxxxxxx 
Hi Jason,


As I told you in my last post, this is NOT an issue with PowerQuest Drive Image. I can reproduce exactly the issue with a single PC, not involving at all any Powerquest or Symantec product:

In fact I reproduced this problem with
a single PIV PC, just installing in it Windows XP (no SP), 'updating' the
hal driver to the PIII hal, installing WinXP SP2, and rolling back to the
original PIV Hal driver => BSOD

As you can see there is no imaging software involved...

***************************************************************************************************************************************
This is WinXP SP2 issue. This is because of a bug in WIndows XP SP2, that doesn't allow to rollback some drivers (hal drivers for example) in device manager after installing SP2.
***************************************************************************************************************************************

Thank you anyway.




"Jason Tan (MSFT)" <v-jasont@xxxxxxxxxxxxxxxxxxxx> escribió en el mensaje news:7XWwu$IUFHA.2476@xxxxxxxxxxxxxxxxxxxxxxxx 
Hi,

Thanks for reply!

Actually, this appears to be an issue with PowerQuest Drive Image, a third
party application. Please note that we are happy to help provide
information on this issue for you, we recommend that you work with the
third party vendor for assistance with this.

I am including some general troubleshooting information, as well as a link
to the third party application's support portal for your convenience.

support home : Norton Ghost
http://www.symantec.com/techsupp/ghost/

In addition, I suggest you attempt to start your computer by using the Last
Known Good Configuration

307852 How to start your computer by using the Last Known Good Configuration
http://support.microsoft.com/?id=307852

This response contains a reference to a third party World Wide Web site.
Microsoft is providing this information as a convenience to you. Microsoft
does not control these sites and has not tested any software or information
found on these sites; therefore, Microsoft cannot make any representations
regarding the quality, safety, or suitability of any software or
information found there. There are inherent dangers in the use of any
software found on the Internet, and Microsoft cautions you to make sure
that you completely understand the risk before retrieving any software from
the Internet.

Thanks & Regards,

Jason Tan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
| From: <cuentanewslabogel@xxxxxxxxxxxxxx>
| References: <epTR0zITFHA.612@xxxxxxxxxxxxxxxxxxxx>
<fIOKBOLTFHA.388@xxxxxxxxxxxxxxxxxxxxx>
| Subject: Re: Rolling back Computer device in device manager (hal.dll)
after installing SP2 gives BSOD after restarting?
| Date: Mon, 2 May 2005 09:10:45 +0200
| Lines: 59
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <#EGfIWuTFHA.2872@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windowsxp.setup_deployment
| NNTP-Posting-Host: kali.gelos.es 212.9.66.214
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windowsxp.setup_deployment:30799
| X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
|
| Hi Jason,
|
|
| thanks for your answer.
|
| I made my comments inlines...
|
|
| "Jason Tan (MSFT)" <v-jasont@xxxxxxxxxxxxxxxxxxxx> escribió en el mensaje
| news:fIOKBOLTFHA.388@xxxxxxxxxxxxxxxxxxxxxxxx
| > Hi,
| >
| > Thanks for posting!
| >
| > I understand that you want to rollback to "Advanced Configuration and
| > Power
| > Interface (ACPI) PC" in Device Manager. However, when rollback it
| > experienced the blue screen, the system cannot startup normally.
|
| No, 'updated' my 'hal driver' from "ACPI Multiprocessor PC" (PIV) to
| "Advanced Configuration and Power Interface (ACPI) PC" (PIII) . Then,
after
| for example a hardware upgrade to a new motherboard, I want to rollback
to
| "ACPI Multiprocessor PC".
|
|
| >
| > Based on the description, please help me know the following information:
| >
| > 1. How did you perform the image installation? Are you using Ghost?
|
| I'm using PowerQuest Drive Image, but in fact I reproduced this problem
with
| a single PIV PC, just installing in it Windows XP (no SP), 'updating' the
| hal driver to the PIII hal, installing WinXP SP2, and rolling back to the
| original PIV Hal driver => BSOD
|
|
| >
| > 2. How about the status of the OS now? Can it boot correctly? If it
cannot
| > boot up normally, Can it boot into Safe Mode?
|
| No, the OS cannot boot in any mode, it allways blue screens giving an
error
| related to ntfs.sys.
|
| >
| > 3. If it can boot up normally, I suggest you do not rollback the driver
in
| > Device Manager. You may choose to update the driver and check to see if
| > the
| > issues disappear.
|
| It cannot boot at all so...
|
|
| Since you told me about imaging, I just wanted to tell you about how
| problematic is this for us: we have lots of WinXP Workstations with PIII
| motherboards, where we installed SP2. Now, if we upgrade this
motherboards
| to PIV, we cannot use the PIV hall driver (we cannot roll back the hal
| driver to the original PIV hal)....
|
|
|







.

Relevant Pages

  • Re: Rolling back Computer device in device manager (hal.dll) after installing SP2 gives BSOD after r
    ... Changing hals should be accompanied with a repair reinstall. ... a single PIV PC, just installing in it Windows XP, 'updating' the ... This is WinXP SP2 issue. ... | hal driver to the PIII hal, installing WinXP SP2, and rolling back to the ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: HI-SPEED USB Device Plugged into non-HI-SPEED USB Hub
    ... I don't have or have had any yellow question marks anywhere after installing ... I have updated the driver ... Device Manager and then let WinXP rebuild the whole thing. ... the same every time - same error message and low USB throughput. ...
    (microsoft.public.windowsxp.general)
  • Error 0xc0000034 - Unable to Load Device Driver
    ... Win2000 installation went fine, video and LAN driver ... shows the name of the sound driver). ... I tried installing in safe mode, ... The troubkleshooter brings up the following "Device Manager Error ...
    (microsoft.public.win2000.setup)
  • Drives missing from My Computer
    ... I downloaded the W2k driver from the HP site, installed it, ... mistake of installing the Direct Letter Access software ... for the DVD drive it gives: "Your registry ... Device Manager Troubleshooter says I should check. ...
    (microsoft.public.win2000.general)
  • Re: No Sound or Sound Device
    ... check your device manager and see if the driver is installed and the device ... Perhaps a new driver was installed that is non functional ... > After installing the latest Windows update, I lost all sound on my HP PC ...
    (microsoft.public.windowsxp.general)