Running the same image on 2 different hardware
Mike Warren
a device that has one of 2 possible motherboards.
My custom shell can load the correct image but the problem
is that I can't get the CD to work properly on both motherboards.
Using the same TD image, if I perform FBA on either system
I get a working CD, but USB will not work on the other system.
Does anyone have an idea how I go about diagnosing/fixing
this problem?
-Mike
Mike Warren
This is the ntbtlog.txt from the good machine. This is the
one that FBA was run on.
Service Pack 2 3 29 2006 18:58:29.500
Loaded driver \XPE\system32\ntoskrnl.exe
Loaded driver \XPE\system32\hal.dll
Loaded driver \XPE\system32\KDCOM.DLL
Loaded driver \XPE\system32\BOOTVID.dll
Loaded driver ACPI.sys
Loaded driver \XPE\system32\drivers\WMILIB.SYS
Loaded driver pci.sys
Loaded driver eltorito.sys
Loaded driver isapnp.sys
Loaded driver MountMgr.sys
Loaded driver ftdisk.sys
Loaded driver pciide.sys
Loaded driver \XPE\system32\drivers\PCIIDEX.SYS
Loaded driver PartMgr.sys
Loaded driver intelide.sys
Loaded driver ACPIEC.sys
Loaded driver \XPE\system32\drivers\OPRGHDLR.SYS
Loaded driver EWF.sys
Loaded driver atapi.sys
Loaded driver cdrom.sys
Loaded driver \XPE\system32\drivers\CLASSPNP.SYS
Loaded driver Fastfat.sys
Loaded driver KSecDD.sys
Loaded driver imapi.sys
Loaded driver disk.sys
Loaded driver \SystemRoot\system32\drivers\processr.sys
Loaded driver \SystemRoot\system32\drivers\usbohci.sys
Loaded driver \SystemRoot\system32\drivers\usbehci.sys
Loaded driver \SystemRoot\system32\DRIVERS\redbook.sys
Loaded driver \SystemRoot\system32\drivers\serial.sys
Loaded driver \SystemRoot\system32\drivers\serenum.sys
Loaded driver \SystemRoot\system32\drivers\swenum.sys
Loaded driver \SystemRoot\system32\drivers\update.sys
Loaded driver \SystemRoot\system32\drivers\usbhub.sys
Loaded driver \SystemRoot\System32\Drivers\Fs_Rec.SYS
Did not load driver \SystemRoot\system32\drivers\kbdhid.sys
Did not load driver \SystemRoot\system32\drivers\i8042prt.sys
Loaded driver \SystemRoot\System32\DRIVERS\mouclass.sys
Loaded driver \SystemRoot\system32\drivers\kbdclass.sys
Loaded driver \SystemRoot\System32\drivers\vga.sys
Loaded driver \SystemRoot\System32\Drivers\Npfs.SYS
Loaded driver \SystemRoot\system32\drivers\TwTouch.sys
Loaded driver \SystemRoot\system32\drivers\hidusb.sys
Loaded driver \SystemRoot\system32\drivers\usbccgp.sys
Loaded driver \SystemRoot\system32\drivers\mouhid.sys
Loaded driver \SystemRoot\system32\drivers\kbdhid.sys
Loaded driver Fastfat.SYS
Loaded driver \SystemRoot\System32\Drivers\Cdfs.SYS
And this is from the one where USB doesn't work. Same HDD has
been swapped to the second machine.
Service Pack 2 3 30 2006 04:37:19.500
Loaded driver \XPE\system32\ntoskrnl.exe
Loaded driver \XPE\system32\hal.dll
Loaded driver \XPE\system32\KDCOM.DLL
Loaded driver \XPE\system32\BOOTVID.dll
Loaded driver ACPI.sys
Loaded driver \XPE\system32\drivers\WMILIB.SYS
Loaded driver pci.sys
Loaded driver eltorito.sys
Loaded driver isapnp.sys
Loaded driver MountMgr.sys
Loaded driver ftdisk.sys
Loaded driver pciide.sys
Loaded driver \XPE\system32\drivers\PCIIDEX.SYS
Loaded driver PartMgr.sys
Loaded driver ACPIEC.sys
Loaded driver \XPE\system32\drivers\OPRGHDLR.SYS
Loaded driver EWF.sys
Loaded driver intelide.sys
Loaded driver atapi.sys
Loaded driver cdrom.sys
Loaded driver \XPE\system32\drivers\CLASSPNP.SYS
Loaded driver Fastfat.sys
Loaded driver KSecDD.sys
Loaded driver redbook.sys
Loaded driver \XPE\system32\drivers\ks.sys
Loaded driver imapi.sys
Loaded driver disk.sys
Loaded driver \SystemRoot\system32\drivers\processr.sys
Loaded driver \SystemRoot\system32\drivers\serial.sys
Loaded driver \SystemRoot\system32\drivers\serenum.sys
Loaded driver \SystemRoot\system32\drivers\swenum.sys
Loaded driver \SystemRoot\system32\drivers\update.sys
Loaded driver \SystemRoot\System32\Drivers\Fs_Rec.SYS
Did not load driver \SystemRoot\system32\drivers\kbdhid.sys
Did not load driver \SystemRoot\system32\drivers\i8042prt.sys
Loaded driver \SystemRoot\System32\DRIVERS\mouclass.sys
Loaded driver \SystemRoot\system32\drivers\kbdclass.sys
Loaded driver \SystemRoot\System32\drivers\vga.sys
Loaded driver \SystemRoot\System32\Drivers\Npfs.SYS
Loaded driver Fastfat.SYS
Loaded driver \SystemRoot\System32\Drivers\Cdfs.SYS
dfer...@gmail.com
If USB is the only device that doesn't work on your 2nd config, try
adding the USB chipset drivers from the 2nd config to your 1st config,
along with PnP User and Kernel mode components. Run through FBA on the
1st config, then try it on your 2nd config. (You should be able to
figure out which components you need by comparing the results of your
TAP components from both configs, or by examining the SETUPAPI.LOG 0
this will show a "driver not found" for the USB chipset device that was
not found.) PnP should then properly detect & install the USB host.
There is a fairly advanced procedure to develop a RAMdisk-based
bootable CD which can run on pretty "generic" hardware. I have used
this technique very effectively. However, it's pretty complicated;
basically, you build an image with all the necessary drivers (for all
h/w configs), run it through FBA, then tweak some registry and files,
then build it as a RAMdisk boot CD.
Here are some links within this group:
http://groups.google.com/group/microsoft.public.windowsxp.embedded/msg/8fdc73848691feed
http://groups.google.com/group/microsoft.public.windowsxp.embedded/msg/6516b12f1b853974
-- Don
Adora Belle Dearheart
and after a certain amount of messing about I've been asked to get a USB
touchscreen working. I've found that putting it through FBA on one and
then puttting the disk into the other unit will result in a working
image, but I have to wait a couple of minutes for the OS to identify
everything needed.
If yours doesn't do that, email me your build log and I'll compare it to
my own and see if I can work out what the difference is.
--
Adora Belle Dearheart
http://pics.livejournal.com/random_c/pic/00001x48
See, not a Sir.
Mike Warren
Thanks for the reply. This is frustrating. I've spent a whole day on this
now (mostly reading groups.google) trying to find some clues. I just
don't have enough knowledge of how this stuff works to make educated
guesses.
> I have an image that needs to work on an intel machine and a via one,
> and after a certain amount of messing about I've been asked to get a
> USB touchscreen working. I've found that putting it through FBA on
> one and then puttting the disk into the other unit will result in a
> working image, but I have to wait a couple of minutes for the OS to
> identify everything needed.
That's what I thought would work too. There are no special hardware
components in the system except "Intel(R) 82092AA PCI IDE Controller"
(with disabled PnP resource). This is required to stop my first hardware
from getting a BSOD on second boot.
I am hoping it may be possible to force PnP on each boot by removing or
changing some registry settings. This is not a very complicated build
and I have looked through the system hive trying to find clues.
> If yours doesn't do that, email me your build log and I'll compare it
> to my own and see if I can work out what the difference is.
The build log is here: http://web.aanet.com.au/miwa/2330CDBoot.log
-Mike
Mike Warren
Thanks for replying,
> You should be able
> to figure out which components you need by comparing the results of
> your TAP components from both configs, or by examining the
> SETUPAPI.LOG 0 this will show a "driver not found" for the USB
> chipset device that was not found.) PnP should then properly detect
> & install the USB host.
The same image works fine on both hardware as long as i perform FBA
on that particular device. Apart from the one Intel component I mentioned
in my reply to Heidi, all the components are generic. I have deliberately
not used TAP.
> There is a fairly advanced procedure to develop a RAMdisk-based
> bootable CD which can run on pretty "generic" hardware.
> Here are some links within this group:
>
> http://groups.google.com/group/microsoft.public.windowsxp.embedded/msg/8fdc73848691feed
> http://groups.google.com/group/microsoft.public.windowsxp.embedded/msg/6516b12f1b853974
Thanks. These messages did not come up on my searches yesterday.
I'll see if I can get any clues from them.
-Mike
Adora Belle Dearheart
> Hi Heidi,
>
Strange... personally I found that with the generic IDE component, if I
put my image through FBA on the Intel hardware it worked on both (or
rather, all three, one of which I am no longer required to support), but
if I put it through FBA on the Via board, it would bluescreen on
everything. Have you tried not using EWF for a while, to see if that
helps get things working?
I would be interested to know if my image boots OK on your hardware and
for that matter what yours does on mine. Perhaps we should swap .slx
files if you're still having trouble?
Mike Warren
> Have you tried not using EWF for a while, to see if that
> helps get things working?
No. I will do that now.
> I would be interested to know if my image boots OK on your hardware
> and for that matter what yours does on mine. Perhaps we should swap
> .slx files if you're still having trouble?
Am I ever still having trouble. I would love to try your slx.
Here's mine
http://web.aanet.com.au/miwa/2330CDBoot.zip
If only Sobodan or Konstantin were still around here.
I'm getting desperate enough to start looking at WinPE but
I really don't like how it works.
-Mike
Mike Warren
http://web.aanet.com.au/miwa/MiwaShell.zip
On this build, all it does is open a command window
(or Explorer if it is included in the build).
-Mike
Adora Belle Dearheart
Mike Warren
> I would be interested to know if my image boots OK on your hardware
> and for that matter what yours does on mine.
I have downloaded and installed the latest updates to get your image
to build. I don't have the "VIA Rhine II Fast Ethernet Adapter" or
"Realtek RTL8139/810x Family Fast Ethernet NIC" but it shouldn't
matter so I disabled them.
I ran FBA on the first machine and if worked fine until the second boot.
It gave a BSOD. I'm familiar with this problem as about a year ago
Sobodan advised me to add "Intel(R) 8092AA PCI IDE Controller"
and disable the PnP resource to solve the BSOD. I don't understand
why he suggested that or why it cured the problem.
I then moved the HDD to the second machine and it booted fine but
the USB keyboard did not work. I let it sit for 10 minutes to see if the
keyboard would start but no luck.
So, your image appears to behave the same for me.
I then rebuilt the image after adding the Intel component above and
ran FBA on the second machine. This resulted in the drive being
able to boot on both machines but USB keyboard did not work on
either one. I then added "Generic USB Input Device Support" but
that only got USB working on one machine.
The 2 platforms are AOpen motherboard with i865 chipset
and Gigabyte motherboard with nVidia nForce 410 chipset
The only functionality I need is serial port, USB keyboard and
mouse, basic VGA display and HDD/CD access to recover
my image.
There has to be something missing from XPe PnP to cause this
problem. I'll try Konstantin's XP Pro Emulation next and see what
that does.
-Mike
Adora Belle Dearheart
of my ears today[1], I'm afraid and I sent you the wrong thing. You
presumably don't need all the networking stuff so you can strip all that
out which should make the image a good bit smaller.
[1] Was up at 5 as I've started going to the gym before work, gave up
smoking last week so am both really missing the breaks and absolutely
desperate for a smoke, and I'm trying to wrap my head around every
aspect of PXE in the half an hour before the meeting nobody told me
about until after lunch.
Mike Warren
> I will email you the image the USB works on.
Thanks. I have received it and will try it shortly.
> My brain is dribbling out of my ears today
Yuk. Must make an awful mess of your clothes.
> [1] Was up at 5 as I've started going to the gym before work, gave up
> smoking last week so am both really missing the breaks and absolutely
> desperate for a smoke, and I'm trying to wrap my head around every
> aspect of PXE in the half an hour before the meeting nobody told me
> about until after lunch.
It's nearly 1am here. Looks like I might not be getting to bed until 5am :-)
been on this since 7am and all day yesterday. :-(
-Mike
Mike Warren
I'm nearly there. I had not included USB User Interface. The clue was
when I added device manager and tried to reinstall the USB drivers.
Windows asked to usbui.dll. I need to gain more knowledge. :-(
I burnt the image to a CD and everything seems to work ok as long
as I have a partitioned HDD connected. If not, I get:
STOP: c000021a {Fatal System Error}
The Windows Logon Process system process terminated unexpectedly
with a status of 0x00000000 (0x00000000 0x00000000)
The system has been shut down.
It's now after 3am and I need to get some sleep. I'll search for that
error on Google in the morning.
Does anyone have any clues for me?
-Mike
Mike Warren
> STOP: c000021a {Fatal System Error}
That error was fixed by deleting everything in "Mounted Devices"
registry key just before creating the final iso.
I'm finally done with this CD :-)
Thanks for your help Heidi and Don.
-Mike
--
Mike Warren
My web photo gallery: http://web.aanet.com.au/miwa/mike