Re: System Cloning and Driver

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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

Date: Fri, 17 Sep 2004 22:57:44 +0200

Unfortunately from your logs I can't see more than one network adapter hardware ID.

You should check in registry if there are VID,PID differences in numbers between those two devices. Something like
pci\ven_8086&dev_1010&subsys_10118086
If there are then you can simply modify your and Intel inf files so each driver correspond to certain piece of hardware. This way
you will not have to change anything manually.

If both adapters are identical (same piece of hardware) then you will have to write your installation application that will
depending on bus position install your or Intel driver.
For this you will have to use Setup API functions, but who ever that wrote this driver he will know how to do this.

BTW:
I'm curious why did you write your own driver? Performance can't be a reason since you can make higher driver that trough NDIS uses
network driver almost directly. I have above 99% gigabit network utililization by using similar approach, and all send and receives
are driven trough callback functions by net driver itself.

Also I did not understand if suggestion that I gave you to test worked?

Best regards,
Slobodan

"Bin Xing" <BinXing@discussions.microsoft.com> wrote in message news:50141EE0-9DBD-4B48-A4E2-F49BC58B6017@microsoft.com...
> Hi Slobodan,
>
> The thing is that there are two Intel PRO 1000 network cards on board.
> Eventually, Intel driver will be only installed on one of two cards. Our own
> real-time driver will be installed on the other one. The reason why I said
> I've installed two Intel drivers for the two Intel PRO 1000 ethernet cards is
> just to make it simple to debug the XPe problem since XPe also doesn't work
> if both ethernet cards are installed with a same Intel driver.
>
> In the real situation, each Intel PRO ethernet card has its own driver. The
> two different drivers, one from Intel and the other is our own, will be
> installed on the ethernet cards. So I guess it won't work if we let XPe boot
> from SDI file and PnP finds them automatically.
>
> I tried XPe with the two different drivers, the Intel driver was
> automatically reinstalled after Remote Boot from the SDI file, so it didn't
> work. I thought maybe our own driver causes this problem, so I rebuilt
> another clean image and install both of the ethernet cards with Intel driver,
> but it's the same problem. If without System Cloning, everthing is fine, even
> the two different drivers all work. But if with System Cloning, it doesn't
> work, no matter I install two same Intel driver or two different driver.
> Therefore, it seems like the problem has something to do with System Cloning,
> even I knew System Cloning works fine in many cases.
>
> According to what you mentioned below, if I remove / don't install the
> network driver, can PnP knows which ethernet card will be installed with
> Intel driver and which one will be installed with our own driver?
>
> Thanks a lot.
>
> Bin
>
> "Slobodan Brcin (eMVP)" wrote:
>
> > Hi Bin,
> >
> > The best general idea would be to have drivers present but without any network adapter installed prior to SDI boot.
> > This will solve your problem with network driver not wanting to unload.
> >
> > You can remove network device driver instance from registry for each adapter you have from:
> >
> > HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VEN_8086&DEV_1011...... probably in your case.
> > You should remove this branch from registry before creating SDI file.
> > When XPe boot from SDI file PnP will find new hardware and automatically install network driver.
> >
> > Best regards,
> > Slobodan
> >
> >
> > "Bin Xing" <BinXing@discussions.microsoft.com> wrote in message news:F625F9E0-04D1-4E4C-9269-C80CC165F403@microsoft.com...
> > > Hi Slobodan,
> > >
> > > Thanks for your reply. But there is something I don't understand:
> > >
> > > "In step 3. Do not install net driver. Instead of installing driver you
> > > should place run reg key that will install it when you boot
> > > XPe next time from SDI file."
> > >
> > > I don't know why I can't install the network driver in step 3, it is
> > > mentioned in making XPe procedure from Microsoft. Anyway, what's the meaning
> > > of "place run reg key"? Does that mean a batch file will be run after XPe
> > > boots from SDI, and the batch file will change the registry key and install
> > > the driver?
> > >
> > > "Or after installing you can remove installation parameters related to your
> > > Network adapters from registry Enum branch." Could you tell me what the
> > > paramters are, please?
> > >
> > > Thanks.
> > >
> > > Bin
> > >
> > >
> > > "Slobodan Brcin (eMVP)" wrote:
> > >
> > >
> > > > Hi Bin,
> > > >
> > > > In step 3. Do not install net driver. Instead of installing driver you should place run reg key that will install it when
you
> > boot
> > > > XPe next time from SDI file.
> > > > Or after installing you can remove installation parameters related to your Network adapters from registry Enum branch.
> > > >
> > > > Best regards,
> > > > Slobodan
> > > >
> > > >
> > > > "Bin Xing" <BinXing@discussions.microsoft.com> wrote in message news:427E6509-5BD7-4C6F-93FD-255FB82CD8B1@microsoft.com...
> > > > > Hi Slobodan,
> > > > >
> > > > > What I did was:
> > > > >
> > > > > 1. Build an image with TD including System Cloning Tools, but no EWF. Image
> > > > > size is about 200MB
> > > > > cmiResealPhase: 0
> > > > > 2. Run FBA
> > > > > 3. Manually install applications and drivers, including the drivers for two
> > > > > Intel PRO 1000 ethernet cards. There are two same Intel PRO 1000 enthernet
> > > > > cards on the cPCI board, so I install the driver downloaded from Intel web
> > > > > site.
> > > > > 4. Run fbreseal
> > > > > 5. Reboot and make SDI file, then import to another SDI file with "sdimgr
> > > > > filename.sdi /readpart:f:"
> > > > > 6. Put the file to server and set Remote Boot Manager to take this SDI file
> > > > > for remote booting
> > > > >
> > > > > Remote Boot Procedure:
> > > > > 1. PXE transfers image to local RAM disk
> > > > > 2. System Cloning
> > > > > 3. XPe booting
> > > > > 4. XPe finds new hardware, installing drivers automatically. Sometimes XPe
> > > > > needs to reboot and network doesn't work, but sometimes network works and no
> > > > > reboot is needed. Let's say I have 6 boards, 2 of them need to reboot, the
> > > > > other 4 don't need to. It's the same image on all of the boards. I'm not 100%
> > > > > sure hardwares on all of the boards are exactly same, but I guess so. And the
> > > > > 2 boards are not always the same boards, this time it's, for example, #2 and
> > > > > #4, next time it's #1 and #5. And the number of boards that needs to reboot
> > > > > also changed at every remote booting. This time maybe there are 2 boards need
> > > > > to reboot, and next time it's 4 boards.
> > > > >
> > > > > I guess this problem has something to do with System Cloning because it
> > > > > always works if I don't use System Cloning. Maybe the reseal phase should not
> > > > > be 0, even through I saw everybody says it should be 0 if I need to manually
> > > > > install applications or drivers after FBA. It seems System Cloning changes
> > > > > something in the image and causes it's not exactly same as it was. And System
> > > > > Cloning does something that I don't know, which causes XPe finds new
> > > > > hardwares and automatically install them. No new hardware is found if I don't
> > > > > use System Cloning. However, if I don't use System Cloning, SID will be same
> > > > > on all of the XPe. Since we use workgroup instead of Domain, SID is important
> > > > > for me.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > Bin
> > > > >
>

