Adrover posted on September 3, UTC. Noah kirsle posted on December 11, UTC. Tagadada posted on July 20, UTC. Anonymous posted on September 3, UTC. Limon93 posted on September 23, UTC. Andrew posted on September 26, UTC. James posted on January 25, UTC. Mike posted on February 11, UTC. Dennis posted on February 14, UTC. Gene posted on February 15, UTC.
Dean posted on February 26, UTC. Noah kirsle posted on May 24, UTC. Pietrr posted on August 4, UTC. Anonymous posted on August 29, UTC.
Noah kirsle posted on October 11, UTC. Jayne posted on December 12, UTC. Iranian man posted on December 16, UTC. Jayne posted on December 17, UTC. Rohit posted on March 2, UTC. Kitten S. Jaron posted on June 14, UTC. Prashant posted on June 19, UTC. Mcsauce posted on July 24, UTC. Lee posted on July 27, UTC. Dale posted on October 12, UTC.
Noah kirsle posted on October 12, UTC. Dale posted on October 13, UTC. Mark posted on December 6, UTC. Anonymous posted on January 5, UTC. James posted on January 15, UTC. Anonymous posted on February 15, UTC. Vic posted on March 18, UTC. Robert posted on April 17, UTC. Ed posted on June 7, UTC. Attila posted on June 10, UTC. Mac posted on June 27, UTC. Simon posted on July 14, UTC. Mousy posted on September 24, UTC. Steve posted on October 5, UTC. Noah kirsle posted on February 3, UTC. Doceave posted on February 10, UTC.
Noah kirsle posted on March 7, UTC. Noah kirsle posted on March 16, UTC. Mark posted on March 31, UTC. Noah kirsle posted on March 31, UTC. Coltan posted on April 24, UTC. Trent posted on May 5, UTC.
Noah kirsle posted on May 5, UTC. Michael posted on May 13, UTC. Noah kirsle posted on May 13, UTC. Michael posted on May 18, UTC.
Max posted on June 17, UTC. Paul posted on August 16, UTC. Tom posted on August 24, UTC. Yee posted on September 17, UTC. Lordmoggy posted on September 28, UTC. Draug posted on October 2, UTC. Continuous posted on October 20, UTC. Noah kirsle posted on October 20, UTC. Continuous posted on October 21, UTC. Stephen posted on November 27, UTC. Noah kirsle posted on November 27, UTC. Stephen posted on November 28, UTC.
Noah kirsle posted on November 28, UTC. Guest posted on December 3, UTC. Tom posted on December 5, UTC. Anonymous posted on February 20, UTC. Gary posted on March 4, UTC. Mick posted on March 31, UTC. Guest posted on April 15, UTC. Bob posted on May 2, UTC. Anonymus posted on May 3, UTC. Jebo posted on May 8, UTC. Jack posted on May 10, UTC. Jerry posted on May 28, UTC. Kro posted on June 26, UTC.
Noah kirsle posted on June 26, UTC. Ahmed hamdy posted on July 26, UTC. Guest posted on August 6, UTC. Stefanos posted on August 13, UTC. Johan posted on October 1, UTC. Johan posted on October 2, UTC. Noah kirsle posted on January 19, UTC. Kluunsoft posted on April 23, UTC. Ben posted on May 13, UTC. Noah kirsle posted on May 14, UTC. Gonzo posted on September 16, UTC. Noah kirsle posted on October 18, UTC. Gilberto posted on February 20, UTC.
Vitons posted on March 21, UTC. Pi4a posted on July 5, UTC. Anonymous posted on August 22, UTC. Honestly, if you have no appreciation for old hardware or software, then this is definitely not for you. If, however, you share my passion for technology, not only for the new hotness [1] of today but also the old and busted and tried and true of yesterday that got us to where we are today, then I think you'll find this interesting.
If you have some old hardware lying around then I hope you'll follow along, but even if not I think you may still find some of this interesting enough to read.
It's a great project that I highly recommend. Note: I provide download links for all discussed software in the relevant section where it's discussed. Links point to the original download location for each file wherever possible, but for the files that no longer have an official source or a reliable one, in the case of the files hosted on Microsoft's amazingly unreliable FTP server , I've linked to a local copy you can download instead.
Tip: I also recommend grabbing a copy of either Universal Extractor or 7-Zip if you're running Windows on your main computer, or p7zip and LHa for UNIX if you're running Linux both should be available in your package management system. These applications should cover all the software I tried to unpack, so having these tools available in advance will save some time and hassle. You can get by with only one floppy diskette by writing the next disk image after the previous one completes installation, but I highly recommend using at least two diskettes so that you can have a copy of Disk 1 on hand at all times.
You'll likely need to boot from or otherwise use that disk a number of times. Since it's free, though, there really isn't a good reason to not upgrade. It's larger than a single floppy, and meant to be downloaded and run directly on the target computer, which is difficult for a freshly installed version of MS-DOS. To workaround, I suggest the following:. This disk is not mandatory, and mostly just includes some extra features from previous versions of DOS that were dropped for version 6.
If you don't want to bother with it you won't be missing out on much, but just to be thorough let's take a look at how to install the more interesting stuff on here. One reason, and one reason alone: QBasic Nibbles! I spent many hours playing this relatively simple but addictive Snake -like game as a kid, and was delighted to discover it on the supplemental disk. To try it yourself, just run qbasic. It's essentially a primitive Windows-like or perhaps more accurately, 'Windows Light' environment that runs on top of DOS and provides a GUI file manager, file associations, a menu-driven task list, and even primitive pseudo-multitasking called Task Swapper here.
It's not something I'll care to use, but it's a pretty interesting idea that I was completely unfamiliar with before this project, and it seems like it could be a reasonably powerful interface if a little time is spent on configuring it just right though, honestly, running Windows 3. I'm not going to dive into this here as it's beyond the scope of " mostly pure MS-DOS", but here are a couple tips if you want to play around with this:.
Next, I recommend installing a couple utilities that will make the rest of the setup process much easier. As with the step-up files above, getting the files to the system is still annoying at this point.
Until we get networking setup later on, I recommend unpacking the programs on your main computer and copying them over with floppies as the easiest option. Tip: You will be repeatedly hand editing your system configuration files throughout this walkthrough, and it's very possible at some point that you may be stuck with a system that won't boot properly.
This will perform a clean boot of the system, ignoring your autoexec. You can then edit them as appropriate to fix the problem, and reboot to load everything again. Note: Most DOS commands and options are not case-sensitive.
While most of the text in the stock autoexec. My personal naming convention, used throughout this document, is pretty simple: variables are fully capitalized, and almost everything else is lowercase. Feel free to leave everything uppercase if that works for you, though. SmartDrive is "a disk caching program LOADHIGH will load the specified program when possible into upper memory, freeing up the all important conventional memory for other applications.
This requires that EMM also be enabled, as shown below. Finally, the DIRCMD variable instructs the DIR command to display files sorted first by name, then by extension, with directories always listed first by default, it lists files sorted by date. Note that this shortens the amount of time you have to press F5 if you need to clean boot your system, but it's still possible if you're fast, or you hold down F5 right before DOS starts loading which is what I do.
I discuss this a bit more in the Addendum below. I recommend rebooting at this point to let the new configuration take effect. NIC Drivers you'll need to grab drivers for your specific NIC; these drivers cover my system, and will be used for the walkthrough :. Now it's time to finally configure networking. Getting this up and running is extremely helpful because it largely eliminates the need for floppy disks.
Unfortunately, networking under DOS is It can be done, but it's somewhat limited, slow, and painful to install due to multiple driver and network protocols.
So, get ready for some fun! The first decision to make is to decide what kind of networking support you want installed. In brief, there are two types of drivers we're going to install:. NDIS - the newer device driver interface co-developed by Microsoft, with somewhat more features and capabilities at the expense of more bugs and significantly more memory usage.
This is required for Microsoft networking utilities, including support for drive mapping. Most non-Microsoft network utilities require a packet driver interface and will not work with only NDIS installed. Fortunately, this isn't a one-or-the-other choice; it's possible to install support for both with some extra work. If you only need one or the other, though, save yourself the hassle and go with that one. I'm going to walk through installing both below, and point out what you should do differently if you only want to install one of the drivers.
For the full experience it's worth setting up NDIS it can be cleanly disabled if you decide it's not worth it , but if you just want to get up and running as quickly is possible, the PD-only option should suffice, and is all I use on my system after experimenting with all of this.
Download the appropriate driver package for your NIC and consult the documentation for details. This file can be manually unpacked, but it's probably easiest to use QStart to unpack them for you:. The 0x60 option for each specifies the software interrupt; 0x60 is the default, and there shouldn't be a reason to change it unless you're using multiple NICs.
Run the above command now to manually load the driver; assuming you have an ethernet cable plugged in, it should automatically detect the connection. NDIS driver installation is quite a bit more involved. It can be installed manually like the PD, but instead we're going to let installation and configuration be handled by Microsoft Network Client 3. Running each EXE file will unpack them to the current directory if you didn't unpack them before hand. If prompted, it's safe to overwrite any files as a few exist on both disks assuming you copied the MS-Client disks to their own directory.
Note: If you are using a 3c90x card, you must edit oemsetup. Comment out or delete the following lines and save the file:. A bug in the MS-Client installer prevents a file necessary for Windows 3. This isn't necessary if running solely under DOS, but it doesn't hurt in anyway, so let's install it just to be safe. If you run into any other trouble, or have questions about some of the options, official MS-Client setup documentation is still available from Microsoft. MS-Client updated your system configuration files during setup, so let's review those changes and make a couple changes.
First, edit config. These are some of the various network services installed by MS-Client. We're requesting that they load themselves into high memory. This indicates you've run out of upper memory, and MS-Client isn't smart enough to load itself into conventional memory instead. This is only required if you plan on mapping shared drives, and can be disabled if you do not wish to auto-mount drives at login.
If you do plan to mount shared drives, go ahead and enter your username now or just press Enter to accept what you specified during MS-Client setup , then enter the password for your account. In either case, choose Y to create a password list when prompted. We can perform a few tests to confirm, but note that the utilities described below, though named the same as modern utilities, work differently than what you're probably used to again, think "primitive".
Next, make sure you can ping your own IP, eg. The bottom line should say "echo received". Finally, make sure you can ping your gateway's IP address this can be found in the ipconfig output :. Again, the bottom line should say "echo received". If all that worked, congrats, you're up and running! However, there's one more major issue we need to take care of. Due to another bug in MS-Client, DNS does not work by default, nor is it possible to configure or enable it through the setup utility; this must be done manually.
Substitute the appropriate values for your network, and be sure to separate the octets with spaces as shown above rather than periods as would be done on modern systems.
Finally, run the above command now to start the Microsoft domain name resolver. You can verify DNS is working properly with ping again:.
All of this work will now let us finally do something very important: map shared network drives. This is especially useful as we can use this to easily copy files and install new applications and drivers without floppy disks.
To map a drive, assuming you already have a shared drive properly configured in Samba or a Windows server which is outside the scope of this HOWTO , run:. Again, assuming everything has been properly setup on the server, and that you logged in with proper credentials, this should just work; you'll get a "command completed successfully" message if it did.
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 all settings are correct, you can highlight "The settings are correct" and press Enter. Install DOS in the default directory by leaving the directory location unchanged in the next window and just hitting Enter. Let your computer copy the files from the first installation disk. A status bar will appear so you can see the progress. Replace disk 1 with disk 2 when prompted and hit Enter to continue.
You will see the status bar appear again. Take out disk 2 and insert disk 3 when the next prompt window appears and press Enter. This will allow files to be copied from the third installation disk until all files have been copied. Remove the final disk from your floppy drive when you see the message appear that says "Remove disks from all floppy disk drives. Include your email address to get a message when this question is answered. However, it is strongly advised that you install the latest version because it supports old as well as new DOS commands and programs.
Helpful 0 Not Helpful 0. Submit a Tip All tip submissions are carefully reviewed before being published. Data can be deleted while installing DOS if you format your hard drive. Create hard drive partitions or backup your important files to avoid data loss.
Helpful 3 Not Helpful 1. You Might Also Like How to. For additional information about fdisk, including a simulation of how fdisk operates, see our fdisk command guide. At the prompt type format and press Enter. Once the hard drive is formatted, reboot the computer with the diskette still in the drive and once back at the setup screen run through the setup of MS-DOS on the computer. Thankfully, there are tools around that can help you accomplish this with the minimum of effort, and not lead you through a huge multiple step process full of manual commands.
Reply Gregg Eshelman 1 year ago.
0コメント