network bootdisk woes
I have a Netgear FA311, & I'm trying to make a DOS bootdisk via the Ghost bootdisk wizard, & also manually. I have used both versions of the FA311 driver (1. 30 & 1. 80) in both methods. When using the Ghost wizard, I have used the default NDIS2 driver, & I have also created a new template using the WFW311 director ...
I have a Netgear FA311, & I'm trying to make a DOS bootdisk via the Ghost bootdisk wizard, & also manually. I have used both versions of the FA311 driver (1.30 & 1.80) in both methods.
When using the Ghost wizard, I have used the default NDIS2 driver, & I have also created a new template using the WFW311 directory driver as per the Netgear support page. I have also disabled PnP in the BIOS. Both of these drivers, from both versions, have returned the same error code under IBM NetBind 2.1: "Warning: Since the MAC driver doesn't support loopback, the NTSNX driver may be necessary. Bind or open adapter request to MAC driver failed: error 5707."
Furthermore, I have attempted to manually create a DOS network bootdisk using NetBEUI as my protocol. However, using both driver versions (1.30 & 1.80), the same error is returned: "IPX or NetBIOS must be running for net services to start." Does this mean that the FA311 NDIS2 driver isn't capable of passing the NetBEUI protocol?
Any help would be greatly appreciated.
When using the Ghost wizard, I have used the default NDIS2 driver, & I have also created a new template using the WFW311 directory driver as per the Netgear support page. I have also disabled PnP in the BIOS. Both of these drivers, from both versions, have returned the same error code under IBM NetBind 2.1: "Warning: Since the MAC driver doesn't support loopback, the NTSNX driver may be necessary. Bind or open adapter request to MAC driver failed: error 5707."
Furthermore, I have attempted to manually create a DOS network bootdisk using NetBEUI as my protocol. However, using both driver versions (1.30 & 1.80), the same error is returned: "IPX or NetBIOS must be running for net services to start." Does this mean that the FA311 NDIS2 driver isn't capable of passing the NetBEUI protocol?
Any help would be greatly appreciated.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
1. What version of Ghost ??
2. Have you tried using the company's drivers
ftp://downloads.netgear.com/files/netgear1/F31XV18.zip
3. I havent tried myself, yet what about PACKET drivers instead of NDIS.
LINKS you need
(Procedure for using Norton Ghost to create a boot disk using NDIS2 driver)
http://www.expressresponse.com/cgi-bin/p...amp;submit.y=16
(FA311/312 NDISDOS2 driver for Ghost (beta release))
http://www.expressresponse.com/cgi-bin/p...amp;submit.y=16
2. Have you tried using the company's drivers
ftp://downloads.netgear.com/files/netgear1/F31XV18.zip
3. I havent tried myself, yet what about PACKET drivers instead of NDIS.
LINKS you need
(Procedure for using Norton Ghost to create a boot disk using NDIS2 driver)
http://www.expressresponse.com/cgi-bin/p...amp;submit.y=16
(FA311/312 NDISDOS2 driver for Ghost (beta release))
http://www.expressresponse.com/cgi-bin/p...amp;submit.y=16
ok well what version of ghost. I use ghost 7.5 enterprise edition for work.
PCDOS or MSDOS being used.
**Hands you a 3com nic**
PCDOS or MSDOS being used.
**Hands you a 3com nic**
well, i just installed the newest version of ghost (was using 7.0, now have 7.5), which has an option to use MS DOS instead of IBM DOS to make the bootdisks. however, it requires the MS DOS network client files, & i don't have an NT server cd here.
i d/l'ed a zip of the m$ client files & put everything together, & made a bootdisk of it all, but the machine wouldn't boot. it just sat there @ the prompt for the boot order, churning away on the floppy drive. i think that the copy of the client files that i d/l'ed is either incomplete or corrupt. either way, i know it was the floppy, b/c i replaced the disk w/a disk made w/the IBM DOS from the 7.5 ghost, & got the same error msg..... (but it DID boot).
i d/l'ed a zip of the m$ client files & put everything together, & made a bootdisk of it all, but the machine wouldn't boot. it just sat there @ the prompt for the boot order, churning away on the floppy drive. i think that the copy of the client files that i d/l'ed is either incomplete or corrupt. either way, i know it was the floppy, b/c i replaced the disk w/a disk made w/the IBM DOS from the 7.5 ghost, & got the same error msg..... (but it DID boot).
How to create a Microsoft Client boot disk
http://service1.symantec.com/SUPPORT/ghost.nsf/pfdocs/1998081310484225?Open&dtype=corp
How to create a Microsoft Network Client Boot Disk using Windows NT 4 Server's Network Client Administrator
http://service1.symantec.com/SUPPORT/ghost.nsf/pfdocs/1999080407471425?Open&dtype=corp
How to troubleshoot problems with Microsoft Client boot disks
http://service1.symantec.com/SUPPORT/ghost.nsf/pfdocs/1998111212052525?Open&dtype=corp
Could also be a resource thing .... you try another PCI slot?
http://service1.symantec.com/SUPPORT/ghost.nsf/pfdocs/1998081310484225?Open&dtype=corp
How to create a Microsoft Network Client Boot Disk using Windows NT 4 Server's Network Client Administrator
http://service1.symantec.com/SUPPORT/ghost.nsf/pfdocs/1999080407471425?Open&dtype=corp
How to troubleshoot problems with Microsoft Client boot disks
http://service1.symantec.com/SUPPORT/ghost.nsf/pfdocs/1998111212052525?Open&dtype=corp
Could also be a resource thing .... you try another PCI slot?