Relevant Pages

  • Re: Adding network and internet to Warp 4
    ... install it "found" my NIC card, and loaded the generic Realtek OS/2 ... You should note that there are more than one driver for RealTek NIC. ... Loading Realtek Fast Ethernet Network Adapter driver ...
    (comp.os.os2.misc)
  • Re: Adding network and internet to Warp 4
    ... install it "found" my NIC card, and loaded the generic Realtek OS/2 ... You should note that there are more than one driver for RealTek NIC. ... Loading Realtek Fast Ethernet Network Adapter driver ...
    (comp.os.os2.misc)
  • How to Share (network) a Hewlett Packard HP Photosmart 8250 across a network
    ... After a LOT of investigation and head scratching, it turns out that it HAD been working ONLY because the systems I was using, both the host and the client, had previously had an HP Deskjet 7350 installed on them that had also been shared over the network. ... The Photosmart 8250 had worked only because the Desktjet 7350 software was being used to print on the 8250. ... First, you will need a driver CD from a late model networkable Deskjet printer that is compatible with the target Photosmart printer; in my case, I used a CD from an HP Deskjet 7350 to share the Photosmart 8250 across a network, and it works fine. ... This is done a zillion different ways, and every product's install CD is different, so all I can tell you is to look around. ...
    (comp.periphs.printers)
  • Re: Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
    ... network before all this happened. ... If the driver won't load, ... You could test the hardware, ... You could also try taking a spare disk, and doing a clean install ...
    (alt.comp.periphs.mainboard.asus)
  • Re: Netowrk printer install Failure
    ... program for the driver also sees it when looking for it. ... Windows Printing Team ... I managed to install a PDF printer without difficulty. ... I have an OKI C5400n printer setup on a Home Network. ...
    (microsoft.public.windowsxp.print_fax)