If you've found yourself in the highly unlikely circumstance of being able to download files from one type of computer, but have no access at all to the type you need to make a boot disk for, then visit this following link. An excellent source of boot disks for all WindowsTM platforms, etc., is this https://trava55.ru/: All Boot Disks .
One of the first things every computer owner should do is make a boot disk. ( I'd suggest that you also have more than one 'known-good' working copy as well!) In the event that your Operating System will not operate, you can often use a boot disk and utility programs that you may have to add to your boot disk to correct problems with system files, saving yourself the hassle of going through a complete reinstall and possibly losing some of your precious data files! (You always remember to make copies of any important data files, right?) If your OS will not boot due to a faulty hard drive or some other equipment failure, a boot disk can be very useful in trying to discover the actual cause of the problem.
Many new computers come with a Boot Disk that is programmed to restore the original files from a CD-ROM. (Actually, your computer's manufacturer may have placed even the system boot files directly on the CD-ROM and set the BIOS to boot the CD-ROM all by itself!)
But you should still make your own boot disk! Why? Because these disks rarely have all the DOS utility programs necessary to fix your system files in the event that your hard drive will not boot.
Assuming that you're already running Windows? 95 or 98, the method shown here to create a new boot disk will begin by using the "My Computer" shortcut icon on your Desktop:
[ NOTE: There's a special tab in the "Add/Remove Programs " section of "Control Panel" which creates what Microsoft calls a "Startup Disk". But it requires your Windows installation CD-ROM to make it. Apart from that, if you wanted to make a second boot disk without all of the utility programs on it, you'd have no control over that and would have to sit there erasing them after it finished copying all those files again! ]
Furthermore, I was using a Windows 98 installation for this display. If your system files have the same date/time as mine, then the values shown above for 'bytes used by system files' and 'bytes available on disk' should be the same too.
All the other values should be the same regardless of which Windows version you are using.
Your Boot Disk has been created and tested. Now it's time to add some utility programs to it. As a minimum, it should contain your CD-ROM drive's DOS driver (a file necessary to access the CD-ROM drive from DOS)and Windows 95 or 98's FDISK.EXE and FORMAT.EXE programs which are found in the C:\WINDOWS\COMMAND directory (orfolder if you prefer).
[Note, however, that the Windows 98 Boot Disk comes with a number of generic CD-ROM drivers that should cover just about any drive out there.]
Here's a file listing from one of my own Boot Disks:
Volume in drive A is BOOT DISK
Volume Serial Number is 19DF-3D28
Directory of A:\
COMMAND.COM **
FDISK.EXE *
FORMAT.COM *
SYS.COM *
MSCDEX.EXE * (for a CD-ROM Drive)
EDIT.COM *
EDIT.HLP
REGEDIT.EXE *
ATTRIB.EXE *
SCANDISK.EXE
SCANDISK.INI
DEBUG.EXE
CHKDSK.EXE
DOSKEY.COM
DELTREE.EXE
DISKCOPY.COM
MODE.COM
MOVE.EXE
EMM386.EXE M*
HIMEM.SYS M*
MEM.EXE
ATAPI_CD.SYS C* (CD-ROM driver)
________________________________________
** The disk won't boot without COMMAND.COM (or the required "hidden" System
files we discussed above: IO.SYS and MSDOS.SYS). (Note: If you updated the
Windows 95/98 OS with any Y2K upgrades from Microsoft, make sure that your
COMMAND.COM file on the floppy has the same date as the one on your HD. My
new y2k COMMAND.COM boot file stats are: 93,974 bytes 02-19-99 10:55a .)
* These files are pretty much mandatory for the disk to be much good to anyone!
EDIT is used to make changes to a drive's CONFIG.SYS or AUTOEXEC.BAT files,
for example. ATTRIB and REGEDIT may be helpful for a Registry problem, etc.
M* These files are used to access memory above 640 kb (to install driver files, for
example). If you use any "devicehigh" or "loadhigh" (LH) statements in your
config.sys or autoexec.bat files, you must use these. Having them on the floppy disk
ensures you can boot-up the computer with access to upper and extended memory
even if the hard drive has been damaged.
C* This last file, "ATAPI_CD.SYS", is my DOS CD-ROM driver. You'll have to find
out what driver your CD-ROM drive needs to be accessible from DOS. ( If your
computer came with its own CD-ROM boot disk, start looking for the file there! )
Copy the files listed above from your Windows Directory's COMMAND folder (usually, C:\WINDOWS\COMMAND) onto your Boot Disk. In the Windows Explorer, you can highlight them and drag them onto the A:drive icon (do NOT depress the Shift key while doing so, or you'll erase them from your hard drive!) You can, of course, use one of the many other methods that may be more familiar to you. (Almost everything you need to do with your computer can be done in many different ways!)
There are two more files on my Boot Disk which are very important; especially if you intend to access a CD-ROM drive with it. You guessed it! They are:
AUTOEXEC.BAT and CONFIG.SYS
These files (see the examples below!) must be created by you 2 with a text editor. NOTEPAD will work just fine in this case (as long as you make sure the file extensions are actually saved as: .BAT and .SYS and not something like '.BAT.TXT.' Just check the filename after saving it. [Of course, you'll need to be able to see the file extensions first! You can read this page for help in doing that: Viewing File Extensions.] If you need to change it, simply highlight the filename, press the F2 key and edit it as necessary; or choose rename from the File menu... many different ways to do this as always!) You could also use the DOS editor, EDIT, which I highly recommend having on your boot disk. (If you've never used it before, you should set aside some time to learn about its features soon. Unlike the old one that came with previous versions of MS-DOS, this one can open multiple files and has a split-screen option!)
The following is a listing of the lines for these two files from my own boot disks (note that the last line in CONFIG.SYS which lists my CD-ROM "driver" must be changed to match your CD-ROM's driver file) :
CONFIG.SYS
===============
DEVICE=HIMEM.SYS /TESTMEM:ON
device=emm386.exe ram /noems
DOS=HIGH,UMB
DEVICEHIGH=ATAPI_CD.SYS /D:MSCD001 /P:1E8
AUTOEXEC.BAT
===============
@ECHO OFF
MSCDEX.EXE /D:MSCD001 /E /L:D /M:8
PROMPT $e[1;40;33m$p ...
If you do have a boot disk from your manufacturer, look for the lines with "MSCD" in the CONFIG.SYS file and "MSCDEX" in AUTOEXEC.BAT. It's probably best if you copy those lines exactly as they are into your own .SYS and .BAT (batch) files. Hopefully this means you will also find your CD-ROM "driver" on that disk as well ( look for a .SYS or .DRV file listed in that "MSCD" line in your CONFIG.SYS file and place a copy of it onto your new boot disk ).
I consider all the files on my boot disks to be useful. So, what do I do if there's another must have utility I just got and the Boot Disk is already full? Well, simply create another bare BOOT DISK and add the files you don't have on the first one! Making your EXTRA 'emergency disks' bootable too will save you from the hassle of having to swap the disks on those occasions that the computer needs to access the DOS COMMAND file again. (A good PC Tech will probably carry an assortment of disks full of programs to cover many different situations!)
If you created the files CONFIG.SYS and AUTOEXEC.BAT on your floppy disk along with the driver necessary to use your CD-ROM drive, then you should also test your boot disk to make sure you can actually access a CD after booting with the floppy. (Remember, once your hard drive fails to boot, it's too late!)
_________________
š My reasons for never using a full drive compression program should be obvious: Slower access times and the possible risk of not being able to recover any of my files! If you really must save some space on a drive, I suggest that you use some type of archiving program, such as WinZip(R), to compress folders or individual files rather than whole drives.