usb keyboard & mouse hung

[Guest]

Hey,

We like to have one El-Torito CD to support 2 PC motherboards - one from
Intel and usb chipset is 82801EB . the other from Fujitsu and chipset is
82801GB).

If I create the boot CD from Intel motherboard PC, the USB keyboard and
mouse work just fine after booting from a final El-Torito CD. If I stick the
same CD in Fujitsu motherboard PC, I have no USB mouse and keyboard but if I
plug in PS/2 keyboard and mouse, it works. With same windows embedded image
but doing FBA on Fujitsu PC, I got USB mouse and keyboard working on Fujitsu
but not Intel PC. Note: I already applied hotfix 822603 and I believe all the
usb drivers should be up to date. FBA processes were normally completed.

I compared FBA logs and PnP PCI devices sections do reflect individual
chipsets, so how to make it works? It seems FBA process build in some sort
personality into El-Torito CD and break thing one way the other?

Please help! Thanks!

Hank
Grass Valley

 

[Adora Belle Dearheart]

Hey,

We like to have one El-Torito CD to support 2 PC motherboards - one from
Intel and usb chipset is 82801EB . the other from Fujitsu and chipset is
82801GB).

If I create the boot CD from Intel motherboard PC, the USB keyboard and
mouse work just fine after booting from a final El-Torito CD. If I stick the
same CD in Fujitsu motherboard PC, I have no USB mouse and keyboard but if I
plug in PS/2 keyboard and mouse, it works. With same windows embedded image
but doing FBA on Fujitsu PC, I got USB mouse and keyboard working on Fujitsu
but not Intel PC. Note: I already applied hotfix 822603 and I believe all the
usb drivers should be up to date. FBA processes were normally completed.

I compared FBA logs and PnP PCI devices sections do reflect individual
chipsets, so how to make it works? It seems FBA process build in some sort
personality into El-Torito CD and break thing one way the other?

Please help! Thanks!

Hank
Grass Valley

I assume you were doing FBA on a hard drive then creating the CD? Did
you put the hard drive in both types of hardware before you created the CD?

 

[Guest]

Thansk for quick response...

Yes. I used HD to do FBA. Here is what I did,
.. Hook IDE HD to one of the target units and detach original HD
.. Boot from bootable CD
.. Network connect to development PC
.. XCopy "Windows Embedded Image" files into FAT drive
.. Generate iso and pre CD
.. Disable boot from CD drive, and do the FBA
.. After FBA done, enable boot from CD, then boot from bootable CD
.. Generate iso and final El-Torito CD

Then I tried to boot from both units. PS/2 mouse and kb works on both units.
USB works on the unit I did FBA.

Your answer is quite interesting.
"Did you put the hard drive in both types of hardware before you created the
CD?"
No, I didn't. How to do this? Can you detail the steps if possible. Thanks
again.

 

[Adora Belle Dearheart]

Thansk for quick response...

Yes. I used HD to do FBA. Here is what I did,
. Hook IDE HD to one of the target units and detach original HD
. Boot from bootable CD
. Network connect to development PC
. XCopy "Windows Embedded Image" files into FAT drive
. Generate iso and pre CD
. Disable boot from CD drive, and do the FBA
. After FBA done, enable boot from CD, then boot from bootable CD
. Generate iso and final El-Torito CD

Then I tried to boot from both units. PS/2 mouse and kb works on both units.
USB works on the unit I did FBA.

Your answer is quite interesting.
"Did you put the hard drive in both types of hardware before you created the
CD?"
No, I didn't. How to do this? Can you detail the steps if possible. Thanks
again.

It doesn't have to go through FBA on both types of hardware - just be
booted in both before you make the ISO.

 

[Guest]

I tried the following and it doesn't work - behave exactly the same. Can you
tell me which step(s) is wrong? Thanks!

.. FBA on one hardware unit
.. do etprep -all on it
.. shutdown after reboot due to etprep process
.. remove HD and move to other other hardware unit
.. put pre-cd in and make sure boot from HD and not from CD drive
.. boot to shell, shutdown
.. change BIOS setting to boot from CD 1st and stick in bootable CD
.. From shell do hd2iso and create iso file
.. copy out iso file through network
.. create final ET-CD