Re: ramdisk on two hard drive

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

From: Greg Chu The Small (_at_)
Date: 07/08/04

Next message: Lilian Redes: "Windows XP could not be contacted with the domain"
Previous message: Günter Wirth: "Terminal Services Client"
In reply to: KM: "Re: ramdisk on two hard drive"
Next in thread: Slobodan Brcin \(eMVP\): "Re: ramdisk on two hard drive"
Reply: Slobodan Brcin \(eMVP\): "Re: ramdisk on two hard drive"
Messages sorted by: [ date ] [ thread ]

Date: Thu, 8 Jul 2004 09:52:15 -0400

I have all the three you listed.
Do you want to see fbalog.txt?
I am not worried about other drivers,
Just need to see hard drive.
I found that after creating the image, it only sees the original hard drive
(where the FBA processed) when it boots up.

If I replaced the hard drive with another drive, then it just does not see
it. My guess the FBA process recorded the hard drive during certain stage.
What I need to do it add a step to repeat the FBA process to install the new
hard drive after it boots up, so system can see it.

Does any one know which step in FBA intall the hard drive?

If after the FBA first boot, I just switch to XP pro (which I dual boot),
and then capture the image without the final boot, then it seems it install
the right drive.

Delete gendisk or other registry keys does not solve the problem. I spend
one or two weeks trying them already.

The conclusion I have at this point is it only worked on one drive that one
I ran FBA on.

I need to run another step to reinstall the hard drive driver.
Any one knows how to do it?

Thanks!

