OT: Is there any EASY way to set up a PCI NIC in MS-DOS?
- Thread starter Sukhoi
- Start date
I think I do...can you look at the file names I have listed in my other post and see if they look like what DOS driver file names would be? 
The Linksys manual lists nothing about DOS at all, so that's why I'm not sure which file is the DOS driver.
Here's what I said in my other post:
<< I'm currently using two LNE100TX version 4 PCI NICs to connect my P133 running Win95A and my C433 running Win98SE. I have TCP/IP, IPX/SPX, and NetBEUI, along with file and printer sharing installed in Windows on both computers.
I would like to use Drive Image 4.0 to make an image file of my P133, and store it on the hard drive of my C433. All of the needed hard drives are shared.
Drive Image will only run in DOS mode. Thus, I need a way to load the NIC drivers for the P133 on a boot floppy. The driver disk Linksys sent with the NICs has a folder on it called mslanman.dos, which I assume is the folder for the DOS drivers. Inside that folder are two other folders, called Fast, and Nif.
In the Fast folder are two files: LNE100.dos and Protocol.ini.
In the Nif folder is one file, which has the name LNE100.nif
Assuming these are the DOS drivers for the NICs, how do I put them on the boot disk so I can send the drive image from my P133 in MS-DOS mode, to my C433 running Win98SE. If needed, I can also run the C433 in MS-DOS mode while doing the image file. Thanks! >>
The Linksys manual lists nothing about DOS at all, so that's why I'm not sure which file is the DOS driver.Here's what I said in my other post:
<< I'm currently using two LNE100TX version 4 PCI NICs to connect my P133 running Win95A and my C433 running Win98SE. I have TCP/IP, IPX/SPX, and NetBEUI, along with file and printer sharing installed in Windows on both computers.
I would like to use Drive Image 4.0 to make an image file of my P133, and store it on the hard drive of my C433. All of the needed hard drives are shared.
Drive Image will only run in DOS mode. Thus, I need a way to load the NIC drivers for the P133 on a boot floppy. The driver disk Linksys sent with the NICs has a folder on it called mslanman.dos, which I assume is the folder for the DOS drivers. Inside that folder are two other folders, called Fast, and Nif.
In the Fast folder are two files: LNE100.dos and Protocol.ini.
In the Nif folder is one file, which has the name LNE100.nif
Assuming these are the DOS drivers for the NICs, how do I put them on the boot disk so I can send the drive image from my P133 in MS-DOS mode, to my C433 running Win98SE. If needed, I can also run the C433 in MS-DOS mode while doing the image file. Thanks! >>
Sukhoi - since no one answered you over on the other post, I'll do so here.
I haven't done what you're talking about in awhile but we used to do that all the time, ie., create a boot disk with the network drivers so that the machine could attach to a network drive and pull over the image.
Some of the files you mention need to go into the config.sys file. We used to use Etherlink cards so we would put an etherlink.dos (you can substitute the LNE100.dos) and a pktdrv.dos (I think you can substitute the mslanman.dos) and a protman.dos (doesn't sound like you have that one) into the config.sys.
Also make sure that your "protocol.int" (ours was protocol.ini) is on the floppy. You may also need something else in your autoexec.bat to actually allow you to make the connection to the shared drive - I recall when getting to windud, using a "net use" command in there somewhere, so I think a "net" executable needs to be there.
If you have a CD burner (and also your 133 has a CDROM), it might be easier to burn the image and run Drive Image from a floppy and point to the image on the CD. That's what we're currently doing at work.
I haven't done what you're talking about in awhile but we used to do that all the time, ie., create a boot disk with the network drivers so that the machine could attach to a network drive and pull over the image.
Some of the files you mention need to go into the config.sys file. We used to use Etherlink cards so we would put an etherlink.dos (you can substitute the LNE100.dos) and a pktdrv.dos (I think you can substitute the mslanman.dos) and a protman.dos (doesn't sound like you have that one) into the config.sys.
Also make sure that your "protocol.int" (ours was protocol.ini) is on the floppy. You may also need something else in your autoexec.bat to actually allow you to make the connection to the shared drive - I recall when getting to windud, using a "net use" command in there somewhere, so I think a "net" executable needs to be there.
If you have a CD burner (and also your 133 has a CDROM), it might be easier to burn the image and run Drive Image from a floppy and point to the image on the CD. That's what we're currently doing at work.
Poof, thanks for the help.
I think you misunderstood part of my earlier post. I don't have a file named mslanman.dos. It's a folder that has that name.
That is a good idea about using the CD to restore images, but currently I'm just trying to make an image of the P133, and store the image on my C433.
I was looking around the Linksys driver floppy some more, and I might of found some useful stuff. There's a folder on the floppy called Ndis that seems to have a lot of DOS networking type stuff in it.
In the Ndis folder are a bunch of text files that seem to say how to use the NIC with different types of DOS networking software and such.
Within the Ndis folder is another folder, amazingly called Dos, that has the following files in it:
Lne100.dos, Lne100.nif, Oemsetup.inf, and Protocol.ini
Also in the Ndis folder is a file called Ndis.txt that seems to say how to try to use the Ndis drivers. I'll put the text from this file at the end of this message.
I was looking through the floppy more, and I found a folder called Pktdrv. The files in that folder are called Lne100tx.com, and Readme.txt. I'll also put the text from the Readme.txt file at the end of this message.
Do you know what actual commands I'd have to put in Config.sys? I'd be surprised if I just put in
Lne100.dos
alone without any commands or anything like that, but I'm not sure.
You can DL the drivers for the LNE100TX from ftp://ftp.linksys.com/pub/network/lne100txv42.exe if you want to actually look at all the files I'm talking about.
Here's the text from Ndis.txt:
<< *****************************************************************************
Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
NDIS 2 Driver Installation
~~~~~~~~~~~~~~~~~~~~~~~~~~
Copyright (C) 2000 Linksys
All rights reserved.
*****************************************************************************
The drivers you need are in the directories MSLANMAN.DOS, MSLANMAN.OS2 and
NDIS. The NDIS drivers contained in these subdirectories are used with 3Com
3+Open, Microsoft OS/2 LAN Manager OEM distribution, Release 1.x or 2.x,
and other compatible OEM versions of LAN Manager. The driver can also used
with IBM LAN Server 3.0, 4.0, Banyan VINES, ARTISOFT LANtastic 5.0, 6.0,
Wollongong Pathway Access, Microsoft Windows for Workgroups v3.11,
DEC PATHWORKS, Sun PC-NFS etc.
The drivers named LNE100 conform to the Network Driver Interface Specification
(NDIS) defined by Microsoft/3Com.
Included in MSLANMAN.DOS, and NDIS subdirectories are the following files:
\MSLANMAN.DOS\DRIVERS\Fast\LNE100\
LNE100.DOS The DOS NDIS MAC driver
PROTOCOL.INI A sample section of PROTOCOL.INI file
\MSLANMAN.DOS\DRIVERS\NIF\
LNE100.NIF Network Information File
\MSLANMAN.OS2\DRIVERS\Fast\LNE100\
LNE100.OS2 The OS2 NDIS MAC driver
PROTOCOL.INI A sample section of PROTOCOL.INI file
\MSLANMAN.OS2\DRIVERS\NIF\
LNE100.NIF Network Information File
\NDIS\
NDIS.TXT This readme file
WFW311.TXT The Installation guide for Windows for
Workgroups v3.11
LANMAN.TXT The Installation guide for LAN Manager
LANSVR.TXT The Installation guide for Lan Server
BANYAN.TXT The Installation guide for Banyan VINES
LANTASTI.TXT The Installation guide for ARTISOFT
LANtastic 5.0, 6.0
PATHWORK.TXT The Installation guide for DEC PATHWORKS
PCNFS.TXT The Installation guide for Sun PC-NFS
\NDIS\DOS\
LNE100.NIF Network Information File for IBM Lan Support
Program
LNE100.DOS The DOS NDIS 2 driver
OEMSETUP.INF Network Information File for Windows for
Workgroups v3.11
PROTOCOL.INI A sample section of PROTOCOL.INI file
\NDIS\OS2\
LNE100.NIF Network Information File for IBM LAN Server
3.0, 4.0
LNE100.OS2 The OS2 NDIS 2 driver
PROTOCOL.INI A sample section of PROTOCOL.INI file
Sample PROTOCOL.INI Files and Parameters
----------------------------------------
[LNE100_NIF]
DriverName = LNE100$
; Slot = 1 ;; {1-4}
; SIA_Mode = AUTODETECT
; {SIA_Mode = UTP, UTP_FD,UTP_100,UTP_100FD, AUTODETECT}
There are several parameters included in the LNE100_NIF section of the
PROTOCOL.INI file. However, the only parameter that you should specify
is the "drivername."
If you change other parameter settings, such as the SIA_MODE, make sure
that it matches the hardware setting. Otherwise, the adapter may fail.
If you don't specify these settings, Linksys's NDIS 2
driver will automatically detect them.
SLOT Specifies which network adapter is used by the driver. If you have
only one Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
in your machine, this parameter is unnecessary! For two or more
Linksys's PCI LAN cards, this parameter
is required and cannot be omitted from PROTOCOL.INI. For the
first LNE100TX adapter, Slot=1, and the second one, Slot=2, third,
Slot=3,..., etc.
SIA_MODE Specifies the medium type used by the adapter.
Acceptable values for this parameter are AUTODETECT, UTP, UTP_FD
,UTP_100 and UTP_100FD. If you didn't specify this settings it
would be AUTODETECT for LNE100TX.
UTP: 10BaseT, UTP_100: Fast Ethernet (100BaseTx)
UTP_FD: 10BaseT with Full_Duplex
UTP_100FD: 100BaseTx with Full_Duplex
Default: AUTODETECT >>
Here's the text from Readme.txt:
<< *****************************************************************************
Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
Packet Driver Installation
~~~~~~~~~~~~~~~~~~~~~~~~~~
Copyright (C) 2000 Linksys
All rights reserved.
*****************************************************************************
I. The driver LNE100TX.COM can be used for the following:
Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
LNE100TX syntax:
LNE100TX [-#] [-a] [-t] [-f] [-s] [-n] [-w] [-u] [-h] <PD_INT_NO>
Parameter Explain
-----------------------------------------------------------------------------
[-#] The "-#" option will let the driver work on a specific adapter
when multiple Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
are found in the computer system. For example, "-1" means
the first adapter will be activated by the driver, "-2" means
the second adapter will be activated, ... etc.
Maximums of 4 adapters are supported simultaneously.
[-a] The "-a" option will let driver perform automatic media
detection during driver initialization. The detection
sequence is
TP 100Mbps Full Duplex ---> TP 10Mbps Full Duplex --->
TP 100Mbps Half Duplex ---> TP 10Mbps Half Duplex
If no physical media is attached to the adapter then TP
100Mbps Full Duplex is the default media.
[-t] The "-t" option is to use Twisted Pair (RJ-45) (10BASE-T) as
the transmission media. And it is also the default setting.
[-f] The "-f" option enables FULL_DUPLEX feature of the adapters.
It has no effect except when Twisted Pair is used.
[-s] The "-s" option sets the adapter line speed to 100Mbps. It is
a dedicated option for the Fast Ethernet adapter.
[-n] Your NOVELL server uses NOVELL ISO-like packets. Your NOVELL
workstation uses NOVELL 8137 packets. You can use this option
to convert NOVELL 8137 packets into NOVELL ISO-like packets.
[-w] Steve Wallace added a hack to let the packet drivers run under
Windows. This is not to be construed with the proper solution,
which is to write a TCP/IP package for Windows.
This hack is enabled only when you use the '-w' switch.
[-u] This option unloads the Packet Driver.
[-h] This option displays the on-line help.
<PD_INT_NO> This specifies the software interrupt (INT) where you'll load
the packet driver. It must be in the range 0x60 to 0x80.
-----------------------------------------------------------------------------
Notice!! The PC/TCP kernel, by default, is loaded at interrupt 0x61
(so don't load the packet driver there!)
Example:
The following command line loads the
Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
Packet Driver at software interrupt 60h, transmission media is
automatically-detected:
LNE100TX -a 0x60 or LNE100TX 0x60
** Note **
The default transmission media is automatic-detection.
The prefix of 0x to the parameters.
II. After the Packet Driver is loaded, you can run the PC/TCP kernel
ETHDRV.EXE. the PC is then ready for PC/TCP communications.
To run PC/TCP applications, You need to load PC/TCP Kernel ("ETHDRV.EXE".
a. Refer to PC/TCP manual, Command Reference section, Chapter 2.3.
b. The following example loads the PC/TCP Kernel and allocates 8 packet
buffers. Increasing the number of packet buffers (from the default of
5) prevents dropping of packets due to buffer shortage.
ETHDRV -p 8 <Enter>
c. At this point, you are ready to run PC/TCP applications
(e.g., 'ftp', 'telnet').
example ftp 192.72.24.202 , 192.72.24.202 is host address.
With regard to host address, you must know its address.
For information regarding the "FTP's PC/TCP Network Software for DOS"
packages, please contact:
FTP Software, Inc.
26 Princess Street
Wakefield, MA 01880
(617) 246-0900
III. How to Communicate with NCSA TelNet.
1. Make sure you have the correct version of NCSA Telnet for the PC.
You need version 2.3 or later to support the packet driver interface.
2. Install the NCSA software onto your system. Please refer to the NCSA
documentation for detailed instructions.
3. Load Packet Driver (LNE100TX 0x60):
a. Refer to "Packet Driver Syntax" section above.
b. To view the hint screen, type
LNE100TX -h <Enter>
c. The following example will load the packet driver using interrupt
vector 60 (hex). The IO_BASE and IRQ will be read from adapter
configuration space:
LNE100TX 0x60 <Enter>
4. At this point you are ready to run NCSA applications
(e.g., 'ftp', 'telnet', etc.)
for example :
ftp 203.70.238.105, while 203.70.238.105 is the host address.
For information regarding NCSA's products please contact:
National Center for Supercomputing Applications
264 Computing Applications Building
605 E. Springfield Ave.
Champaign, Ill. 61820
(217) 244-0638
telbug@ncsa.uiuc.edu >>
So, do you have any idea if I even have all the files I'd need to get this NIC running in DOS? If I do have all the files I need, do you have any idea of the lines I'd need to put in Config.sys and Autoexec.bat?
One last thing I thought of...if I can get the P133's NIC drivers loaded in MS-DOS mode, what OS should I have running on the C433 when I'm sending the image files to it? The C433 is also using an identical NIC, so I could also have it running in DOS if need be. Thanks!
P.S. Sorry the post was so long.
I think you misunderstood part of my earlier post. I don't have a file named mslanman.dos. It's a folder that has that name.
That is a good idea about using the CD to restore images, but currently I'm just trying to make an image of the P133, and store the image on my C433.
I was looking around the Linksys driver floppy some more, and I might of found some useful stuff. There's a folder on the floppy called Ndis that seems to have a lot of DOS networking type stuff in it.
In the Ndis folder are a bunch of text files that seem to say how to use the NIC with different types of DOS networking software and such.
Within the Ndis folder is another folder, amazingly called Dos, that has the following files in it:
Lne100.dos, Lne100.nif, Oemsetup.inf, and Protocol.ini
Also in the Ndis folder is a file called Ndis.txt that seems to say how to try to use the Ndis drivers. I'll put the text from this file at the end of this message.
I was looking through the floppy more, and I found a folder called Pktdrv. The files in that folder are called Lne100tx.com, and Readme.txt. I'll also put the text from the Readme.txt file at the end of this message.
Do you know what actual commands I'd have to put in Config.sys? I'd be surprised if I just put in
Lne100.dos
alone without any commands or anything like that, but I'm not sure.
You can DL the drivers for the LNE100TX from ftp://ftp.linksys.com/pub/network/lne100txv42.exe if you want to actually look at all the files I'm talking about.
Here's the text from Ndis.txt:
<< *****************************************************************************
Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
NDIS 2 Driver Installation
~~~~~~~~~~~~~~~~~~~~~~~~~~
Copyright (C) 2000 Linksys
All rights reserved.
*****************************************************************************
The drivers you need are in the directories MSLANMAN.DOS, MSLANMAN.OS2 and
NDIS. The NDIS drivers contained in these subdirectories are used with 3Com
3+Open, Microsoft OS/2 LAN Manager OEM distribution, Release 1.x or 2.x,
and other compatible OEM versions of LAN Manager. The driver can also used
with IBM LAN Server 3.0, 4.0, Banyan VINES, ARTISOFT LANtastic 5.0, 6.0,
Wollongong Pathway Access, Microsoft Windows for Workgroups v3.11,
DEC PATHWORKS, Sun PC-NFS etc.
The drivers named LNE100 conform to the Network Driver Interface Specification
(NDIS) defined by Microsoft/3Com.
Included in MSLANMAN.DOS, and NDIS subdirectories are the following files:
\MSLANMAN.DOS\DRIVERS\Fast\LNE100\
LNE100.DOS The DOS NDIS MAC driver
PROTOCOL.INI A sample section of PROTOCOL.INI file
\MSLANMAN.DOS\DRIVERS\NIF\
LNE100.NIF Network Information File
\MSLANMAN.OS2\DRIVERS\Fast\LNE100\
LNE100.OS2 The OS2 NDIS MAC driver
PROTOCOL.INI A sample section of PROTOCOL.INI file
\MSLANMAN.OS2\DRIVERS\NIF\
LNE100.NIF Network Information File
\NDIS\
NDIS.TXT This readme file
WFW311.TXT The Installation guide for Windows for
Workgroups v3.11
LANMAN.TXT The Installation guide for LAN Manager
LANSVR.TXT The Installation guide for Lan Server
BANYAN.TXT The Installation guide for Banyan VINES
LANTASTI.TXT The Installation guide for ARTISOFT
LANtastic 5.0, 6.0
PATHWORK.TXT The Installation guide for DEC PATHWORKS
PCNFS.TXT The Installation guide for Sun PC-NFS
\NDIS\DOS\
LNE100.NIF Network Information File for IBM Lan Support
Program
LNE100.DOS The DOS NDIS 2 driver
OEMSETUP.INF Network Information File for Windows for
Workgroups v3.11
PROTOCOL.INI A sample section of PROTOCOL.INI file
\NDIS\OS2\
LNE100.NIF Network Information File for IBM LAN Server
3.0, 4.0
LNE100.OS2 The OS2 NDIS 2 driver
PROTOCOL.INI A sample section of PROTOCOL.INI file
Sample PROTOCOL.INI Files and Parameters
----------------------------------------
[LNE100_NIF]
DriverName = LNE100$
; Slot = 1 ;; {1-4}
; SIA_Mode = AUTODETECT
; {SIA_Mode = UTP, UTP_FD,UTP_100,UTP_100FD, AUTODETECT}
There are several parameters included in the LNE100_NIF section of the
PROTOCOL.INI file. However, the only parameter that you should specify
is the "drivername."
If you change other parameter settings, such as the SIA_MODE, make sure
that it matches the hardware setting. Otherwise, the adapter may fail.
If you don't specify these settings, Linksys's NDIS 2
driver will automatically detect them.
SLOT Specifies which network adapter is used by the driver. If you have
only one Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
in your machine, this parameter is unnecessary! For two or more
Linksys's PCI LAN cards, this parameter
is required and cannot be omitted from PROTOCOL.INI. For the
first LNE100TX adapter, Slot=1, and the second one, Slot=2, third,
Slot=3,..., etc.
SIA_MODE Specifies the medium type used by the adapter.
Acceptable values for this parameter are AUTODETECT, UTP, UTP_FD
,UTP_100 and UTP_100FD. If you didn't specify this settings it
would be AUTODETECT for LNE100TX.
UTP: 10BaseT, UTP_100: Fast Ethernet (100BaseTx)
UTP_FD: 10BaseT with Full_Duplex
UTP_100FD: 100BaseTx with Full_Duplex
Default: AUTODETECT >>
Here's the text from Readme.txt:
<< *****************************************************************************
Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
Packet Driver Installation
~~~~~~~~~~~~~~~~~~~~~~~~~~
Copyright (C) 2000 Linksys
All rights reserved.
*****************************************************************************
I. The driver LNE100TX.COM can be used for the following:
Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
LNE100TX syntax:
LNE100TX [-#] [-a] [-t] [-f] [-s] [-n] [-w] [-u] [-h] <PD_INT_NO>
Parameter Explain
-----------------------------------------------------------------------------
[-#] The "-#" option will let the driver work on a specific adapter
when multiple Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
are found in the computer system. For example, "-1" means
the first adapter will be activated by the driver, "-2" means
the second adapter will be activated, ... etc.
Maximums of 4 adapters are supported simultaneously.
[-a] The "-a" option will let driver perform automatic media
detection during driver initialization. The detection
sequence is
TP 100Mbps Full Duplex ---> TP 10Mbps Full Duplex --->
TP 100Mbps Half Duplex ---> TP 10Mbps Half Duplex
If no physical media is attached to the adapter then TP
100Mbps Full Duplex is the default media.
[-t] The "-t" option is to use Twisted Pair (RJ-45) (10BASE-T) as
the transmission media. And it is also the default setting.
[-f] The "-f" option enables FULL_DUPLEX feature of the adapters.
It has no effect except when Twisted Pair is used.
[-s] The "-s" option sets the adapter line speed to 100Mbps. It is
a dedicated option for the Fast Ethernet adapter.
[-n] Your NOVELL server uses NOVELL ISO-like packets. Your NOVELL
workstation uses NOVELL 8137 packets. You can use this option
to convert NOVELL 8137 packets into NOVELL ISO-like packets.
[-w] Steve Wallace added a hack to let the packet drivers run under
Windows. This is not to be construed with the proper solution,
which is to write a TCP/IP package for Windows.
This hack is enabled only when you use the '-w' switch.
[-u] This option unloads the Packet Driver.
[-h] This option displays the on-line help.
<PD_INT_NO> This specifies the software interrupt (INT) where you'll load
the packet driver. It must be in the range 0x60 to 0x80.
-----------------------------------------------------------------------------
Notice!! The PC/TCP kernel, by default, is loaded at interrupt 0x61
(so don't load the packet driver there!)
Example:
The following command line loads the
Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
Packet Driver at software interrupt 60h, transmission media is
automatically-detected:
LNE100TX -a 0x60 or LNE100TX 0x60
** Note **
The default transmission media is automatic-detection.
The prefix of 0x to the parameters.
II. After the Packet Driver is loaded, you can run the PC/TCP kernel
ETHDRV.EXE. the PC is then ready for PC/TCP communications.
To run PC/TCP applications, You need to load PC/TCP Kernel ("ETHDRV.EXE"
.a. Refer to PC/TCP manual, Command Reference section, Chapter 2.3.
b. The following example loads the PC/TCP Kernel and allocates 8 packet
buffers. Increasing the number of packet buffers (from the default of
5) prevents dropping of packets due to buffer shortage.
ETHDRV -p 8 <Enter>
c. At this point, you are ready to run PC/TCP applications
(e.g., 'ftp', 'telnet').
example ftp 192.72.24.202 , 192.72.24.202 is host address.
With regard to host address, you must know its address.
For information regarding the "FTP's PC/TCP Network Software for DOS"
packages, please contact:
FTP Software, Inc.
26 Princess Street
Wakefield, MA 01880
(617) 246-0900
III. How to Communicate with NCSA TelNet.
1. Make sure you have the correct version of NCSA Telnet for the PC.
You need version 2.3 or later to support the packet driver interface.
2. Install the NCSA software onto your system. Please refer to the NCSA
documentation for detailed instructions.
3. Load Packet Driver (LNE100TX 0x60):
a. Refer to "Packet Driver Syntax" section above.
b. To view the hint screen, type
LNE100TX -h <Enter>
c. The following example will load the packet driver using interrupt
vector 60 (hex). The IO_BASE and IRQ will be read from adapter
configuration space:
LNE100TX 0x60 <Enter>
4. At this point you are ready to run NCSA applications
(e.g., 'ftp', 'telnet', etc.)
for example :
ftp 203.70.238.105, while 203.70.238.105 is the host address.
For information regarding NCSA's products please contact:
National Center for Supercomputing Applications
264 Computing Applications Building
605 E. Springfield Ave.
Champaign, Ill. 61820
(217) 244-0638
telbug@ncsa.uiuc.edu >>
So, do you have any idea if I even have all the files I'd need to get this NIC running in DOS? If I do have all the files I need, do you have any idea of the lines I'd need to put in Config.sys and Autoexec.bat?
One last thing I thought of...if I can get the P133's NIC drivers loaded in MS-DOS mode, what OS should I have running on the C433 when I'm sending the image files to it? The C433 is also using an identical NIC, so I could also have it running in DOS if need be. Thanks!
P.S. Sorry the post was so long.
Oh BTW, don't spend a ton of time trying to figure this out.
If I can't easily get the NIC working in DOS, I'll just use MS Backup to make a backup of the P133 onto the C433.
If I can't easily get the NIC working in DOS, I'll just use MS Backup to make a backup of the P133 onto the C433.
Download these two disks from ftp://ftp.microsoft.com/BusSys/Clients/MSCLIENT/
and then run the setup to create a network client in DOS.
You might have to edit the autoexec.bat/config.sys...I dont remember.
and then run the setup to create a network client in DOS.
You might have to edit the autoexec.bat/config.sys...I dont remember.
Extract the two disks to a folder. From there run the setup.exe.
Make sure you made a blank bootable dos disk.
Once you run the setup point it to the A: drive as the destination. You might have to choose something like "Network adapter not shown..." and have it point where your DOS network driver is stored. Play with the settings. It should not mess with your windows at all. It's good practice to a backup of your autoexec.bat and config.sys that is stored in C: drive anyway.
Make sure you made a blank bootable dos disk.
Once you run the setup point it to the A: drive as the destination. You might have to choose something like "Network adapter not shown..." and have it point where your DOS network driver is stored. Play with the settings. It should not mess with your windows at all. It's good practice to a backup of your autoexec.bat and config.sys that is stored in C: drive anyway.
RaySun2Be
Lifer
- Oct 10, 1999
- 16,565
- 6
- 71
Another way to do it is to go back to the PowerQuest site, and download the Drive Image Pro version. It has a diskette builder program that will build bootable diskettes with selected NIC drivers, and even map network drives.
I've used it to image and then broadcast image the work PCs. I had to fiddle with the NIC drivers some, and it allows you to load additional drivers if it doesn't have yours.
I think (I'm not at work, so I can't double check to be sure) but I believe that there is an option for building DOS Network diskettes without the Drive Image or Powerquest stuff.
Ray
I've used it to image and then broadcast image the work PCs. I had to fiddle with the NIC drivers some, and it allows you to load additional drivers if it doesn't have yours.
I think (I'm not at work, so I can't double check to be sure) but I believe that there is an option for building DOS Network diskettes without the Drive Image or Powerquest stuff.
Ray
Ray, are you using a server to create your client boot disks?
Sukhoi, my original post on this very subject was about 4 years ago in GH. I didn't get any help back then and I really think it was because nobody knew how to do it without a server involved. NT server will make a boot disk that connects to NT so you can do this.
I can tell up you up front the time it takes to figure out how to make this work far exceeds the time it would take to move the drive to be imaged into the box the image is to be stored (i.e. slave the drives).
Since back then, after searching for weeks for help on this and finding nothing, I decided I would try an idea I had using my external Zip drive.
With mine, I started the Zip drive with the boot disk and loaded MS Client for networks from the Zip drive. The problem comes in that you need more space than a floppy provides for the files required to get a peer to peer connection. The Zip gave plenty of room. I want to point out that although I made this work in a DOS to 95 peer to peer network, I have not been able to make it work in a DOS to 98 peer to peer network! Something is different in 98 and I just decided that it was easier to move the drive than go through the ton of hours required to figure it out! It took me long enough to figure it out with DOS and 95!
Since that time a technique using Drivespace on a floppy has been developed. You can check this one out here:
Find the peer to peer section on this page
I tried this too after I stumbled upon it hoping it would fix my DOS to 98 problem, I couldn't get it to work either. I thought it was funny as hell to compress a floppy using drivespace though!
Good luck, and unless you just want to know how to do that peer to peer networking, move the drive!
Sukhoi, my original post on this very subject was about 4 years ago in GH. I didn't get any help back then and I really think it was because nobody knew how to do it without a server involved. NT server will make a boot disk that connects to NT so you can do this.
I can tell up you up front the time it takes to figure out how to make this work far exceeds the time it would take to move the drive to be imaged into the box the image is to be stored (i.e. slave the drives).
Since back then, after searching for weeks for help on this and finding nothing, I decided I would try an idea I had using my external Zip drive.
With mine, I started the Zip drive with the boot disk and loaded MS Client for networks from the Zip drive. The problem comes in that you need more space than a floppy provides for the files required to get a peer to peer connection. The Zip gave plenty of room. I want to point out that although I made this work in a DOS to 95 peer to peer network, I have not been able to make it work in a DOS to 98 peer to peer network!
Something is different in 98 and I just decided that it was easier to move the drive than go through the ton of hours required to figure it out! It took me long enough to figure it out with DOS and 95!Since that time a technique using Drivespace on a floppy has been developed. You can check this one out here:
Find the peer to peer section on this page
I tried this too after I stumbled upon it hoping it would fix my DOS to 98 problem, I couldn't get it to work either. I thought it was funny as hell to compress a floppy using drivespace though!
Good luck, and unless you just want to know how to do that peer to peer networking, move the drive!
Sukhoi - as you can see from the rest of the posts, it can be a pain in the butt to do. I know the folks at work who I supervised had a doozy of a time, but once they got it, we tried to hang on to that version of DriveImage as long as we could (after that a new version came out and we had to go through it all over again when we switched networks, so we ended up going the CD burner route).
With the config.sys file, the files LNE100.dos, pktdrv.dos, etc., are the device drivers that would load via the config.sys, and as long as the path for them is specified or they're in the root of A:, then they'll load. But you now mention the LNE100.com. I recall 3COM having similar .com files (eg., 3c95x.com I think), and that might have been an alternative to loading the individual device drivers by having that .com run in the autoexec.bat instead.
As MWalkden has mentioned, it's been a long time and even then our office had been connecting to a non-windoze network to store/retrieve the images. Creating that net-based disk that Regulator mentioned will get the "net" command on there so you can login and/or map to the drive on the other PC. It works pretty good going to NT server but attaching to another 95/98 might be a problem.
The easiest ways other than the zip drive method mentioned (forgot about that) and moving the drive, is getting a CD burner. Then you'll forever have an image. Compaq does that with their "Quick Restore" CD where they use a specially licensed version of DriveImage and then add batch files so that it reformats the drive and restores the factory images to the machine.
Remember though, if you do decide that all of the above is a pain and choose to use M$'s backup program, make sure you backup your registry. Nothing worse than doing a complete system backup and later realize that you have to reinstall everything anyway because you don't have a copy of your registry!
With the config.sys file, the files LNE100.dos, pktdrv.dos, etc., are the device drivers that would load via the config.sys, and as long as the path for them is specified or they're in the root of A:, then they'll load. But you now mention the LNE100.com. I recall 3COM having similar .com files (eg., 3c95x.com I think), and that might have been an alternative to loading the individual device drivers by having that .com run in the autoexec.bat instead.
As MWalkden has mentioned, it's been a long time and even then our office had been connecting to a non-windoze network to store/retrieve the images. Creating that net-based disk that Regulator mentioned will get the "net" command on there so you can login and/or map to the drive on the other PC. It works pretty good going to NT server but attaching to another 95/98 might be a problem.
The easiest ways other than the zip drive method mentioned (forgot about that) and moving the drive, is getting a CD burner. Then you'll forever have an image. Compaq does that with their "Quick Restore" CD where they use a specially licensed version of DriveImage and then add batch files so that it reformats the drive and restores the factory images to the machine.
Remember though, if you do decide that all of the above is a pain and choose to use M$'s backup program, make sure you backup your registry. Nothing worse than doing a complete system backup and later realize that you have to reinstall everything anyway because you don't have a copy of your registry!
Wow, I never imagined DOS networking could be that hard.
Ray, I'm going to try downloading the Drive Image Pro demo now, and seeing if the boot disks it makes have network support.
Later on this week I'm also going to try messing around with some boot floppies and that lne100tx.com file, and seeing if I can get it to do anything. How would I test if it actually worked though? Should I just try to ping my main machine and see if i get a reply? Thanks for the help.
Oh, I do have a burner in my C433, but I'd rather not have to take it over to my P133 every time I want to backup that machine. I'll probably end up either bringing the HDD from the P133 over to this computer, or just using M$ Backup if I can't get Drive Image Pro's boot disks to give me network support.
Ray, I'm going to try downloading the Drive Image Pro demo now, and seeing if the boot disks it makes have network support.
Later on this week I'm also going to try messing around with some boot floppies and that lne100tx.com file, and seeing if I can get it to do anything. How would I test if it actually worked though? Should I just try to ping my main machine and see if i get a reply? Thanks for the help.
Oh, I do have a burner in my C433, but I'd rather not have to take it over to my P133 every time I want to backup that machine. I'll probably end up either bringing the HDD from the P133 over to this computer, or just using M$ Backup if I can't get Drive Image Pro's boot disks to give me network support.
<< How would I test if it actually worked though? Should I just try to ping my main machine and see if i get a reply? >>
If you want to try that, you'd need to make sure the ping executable is copied to your floppy....
And yes, doing dos networking was a pain. I remember first getting it setup on win 3.1 machines running DOS 5.0 or 6.22 and having to find a good TCP/IP stack program (we used Acadia). Win 3.11 at least had Windows for Workgroups and its Netbios stuff. Now when you create a network disk with 95 or 98, etc., it puts that stuff there... (hopefully
)
RaySun2Be
Lifer
- Oct 10, 1999
- 16,565
- 6
- 71
MWalkden,
I did not use a server to create the diskettes. Once I installed Drive Image Pro, it had a program that would create DOS Boot & Networking diskettes. I just rememebered that it asked me for the NT 4.0 Server CD during install though, so apparently it copies some of the NT files over for it to use to create the Dos diskettes. so that might be a problem.
I did not use a server to create the diskettes. Once I installed Drive Image Pro, it had a program that would create DOS Boot & Networking diskettes. I just rememebered that it asked me for the NT 4.0 Server CD during install though, so apparently it copies some of the NT files over for it to use to create the Dos diskettes. so that might be a problem.
<< I just rememebered that it asked me for the NT 4.0 Server CD during install though, so apparently it copies some of the NT files over for it to use to create the Dos diskettes. so that might be a problem. >>
Ah, dang. I'm glad I only got a few MB of the Drive Image Pro demo DLed yesterday.
I thought of another way to backup my P133 that should work just as well. Currently it has a 5.1 GB 5400 RPM HDD in it. I have an extra 1.6 GB 5200 RPM HDD though. I'm going to leave the 1.6 GB HDD in the P133's case, but have it unplugged. Then whenever I want to back it up I'll just have to plug in the 1.6 GB, and I can use Drive Image to image the 5.1 GB onto the 1.6 GB drive. There's only about 2 GB of stuff on the P133 anyway, so I won't have to worry about the drive image getting over 1.6 GB for a while.
dos networking
Sukhoi,
Try that link,
Its the old dos networking client. You can install it on the hard drive. If you use the two disk Msclient one mentioned earlier on a win98 or 95 machine it will lock up windows. If you use this one you can install it and it will allow access to the network from while shelled out of windows.
I did this with ghost. I just installed dos on the target drive. Then installed this dos client. Then you can map the drive. I beleive the command goes something like this c:\net use x: \machine name\share name. where x is the drive letter to assign. When you install it make sure you have all the machine name, drivers and stuff handy cuz it will ask for all that info and build up all the support files you need. Just be patient with it sometimes its not real clear about what its asking for. Also I couldn't find a dos driver either so I used the win311 driver and it worked. It works great and is worth the hour you might have to spend figuring it out.
Sukhoi,
Try that link,
Its the old dos networking client. You can install it on the hard drive. If you use the two disk Msclient one mentioned earlier on a win98 or 95 machine it will lock up windows. If you use this one you can install it and it will allow access to the network from while shelled out of windows.
I did this with ghost. I just installed dos on the target drive. Then installed this dos client. Then you can map the drive. I beleive the command goes something like this c:\net use x: \machine name\share name. where x is the drive letter to assign. When you install it make sure you have all the machine name, drivers and stuff handy cuz it will ask for all that info and build up all the support files you need. Just be patient with it sometimes its not real clear about what its asking for. Also I couldn't find a dos driver either so I used the win311 driver and it worked. It works great and is worth the hour you might have to spend figuring it out.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 24K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 20K
-
-
-
Facebook
Twitter