Dos Boot Disk - Intel Pro/100 Mobile Cardbus

[JeremyP55]

I need to make a boot disk to use the
Intel Pro/100 SR Combo mobile Adapter
(Pcode MBLA3456C3). I am using TCP/IP
to login to a NT domain. The card after
using many settings finally gets past
the driver lockup using:
CBcombo nocheck nocom memory=0d000.
The card indicates link and activity
but cannot get an IP from DHCP and cannot
see the network when given a static IP.
PC is a Dell Lattitude CPt, celron 600, 256M.
What should the files look like?
Autoexec.bat
Config.sys
protocol.ini
system.ini
Below are my files.

Thanks,
Jeremy

Autoexec.bat
A:\NET\net initialize
@ECHO OFF
PROMPT $p$g
PATH A:\NET;A:\DOS
SET TEMP=A:\DOS
A:\NET\netbind.com
A:\NET\umb.com
A:\NET\tcptsr.exe
A:\NET\tinyrfc.exe
A:\NET\nmtsr.exe
A:\NET\emsbfr.exe
A:\NET\net start

Config.sys
DEVICE=A:\DOS\HIMEM.SYS
DOS=HIGH
FILES=40
devicehigh=A:\NET\ifshlp.sys
LASTDRIVE=Z
device=a:\net\protman.dos /i:a:\net
device=a:\net\Cbcombo.exe nocheck nocom memory=D0000 irq=11 ioaddress=0x300 verbose
;device=a:\net\drivers.dos
device=a:\net\e100b.dos
device=a:\net\TCPDRV.DOS
device=a:\net\NEMM.DOS

Protocol.ini
[network.setup]
version=0x3110
netcard=E100B,1,E100B,1
transport=tcpip,TCPIP
lana0=E100B,1,tcpip

[TCPIP]
NBSessions=6
SubNetMask0=255 0 0 0
IPAddress0=0 0 0 0
DisableDHCP=0
DriverName=TCPIP$
BINDINGS=E100B
LANABASE=0

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

[E100B]

DRIVERNAME = E100B$

System.ini
[network]
sizworkbuf=1498
filesharing=no
printsharing=no
autologon=yes
computername=Boot
lanroot=a:\NET
username=User
workgroup=DOMAIN
reconnect=yes
dospophotkey=Y
lmlogon=Y
logondomain=DOMAIN
preferredredir=full
autostart=full
maxconnections=8

[network drivers]
netcard=Cbcombo.exe
transport=tcpdrv.dos,nemm.dos
devdir=a:\NET
LoadRMDrivers=yes

[386enh]
TimerCriticalSection=5000
UniqueDosPSP=TRUE
PSPIncrement=2

[Password Lists]
*Shares=a:\NET\Shares.PWL

[Intel(R) Internet Support(John C.)]

Hello Jeremy:

Thank you for the opportunity to assist you with your technical support
issue.

Rather than me take the time to debug your files, I have a set THAT I KNOW
WORKS. :)

You will need to keep your cbcombo string, however all else will work as I
show you below.

Autoexec.bat

path=a:\net
lh a:\net\cbcombo memory=e000
a:\net\net initialize
a:\net\netbind.com
a:\net\umb.com
a:\net\tcptsr.exe
a:\net\tinyrfc.exe
a:\net\nmtsr.exe
a:\net\emsbfr.exe
a:\net\net start
net use z: \\ORSCHUCK001\CLIENTS
echo Running Setup...
z:\msclient\netsetup\setup.exe /$

Config.sys

DEVICE=A:\NET\HIMEM.SYS
DEVICE=A:\NET\EMM386.EXE NOEMS x=e000-e400
DOS=HIGH,UMB
files=30
device=a:\net\ifshlp.sys
lastdrive=z

Protocol.ini

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

[ms$ee16]
drivername=e100b$
; IRQ=3
; IOADDRESS=0x310
; IOCHRDY=Late
; TRANSCEIVER=Thin Net (BNC/COAX)

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

[tcpip]
NBSessions=6
DefaultGateway0=
SubNetMask0=
IPAddress0=
DisableDHCP=0
DriverName=TCPIP$
BINDINGS=ms$ee16
LANABASE=0

System.ini

[network]
filesharing=no
printsharing=no
autologon=yes
computername=JAC-test4301
lanroot=A:\NET
username=jacooper
workgroup=orrd02
reconnect=no
dospophotkey=N
lmlogon=0
logondomain=mad1
preferredredir=full
autostart=full
maxconnections=8

[network drivers]
netcard=e100b.dos
transport=tcpdrv.dos,nemm.dos
devdir=A:\NET
LoadRMDrivers=yes

[Password Lists]
*Shares=a:\net\Share000.PWL
JACOOPER=A:\NET\JACOOPER.PWL

If the above does not work, then cbcombo.exe may not be allowing real and
compete access to your cardbus controller.

What happens if you do not use the "nocheck" parameter? You should NOT be
using the nocom parameter; your adapter does indeed have a modem installed.

It is important to us that we know if we are answering and solving your
technical support issues. Please let us know how you come out and what you
find.

--
====================
John C.
Intel(R) Internet Support

*Other names and brands may be claimed as the property of others.

For the very best in online technical support, please see:

http://support.intel.com/

====================

"JeremyP55" <jer...@michigancat.com> wrote in message
news:eea37...@WebX.9CDEEn2n...

[jmparkin]

This did fix he problem.
I do have to have the nocheck option enabled.
The PC locks up if it is not enabled.

Jeremy