Re: System Cloning and Driver

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Slobodan Brcin \(eMVP\) (sbrcin_at_ptt.yu)
Date: 09/16/04 

Date: Thu, 16 Sep 2004 20:21:55 +0200

Hi Bing,

Check this it might explain some things and you can use it:
http://www.sysinternals.com/ntw2k/source/newsid.shtml

Best regards,
Slobodan

"Bin Xing" <BinXing@discussions.microsoft.com> wrote in message news:A7355582-4B72-412C-AD79-DDFB3EF37C56@microsoft.com...
> Hi Slobodan,
>
> Thanks for your reply. I have more questions:
> 1. You said "SID and computer name differentiate computers", if computer
> names are different on machines, even with a same SID, it still means
> different machines because it's SID "AND" computer name. So I don't see why
> we need SID.
>
> 2. I need network and also I need Remote Boot. Does that mean I have to run
> pre FBA on each board and get post FBAs, then create SDI files for different
> boards? The hardwares on each board are exactly same. Can I just make
> different copies of the SDI file for Remote Boot? I don't think I can since
> SID has been generated in the post FBA.
>
> The reason why I want to do this is just because System Cloning causes
> problems as I mentioned before, I have no other choice.
>
> Thanks.
>
> Bin
>
> "Slobodan Brcin (eMVP)" wrote:
>
> > Hi Bin,
> >
> > Few answers for you:
> > SID has nothing to do with legal issues. If your computer participate on network, SID and computer name differentiate computers
> > between each other. Without the network support you should not worry about same SID.
> >
> > You don't have to build few images, one pre FBA image is enough.
> > Computer SID is generated during the FBA, so if you have pre FBA image it will bind nicely to the machine.
> >
> > Best regards,
> > Slobodan
> >
> >
> > "Bin Xing" <BinXing@discussions.microsoft.com> wrote in message news:79BA0325-0BC7-4A5F-8E06-19F82CB2EBE3@microsoft.com...
> > > Hi Slobodan,
> > >
> > > If you search "reboot", you'll see other "reboot" beside the RAM disk. I
> > > don't think the problem comes from the RAM disk because it also happened on
> > > hard disk booting. I'll try to remove the RAM disk later.
> > >
> > > Another question: If I don't use System Cloning and I just get a few copies
> > > of the image, one for each board, will that cause problem? I can change the
> > > host name by a batch file. But one I don't understand is SID. That means I'll
> > > have all image with the same SID, right? Nobody says what is going to happen
> > > if I use the same SID for different board. I knew SID has something to do
> > > with user account, but what will happen if I use one SID? The next image
> > > can't logon? If it's just legal problem, we'll pay for the licenses. If I
> > > build a few images, each one for one board, XPe will make sure each board has
> > > its own SID, which is different from others, right?
> > >
> > > Bin
> > >
> > > "Slobodan Brcin (eMVP)" wrote:
> > >
> > > > Hi Bin,
> > > >
> > > > What is wrong with ramdisk?
> > > > Can you try removing ramdisk for testing purposes.
> > > >
> > > > Best regards,
> > > > Slobodan
> > > >
> > > > "Bin Xing" <BinXing@discussions.microsoft.com> wrote in message news:FFA0CB25-6DD5-45AE-B35F-28364C931081@microsoft.com...
> > > > > Hi,
> > > > >
> > > > > Here is the some information in file setupapi.log, I found some reboot
> > > > > messages. BTW, there are two Intel PRO 1000 ethernet cards and 4 COM ports on
> > > > > board.
> > > > >
> > > > > [2004/09/16 12:37:41 1316.41]
> > > > > #-199 Executing "C:\WINDOWS\system32\fbreseal.exe" with command line: fbreseal
> > > > > #-166 Device install function: DIF_PROPERTYCHANGE.
> > > > > #I292 Changing device properties of "ROOT\MS_PSCHEDMP\0000".
> > > > > #I306 DICS_START: Device has been started.
> > > > > [2004/09/16 10:27:17 460.5]
> > > > > #-198 Command line processed: C:\windows\system32\services.exe
> > > > > #W389 No [STRINGS.0409] or [STRINGS.0009] section in
> > > > > c:\windows\inf\oem0.inf, using [STRINGS] instead.
> > > > > [2004/09/16 10:27:17 460.32]
> > > > > #-198 Command line processed: C:\windows\system32\services.exe
> > > > > #-166 Device install function: DIF_PROPERTYCHANGE.
> > > > > #I292 Changing device properties of "ROOT\MS_PSCHEDMP\0000".
> > > > > #I306 DICS_START: Device has been started.
> > > > > [2004/09/16 10:27:17 460.33]
> > > > > #-198 Command line processed: C:\windows\system32\services.exe
> > > > > #-166 Device install function: DIF_PROPERTYCHANGE.
> > > > > #I292 Changing device properties of "ROOT\MS_PSCHEDMP\0002".
> > > > > #I306 DICS_START: Device has been started.
> > > > > [2004/09/16 10:27:17 460.37 Driver Install]
> > > > > #-019 Searching for hardware ID(s): ms_pschedmp
> > > > > #-198 Command line processed: C:\windows\system32\services.exe
> > > > > #I022 Found "ms_pschedmp" in C:\windows\INF\netpsa.inf; Device: "Packet
> > > > > Scheduler Miniport"; Driver: "Packet Scheduler Miniport"; Provider:
> > > > > "Microsoft"; Mfg: "Microsoft"; Section name: "PSchedMP.ndi".
> > > > > #I023 Actual install section: [PSchedMP.ndi]. Rank: 0x00000000. Effective
> > > > > driver date: 07/01/2001.
> > > > > #I063 Selected driver installs from section [PSchedMP.ndi] in
> > > > > "c:\windows\inf\netpsa.inf".
> > > > > #I320 Class GUID of device remains: {4D36E972-E325-11CE-BFC1-08002BE10318}.
> > > > > #I060 Set selected driver.
> > > > > #I058 Selected best compatible driver.
> > > > > #-166 Device install function: DIF_REGISTER_COINSTALLERS.
> > > > > #I056 Coinstallers registered.
> > > > > #-166 Device install function: DIF_INSTALLINTERFACES.
> > > > > #-011 Installing section [PSchedMP.ndi.Interfaces] from
> > > > > "c:\windows\inf\netpsa.inf".
> > > > > #I054 Interfaces installed.
> > > > > #-166 Device install function: DIF_INSTALLDEVICE.
> > > > > #I123 Doing full install of "ROOT\MS_PSCHEDMP\0001".
> > > > > #I121 Device install of "ROOT\MS_PSCHEDMP\0001" finished successfully.
> > > > > #-166 Device install function: DIF_PROPERTYCHANGE.
> > > > > #I292 Changing device properties of "ROOT\MS_PSCHEDMP\0001".
> > > > > #I306 DICS_START: Device has been started.
> > > > > [2004/09/16 10:27:17 460.45]
> > > > > #-198 Command line processed: C:\windows\system32\services.exe
> > > > > #-166 Device install function: DIF_PROPERTYCHANGE.
> > > > > #I292 Changing device properties of
> > > > > "PCI\VEN_8086&DEV_1010&SUBSYS_10118086&REV_01\3&36B8E21F&0&09E0".
> > > > > #I306 DICS_START: Device has been started.
> > > > > [2004/09/16 10:27:16 460.3 Driver Install]
> > > > > #-019 Searching for hardware ID(s):
> > > > >
> > > >
> >
pci\ven_8086&dev_1010&subsys_10118086&rev_01,pci\ven_8086&dev_1010&subsys_10118086,pci\ven_8086&dev_1010&cc_020000,pci\ven_8086&dev_
> > > > 1010&cc_0200
> > > > > #-018 Searching for compatible ID(s):
> > > > >
> > > >
> >
pci\ven_8086&dev_1010&rev_01,pci\ven_8086&dev_1010,pci\ven_8086&cc_020000,pci\ven_8086&cc_0200,pci\ven_8086,pci\cc_020000,pci\cc_020
> > > > 0
> > > > > #-198 Command line processed: C:\windows\system32\services.exe
> > > > > #W389 No [STRINGS.0409] or [STRINGS.0009] section in
> > > > > C:\windows\inf\oem0.inf, using [STRINGS] instead.
> > > > > #I022 Found "PCI\VEN_8086&DEV_1010&SUBSYS_10118086" in
> > > > > C:\windows\inf\oem0.inf; Device: "Intel(R) PRO/1000 MT Dual Port Server
> > > > > Adapter"; Driver: "Intel(R) PRO/1000 MT Dual Port Server Adapter"; Provider:
> > > > > "Intel"; Mfg: "Intel"; Section name: "E1010Copper.ndi".
> > > > > #I023 Actual install section: [E1010Copper.ndi.NTx86]. Rank: 0x00000001.
> > > > > Effective driver date: 03/12/2004.
> > > > > #I022 Found "PCI\VEN_8086&DEV_1010" in C:\windows\inf\oem0.inf; Device:
> > > > > "Intel(R) PRO/1000 MT Dual Port Network Connection"; Driver: "Intel(R)
> > > > > PRO/1000 MT Dual Port Network Connection"; Provider: "Intel"; Mfg: "Intel";
> > > > > Section name: "E1010.ndi".
> > > > > #I023 Actual install section: [E1010.ndi.NTx86]. Rank: 0x00002001. Effective
> > > > > driver date: 03/12/2004.
> > > > > #I022 Found "PCI\VEN_8086&DEV_1010" in C:\windows\inf\oem2.inf; Device:
> > > > > "I8254x Driver 1010"; Driver: "I8254x Driver 1010"; Provider: "CAE Inc.";
> > > > > Mfg: "CAE Inc."; Section name: "CaeI8254xPci".
> > > > > #I023 Actual install section: [CaeI8254xPci]. Rank: 0x00002001. Effective
> > > > > driver date: 01/01/1601.
> > > > > #I393 Modified INF cache "C:\windows\inf\INFCACHE.1".
> > > > > #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> > > > > #I063 Selected driver installs from section [E1010Copper.ndi] in
> > > > > "c:\windows\inf\oem0.inf".
> > > > > #I320 Class GUID of device remains: {4D36E972-E325-11CE-BFC1-08002BE10318}.
> > > > > #I060 Set selected driver.
> > > > > #I058 Selected best compatible driver.
> > > > > #-166 Device install function: DIF_ALLOW_INSTALL.
> > > > > #W389 No [STRINGS.0409] or [STRINGS.0009] section in
> > > > > c:\windows\inf\oem0.inf, using [STRINGS] instead.
> > > > > #-166 Device install function: DIF_INSTALLDEVICEFILES.
> > > > > #I124 Doing copy-only install of
> > > > > "PCI\VEN_8086&DEV_1010&SUBSYS_10118086&REV_01\3&36B8E21F&0&09E0".
> > > > > #W389 No [STRINGS.0409] or [STRINGS.0009] section in
> > > > > c:\windows\inf\oem0.inf, using [STRINGS] instead.
> > > > > #-011 Installing section [E1010Copper.ndi.NTx86] from
> > > > > "c:\windows\inf\oem0.inf".
> > > > > #W389 No [STRINGS.0409] or [STRINGS.0009] section in
> > > > > c:\windows\inf\oem0.inf, using [STRINGS] instead.
> > > > > #-166 Device install function: DIF_REGISTER_COINSTALLERS.
> > > > > #W389 No [STRINGS.0409] or [STRINGS.0009] section in
> > > > > c:\windows\inf\oem0.inf, using [STRINGS] instead.
> > > > > #I056 Coinstallers registered.
> > > > > #-166 Device install function: DIF_INSTALLINTERFACES.
> > > > > #W389 No [STRINGS.0409] or [STRINGS.0009] section in
> > > > > c:\windows\inf\oem0.inf, using [STRINGS] instead.
> > > > > #-011 Installing section [E1010Copper.ndi.NTx86.Interfaces] from
> > > > > "c:\windows\inf\oem0.inf".
> > > > > #I054 Interfaces installed.
> > > > > #-166 Device install function: DIF_INSTALLDEVICE.
> > > > > #W389 No [STRINGS.0409] or [STRINGS.0009] section in
> > > > > c:\windows\inf\oem0.inf, using [STRINGS] instead.
> > > > > #I123 Doing full install of
> > > > > "PCI\VEN_8086&DEV_1010&SUBSYS_10118086&REV_01\3&36B8E21F&0&09E0".
> > > > > #W389 No [STRINGS.0409] or [STRINGS.0009] section in
> > > > > c:\windows\inf\oem0.inf, using [STRINGS] instead.
> > > > > #I121 Device install of
> > > > > "PCI\VEN_8086&DEV_1010&SUBSYS_10118086&REV_01\3&36B8E21F&0&09E0" finished
> > > > > successfully.
> > > > > #I292 Changing device properties of
> > > > > "PCI\VEN_8086&DEV_1010&SUBSYS_10118086&REV_01\3&36B8E21F&0&09E0".
> > > > > #W114 Device
> > > > > "PCI\VEN_8086&DEV_1010&SUBSYS_10118086&REV_01\3&36B8E21F&0&09E0" required
> > > > > reboot: Device has problem: 0x26: CM_PROB_DRIVER_FAILED_PRIOR_UNLOAD.
> > > > > #I304 DICS_PROPCHANGE: Device could not be restarted.
> > > > > [2004/09/16 10:27:26 460.48 Driver Install]
> > > > > #-019 Searching for hardware ID(s): ramdisk\ramvolume
> > > > > #-198 Command line processed: C:\windows\system32\services.exe
> > > > > #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> > > > > #W059 Selecting best compatible driver failed. Error 0xe0000228: There are
> > > > > no compatible drivers for this device.
> > > > > #W157 Default installer failed. Error 0xe0000228: There are no compatible
> > > > > drivers for this device.
> > > > > [2004/09/16 10:27:27 272.2]
> > > > > #-199 Executing "C:\windows\system32\rundll32.exe" with command line:
> > > > > rundll32.exe newdev.dll,ClientSideInstall
> > > > > \\.\pipe\PNP_Device_Install_Pipe_0.{064C6A95-B387-4219-A042-6DABA18E45CE}
> > > > > #I060 Set selected driver.
> > > > > #-019 Searching for hardware ID(s): ramdisk\ramvolume
> > > > > #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> > > > > #W059 Selecting best compatible driver failed. Error 0xe0000228: There are
> > > > > no compatible drivers for this device.
> > > > > #W157 Default installer failed. Error 0xe0000228: There are no compatible
> > > > > drivers for this device.
> > > > > #I060 Set selected driver.
> > > > > #-166 Device install function: DIF_INSTALLDEVICE.
> > > > > #I125 Installing NULL driver for
> > > > > "RAMDISK\RAMVOLUME\{D9B257FC-684E-4DCB-AB79-03CFA2F6B750}".
> > > > > #W100 Query-removal during install of
> > > > > "RAMDISK\RAMVOLUME\{D9B257FC-684E-4DCB-AB79-03CFA2F6B750}" was vetoed by
> > > > > "Ramdisk\RamVolume\{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}" (veto type 6:
> > > > > PNP_VetoDevice).
> > > > > #W104 Device "RAMDISK\RAMVOLUME\{D9B257FC-684E-4DCB-AB79-03CFA2F6B750}"
> > > > > required reboot: Query remove failed (install) CfgMgr32 returned: 0x17:
> > > > > CR_REMOVE_VETOED.
> > > > > #I121 Device install of
> > > > > "RAMDISK\RAMVOLUME\{D9B257FC-684E-4DCB-AB79-03CFA2F6B750}" finished
> > > > > successfully.
> > > > >
> > > > > Bin
> > > > >
> > > > > "Bin Xing" wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I have a few cPCI boards and I'm using Remote Boot with System Cloning
> > > > > > Tools, and no EWF. There are two devices were disabled because we don't have
> > > > > > the drviers for them and we don't need them, either. After post FBA, I
> > > > > > installed all of the other drivers except the two. Then, I ran fbreseal.
> > > > > >
> > > > > > The problem is: When sysmtem finishes booting, it automatically finds new
> > > > > > devices and automatically install drviers for them, even though the drivers
> > > > > > are already installed, such as keyboard, COM ports, sound device, network
> > > > > > card ... After the installation finishes, it shows:
> > > > > >
> > > > > > "Windows has finished installing new devices. The software that supports
> > > > > > your device requires that you restart you computer. You must restart you
> > > > > > computer before the new settings will take effect.
> > > > > >
> > > > > > Do you want to restart your computer now? ( Yes / No )"
> > > > > >
> > > > > > If I check with Device Manager, I found network driver is yellow mark. And
> > > > > > if I right click the network driver (Intel PRO1000 1GB network card) and
> > > > > > choose "properties", it shows Device Status as:
> > > > > >
> > > > > > "Windows cannot load the device driver for this hardware because a previous
> > > > > > instance of the device driver is still in memory. (Code 38)
> > > > > >
> > > > > > You need to restart your computer before the changes you made to this device
> > > > > > will take affect."
> > > > > >
> > > > > > I can also reproduce this problem on my hard disk instead of on Remote Boot
> > > > > > RAM disk with Cloning. However, if I don't run fbreseal, no this kind of
> > > > > > problem. It seems it has something to do with System Cloning. Here is the
> > > > > > Extended Properties for System Cloning Tools:
> > > > > >
> > > > > > cmiServicePackLevel: 1
> > > > > > cmiResealDLL: (empty)
> > > > > > cmiResealDllEntry: (empty)
> > > > > > CmiResealPhase: 0
> > > > > > cmiRemoveAutoLogon: FALSE
> > > > > > cmiGenerateComputerName: 1
> > > > > > cmiNoHelpFiles: FALSE
> > > > > > cmiLangEnableMUI: TRUE
> > > > > > cmiProtPropList: 'cmiServicePackLevel"... (including cmiResealPhase)
> > > > > > SrcFileSize: 81920
> > > > > >
> > > > > > Since it also happens on hard disk with System Cloning, if I reboot on hard
> > > > > > disk and got pop up window for rebooting, then I clicked "Yes" button to
> > > > > > reboot for once. Then, I ran fbreseal again. After that, next boot will fix
> > > > > > network card driver problem, but I saw yellow mark on COM port and sound card
> > > > > > in Device Manager. And this time, there is no reboot pop up window any more.
> > > > > > If I use this resealed image on other boards, they still pop up window to
> > > > > > reboot the machine and network driver doesn't work, which shows yellow mark
> > > > > > in Devce Manager.
> > > > > >
> > > > > > Is there anyone can help me?
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > > Bin
> > > >
> > > >
> > > >
> >
> >
> >

Relevant Pages

  • Re: clarification please
    ... If you have an image and you run FBA on every target device does it ... FBA will always create random SID. ... If i must add the system cloning tools, then the process is normal run ...
    (microsoft.public.windowsxp.embedded)
  • Re: clarification please
    ... If you have an image and you run FBA on every target device does it ... FBA will always create random SID. ... If i must add the system cloning tools, then the process is normal run ...
    (microsoft.public.windowsxp.embedded)
  • Re: fbreseal.exe
    ... At the end phase of the FBA, ... This is like the sysprep. ... setting a new SID. ... upon a reboot, and that I do not need to use SYSPREP? ...
    (microsoft.public.windowsxp.embedded)
  • Re: System Cloning and Driver
    ... You said "SID and computer name differentiate computers", ... different machines because it's SID "AND" computer name. ... SID has been generated in the post FBA. ... If your computer participate on network, SID and computer name differentiate computers ...
    (microsoft.public.windowsxp.embedded)
  • Re: Problem with the System Cloning Tool
    ... If you do not need machine names then why do you concern yourself with SID ... Regards, ... Slobodan ... If so which componet should i remove to not have machine ...
    (microsoft.public.windowsxp.embedded)