I want to copy an image from a network drive and I have the same problem. I have the latest drivers from 3Com which seem to load fine... I have a 3C905B-TX card. A network boot disk would be really really useful.

0

Okay, I have the original problem error 33 with a 3c905b-tx-m card. My question where do you change the configuration to use the new driver? I have edited protocol.ini and various other files to no avail. Thanks

0

I've got a 3com Etherlink 3 3c589D cc and the newest drivers from 3com's web site and I still get the same problem. any suggestions

0

I have exactly the same error : NETBIND ERROR 33. But only with Integrated AMD PCNET In HP Vectra VE5 PC. I have successfully build boot disks for XIRCOM, SMC8000 and 3C509B-TX. I think the problem went from the supported protocols of .DOS drivers. For me PCNTND.DOS. I'll try using NetBEUI. But what i want to know is the meaning of this ERROR 33. Any one know it ?

0

My problem is 'Error 8: There is no more memory available'. I am using a Compaq Netflx3 card. I don't get any binding errors. Any Suggestions, anyone.

0

ok guys/gals i have a 3com 905-tx and am getting the same problem but i can help some of you the new drivers need to be loaded in the protocol.ini your command will be change the line stating (netcard=tcm$el90x,1,tcm$el90x,1) the e190x is the name of your drive the .dos is not needed. "easy way out" rename you new drivers and over right the old drivers the drivers should be in the \net folder. if any of you can get a running boot disk for network i need one if i get one ill e-mail the files to you.

0

Hoi, Getting the same Error 33 running the NETBIND command on a INTEL 10/100+ Managment Adapter. I have tried editing all files I can find and I'm getting MAD... anyone have any ideas?

0

I've found that a lot of network boot disk problems come from incorrect settings in the .ini files. These are the ini file settings that I have used with success. Hope this helps: PROTOCOL.INI [network.setup] version=0x3110 netcard=ms$ibmfe,1,MS$IBMFE,1 transport=ms$tcpip,MS$TCPIP lana0=ms$ibmfe,1,ms$tcpip [TCPIP] NBSessions=6 DisableDHCP=0 DriverName=TCPIP$ BINDINGS=MS$IBMFE LANABASE=0 [protman] DriverName=PROTMAN$ PRIORITY=MS$NDISHLP [MS$IBMFE] DriverName=IBMFE$ ;INTERRUPT=11 ;IOADDRESS=0x240 SYSTEM.INI [network] sizworkbuf=1498 filesharing=no printsharing=no autologon=yes computername=bob lanroot=a:\NET username= workgroup=CHCH reconnect=yes dospophotkey=N lmlogon=0 logondomain=CHCH preferredredir=full autostart=full maxconnections=8 [network drivers] netcard=ibmfe.dos transport=tcpdrv.dos,nemm.dos devdir=a:\net LoadRMDrivers=yes [386enh] TimerCriticalSection=5000 UniqueDosPSP=TRUE PSPIncrement=2 [Password Lists] *Shares=a:\NET\Shares.PWL

0

Here's the answer. Obtain your NT server CD. Download the latest NDIS2 driver for DOS that complies with your Card. Browse from a dos-prompt to the directory #:\Clients\MsClients\disks\disk1 on the NT server CD. Run setup.exe and hit Enter. Specify the place were to put your bootfiles (don't choose a:, because it's more than 1 disk). Enter the username to logon with. Now you get the abillity to alter your network settings. Add the specific adapter you want by choose *Network adapter not shown on list below. This will ask you for the place of the OEM*.inf file. This is added to the latest adapter drivers (Disk2). Point it to a:\ (don't forget the \). Select your adapter from the list shown. (I selected not to optimize.) Default protocol is just IPX. Adding TCP/IP is no problem, but you need to alter the .ini files. Save your settings, and your disk will be created. If you install TCP/IP, you'll be asked for some additional drivers. These are located on the CD-Rom under #\.\Disk2. Remember to customize the .ini files. Also, to make the disk smaller, you can choose to delete several .exe files. If you use the disk to get to your ghost image on the network, feel free to delete all.exe files except: ADDNAME.exe EMSBFR.EXE; NET.EXE; NMTSR.EXE; NWLINK.EXE; ROTMAN.EXE; SOCKETS.EXE; TCPTSR.EXE; TINYRFC.EXE; Have fun

0

I am creating an network boot disk but would like to be able to detect what network card is in the machine. I am using a list of known cards but once I use netbind I cannot seem to unbind the card to test the next card. Anyone know how to unbind a nic? Thanks!!!

0