Member Avatar for jimsn

I am trying to make an image of one computer on another using a Ghost boot disk. I cannot make it work with the LAN (presumably becaue of an unsupported NIC), so I bought a supported USB cable. Now, on one of the computers, the USB Ghost boot disk locks up during boot. If I go to config.sys and comment out "device = usb\ohci.exe", it boots but refuses to do peer to peer, as if there were no USB port. If I comment out the other line, " device = usb\uhci", it still locks up.

I also bought a new USB card and disabled the one on the motherboard, but it behaves the same way.

It works fine on the other computer.

Does anyone have any ideas how to make this work? Thanks.

Jim

  • 3 Contributors
  • 2 Replies
  • 247 Views
  • 5 Months Discussion Span
  • Latest Post Latest Post by tupelo20

Dani AI

Generated

Short diagnosis and context — the symptoms describes (one PC hanging while DOS USB drivers initialise, the other working) are a classic Ghost/boot-disk vs. DOS-USB-controller incompatibility: Ghost and the DOS USB driver set will try to take control of the USB host controller and some BIOS/controller combinations simply hang. Running Ghost with USB disabled (or excluding USB when building the boot disk) is a common workaround. (community.broadcom.com)

Practical troubleshooting steps to try next:

  • Toggle the motherboard BIOS USB/legacy-USB settings (legacy USB emulation/legacy support) before loading any DOS USB driver — BIOS-level emulation often changes whether DOS drivers can attach cleanly. (pmwiki.xaver.me)
  • If the machine boots once you remove the DOS USB drivers, try running Ghost with USB disabled using the Ghost switch ghost -nousb (that prevents Ghost from grabbing USB ports). If that gets Ghost running, the problem is the DOS USB stack rather than Ghost itself. (community.broadcom.com)
  • If USB access is required from DOS, rebuild the boot media with alternate DOS USB driver packs (DUSE / USBASPI / vendor driver + helper like GUEST.EXE) and test each — different driver sets work on different host controllers. (bootdisk.com)

About the USB→LAN/driver INF problem raised by and the GBW question from — Ghost’s boot-disk builder expects drivers laid out in the older NDIS/NDIS2DOS-style structure and will fail on some modern Windows-style INFs or nested folders; point GBW at the correct NDIS2DOS folder (or locate an actual DOS/packet driver for that NIC) or use a small, known-supported PCI NIC instead. If these fail, fall back to using an external USB disk or network imaging (or a newer WinPE-based Ghost recovery environment on modern Ghost builds). (community.broadcom.com)

Immediate suggested plan: toggle BIOS USB support, test boot with DOS USB drivers removed, try ghost -nousb, then if USB access is essential rebuild the disk with one of the DOS USB driver packs and make sure both ends use the same driver set. If P2P via USB still proves unreliable, use a supported NIC or an external USB drive as the transfer medium. (bootdisk.com)

Recommended Answers

All 2 Replies

Member Avatar for feigned

Unsupported NIC? You give it the driver, it configures the disk, you boot off of it, ghost, and go on about your day.

How did you configure the ghost disk in the first place?

Member Avatar for tupelo20

I got a similar problem only with a adm8511 usb to lan convertor,
when I try to create a template Packet or Ndis makes no difference Norton says the oemsetup.inf file is not in a recognised format I provided norton with the original disk wich contains: net8511.inf, net8511.CAT, ADM8511.sys, AN986n.inf, release.txt

Does anybody know how to work this problem
:sad:

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.