Kompx.com or Compmiscellanea.com

Network setup in DOS. Microsoft Network Client 3.0

Operating systems : MS-DOS 6.0+, FreeDOS 1.0+

In order to install Microsoft Network Client 3.0 and set up network in DOS, there have to be several programs at hand:

1. Microsoft Network Client 3.0 [ Download ]

2. NDIS 2.0 driver for Ethernet network card. For example: Realtek RTL8029AS [ Download ]. Drivers for other network cards may be found, for instance, on web sites of Ethernet cards manufacturers.

3. If it is not MS-DOS 6.0+ to be used, QEMM97 [ Download ]

Installing Microsoft Network Client 3.0 and setting up network in DOS, step by step:

1. Create a folder, for example C:\DRIVERS\. Put there: a NDIS 2.0 driver for Ethernet network card.

2. Prepare installation floppies of Microsoft Network Client 3.0:

DSK3-1.EXE -d A:

DSK3-2.EXE -d A:

3. Start setup.exe from the first floppy and begin Microsoft Network Client 3.0 installation.

Installation is starting. Press Enter to continue

[ Image ] : Microsoft Network Client 3.0 : installation : 1

Select folder for Microsoft Network Client 3.0 to be installed to. It may be any or the suggestion of the installer may be left as it is - in the case discussed it is left as it is. Enter

[ Image ] : Microsoft Network Client 3.0 : installation : 2

Microsoft Network Client 3.0 installer examining the system files

[ Image ] : Microsoft Network Client 3.0 : installation : 3

Select driver for Ethernet network card. If there is no right driver on the list, choose "*Network adapter not shown on list below ..." Enter

[ Image ] : Microsoft Network Client 3.0 : installation : 4

This dialogue appears if there was no right driver on the proposed list of Ethernet network card drivers and "*Network adapter not shown on list below ..." has been selected. Specify the path to the folder containing the appropriate driver for the Ethernet network card. In the case discussed it is C:\DRIVERS\, typing it in. Enter

[ Image ] : Microsoft Network Client 3.0 : installation : 5

Select driver from C:\DRIVERS\ folder specified in the previous step. In the case discussed it is RTL8029AS PCI Ethernet Adapter. Enter

[ Image ] : Microsoft Network Client 3.0 : installation : 6

Choose to let or not to let Microsoft Network Client 3.0 use more RAM in its work to get the best performance. Any of the two choices is acceptable. For example - let it to. Enter

[ Image ] : Microsoft Network Client 3.0 : installation : 7

Enter user name of up to 20 characters. It can contain Latin letters, numbers and characters listed. In the case discussed it is "net". Enter

[ Image ] : Microsoft Network Client 3.0 : installation : 8

Confirm the selected settings are correct to start copying the files to the folder Microsoft Network Client 3.0 is be installed in. It may be chosen here to change some or all settings and repeat some steps described above or to confirm the selected settings are correct. In the case discussed the selected settings are confirmed, so no changes made and just - Enter

[ Image ] : Microsoft Network Client 3.0 : installation : 9

Microsoft Network Client 3.0 files are being copied to the folder Microsoft Network Client 3.0 is to be installed in

[ Image ] : Microsoft Network Client 3.0 : installation : 10

Microsoft Network Client 3.0 is installed in C:\NET\ folder. In order to begin to use Microsoft Network Client 3.0, press Enter and computer will restart

[ Image ] : Microsoft Network Client 3.0 : installation : 11

4. After computer restart, Microsoft Network Client 3.0 will prompt for a name or to press Enter to proceed with the name selected during the installation process. In the case discussed it is "net", no new names are entered - Enter. Next, password prompt; since there is no password created, just press Enter. After that a password may be created or not. If not - just Enter.

5. Run MemMaker or OPTIMIZE from QEMM97 to optimize base memory management. If it is MemMaker then press Enter at any suggestion - MemMaker will handle it itself. Computer is going to restart several times, each time MemMaker will be re-running - again nothing, just Enter, is a safe choice. If it is QEMM97 (specifically OPTIMIZE), then there is going to be several restarts too and each time just pressing Enter is OK.

Network connection is up and ready. Each time after computer restart Microsoft Network Client will automatically re-establish network connection of the computer.


Aliosque subditos et thema


Renaming folders in DOS


Renaming a folder in DOS by MOVE command: MOVE FOLDER1 FOLDER2 - Renames FOLDER1 into FOLDER2 The method works in Windows command prompt as well. [ 1 ] MS-DOS 6.0+ tested - but it also may happen to work well under other versions of MS-DOS or other DOS'es.

Unzip multiple files. Linux


Unzip multiple zip files into one directory by Linux command line unzip. Contrary to possible expectations, "unzip *.zip" is not going to work, *.zip should be put into quotes: unzip "*.zip" There may be files with the same names in these archives. To avoid overwriting: unzip -B "*.zip" "Unzip -B" makes unzip to overwrite duplicates during extraction process, but saving a backup copy of each overwritten file. The names for these backup copy files are created by adding tilde ("~") at the end of the original names of the files. If a file extension is present, then "~" is added after it. If that is not enough, unique sequence number (up to 5 digits) is appended after the "~". "Unzip -B" is not too practical. For example, since when the sequence number range for numbered backup files gets exhausted (99999, or 65535 for 16-bit systems), the backup file with the maximum sequence number is deleted and replaced by the new backup version without notice ( More on the subject ). The number of files in an archive may not be always known in advance or may be more than possible sequence number range, so "Unzip -B" is not a great choice. Renaming duplicate files by adding "~" at the end of their names, after the extension, is not too convenient either. But another built-in option is even worse. If the "-B" modifier is not used, each time a file with same name as there already unpacked is being extracted, unzip asks "replace example.txt? [y]es, [n]o, [A]ll, [N]one, [r]ename:". And each time "r" must be hit, then a new name has to be input. So some bash or another script solving the problem should probably be prepared and used instead.