To test, try running dir e: and verify that you get output. If it doesn't as expected, and you followed all instructions above, the error is most likely on the server side. I've had mixed results myself - on my initial testing with MS-Client about three years ago , I was able to get this working perfectly with Samba; this time, however, I can't.
The final bit of network setup we're going to do for the NDIS driver is installing a "shim" packet driver. This is necessary if you want to use both Microsoft including mapped drives and non-Microsoft network utilities on the system which is highly recommended. Also, while the driver itself works great, the whole concept is a hack and as a result requires a manual and rather complicated setup process. Save your changes to protocol. Add the following after "ifshlp. As a result, this command is no longer needed, and will in fact cause errors if you try to run it with the other drivers already loaded.
This is also a good time to decide whether or not you want to automatically map shared drives on boot. If you do not plan on using shared drives, or you prefer to map them manually each time they're needed which can be done by simply running net start , comment out the following line to save a fair amount of conventional memory:. Finally, reboot to load the new driver. You should see the following message during the boot process to confirm the shim driver was loaded:.
Fortunately, both stacks can installed and enabled simultaneously, so we'll setup both. Edit the values as appropriate, then save and close the file. Finally, add the following line to autoexec. Run the above command now to manually set the configuration variable. Next, let's install a couple diagnostic utilities. Copy tcpinfo. The top line should state, "Reading Waterloo TCP configuration file," which indicates that it was able to find your config file. The network parameters output by tcpinfo should either match your static configuration, or should be appropriate for your DHCP network.
To test, try the following:. Finally, add the following to autoexec. If you are using a static address you can skip the dhcp line in autoexec. Run those autoexec. To test, copy ping. It's time install a few essential network applications. Quite a few exist, but these are the ones I find most useful. I primarily run Linux systems, so SSH is very important to me. It can be downloaded from the link above. If you setup both of these as instructed earlier, you're already good to go.
Run ssh username servername to verify SSH works as well. If you're having any trouble with your WATTCP apps, or you want to poke around to see what other options are available, take a look at the included wattcp.
If you decide to edit and use this version of the file, you can either replace the existing wattcp. CFG variable in autoexec. This is a command line download manager that can download files from pretty much any web or FTP server and, happily, there's a DOS version available from the link above though the DOS version is no longer maintained at this point.
Now let's install some mTCP applications. Each of these will utilize your mTCP configuration file so you can go ahead and use them directly. You can use this to automatically set your computer's clock to the correct current time, which is very handy on ancient computer hardware with bad CMOS batteries. After running the above, you should see your current system time as well as the current NTP server time listed as "Time should be set to". To actually set the time, use the -set parameter.
To always set your system clock to the appropriate time on boot strongly recommended , add the above, with -set to autoexec. Bonus tip: once you get the mTCP utilities installed, try running telnet towel.
Feel free to play around with the others, though. The bad news is that you lose the ability to concurrently use many but apparently not all other PD-based applications. The reason is that XFS installs it's own driver literally on top of your packet driver, which conflicts with most other PD applications.
If you only otherwise use NDIS-based applications, this is not an issue. If you only use PD-based applications, theoretically you should be able to get them to work with the XFS driver loaded by configuring them to use interrupt vector 0x62 instead of 0x60 search for "redirected PKTDRVR" in xfs.
See the end of this section for an alternative approach that you can use instead. It was a commercial program, but as noted above it's long since been abandoned, so grab a copy if you're so inclined and let's get to work. Note: Before installing, take a look at kernels. Note that XFS requires a local hostname to be set.
If you're using a static IP address, this should be taken care of. If everything worked, you should be able to do run dir f: and see a list of files on your NFS server. Switch to F: and run ls or lsx to see the long file names. Be sure it's added after any other PD applications included in autoexec.
However, XFS provides the ability to temporarily unload and then reload it's PD shim as needed, so you can leverage this to run other PD applications without completely tearing down NFS support or rebooting. As an example of how to do this, say you want to SSH to another system while you have an NFS share mounted; you can do this by calling the following additional commands before and after SSH:. While in the "stopped" state, your mounted shares will still exist but will not be accessible.
Issuing the restart will make them available again. It's not ideal, but it's a fairly reasonable compromise, and can be made less annoying by using a 4DOS alias to simplify that much more see the 4DOS section below.
Whew, now that we're finally finished with networking, everything else should be a breeze in comparison. As an alternative I recommend the Toshiba driver linked above. This driver should offer roughly the same compatibility and capabilities, but only uses a svelte 7 KB of memory.
SYS v2. SYS driver. To install the driver, copy cdromdrv. Then, edit config. Next, edit autoexec. Reboot to load the new driver. If both the driver and MSCDEX were loaded properly, you'll see the following message in the output while the system is booting:. Next we'll install a mouse driver. This is optional, as DOS itself doesn't utilize mice, only the applications programmed to support them such as Pedit.
So, unless you plan on running an application or game that uses a mouse, you can skip this. The first option is to use the original mouse driver provided by Microsoft with Windows 3. COM, and can again be downloaded from the Computer Hope hardware downloads page. The second option is a much newer, open source mouse driver called CuteMouse. It's still actively developed for the FreeDOS project and available from the site linked above. CuteMouse provides support for modern mice and mouse features such as wheels though few applications support the wheel , and is significantly smaller than MOUSE.
COM, using only about 3. COM if preferred. Then, edit autoexec. CuteMouse supports quite a few options, so run ctmouse. Auto-detection should generally work fine, though. Run the above command to manually load the driver.
Pedit supports mice, so you can fire that up to verify that your mouse was properly detected and enabled, or use the included mousetst. Next up is sound. You'll need to install drivers appropriate for your sound card. Your setup should be at least somewhat similar, but certainly some of the details will be different. To begin, unpack and copy over both the driver disk and configuration manager linked above , then change to the driver disk directory.
We'll need to reboot to activate the sound card, so do that now. This will let you verify that your sound card is installed and working properly. While here, you can also run mixerset. I find the default config too loud leading to noticeable distortion on my speakers , so I turn the Master volume down a couple clicks. You may also like to try enabling 3DSE 3D Stereo Enhancement and see if that improves the sound; I generally don't care for this, but it can make a positive difference with cheap stereo or embedded monitor speakers.
At this point it's time to do some configuration cleanup and memory optimization. My system, after installing everything listed above and despite tweaking the config files a bit, currently has only KB of conventional memory available.
This is actually pretty decent given everything I have loaded, but unfortunately it's not enough for some of the other programs I want to install, and definitely isn't large enough for many games. Startup order is very important under DOS; loading drivers and programs in the "wrong" order can drastically increase memory usage.
Unfortunately, there's no way to guarantee an optimal order. You can find a lot of advice about tweaking MS-DOS memory settings on the internet, but the basic advice I've found that works the best boils down to three parts:. I recommend giving it a shot, though; it may work better on your hardware, and even if it doesn't it provides an option to easily undo the changes.
In order to hit KB I'll need to disable some things. Good candidates:. I elected to disable MS-Client and just load the native packet driver, which took me way beyond my target to KB free. Aside from mapped drives, MS-Client provides almost no benefit to a home user over the PD applications, and even mapped drives is very flaky with recent versions of Samba.
At this point, I'd consider the base OS install to be complete. Everything we installed should be very stable and functional, and should, for the most part, be usable under Windows for Workgroups 3.
Using this base, you can install additional applications, games, utilities, drivers, etc. I'll cover a few of the more useful or interesting additions I've found here. It provides a great many significant enhancements over the default DOS shell, command.
To read up on it and download a copy, visit it's home page. The open source version called "Free 4DOS"? Basic installation is quite easy. You can choose to have it automatically update autoexec. Edit autoexec. That's a bummer. Run help keystack. If you don't need this, comment out the kstack. You can run option. There are a lot to play with, but I personally like to set the following non-default options:.
One handy feature 4DOS provides is the ability to use aliases. If you're familiar with the concept from Linux, it works similarly; if no, it's easiest to see it in action. You should get a directory listing in the same style as the default ls command on Linux. This is a pretty trivial example, but you can use it to provide a number of useful conveniences.
For example, here's my aliases. It isn't necessary to use an alias file, but I find it convenient to keep all alieses grouped together.
Another neat, but this time entirely superfluous, trick is to enable support for colored directory listing output. This is similar to what modern Linux distributions do by default as shown in this simple example if you're not familiar with it , and makes it possible to quickly and easily recognize common file types at a glance. I modeled the following configuration based on Linux's default scheme for dircolors, with a couple differences and pruned down a bit:.
There are a couple additional points to be aware of. The extension list can also be a special type of file, such as dirs directories , hidden hidden files , rdonly read-only files , etc. So, the first item in the line sets my directories blue. Then click 'Add floppy controller'. Click on the 'Add Floppy Device' button.
In the windows that pops up, click 'Leave Empty'. Next go to the 'Audio' page and make sure it is set to SoundBlaster Go to the 'Network' tab and choose 'Bridged Adapter', then choose your network adapter. I don't know if DOS can access the internet, but this is the setting you would need to perform for any virtual machine to access the internet and the network.
This is optional: Next to go the 'Serial Ports' page. If you need serial support, you need to check the check box 'Enable Serial Port', and if you need two ports, go to the 'Port 2' tab and uncheck the same box.
Click 'OK' at the bottom of the window. Double click on the virtual machine that you created for DOS. Close the virtual machine's windows and select 'Power off the machine'.
Follow the setup instructions to install DOS 6. To insert disks 2 and 3 when setup asks you to, just follow the second direction in this step. Leave comments at the appropriate step about anything you have to say about it. Use this step to leave comments regarding the entire Instructable. Good luck! Bootable Dos 6.
Teacher Notes Teachers! Step 4: Step 4: Configuring the Virtual Machine Right click on the virtual machine you just created and click settings. Step 6: Step 5: Congratulations! The new FreeDOS release candidate is now available! We've been working hard on the next FreeDOS distribution, and we'd like your help testing this new release candidate.
The main goals for 1. Some of these include a LiveCD, a Floppy Edition, new packages, updated packages, and many improvements to the installer to provide hardware compatibility and multi-language support. Download FreeDOS 1. The FreeDOS 1. Most users should use this image to install FreeDOS.
A bootable CD image designed for older hardware.
0コメント