FreeDOS Networking with VirtualBox 4.xImportant!This page is outdated! IntroductionRunning a FreeDOS guest in VirtualBox is a bit complicated. Especially exchanging files with the host is tricky. A networked FreeDOS guest would solve the problem, as it could exchange the files over the network. To make things a bit easier I have built a FreeDOS Virtual Machine with an already activated network. Bug: High CPU usage of DOS installations in VirtualBox You may note increased fan activity when running a DOS / FreeDOS installation in VirtualBox. Please read this document carefully to learn more about the problem and to prevent possible damage to your real computer. Ulrich Hansen, October 11th, 2011 Installation
StartupThe bootmenu options are:
The last two options (NetBEUI and IPX) are only useful, if you have another client in the network that is still running these protocols. After FreeDOS started, you can use the shortcut "mc" or "nc" to start up the Norton Commander clone Doszip and get an overview over the FreeDOS system.
Networking with the FreeDOS virtual machineBoot with option 3 activated (or 4,5 or 6 if you need MS-Client). Networking applications preinstalled are:
and basic networking applications like ping, ftp, etc. that come as part of these TCP/IP software packages:
ConfigurationDHCPSome apps like Arachne, mTCP and wget are configured automatically with DHCP. So if you have a router with DHCP activated (default) and broadband internet, you just can start to surf the web by typing "Arachne" or download files with wget. DHCP is configured for Arachne, mTCP and wget in
The only thing you have to correct manually is the IP of your
router. Preconfigured is the IP
mTCPThe mTCP apps are configured by running "DHCP.EXE" from the
directory Fixed IPsIn some configurations you need to use fixed IP adresses. The programs in C:\NETWORK\WATTCP and C:\NETWORK\WATT32 need fixed IPs. And also NTCPDRV (the Sioux webserver) needs fixed IPs You can set fixed IP in these configuration files:
Preconfigured in NTCPCFG.BAT is the IP "192.168.1.80" and the Router/Gateway/DNS server as "192.168.1.1". In most cases you want to change these settings. In AUTOEXEC.BAT the mTCP DHCP client is automatically started. Please deactivate the line, if you like to work with fixed IPs in mTCP and configure C:\FDOS\MTCP.CFG manually instead.
MS-ClientPlease set the name of your workgroup in the following lines of
By default MS Client works with DHCP. If you need fixed IPs, set
them in the section How to exchange files between your host and your FreeDOS client.FTPThe easiest way to exchange files between host and FreeDOS guest is FTP. Start the mTCP FTP-Server in the FreeDOS client:
This shortcut starts the server To connect with Filezilla open the Site Manager and add a new site. Enter the IP address of the server into the line "Host:". Normally mTCP ftpsrv should have retrieved an IP automatically by your DHCP server. It is shown at boot. Or look into C:\FDOS\MTCP.CFG to see the IP. The preconfigured username is "freedos" and the password is "freedos". Please change this in the mTCP password file C:\FDOS\FTPPASS.TXT as soon as possible. After your FTP session stop the server by typing CTRL-C in the FreeDOS guest. FTP with WATT32 ftpsrv32 mTCP ftpsrv is still in development. If you prefer the older FTP-server ftpsrv32 of the WATT32 applications, please start the server by entering
Please be sure you have configured the configuration file C:\FDOS\WATTCP.CFG manually to use fixed IPs. The server doesn't seem to run with DHCP. WATT32 ftpsrv32 doesn't need a password. So use "Anonymous" as Logon Type in Filezila. After your FTP session stop the server by typing ESC in the FreeDOS guest. Warning: The ftpsrv32.exe FTP Server accepts
anonymous login only. So be careful to have a firewall or a router
between the machine and the internet! MS Client
That's it. Change to E: in the FreeDOS client to work with the shared folder of your host. Have fun ! |
CHANGELOG: Changes to FreeDOS 1.1 Beta:
I did some changes to the original Beta: