ITNinja

- Full duplex in DOS does not always work so well, problems may range from slow connections to failure to connect a tall. Make sure that you have the NICs set to half duplex to avoid these issues.
- If you are using an ISA network card, make sure the interrupt and IO Address are set correctly.
- NICs with large DOS drivers (75k or more) may cause issues in running software such as imaging tools after the network stack is loaded, they just take up too much memory.
- If your BIOS has a "plug and play" setting, be sure to disable it in the BIOS.

---

"Unable To Bind"
1. Make sure you are using Windows 95b or Windows 98 system files with memory management. Sometimes straight DOS may not provide enough memory to allow the card to bind.
If you still get "Unable to bind" errors after doing this try editing the CONFIG.SYS and removing the following line if it exists:
device=emm386.exe /noems
2. Make sure that you have the correct DOS driver. Try doing a step by step boot by hitting the F8 key as soon as the computer starts. If the driver is unable to find the Network Card then either the driver is incorrect or the card has gone bad.

---

One of the most common mistakes made when creating a Network Boot Disk for a TCP/IP connection is to use the default option for DHCP when the computer is on a home network. Often times a DHCP server is not available at home and therefore the client will be unable to obtain a proper IP address.
On some systems, when the computer's BIOS is set to Yes for the PnP OS (Plug and Play Operating System) option, DOS might be unable to access the network interface card (NIC). When DOS cannot access the NIC, the network driver will be unable to load. To resolve this problem, disable the PnP OS option in the computer's BIOS before booting to your floppy. After imaging is complete you may enable the PnP OS option again.