DOS/Windows 98 boot problem

[MasterPhil]

I am trying to create a DOS boot disk so I can run Ghost from a server but the batch file keeps crashing out with the error :-

Error 7361: IPX or NetBIOS must be running in order to load the network services.

Now I have looked around the internet at this problem and I was given a number of suggestions about not running net start in the autoexec.bat file and changing that to net start netbind at the start of the batch file and net logon at the end.

The rest of the setup runs as it should but keeps crashing out on the net start or net logon line.

One piece of info on the internet tells me that the nic adapter may not be binding properly but how can I check?

Any help appreciated as I have been trying to get this working for 2 days and it is driving me nuts!

Phil

 

[G0AOZ]

Here's what's in my DOS boot disk CONFIG.SYS file:-

device=a:\dos\himem.sys
dos=high,umb
rem device=a:\dos\emm386.exe noems
FILES=30
buffers=60
LASTDRIVE=Z
devicehigh=a:\net\ifshlp.sys


And in AUTOEXEC.BAT

@echo off
cls
path=a:\;a:\dos;a:\net
prompt $P$G
lh a:\net\net initialize
lh a:\net\nwlink
lh a:\net\net start
smartdrv
cd

I'm basically using NT's MS Client software to make this boot disk. Once connected to my remote server, I run Power Quest Drive Image.

Hope that helps...


ROGER.

 

[MasterPhil]

If only mate,
This is what my auto looks like:-

path=a:\net
set temp=a:\net
a:\net\net initialize
a:\net\net start netbind
a:\net\umb.com
a:\net\tcptsr.exe
rem a:\net\tinyrfc.exe
a:\net\nmtsr.exe
a:\net\emsbfr.exe
a:\net\net logon

and this is my protocol.ini:-


[network.setup]
version=0x3110
netcard=ms$elnk,1,MS$ELNK,1
transport=tcpip,TCPIP
lana0=ms$elnk,1,tcpip

[ms$elnk]
drivername=e100b$
; INTERRUPT=9
; IOADDRESS=0x300
; DMACHANNEL=none
; DMAMODE=burst
; MAXTRANSMITS=12
; MAXREQUESTS=8

[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP

[tcpip]
NBSessions=6
DefaultGateway0="10.205.40.200"
SubNetMask0="255.255.0.0"
IPAddress0="10.205.40.2"
DisableDHCP=1
DriverName=TCPIP$
BINDINGS=ms$elnk
LANABASE=0

 

[G0AOZ]

I see you're using the E100B driver... As I recall I had trouble trying to get an E100B network interface on a rack mount server to work until I changed driver which had been supplied on the motherboard utilities disk.


ROGER.

 

[MasterPhil]

hmmmmm, I have updated to Intel's latest driver (before which the nic wouldn't bind at all). I wonder if there is another driver somewhere to try. Will go back and look for the motherboard drivers.

Thanks for the suggestion.

 

[MasterPhil]

Sadly, even after changing the driver to the earlier version on the motherboard CD, I still have the same problem. Three different drivers, 1998, 2003 and 2004 and it is still not working!

 

[MasterPhil]

Amazing how you can get word blind! I just noticed that I had rem'd out the tinyrfc line whist I tried to find out the problem. Once I removed the rem, everything works.... ish.

Now I have a new problem but I am going to start a new thread on that one as it makes NO sense to me.

 

[KyoAD]

Hi,

Would it be also possible to do the above if i am using a PXE packet driver? There is no protocol.ini file that come together with it. Do i have to create a new one manually?

The tcp driver is not loading because i have not started netbind.