Re: BDD, ZTI, OSD, SMS Sysprep...

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thanks for reply. I'm going to give it a try. Since it's early in the
project development, I'll rebuild the WIM. I appreciate your help.

regards,
Jason


rmolenaar@xxxxxxxxxxx wrote:
> try this http://support.microsoft.com/default.aspx?scid=kb;en-us;883667
>
> if you do not want to recreate your image with the hotfix, you can copy the
> newdev.dll file in the postinstall phase, using a userexit routine
>
> rob
> "Jryde21 (JWR)" <jason.rutherford@xxxxxxxxx> wrote in message
> news:1134408092.657418.254080@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Hi,
> >
> >
> > I'm using the BDD/OSD/ZTI process, everything with the complicated
> > pieces is working fine. The problem I'm having is with Sysprep.
> >
> >
> > When I throw the image down to the machine the install happens fine,
> > the phases are ran through without problem. When it reboots after the
> > postinstall phase, and starts syprep, the Sysprep just hangs on the
> > Windows XP Setup please wait... Screen. The logo is quite large at
> > that point as well. So I thought it's the video driver, well according
> >
> > to the setupapi.log the video driver installs just fine. The point
> > where it chokes is the Plug and Play monitor driver.
> >
> >
> > I let the machine sit and think about things for a while, and then if
> > it doesn't finsih sysprep in a resaonable amount of time, I reboot it.
> > After a reboot the logo is now small, and sysprep continues without a
> > hitch. So to troubleshoot I look in the setupapi.log for the time
> > difference, here is some of the log around the time of the reboot...
> >
> >
> > [2005/12/09 14:12:54 428.476]
> > #-198 Command line processed: C:\WINDOWS\system32\services.exe -setup
> > #I060 Set selected driver.
> > #-019 Searching for hardware ID(s): monitor\sec4a58
> > #-018 Searching for compatible ID(s): *pnp09ff
> > #I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1".
> > #I022 Found "*PNP09FF" in C:\WINDOWS\inf\monitor.inf; Device: "Plug and
> >
> > Play Monitor"; Driver: "Plug and Play Monitor"; Provider: "Microsoft";
> > Mfg: "(Standard monitor types)"; Section name: "VESADDC.Install".
> > #I023 Actual install section: [VESADDC.Install]. Rank: 0x00002000.
> > Effective driver date: 06/06/2001.
> > #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> > #I063 Selected driver installs from section [VESADDC.Install] in
> > "c:\windows\inf\monitor.inf".
> > #I320 Class GUID of device remains:
> > {4D36E96E-E325-11CE-BFC1-08002BE10318}.
> > #I060 Set selected driver.
> > #I058 Selected best compatible driver.
> >
> >
> > THEN IT HANGS...
> > AFTER THE REBOOT THIS LINE APPEARS IN THE LOG...
> > #W082 Could not locate a non-empty service section [Clean.Services] in
> > "C:\WINDOWS\system32\$winnt$.inf". Error 0xe0000102: The required line
> > was not found in the INF.
> >
> >
> > Then it starts where it left off again, only installing sucessfully.
> > [2005/12/09 14:24:36 556.3 Driver Install]
> > #-019 Searching for hardware ID(s): monitor\sec4a58
> > #-018 Searching for compatible ID(s): *pnp09ff
> > #-198 Command line processed: C:\WINDOWS\system32\services.exe -setup
> > #I022 Found "*PNP09FF" in C:\WINDOWS\inf\monitor.inf; Device: "Plug and
> >
> > Play Monitor"; Driver: "Plug and Play Monitor"; Provider: "Microsoft";
> > Mfg: "(Standard monitor types)"; Section name: "VESADDC.Install".
> > #I023 Actual install section: [VESADDC.Install]. Rank: 0x00002000.
> > Effective driver date: 06/06/2001.
> > #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> > #I063 Selected driver installs from section [VESADDC.Install] in
> > "c:\windows\inf\monitor.inf".
> > #I320 Class GUID of device remains:
> > {4D36E96E-E325-11CE-BFC1-08002BE10318}.
> > #I060 Set selected driver.
> > #I058 Selected best compatible driver.
> > #-166 Device install function: DIF_INSTALLDEVICEFILES.
> > #I124 Doing copy-only install of
> > "DISPLAY\SEC4A58\4&186BBD0C&0&80871400&00&22".
> > #-166 Device install function: DIF_REGISTER_COINSTALLERS.
> > #I056 Coinstallers registered.
> > #-166 Device install function: DIF_INSTALLINTERFACES.
> > #-011 Installing section [VESADDC.Install.Interfaces] from
> > "c:\windows\inf\monitor.inf".
> > #I054 Interfaces installed.
> > #-166 Device install function: DIF_INSTALLDEVICE.
> > #I123 Doing full install of
> > "DISPLAY\SEC4A58\4&186BBD0C&0&80871400&00&22".
> > #I121 Device install of "DISPLAY\SEC4A58\4&186BBD0C&0&80871400&00&22"
> > finished successfully.
> >
> >
> > So does anyone have any insight on how to get rid of this problem? Any
> >
> > help is greatly appreciated!
> >
> >
> > thanks,
> > Jason
> >

.

Relevant Pages

  • SBS2003 corrupt files after installing exchange2003 sp1
    ... I installed SBS2003 via oem sysprep method. ... Installed Windows updates all of them OK. ... on reboot before you even see the windows 2003 server logo. ... install process from scratch without sysprep. ...
    (microsoft.public.windows.server.sbs)
  • Re: System Cloning and Driver
    ... > #I060 Set selected driver. ... > #I058 Selected best compatible driver. ... >> Since it also happens on hard disk with System Cloning, if I reboot on hard ...
    (microsoft.public.windowsxp.embedded)
  • Re: MULTI-PROCESSOR HAL INSTALLATION ERROR - ACCESS DENIED
    ... Plug and Play detects that the computer devnode's hardware ... Below is the install log file with the error. ... #-018 Searching for compatible ID: ... #I060 Set selected driver. ...
    (microsoft.public.windows.server.general)
  • Re: Bluetooth Protocol Stack in XPE SP2
    ... > #I060 Set selected driver. ... > #I058 Selected best compatible driver. ...
    (microsoft.public.windowsxp.embedded)
  • Re: WMP 10 wont install after sucessful download
    ... > #I060 Set selected driver. ... > #-019 Searching for hardware ID: ... >>> Finished updating install list. ...
    (microsoft.public.windowsmedia.player)