Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Symantec Ghost - IBM Netbind version 2.1 Hangs

Status
Not open for further replies.

achcommerce

IS-IT--Management
Dec 23, 2003
1
US
I am attempting to create a Ghost image of a workstation that contains a Netgear 311(a) PCI NIC. I have created the bootdisk using Symantec Ghost Enterprise v.7 and also with Norton Ghost 2003. I receive the same error with both boot disks:

Adapter for FA311$ driver was found successfully.
MS-DOS LAN Manager v2.1 Netbind
IBM Netbind Version 2.1
[hangs]

I am unable to get past this point. I have tried several different brands of diskettes to no avail.

As a side note, I have switched out the Netgear 311 for a 3Com 3C509 NIC with this particular NIC, I receive an error message of "Divide Overflow".

Neither of which am I able to find anything related to these errors on the internet.

Any recommendation would be highly appreciated.

 
Hi,

I had exactly thr same problem in early Dec 2003 and gave it awy as too hard.

Came back to it today and solved it, following a suggestion from NETGEAR.COM on the FA312. First get the latest driver version 1.04 I think. Then create a boot diskette with Ghost Wizard as normal.

Then rename \net\fa312.dos to \net\xyz.dos. Then edit CONFIG.sys line DEVICE=\net\fa312.dos to DEVICE=\net\xyz.dos.

The clue is the driver ie FA312 must not reside in a file of the same name ie in a file called FA312.DOS. Weird but it works.

Please advise me of how you get on.


Regards

Tery.Anstey@cdu.edu.au

 
I had the exact same problem with the exact same card... I disabled plug and play (PNP) in the bios and it fixed it!

straight from netgears website:

Question

Computer hangs at NETBIND when booted from DOS boot disk created from Ghost and the NDIS2 driver

Answer

Since the system is booted in DOS mode, which does not have the PNP feature, this setting should be set to "NO" in BIOS. This avoids the system leaving the task of assigning IRQs to the OS and thus causing possible conflicts in some systems.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top