A) DOS (disk operating system) was the operating system software developed for 16-bit Intel processors and shipped with the first IBM PCs, and until the introduction of Microsoft Windows. DOS uses a command-line user interface.

I have a NetWare 5.1 server and I need to create a multiple config boot. With MS-DOS, it was as simple as using the following structure in CONFIG.SYS. [Menu] Menuitem=BootServ, Boot Server Menuitem=BootWork, Boot Workstation Menudefault=BootServ, 10 [BootServ] [BootWork] Files=60 Buffers=20 Device=c:\CDROMDRV.SYS /D:CD001 Then AUTOEXEC.BAT looked like this. Prompt $P$G Goto %config% :BootServ cd\nwserver server goto END :BootWork mscdex /d:CD001 goto END :END Here is a sample CONFIG.

You can use Peter Watson's MUG! program on your IIgs to transfer files via MS-DOS Iomega Zip disks. MUG! will let you read Zip disks on a IIgs equipped with a Zip drive and a SCSI interface. MUG is an NDA; so, it can be installed like other NDA's-- e.g. having the main MUG! file (probably MUG.1.01) in the System/Desk.Accs/ folder when booting. For easy use, start with a regular ProDOS Zip disk in your IIgs Zip Drive. Start a standard IIgs desktop program that does not test inserted disks.

First, start up SmartDrive to speed things up. Next, run WINNT from the I386 folder. Setup should launch, warn you if you don't have SmartDrive loaded, copy the cd to a temporarily to your hard disk and reboot your computer. A more detailed guide.

There is some work being done to create a free port of XFree86 to Microsoft Windows. However, in the mean time, if you need to run X on such a platform you'll need to use one of the available commercial servers. One of the commercial products, X Appeal, is from an XFree86 sponsor and is a port of the XFree86 servers to MS-DOS. They also have a freely available demo version. X11R6.3 does include some support for MicroSoft Windows NT.

It is likely that you have run into the USB problems that Windows 98 has brought with it. If you have a USB device plugged into your computer (Gamepads etc) then sometimes, when you shut down into DOS - Windows 98 will give you a blue screen error, that only a reboot can fix. The work around is to unplug the USB device before rebooting.

MS-DOS isn't gone, its just harder to get too. Just create a Windows Start Up disk and you can easily get to MS-Dos. Programs like Scandisk no longer need to run in Dos if there is a bad shutdown, Microsoft has improved the program to run when Windows restarts. No. Creating a boot disk to run a bios update is easily done. Read our tip for details on how to create one.

The CPHANTOM project is a 'C' language skeleton for a MS-DOS Int 2F file system redirector. The example is inspired by the Pascal language PHANTOM redirector example provided in the book Undocumented DOS by Andrew Schulman, Raymond J. Michels, Jim Kyle, Tim Paterson, David Maxey and Ralf Brown, published by Addison Wesely, 1990. CPHANTOM is provided as a Borland C++ 4.5 project. The PCA CPHANTOM redirector was designed to illustrate a few more functions than the original PHANTOM example.

If LILO doesn't work, and if the machine has MS-DOS or Microsoft Windows, you may be left with a computer that won't boot. This can also happen on an upgrade to your Linux distribution. Re-installing LILO is the last thing that the installation does. So it is vitally important when installing or upgrading Linux on a dual boot machine, to have a MS-DOS or Windows rescue disk nearby so you can FDISK -MBR. Then you can go about using LOADLIN.EXE instead of LILO.

John Dallman* has written a program ''#!perl.exe" which will do this. It is available through anonymous ftp from ftp.ee.umanitoba.ca in the directory /pub/msdos/perl/hbp_30.zip. This program works by finding the script and perl.exe, building a command line and running perl.exe as a child process. For more information on this, contact John directly.

We are assuming that you are accessing MS-DOS through the Windows "Run CMD" capability. Since the normal Windows keyboard and mouse drivers are still running, the orbiTouch? will work fine. As for the optical mouse, that should work also. If the optical mouse is occupying one of the PS/2 ports, we suggest that you plug the orbiTouch? in via the included USB adapter. Back to Top

If LILO doesn't work, and if the machine has MS-DOS or Microsoft Windows, you may be left with a computer that won't boot. This can also happen on an upgrade to your Linux distribution. Re-installing LILO is the last thing that the installation does. So it is vitally important when installing or upgrading Linux on a dual boot machine, to have a MS-DOS or Windows rescue disk nearby so you can FDISK -MBR. Then you can go about using LOADLIN.EXE instead of LILO.

