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

 

Imapsync. IMAP migration

 

Migrating an IMAP account from one IMAP server to another [ 1 ] / Linux, command line: imapsync --host1 imap.this.com --user1 email@example.com --passfile1 /home/user/imap/passwordfile1 --ssl1 --host2 imap.another.com --user2 email@example.com --passfile2 /home/user/imap/passwordfile2 --ssl2 --skipsize --allowsizemismatch - There is a web site (example.com) and an email box (email@example.com) hosted at a web hosting company. The IMAP server: imap.this.com. The IMAP server supports SSL. - The example.com web site is to be transfered to another web hosting company. So is the email@example.com box with all its contents and keeping its folders structure. The IMAP server of another web hosting company: imap.another.com. The IMAP server supports SSL. 1. Set up an email box named email@example.com and a password to it on the server of the web hosting company the email@example.com mailbox is to be transfered to - from the previous web hosting company. 2. Create two text files in /home/user/imap/: passwordfile1 with the password for the mailbox on the first IMAP server and passwordfile2 with the password for the mailbox on the second IMAP server. 3. chmod 600 /home/user/imap/passwordfile1 4. chmod 600 /home/user/imap/passwordfile2 5. Install imapsync 6. Run imapsync Imapsync transfers a mailbox - keeping its folders structure - from imap.this.com to imap.another.com. SSL is used to enable encryption and passwords are saved to protected files (chmod 600). Migration between two email service boxes may happen to require to make use of more imapsync options [ 2 ]. Like transfering contents of one Gmail.com box to another demands to have "--port1" and "--port2" specified: imapsync --host1 imap.gmail.com --port1 993 --user1 email1@gmail.com --passfile1 /home/user/imap/passwordfile1 --ssl1 --host2 imap.gmail.com --port2 993 --user2 email2@gmail.com --passfile2 /home/user/imap/passwordfile2 --ssl2 --skipsize --allowsizemismatch [ 1 ] A simple and common case: contents of one email box are transfered to another, empty mailbox. But there can be more complicated ones like: Gmail to Google Apps Email Migration and Moving to Google Apps with imapsync. [ 2 ] For more command options: Migrate mail from one server to another with imapsync and imapsync(1) - Linux man page.

Web browsers for DOS

 

Arachne : Dillo : DOSLYNX : Lynx : Links : ELinks Web browsers for DOS may be looked at as existing roughly in two categories. Web browsers which can be installed without excessive efforts + work stably within their capability. And the rest of the web browsers of functionality more or less limited or problematic. The major web browsers for DOS include applications with GUI and text-based browsers. The graphical web browsers for DOS are several versions of Arachne - GPL version, Arachne Labs version, Ray Andrews version - and Dillo. As well as DR-WebSpyder based on Arachne and WebSpyder's variation - Lineo Embrowser. Text-based web browsers for DOS are a little bit more numerous: DOSLYNX, lynx, links, elinks. The graphical web browsers for DOS even if being prominent among DOS web browsers for their capabilities are definitely inferior in comparison with major web browsers for Windows, Linux or Mac OS X due to the restrictions of the DOS nature, small user and developer base, some other reasons.