Changes between Version 5 and Version 6 of Sharing_files_with_DOS
- Timestamp:
- Aug 31, 2011 11:31:03 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Sharing_files_with_DOS
v5 v6 3 3 == Overview == 4 4 5 Below you find tips on how to set up host/guest networking. The guest is a DOS 6.22 VM.6 My host system is a typical Win XP machine with a 1280 x 1024 display. I used !VirtualBox 1.4.0.5 Below you find tips on how to set up host/guest networking. The guest was a DOS 6.22 VM, but any DOS 5.0 or later version may be used. 6 My host system is a typical Windows machine. I used !VirtualBox 1.4.0. 7 7 8 8 == Prerequisites == 9 9 10 What do you need (apart from having a basic DOS 6.22VM):11 * MS Client for networks (two self-extracting files DSK3-1.EXE, DSK3-2.EXE)12 * wg1049.exe13 * netshar.exe14 * Microsoft KB 128800 - on how to add extra NDIS2 drivers to the client setup15 * AMD NIC drivers10 What you need (apart from having a basic DOS VM): 11 * MS Client for networks (two self-extracting files [ftp://ftp.microsoft.com/bussys/clients/MSCLIENT/DSK3-1.EXE DSK3-1.EXE], [ftp://ftp.microsoft.com/bussys/clients/MSCLIENT/DSK3-2.EXE DSK3-2.EXE]) 12 * AMD NDIS2 (not NDIS3!) NIC [http://support.amd.com/us/Embedded_TechDownloads/wfw31.zip drivers] for Windows 3.1 13 * [ftp://ftp.microsoft.com/Softlib/MSLFILES/WG1049.EXE wg1049.exe] (optional) 14 * [ftp://ftp.microsoft.com/Softlib/MSLFILES/WG1049.EXE netshar.exe] (optional) 15 * [http://support.microsoft.com/kb/128800 Microsoft KB 128800] - on how to add extra NDIS2 drivers to the client setup (optional) 16 16 17 All the above is available at the web; e.g. check contributions by Johannes Helmig on connecting DOS clients. I used these AMD drivers: "NDIS2 driver for Windows 3.1 - 166 KB" which results in a file wfw31.exe.17 Important: Set up the VM's network adapter to use bridged networking. See the [/wiki/Downloads VirtualBox manual] for additional explanation and details. The default NAT networking does not allow the VM to communicate with the host, which is what most users want. 18 18 19 Important: create a host interface .e.g VM1 external, and select Host Interface networking for your DOS VM, connecting it to VM1 external. See the [/wiki/Downloads VirtualBox manual] for additional explanation and details. 19 === Add AMD PCnet NDIS driver to MS Client setup === 20 20 21 === Add AMD NDIS driver to MS Client setup === 22 23 With the AMD drivers available and the files dsk3-1.exe and dsk3-2.exe: 24 * run dsk3-1 and dsk3-2 in a temporary directory 25 * follow MS KB 128800 instructions on how to add the AMD NDIS drivers to the setup routine 21 With the AMD PCnet drivers available and the files dsk3-1.exe and dsk3-2.exe: 22 * Run dsk3-1 and dsk3-2 in a temporary directory (or unzip them, as they are self-extracting ZIP archives). 23 * Follow MS KB 128800 instructions on how to add the AMD NDIS drivers to the setup routine. 26 24 27 25 === MS Client setup === 28 26 29 Run setup from the temporary directory above. Hints: 30 * give host and guest the same workgroup name31 * select basic redirection (to save memory in the DOS VM)32 * when done: set filesharing to yes in the \NET\SYSTEM.INI file.27 Run setup from the temporary directory above. Hints: 28 * Give host and guest the same workgroup name. 29 * Select basic redirection (to save memory in the DOS VM). 30 * When done: set filesharing to yes in the \NET\SYSTEM.INI file. 33 31 34 The default protocol is the NWlink one and that should do. No need to add e.g. NetBEUI.32 The default protocol is NWlink and that should do. No need to add e.g. NetBEUI. 35 33 36 Additional steps: 37 * copy netshar.exe and wg1049.exe to the \NET directory38 * run these two executables there, they'll add and/or overwirte some files.34 Additional steps: 35 * Copy netshar.exe and wg1049.exe to the \NET directory. 36 * Run these two executables there, they'll add and/or overwrite some files. 39 37 40 === Host preparation s===38 === Host preparation === 41 39 42 Before creating the DOS VM I created a Host Interface (see the [/download/UserManual.pdf VirtualBox manual]). Using WinXP Network setup I modified TCPIP proterties to use this IP address: 192.168.0.1 (subnetmask 255 255 255 0). 40 If you want to share your host's c:\ drive, allow c:\ to be shared (e.g. as 'C'), and allow users to modify your files as well; this will give read/write access to your c:\ drive. Keep security in mind; restrict access and require passwords to access data. 43 41 44 If you want to share your c:\ drive: allow c:\ to be shared (e.g. as C, and allow users to modify your files as well; this will give read/write access to your c:\ drive (note: not recommended for security reasons). 42 Be sure to have the same workgroup set up for both machines - host and guest. 43 44 === Client preparation === 45 45 46 Be sure to have the same workgroup for both machines - host and guest.46 Once your VM reboots, you can map or share drives. 47 47 48 === Client preparations === 49 50 Once your VM reboots you can export and import drives. 51 52 Assuming that the VM computer name is DOSCLNT: 48 Assuming that the VM computer name is DOSCLNT: 53 49 {{{ 54 50 C:\> net share dosc c:\ 55 51 }}} 56 52 57 and assuming that your host computer name is XPHOST:53 and assuming that your host computer name is WINHOST: 58 54 {{{ 59 C:\> net use e: \ xphost\c55 C:\> net use e: \winhost\c 60 56 }}} 61 57 62 Results can be schecked by the follwng towcommands:58 Results can be checked by the following two commands: 63 59 {{{ 64 60 C:\> net share … … 70 66 == Final result == 71 67 72 Now I can read from and write to my hosts drive from the !VirtualBox DOS machine! Internet access via the physical host IC is still possible including keeping the host firewall alive.68 Now I can read from and write to my hosts drive from the !VirtualBox DOS machine! Internet access via the physical host NIC is still possible including keeping the host firewall alive. 73 69 74 70 I did not care much about optimization, just wanted to get it up and running. 75 71 76 72 Limitations: 77 * I was not able to read guest files from the host. 78 * for security reasons I would not recommend sharing your root drive with anyone.73 * I was not able to read guest files from the host. 74 * For security reasons I would not recommend sharing your root drive with anyone.
