G
Guest
We just received a Dell 755 optiplex and it has a new SATA Controller ( I
assume)...bios shows AHCI Our existing sysprepped uniprocessor image would
not boot (it loops). We have the buildmasstorage line in sysprep set to yes,
and this image has worked for lots of dell laptop and desktops models just
fine. I tried adding the drivers to the sysprep folder but it doesn't make
it that far to read it. As a result, I decided to create a new image on the
755 (multiprocessor) and use it as the base image. It seems to run the
minisetup on a multiprocessor (Core2) machine pretty quickly and reboots. On
an uniprocessor machine (i.e dell latitude d610 or d410) it finishes the line
that says removing temporary files and then goes to a black screen with the
white arrow in the middle of the screen. If you let it sit for about 30
minutes, it will reboot itself. It successfully goes into windows at that
point. If I reboot when I see the white arrow (don't wait), it also boots
successfully into windows. I compared our existing image file setupapi.log
loaded on a d610 and the new image loaded on the same machine and don't see
any type of failure. Does anybody know what is going on here and a fix?
I've read where some say change the hal to acpi but indicated that
effectively cripples the multiprocessor, and I'm concerned about how power
managemant would function (or not function). I have loaded the video driver
fixes (for unsigned drivers), so that is not it.
Thanks
assume)...bios shows AHCI Our existing sysprepped uniprocessor image would
not boot (it loops). We have the buildmasstorage line in sysprep set to yes,
and this image has worked for lots of dell laptop and desktops models just
fine. I tried adding the drivers to the sysprep folder but it doesn't make
it that far to read it. As a result, I decided to create a new image on the
755 (multiprocessor) and use it as the base image. It seems to run the
minisetup on a multiprocessor (Core2) machine pretty quickly and reboots. On
an uniprocessor machine (i.e dell latitude d610 or d410) it finishes the line
that says removing temporary files and then goes to a black screen with the
white arrow in the middle of the screen. If you let it sit for about 30
minutes, it will reboot itself. It successfully goes into windows at that
point. If I reboot when I see the white arrow (don't wait), it also boots
successfully into windows. I compared our existing image file setupapi.log
loaded on a d610 and the new image loaded on the same machine and don't see
any type of failure. Does anybody know what is going on here and a fix?
I've read where some say change the hal to acpi but indicated that
effectively cripples the multiprocessor, and I'm concerned about how power
managemant would function (or not function). I have loaded the video driver
fixes (for unsigned drivers), so that is not it.
Thanks