Note that adding those keys could pose a security issue for your host computer.

Make sure you restart the SSH server to reload the config file. Then, you need to be root on your host Linux box, and add those keys, because DOS SSH does not use the most modern key exchange algorithms (but see note at top of this post), and then you’re ready. (PCNTPK.COM) (By the way, a really good place to find out about a lot of this is.

You make sure the packet driver is loaded, and then that’s about it. Essentially, you leave the VirtualBox defaults alone (PCNETIII Fast network adapter or whatever it is) and install the FDNET package and SSH2DOS package, and you make sure that the WATTCP.CFG environment variable points to the directory containing the WATTCP.CFG file that was installed with FDNET. That is not too hard, because the maintainers know that VirtualBox is probably the most likely way users will play with FreeDOS - bare metal installs are of course possible, but less likely these days. The first step is to get networking working in the FreeDOS VM. However, if you can set the host machine up as an SSH server, you can use the DOS versions of SSH and SCP to move files back and forth with relative ease, at least with a Linux host. But of course there are no Guest Additions for it, no shared folders and the like. The rest of this post assumes we’re using the SSH2DOS that is as of writing part of the FreeDOS repository.įreeDOS works very nicely in a VirtualBox VM. Note: There is now a version of SSH2DOS that can do a more up-to-date key exchange, though it does not seem to work with public/private key pairs.

Transfer file to vm virtualbox