G
Guest
Hello! We are coming across an annoying glitch with some new laptops and SATA
drives . . .
When setting up our master workstation (in prep to creating images for
deployment), we've discovered that XP will NOT install unless the SATA
Controller mode is set for Compatible in the BIOS. Is XP SATA-compatible or
not? (In other words, will XP be able to work with SATA controllers in AHCI
mode?)
After completing the master setup, sysprepping, and imaging it, we've
discovered that the target unit will not boot correctly unless it, too, is
set in Compatibility mode. Otherwise, in AHCI mode, the Windows splash screen
bar goes about 3/4 across, stops, then a 0x0000007B BSOD appears. If the unit
is restarted and set back into compatibility mode, it boots normally.
According to booting in Safe mode, the file it chokes at is mup.sys.
These variables have been tried:
-master=Compatibility (for burn), target=AHCI (BSOD result)
-master=AHCI (for burn), target=AHCI (BSOD result)
-master=Compatibility (for burn), target=Compatibility (boot)
-master=AHCI (for burn), target=Compatibility (boot)
On the BSOD result occurrences, switching to Compatibility allowed the unit
to boot.
The master is not being booted to its own drive, as that has been sysprepped
for capturing. But i suspect that if i did, it, too, would BSOD in AHCI mode.
This has been seen in a ThinkPad R60 and Z61m.
It's really looking like XP doesn't like the SATA drives, at least in
laptops. (Haven't had a SATA desktop to try with.)
If anyone knows that this is a fact, please let me know; i'll add a step to
the deployment to switch the BIOS SATA mode to Compatibility before doing
anything else on new units.
If this isn't a fact, let me know and give me ideas on what's going on,
please!
Thank you!
drives . . .
When setting up our master workstation (in prep to creating images for
deployment), we've discovered that XP will NOT install unless the SATA
Controller mode is set for Compatible in the BIOS. Is XP SATA-compatible or
not? (In other words, will XP be able to work with SATA controllers in AHCI
mode?)
After completing the master setup, sysprepping, and imaging it, we've
discovered that the target unit will not boot correctly unless it, too, is
set in Compatibility mode. Otherwise, in AHCI mode, the Windows splash screen
bar goes about 3/4 across, stops, then a 0x0000007B BSOD appears. If the unit
is restarted and set back into compatibility mode, it boots normally.
According to booting in Safe mode, the file it chokes at is mup.sys.
These variables have been tried:
-master=Compatibility (for burn), target=AHCI (BSOD result)
-master=AHCI (for burn), target=AHCI (BSOD result)
-master=Compatibility (for burn), target=Compatibility (boot)
-master=AHCI (for burn), target=Compatibility (boot)
On the BSOD result occurrences, switching to Compatibility allowed the unit
to boot.
The master is not being booted to its own drive, as that has been sysprepped
for capturing. But i suspect that if i did, it, too, would BSOD in AHCI mode.
This has been seen in a ThinkPad R60 and Z61m.
It's really looking like XP doesn't like the SATA drives, at least in
laptops. (Haven't had a SATA desktop to try with.)
If anyone knows that this is a fact, please let me know; i'll add a step to
the deployment to switch the BIOS SATA mode to Compatibility before doing
anything else on new units.
If this isn't a fact, let me know and give me ideas on what's going on,
please!
Thank you!