I do not know what network adapter is on the D510 motherboard ... so I cannot help with this part.
Can I assume that you have built a Ghost DOS boot disk before for some other system and gotten it to work?
On the surface, it appears that the driver is not finding the adapter which could be that you don't have the right driver; that is what the 1st error message is saying and it should be coming from the b44.dos module when it is loaded in Config.sys . The second error message is coming from netbind.com (invoked in Autoexec.bat) when it attempts to bind to your nic and the driver isn't there ... that 1st message directly lead to the 2nd.
If you just put the B44.DOS module on some other system's Ghost diskette and left the original network driver there and did not change Config.sys, then the original network driver would load and not find the adapter it supports ... the B44.DOS module would never run. Do you get a message indicating that the B44 Broadcom driver is running? Usually there is at least one message indicating the name of the adapter driver before it puts out the error message but some times these routines don't say much.
Are you familiar with the internal structure of the Ghost disk?
Did you build it by hand or did you let the Ghost Wizard do it?
From one of my Config.sys files on a DOS Ghost disk:
I have all my network modules and supporting files in A:\net\ . I cannot remember if the Ghost Wizard builds it this way or I just did it this way. Everything can be in the root if you do it correctly.
DCookies
20 Posts
0
November 14th, 2005 04:00
Can I assume that you have built a Ghost DOS boot disk before for some other system and gotten it to work?
On the surface, it appears that the driver is not finding the adapter which could be that you don't have the right driver; that is what the 1st error message is saying and it should be coming from the b44.dos module when it is loaded in Config.sys . The second error message is coming from netbind.com (invoked in Autoexec.bat) when it attempts to bind to your nic and the driver isn't there ... that 1st message directly lead to the 2nd.
If you just put the B44.DOS module on some other system's Ghost diskette and left the original network driver there and did not change Config.sys, then the original network driver would load and not find the adapter it supports ... the B44.DOS module would never run. Do you get a message indicating that the B44 Broadcom driver is running? Usually there is at least one message indicating the name of the adapter driver before it puts out the error message but some times these routines don't say much.
Are you familiar with the internal structure of the Ghost disk?
Did you build it by hand or did you let the Ghost Wizard do it?
From one of my Config.sys files on a DOS Ghost disk:
DEVICE=\net\protman.dos /I:\net
DEVICE=\net\dis_pkt.dos
DEVICE=\net\YUKND.dos
You would need to change YUKND.dos to B44.dos
I have all my network modules and supporting files in A:\net\ . I cannot remember if the Ghost Wizard builds it this way or I just did it this way. Everything can be in the root if you do it correctly.
The related Protocol.ini looks like:
[protman]
drivername=PROTMAN$
[pktdrv]
drivername=PKTDRV$
bindings=nic
intvec=0x60
chainvec=0x66
[nic]
drivername = YUKND$
You would need to change YUKND$ I think to B44$ .
Hope this helps.