Greg
"KM" <konstmor@nospam_yahoo.com> wrote in message
news:%23I7epLJZEHA.2500@TK2MSFTNGP09.phx.gbl...
> Greg,
>
> I guess you posted SetupApi.log errors, did you? (not Fbalog.txt)
>
> Actualy, it seems you are having a bunch of driver problems.
> Coud you check if you included these components:
> - "PnP (Kernel-Mode)"
> - "PnP (User-Mode)"
> - "Plug and Play Software Device Enumerator"
>
> How did you create the image? Have you used TA/TAP output?
>
> KM
>
> > In the device manager, I have error for
> >
> > pci to pci bridge
> > plug and play software device device emulator
> >
> > the fabapi.log errors are listed below:
> > if you check the last section, it seems to me that the hard drive
> installed
> > OK, but ramdisk failed.
> > I am going to do the one you suggested and see if that works!
> >
> > Thanks!
> > Greg
>
> --------------------------------------------------------------------------
> --
> >
> > #E089 Failed to load the OLE Control "C:\WINDOWS\System32\txflog.dll".
> Error
> > 126: The specified module could not be found.
> > #E291 Failed to register OLE server "C:\WINDOWS\System32\txflog.dll".
> Error
> > 126: The specified module could not be found.
> > #E090 Failed to create a process for the OLE Server
> > "C:\WINDOWS\System32\msiexec.exe" with arguments "/regserver /q". Error
2:
> > The system cannot find the file specified.
> > #E339 Add Service: Binary "C:\WINDOWS\System32\DRIVERS\swenum.sys" for
> > service "swenum" is not present.
> > #E032 Error 0xe0000217: A service installation section in this INF is
> > invalid.
> > #E275 Error while installing services. Error 0xe0000217: A service
> > installation section in this INF is invalid.
> > #E122 Device install failed. Error 0xe0000217: A service installation
> > section in this INF is invalid.
> > #E157 Default installer failed. Error 0xe0000217: A service installation
> > section in this INF is invalid.
> > #E339 Add Service: Binary "C:\WINDOWS\System32\DRIVERS\p3.sys" for
service
> > "P3" is not present.
> > #E032 Error 0xe0000217: A service installation section in this INF is
> > invalid.
> > #E275 Error while installing services. Error 0xe0000217: A service
> > installation section in this INF is invalid.
> > #E122 Device install failed. Error 0xe0000217: A service installation
> > section in this INF is invalid.
> > #E157 Default installer failed. Error 0xe0000217: A service installation
> > section in this INF is invalid.
> >
> > #-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.
> > #I125 Installing NULL driver for
> > "PCI\VEN_1106&DEV_3038&SUBSYS_12340925&REV_1A\3&61AAA01&0&12".
> > #E122 Device install failed. Error 0xe0000219: The installation failed
> > because a function driver was not specified for this device instance.
> > #I125 Installing NULL driver for
> > "PCI\VEN_1106&DEV_3038&SUBSYS_12340925&REV_1A\3&61AAA01&0&12".
> >
> > #I125 Installing NULL driver for
> > "PCI\VEN_1106&DEV_3038&SUBSYS_12340925&REV_1A\3&61AAA01&0&13".
> > #E122 Device install failed. Error 0xe0000219: The installation failed
> > because a function driver was not specified for this device instance.
> >
> > #E339 Add Service: Binary "C:\WINDOWS\System32\DRIVERS\viaagp.sys" for
> > service "viaagp" is not present.
> > #E032 Error 0xe0000217: A service installation section in this INF is
> > invalid.
> > #E275 Error while installing services. Error 0xe0000217: A service
> > installation section in this INF is invalid.
> > #E122 Device install failed. Error 0xe0000217: A service installation
> > section in this INF is invalid.
> > #E157 Default installer failed. Error 0xe0000217: A service installation
> > section in this INF is invalid.
> > #I060 Set selected driver.
> > #I125 Installing NULL driver for
> > "PCI\VEN_1106&DEV_8605&SUBSYS_00000000&REV_00\3&61AAA01&0&08".
> > #E122 Device install failed. Error 0xe0000219: The installation failed
> > because a function driver was not specified for this device instance.
> >
> > #I125 Installing NULL driver for "ACPI\PNP0700\4&2562C2FD&0".
> > #E122 Device install failed. Error 0xe0000219: The installation failed
> > because a function driver was not specified for this device instance.
> >
> > [2004/07/07 13:25:48 272.6 Driver Install]
> > #-019 Searching for hardware ID(s):
> >
>
ide\diskwdc_wd800jb-00eta0______________________77.07w77,ide\wdc_wd800jb-00e
> >
>
ta0______________________77.07w77,ide\diskwdc_wd800jb-00eta0________________
> > ______,wdc_wd800jb-00eta0______________________77.07w77,gendisk
> > #-018 Searching for compatible ID(s): gendisk
> > #-198 Command line processed: C:\windows\system32\services.exe
> > #I022 Found "GenDisk" in C:\windows\inf\disk.inf; Device: "Disk drive";
> > Driver: "Disk drive"; Provider: "Microsoft"; Mfg: "(Standard disk
> drives)";
> > Section name: "disk_install".
> > #I023 Actual install section: [disk_install.NT]. Rank: 0x00000004.
> Effective
> > driver date: 07/01/2001.
> > #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> > #I063 Selected driver installs from section [disk_install] in
> > "c:\windows\inf\disk.inf".
> > #I320 Class GUID of device remains:
> {4D36E967-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
> >
>
"IDE\DISKWDC_WD800JB-00ETA0______________________77.07W77\4457572D41434C4837
> > 3438393637_038_0_0_0_0".
> > #-166 Device install function: DIF_REGISTER_COINSTALLERS.
> > #I056 Coinstallers registered.
> > #-166 Device install function: DIF_INSTALLINTERFACES.
> > #-011 Installing section [disk_install.NT.Interfaces] from
> > "c:\windows\inf\disk.inf".
> > #I054 Interfaces installed.
> > #-166 Device install function: DIF_INSTALLDEVICE.
> > #I123 Doing full install of
> >
>
"IDE\DISKWDC_WD800JB-00ETA0______________________77.07W77\4457572D41434C4837
> > 3438393637_038_0_0_0_0".
> > #I121 Device install of
> >
>
"IDE\DISKWDC_WD800JB-00ETA0______________________77.07W77\4457572D41434C4837
> > 3438393637_038_0_0_0_0" finished successfully.
> > [2004/07/07 13:25:49 272.11 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.
> >
> >
> > "Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
> > news:uBaZYW6YEHA.2388@TK2MSFTNGP11.phx.gbl...
> > > Hi Greg,
> > >
> > > Try removing only things from 1, 2.
> > > If it does not work try removing 1,2,5.
> > >
> > > 1. HLKM\System\Setup\SystemPartition
> > > 2. HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices
> > >
> > > Please try reading error from device manager and give it to us.
> > > Also examine setupapi.log from XPe when you boot to your image it
should
> > tell you what went wrong.
> > >
> > > Best regards,
> > > Slobodan
> > >
> > > "Greg Chu The Small" <greg_chu @ wendys.com> wrote in message
> > news:%231BDY%235YEHA.384@TK2MSFTNGP10.phx.gbl...
> > > > Hi, I could not find my old thread. So let me continure my problem.
> > > >
> > > > The hard drive that used to do FBA to create the RAMDISK image boot
> fine
> > and
> > > > I can use diskpart.
> > > >
> > > > But if I use another hard drive to boot with the same image then
could
> > not
> > > > use diskpart to see the hard drive.
> > > >
> > > > I searched through registry and find there are some entries withe
the
> > hard
> > > > drive model saved in there.
> > > >
> > > > Have tried all suggestions in the past posts
> > > >
> > > > 1. deleted system partioin
> > > > 2. deleted moutted device
> > > > 3. deleted mshdc.inf
> > > > 4. deleted disk.inf
> > > > 5. deleted gendisk
> > > > 6. removed class entries
> > > >
> > > > Just could not get it to work.
> > > >
> > > > Any one has any clue?
> > > >
> > > > Thanks!
> > > >
> > > > Greg
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Next message: Lilian Redes: "Windows XP could not be contacted with the domain"
Previous message: Günter Wirth: "Terminal Services Client"
In reply to: KM: "Re: ramdisk on two hard drive"
Next in thread: Slobodan Brcin \(eMVP\): "Re: ramdisk on two hard drive"
Reply: Slobodan Brcin \(eMVP\): "Re: ramdisk on two hard drive"
Messages sorted by: [ date ] [ thread ]

Relevant Pages

Re: URGENT: Strange problem during installation a device drivers
... deleted that oem*.inf/pnf files, rebooted and selected my inf from the ... beginning, the installation faile the same way, driver coping while the ... debice reboots with another VID/PID and asks for another driver. ...
(microsoft.public.development.device.drivers)
Re: PRB - No Network Connections in new image
... I am surprised the "Broadcom NetXtreme" adapter didn't work for you. ... INF import? ... Make sure the driver service data is in FBA resources for that component - it is the key to make it working. ... > installation section in this INF is invalid. ...
(microsoft.public.windowsxp.embedded)
Re: What registry key to delete to reinstall a device
... > I am a newbie in device driver programming and installation. ... the PC will ask for .inf file for driver installation. ... > installation had been saved to registry. ...
(microsoft.public.development.device.drivers)
RE: DIFxAPI
... The inf we use does have the setting to indicate that it is ... This driver package installs correctly using this ... > LOG Event: 1, No matching devices found in INF ... Installation completed with code 0xE000020B. ...
(microsoft.public.development.device.drivers)
Re: WINDOWS INF File help
... earlier I tried with the "DefaultInstall" option in INF, ... even it said your driver is not digitally signed.... ... can we debug the INF file installation? ...
(microsoft.public.development.device.drivers)