If you are running 32-bit Windows you don't want a DOS version. Ghostscript for MS-Windows includes a Windows console mode executable named gswin32c.exe. The last 16-bit DOS version was either GS 2.61 or 3.33. The last 32-bit DOS extended version was GS 5.10.

You can't. Crack is Unix software, written for Unix systems and running primarily on Unix systems, and if you don't know what Unix is, then you don't need to know about Crack.

Place a blank formatted disk in the A: drive. Then from the DOS prompt of your boot hard drive type 'SYS A:\'. This will place the DOS system files and command file onto the floppy. Note that this will not copy any DOS system configuration or memory management programs. You will need to copy those over to the floppy as well if you need them (fdisk, format, etc.) Sometimes this happens.

If you are programming for MS-DOS, you will need to write an interrupt driven handler for the RS-232 ports. Only the most trival output-only applications can use the BIOS functions built into the PC. Anything that needs reliable input needs to use interrupts. Win16 and Win32 supply drivers that take care of that problem. All you have to learn with those is how to use the API, which is significantly different between the two platforms.

No. We have never supported running on MS-DOS or Windows 3.1, and in fact have long since deleted all MS-DOS-related code. We're not particularly interested in patches for these platforms, as they would introduce huge amounts of code clutter due to the woefully underfeatured nature of these systems. (See GNU Emacs for a port to MS-DOS.)

This would be illegal. We would have to license DOS from Microsoft, a license is needed for every diskette image we would send or make available for download. You do not want to know how expensive that is. In addition, Freedos has proven itself to be a worthy replacement when it comes to harddisk recovery.

NOTE: Before attempting to install *bsd on a computer with an active DOS partition, ALWAYS back up your hard drive. No one on the net, no matter how talented, can help you recover a hosed MS-DOS file system. If you lose all of your data, it is YOUR fault. During the install phase, you need to have un-allocated space left on your disk drive. This allows the install program to correctly install the *bsd partition in the partition table and DOS to peacefully co-exist with *bsd.

No. If you are using a utility such as Stacker(tm) or DoubleSpace(tm), FreeBSD will only be able to use whatever portion of the filesystem you leave uncompressed. The rest of the filesystem will show up as one large file (the stacked/double spaced file!). Do not remove that file or you will probably regret it greatly! It is probably better to create another uncompressed primary MS-DOS partition and use this for communications between MS-DOS and FreeBSD.

Yes. DOS extended partitions are mapped in at the end of the other ''slices'' in FreeBSD, e.g., your D: drive might be /dev/da0s5, your E: drive, /dev/da0s6, and so on. This example assumes, of course, that your extended partition is on SCSI drive 0. For IDE drives, substitute ad for da appropriately if installing 4.0-RELEASE or later, and substitute wd for da if you are installing a version of FreeBSD prior to 4.0.

of Emacs 20, detection and handling of MS-DOS (and Windows) files is performed transparently. You can open MS-DOS files on a Unix system, edit it, and save it without having to worry about the file format. When editing an MS-DOS style file, the mode line will indicate that it is a DOS file.

A pre-built binary distribution of Emacs is available from the SimTel.NET archives. This version apparently works under MS-DOS and Windows (3.X, 9X, ME, NT, and 2000) and supports long file names under Windows 9X, Windows ME, and Windows 2000. More information is available from If you prefer to compile Emacs for yourself, you can do so with the current distribution directly. You will need a 386 (or better) processor, and to be running MS-DOS 3.0 or later.

No, no and no. Microsoft bought MS-DOS from a Seattle company, and it was called QDOS then (Quick and Dirty Operating System). Some say it is not quick anymore, but the rest stays the same. True, Microsoft made some modifications to it, and probably Bill Gates helped in it, but he did not write the OS in the true sense of these words. By that time, MS was in dire need of an OS to use with IBM PC, because IBM could make business with Digital Research (see above, III.

Version 1 of MS-DOS didn't have subdirectories or paths, and wasn't much like Unix at all. The '/' character was used to denote command options (like '-' in Unix); this was rather common in CP/M, and is the standard in many DEC operating systems. In version 2.0 of MS-DOS, many new Unix-like features were added, including subdirectories. Since '/' was used for command options by many programs, that character couldn't be used in paths.

Windows ME has an installable option that permits the use of a DOS prompt. Please see their help files for an explanation of installing this. Also, you might want to read article Q179644 in the Microsoft knowledge base (http://www.msdn.microsoft.com).