sysprep image reboots continually during mini-setup....

[Joe]

We have been using sysprep (currently version 5.1.2600.2180
(xpsp_sp2_rtm.040803-2158)) for quite a while now with a lot of
success. Up until recently, we were very careful to always choose a
motherboard VERY similar to our master image. We use ASUS motherboards
exclusively, with the SiS chipset (P4S800-X, P4S800D-X, etc).

We recently purchased 5 more ASUS motherboard systems with an Intel
Chipset instead of the SiS chipset (a P5P800S).

When we try to image to one of these new systems, it continually
reboots during mini-setup. We tried safe mode, and the last thing
before it abnormally reboots in the list is MUP.SYS.

We installed XP to one of the systems manually, and it works well.

We compared the 2 installed XPs (manual install on the P5P and sysprepd
on the P4S), and the HALs appear to be exactly the same (halaacpi.dll).

The other difference between the 2 motherboards would of course be the
mass storage drivers. To alleviate this, we tried a sysprep -bmsd on
the source P4S. Same problem.

Only other piece of information I can provide is that on the manually
installed XP, the last driver in the list during a safe mode boot is
AGP440.SYS.

Any help would be greatly appreciated,

Thanks,

Joe

 

[Guest]

I am having sim problem with mup.sys after imaging a new system. I do not
even get to the mini setup because it stops at loading mup.sys. Found this
out by doing safe mode boots.

We have tried everything from new cables for the hard drives bios updates
all with no joy.

I would really like to find out the trick for this. Having 20 images is not
that prctical.

Jon M Honhart

 

[Hunter1]

It ain't MUP.SYS then, it'll be the next file along that's stopping it.
What did you set as a HAL prior to making your initial image? This is
fairly critical, and makes the difference between needing a shitload of
images and having one that will fit nearly all (still the occasional
exception, we have a "one fits all" image, and 2 pieces of hardware (one
of them a laptop) that need their own images. But that's not bad going
with about 12 different platforms floating around).

 

[Guest]

Thanks this answered. It is all about the HAL. Did not understand fully the
dif HAL's.

Jon M Honhart

 

[Hunter1]

No probs, was a serious stumbling block for us in our initial sysprep
stages too, doesn't seem to actually be well documented anywhere that we
found, stumbled on the answer in an old usenet post ourselves.