Hi,
I'm using the BDD Computer Imaging System to build my base image. When
I insert the OSD capture Cd, I run through the wizard (naming the wim,
where to place the wim etc...) and then Sysprep starts. Well I let it
run yesterday for about 3 hours, and nothing. I looked at the
SMSCapture.log and here is some relevant exerpts:
-------------------------------------------------------------------------------------------------------------------
Retrieve SysprepParams Completed OSDICW 11/29/2005 4:25:27 PM 2400
(0x0960)
ChangeAdminPassword Completed OSDICW 11/29/2005 4:25:27 PM 2400
(0x0960)
RunSysprep executing C:\sysprep\sysprep.exe -reseal -mini -quiet
OSDICW 11/29/2005 4:25:27 PM 2400 (0x0960)
RunSysprep finished executing exitcode =259 OSDICW 11/29/2005 4:25:27
PM 2400 (0x0960)
RunSysprep Completed OSDICW 11/29/2005 4:25:27 PM 2400 (0x0960)
-------------------------------------------------------------------------------------------------------------------

>From what I can tell, sysprep runs for less than a second and returns
the infamous "no more data" exit code (259). I know I have seen posts
very similar to this, however I could not find a resolution that will
work for my situation. I've checked the sysprep tools version, and the
Broadcom NIC drivers (I know... how would drivers be the problem
here... Well we all know broadcom nic's haven't been the easiest to
work with, it was a long shot).

If anyone could help, your time is greatly appreciated.

Regards,
Jason

An Update...
I have an extensive OEMPNPDriverspath set in my sysprep.inf (1,017
charcters long) which is well under the limit (4,096), however when I
removed about half of the path, sysprep took off, and everything
worked. To my knowledge even if the path was too long, it won't halt
the build... I'm going to test, and re-test to see if it's a fluke.

Try to run it without building the mass storage devices (comment out
the line in sysprep.inf). If that works, you only need to find out
which of the 700+ drivers that is causing sysprep to choke...

regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment


On 30 Nov 2005 06:34:43 -0800, "Jryde21 (JWR)"
<jason.rutherford@gmail.com> wrote:

>Hi,
>I'm using the BDD Computer Imaging System to build my base image. When
>I insert the OSD capture Cd, I run through the wizard (naming the wim,
>where to place the wim etc...) and then Sysprep starts. Well I let it
>run yesterday for about 3 hours, and nothing. I looked at the
>SMSCapture.log and here is some relevant exerpts:
>-------------------------------------------------------------------------------------------------------------------
>Retrieve SysprepParams Completed OSDICW 11/29/2005 4:25:27 PM 2400
>(0x0960)
>ChangeAdminPassword Completed OSDICW 11/29/2005 4:25:27 PM 2400
>(0x0960)
>RunSysprep executing C:\sysprep\sysprep.exe -reseal -mini -quiet
> OSDICW 11/29/2005 4:25:27 PM 2400 (0x0960)
>RunSysprep finished executing exitcode =259 OSDICW 11/29/2005 4:25:27
>PM 2400 (0x0960)
>RunSysprep Completed OSDICW 11/29/2005 4:25:27 PM 2400 (0x0960)
>-------------------------------------------------------------------------------------------------------------------
>
>>From what I can tell, sysprep runs for less than a second and returns
>the infamous "no more data" exit code (259). I know I have seen posts
>very similar to this, however I could not find a resolution that will
>work for my situation. I've checked the sysprep tools version, and the
>Broadcom NIC drivers (I know... how would drivers be the problem
>here... Well we all know broadcom nic's haven't been the easiest to
>work with, it was a long shot).
>
>If anyone could help, your time is greatly appreciated.
>
>Regards,
>Jason

For whatever reason it's running a bit faster. It's only taking about
35 minutes now. Not sure why. Nothing changed.

I'll look into the massstorage section fix.

Thanks for the post.

Regards,
Jason