There are a lot of posts regarding bootdisks and the problems people encounter in using them, so I thought I would share what I do when I create a bootdisk. To begin with, all versions of Windows 95-98-ME-2000-XP allow you to create a bootdisk with the click of a mouse, but these disks actually only set up a very basic operating system on a floppy and use the "current" command.com and cd-rom drivers for support. There is usually not much else. The problem with this is that if the computer has an issue severe enough to keep it from booting the hard disk drive (HDD), then you need ways to investigate the machine and determine what is bothering it. So, I do things a bit differently, beginning with using a dos floppy on which I've "sys'ed" the DOS6 or DOS6.22 command com, along with the io.sys, msdos.sys, and drvspace.sys. That's a basic system which will boot most desk or laptop computers. I add the following files to the "system" disk. (for memory management) himem.sys emm386.exe (for cdrom management) btcdrom.sys cd_atapi.sys oakcdrom.sys mscdex.exe (most cdr - cdwr will respond to one of them) (HDD checking) fdisk.exe format.exe chkdsk.exe label.exe (format uses chkdsk and label automatically) (interface) edit.com dosshell.com dosshell.exe qbasic.exe qbasic.hlp graphics.com graphics.pro ega.sys ega.cpi ega2.cpi help.com help.hlp mouse.com mouse.ini (these provide a working desktop and file manager with mouse support, in addition to a help system to tell you about the commands) (file and directory functions) attrib.exe more.com choice.com sys.com (starting order) Typical config.sys: device=a:\himem.sys device=a:\emm386.exe device=a:\oakcdrom.sys /d:mscd0001 REM device=a:\ramdrive.sys 2048 512 1024 /e dos=high dos=umb files=30 buffers=10,0 (sometimes I use a ramdrive, note REM) (Typical autoexec.bat) path=a:\;c:\ prompt $p$g lh a:\mscdex.exe /d:mscd0001 /m:30 /e a:\mouse.com dir/w/o (This setup starts computer from a:\ and displays directory of a:\ ) Notes: The line containing the cdrom.sys may need to be changed to one of the other drivers to start the cdrom The *.hlp files can be eliminated to make room for other programs, but this is my "standard" that allows me to view and edit a lot of files from autoexec.bat and config.sys to win.ini and other windows initiation and *.pif files. Using the help files also gives access to a lot of information concerning the commands used in the start-up files. IF C:\ can be accessed, then you should only need to type C:\ (enter) and DIR /w/o/p (enter) to see what's on it. If the computer objects, claiming c:\ is invalid, you can use fdisk to potentially locate problems with partitions, master boot records, or FAT Tables. The same process will work with a Dos5 system disk and the proper versions of the listed files, the main difference being that there will be more free space on the disk, and drvspace.sys would probably be dblspace.sys instead. Downloaded bootdisks: These are generally good if you don't mind your cdrom being named "r:\" or "z:\" on occasion .. most come with multiple cd-rom drivers, format, and fdisk. Another reason I make boot disks with these "extra" files on them is because quite often the only thing wrong with a computer is that someone has inadvertently changed something important which can later be edited from dos in the event of a no-start of windows. I've done it myself! While this disk configuration will not solve all pc problems, it will give you a head-start should you decide to poke around a little and look for a solution yourself. Good luck! You don't have to be realistic to be cynical, but you DO have to be cynical to be realistic!

AS you stated at the beginning, all versions of Windows allow you to create a boot disk. Most of the files you mention will be put on a a boot disk anyway. However, if you are working on Window 98, A DOS 6.22 disk is not going to be a lot of use to you as it won't have long file name support nor large disk support and FAT32 support in Fdisk. Best stick with the Boot disk designed for the OS it is working on. There are a few gotchas along the way. Stuart

I agree with Stuart. Unless you are very knowledgeable about Dos, I think it's better to stick with the diskette created by the appropriate OS.

Hi Doormat, I applaud your efforts. I'm intrigued at the concept of 2k/XP creating a boot floppy. Maybe you can give me a few hints for the handicapped. I always assign a letter to the CDROM so I know where it is. I've seen hundreds of msgs representing thousands of hours of wasted time trying to 'find the CD.' I usually set lastdrv v, leaving w x y z for Novell. (Old habits die hard.) For CD drivers, you can have multiple drivers in config, as does a 98 startup, which is messy, but saves your having to edit config if it doesn't load the one you chose. Note the a:\ preceding the device is superflous. This will save you setting a path to a non-exisyen drive: if exist c:\nul path=a:\;c:\; And this will not change to the c drive: c:\ [enter] This will: c: [enter] And if c is non-existent, you'll get hung. It's a better idea to: dir c:\ Stuart, No, DOS 6 will not have LFN support. But neither will 7.10.2222 unless and until the 32 bit kernel is loaded. M2

I too agree with the others. If you're working on large disks, the proper support isn't there. As well, if you're setting up a machine for 95 and up, sys.com won't be of any value either really. Actually, all MS and MS Windows O/S loads sys the drive for you. About the only time you'd need to sys the drive is when you're setting up a machine with proprietary cdrom drivers in config.sys/autoexec.bat, so the machine doesn't loose the cdrom when it first reboots to "Continue to load windows" setting up the hardware end of it.

>> I'm intrigued at the concept of 2k/XP creating a boot floppy. Maybe you can give me a few hints for the handicapped. << Windows Explorer. Right click Drive A: Select format and click "Create MS-DOS Startup Disk." All this will contain in the bare minimum to get the system up and running, but with Windows XP, that is all that is needed. Everything else can be done form the bootable CD drive. The boot floppy is designed to be used when flashing the BIOS. Stuart

I don't mean that the proposed setup for a boot disk will always work, but I have had pretty good luck with the older computers. Speaking of old habits that die hard, I tend to use 8-character filenames as often as possible, reducing the problem associated with mis-handling of long filenames. Agreed, "a:\" is superfluous, and "C:" is appropriate for changing drives ... I just wrote it this way for those of us who are not experts, but have SEEN this notation in books, web pages, and help forums ... sometimes it is more confusing to leave out a superfluous character or command than it is to include it for the sake of clarity. I'll just sit quietly and watch for a bit ... You don't have to be realistic to be cynical, but you DO have to be cynical to be realistic!