Driver difference between unattended/sysprep image...

[_jd_]

Odd situation with the Toshiba Tecra M2. My unattended installs without issue - only three non-critical devices require manual installation on completion (video, audio and one unknown device). Nothing I can't handle. However, if I drop my sysprep image on the M2 it won't even boot - normal or safe mode. The odd thing is that my sysprep image is built from the same unattended, and both are populated with the same driver set.

I've seen this behaviour with one our standard notebooks and the problem was linked to the SATA controller. I resolved this by adding the appropriate drivers for the controller. In this case the M2 appears to use an Intel 828 chipset, and those drivers are accounted for.

Thoughts?

[IcemanND]

It could be a HAL issue or a HDD controller issue.

[_jd_]

It's a standard ACPI HAL. I intentionally built my sysprep images to support both UP and MP ACPI HAL's (default is MP and the "upgrade" HAL is UP). From Microsoft's knowledge base the APCI UP HAL support's standard ACPI systems as well. This is confirmed because the image lands fine on systems that use the "standard" HAL. I also think it's the IDE controller, but I can't say why it's a problem. The drivers are in place and the path is referenced properly... i've even rebuilt the mass storage drivers in sysprep.inf without any luck. And since it won't boot, I have no setup*.log files to work from.

Doh... this one's getting an unattended I suppose.