FreeDOS beta9 Service Release #1 (2004-11-30) Readme file Table of Contents: --------------------------------- I) How to view this document II) What to get, platform dependant III) How to boot up IV) Installation V) Post-installation disk/RAM layout and configuration files VI) Using FreeDOS VII) Updates and help --------------------------------- I - How to view this document This document is posted online and thus may incidentally not comply with the DOS specification of keeping line width below 80 characters. We recommend using a HTML viewer or the FreeDOS program PG, which supports line wrapping, found at http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/file/pg/ --------------------------------- II - What to get, platform dependant The FreeDOS distribution is available in several ways. Users only wanting to use the kernel don't need to download the entire distribution. Owners of a computer older than 80386 often don't have a cdrom drive in their systems. FreeDOS Beta9 Service Release #1 is offered for: Platform: what to download: --------------------------------------------------------------------- 8086/80186/80286 : - download diskette distribution if available http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/old/beta9sr1/disksets - alternative #1: download ODIN (One Disk INstaller) http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/old/beta9sr1/disksets/ODIN - alternative #2: download zipfile and split onto disks: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/old/beta9sr1/disksets/zipfiles - alternative #3: get FreeDOS install disk http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/old/beta9sr1/fdos1440.img There are no known cdrom drivers for pre-386 systems, please contact us if you have a pre-386 system equiped with a CD or DVD drive, so we might consider writing a cdromdriver for these old systems. 80386 or newer : - download the bootable freedos installer cdrom http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/old/beta9sr1/fdbootcd.iso We recommend to boot from the cdrom as our open source cdrom driver (atapicdd.sys , ALPHA status) is still in experimental stage. Developers welcome! If you boot from cdrom then a stable special driver is used, called ELTORITO.SYS If you cannot boot from cdrom, please download bootdisk http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/old/beta9sr1/fdos1440.img The bootdisk can access the FreeDOS cdrom, an ISO version of it placed on harddisk, (C:\FDBOOTCD.ISO) or the files from the cdrom if extracted to a directory on harddisk Replace our cdrom driver with the vendor-supplied one if desired, by renaming the driver to ATAPICDD.SYS and overwriting the ATAPICDD.SYS that's already on the diskette [ e.g. http://www.opus.co.tt/dave/indexall.htm ] This special bootdisk also allows you to boot from cdrom, even if your computer's BIOS (Basic Input/Output System) does not allow it (mainly 80386 and 80486 systems). Just select Smart Boot Manager from the 386+ menu and select CDROM. This program also seems to help against a crashing FreeDOS due to badly designed/programmed PC BIOS. You may need to write the bootdisk image to a diskette using one of several available programs found at: http://www.fdos.org/ripcord/rawrite/ (RAwrite downloadable from : http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/old/beta9sr1/rawrite.exe ) If the target diskette contains information, it will be erased when writing the image contents to the diskette. The .iso file (ISO9660 filesystem) can be written to a blank recordable medium [CD-R(W) or DVD+/-R(W)] using a cd writing program that can write a disk image. Most used is Ahead's Nero Burning Rom, and the Unix/Linux program CDrecord Make sure contents of the fdbootcd.iso file is stored on the written medium, not the file itself. In other words, you should see a file called autorun.inf and the directories called FREEDOS and ISOLINUX, and *not* a file with the extension ISO (example: FDBOOTCD.ISO) --------------------------------- III - How to boot up Virtually all the computer systems that FreeDOS can be installed on allow booting from another medium than the harddisk. This is required for installing FreeDOS to your harddisk. Old computers support diskette booting, recent computers also support starting up from cdrom (the so called El Torito standard dating from 1995) If you cannot boot from cdrom or do not know how to set up your BIOS settings (most systems use DEL, ESC, F2 or F10 keys to access the BIOS) to allow booting from cdrom, please boot from diskette. If you are able to get your system to allow booting from cdrom, that's the easiest and best way of installing FreeDOS. Type "1" at the BOOT: prompt and then you'll see FreeDOS starting. You should now see another menu. Select option 1 to load memory and cdrom drivers. the CDROM is accessed and then you can select what to do next (Install FreeDOS, Run FreeDOS, Create bootdisk), but more about that later. First the floppy explanation. For booting from diskette, insert the diskette to which you have written the contents of FDOS1440.iIMG using WinImage or Rawrite for example. You should now see a boot menu with 2 options: *Select 1 (default and started if waiting 10 seconds) to gain access to additional options for recent computers only (386 or newer). In the follow-up menu: *entering 1 followed by ENTER boots up a faster version of the bootdisk (bootdisk is read into system RAM and then started) *entering 2 followed by ENTER allows you to test your system's RAM for potential errors, using the Memtest86+ program, now at version 1.26 *entering 3 followed by ENTER starts the Smart Boot Manager. it is here that you can select to boot from the cdrom device, even on systems which BIOS's won't allow this (mainly 386 and 486 computers) see above at cdrom description how to go on. *Select 2 (most compatible) to load FreeDOS from the cdrom. see below on how to work with FreeDOS once you see the menu that offers driver and cdrom loading. Working with FreeDOS: you'll see 2 menu entries, so you need to select the correct one. Option 1 loads FreeDOS in default configuration, loading all drivers which can speed up the installation process. Option 2 loads FreeDOS in safe mode. This mode is useful for things like updating system BIOS and/or firmware, or troubleshooting if you are an experienced DOS user. It's possible to continue the installation procedure by typing SETUP. Almost no drivers will be loaded. -if the cdrom is found, you'll be presented with a new menu (1: Install, 2:Run from cdrom, 3:Create Bootdisk). -if the cdrom is not found, you'll be presented an error message (cdrom driver not loaded, cdrom not found) you get the chance to specify where the setup files can be found (a directory on harddisk, precopy the contents of the cdrom before starting installation), doing a diskette install (if made available by the FreeDOS project), specifying an ISO file which contains the wanted setup files (enter correct path+filename) or giving up (you're on your own then). Installation through using the harddisk (either ISO file or a directory with setup files) is the fastest and most stable way of installing FreeDOS. As we allow dualbooting with popular operating systems, you might want to place the FreeDOS files on harddisk first to experience a smooth installation process. see chapter IV - Installation for further info. --------------------------------- IV - Installation Regardless of which way you booted, installing FreeDOS is made up of several steps. If you want (or need) to change your disk layout (using a partitioning program) , you will need to reboot at least once in this process. These are the steps you need to follow: 1) Partition your harddisk (not recommended unless necessary!) 2) Create a filesystem (not recommended unless necessary!) 3) Install and configure FreeDOS core files and additional files. Step1: (not recommended unless necessary!) You can change your disk layout by using any partition program. most known ones are Fdisk ("program for Fixed Disks") and the Partition Magic product from the company Symantec (was PowerQuest Partition Magic). Other often used programs are FIPS (DOS, freeware) and PARTED (Linux, GPL). A program called NTFSRESIZE might also be usefull if your harddisk was partitioned as a single primary partition of the NTFS filesystem type. DOS *requires* a primary partition with the FAT filesystem that it recognizes as C:. Having a C: partition under your modern Windows system using NTFS is not suitable, as DOS won't recognize that partition, let alone assign a driveletter (C:) to it! KNOW WHAT YOU ARE DOING - ALTERING DISK PARTITION LAYOUT CAN CAUSE DATA LOSS FreeDOS provides its own version of FDISK, called FreeFdisk. Here's what you need to do: *Answer yes to the first question (do you want support for FAT32 (big disks?)) *Create some free (actually unpartitioned) disk space by making sure not all disk space is allocated. *Create a primary partition in the unallocated space, at least 20 MegaBytes (option 1, then option 1), though we recommend at least 40MB *Set it active (option 2 from the main menu) *Exit FDISK. You will probably have to reboot. Be sure to boot from the same boot device again (diskette/cdrom) Step2: (not recommended unless necessary) Once an (active primary) FAT partition exists, FreeDOS detects this and assigns a driveletter to it (starting with C: for the first FAT partition on the first physical harddisk). However it still allows to change disk layout by calling the supplied FDISK. and offers you to format the partition. If the partition was not yet formatted then FreeDOS auto-formats it. If it was formatted, we recommend not to format the partition again, as it may contain programs and data you wish to keep (creating the FAT [File Allocation Table] filesystem using the FORMAT program erases all previous contents) Step3: Once the active primary partition actually contains a filesystem, be it already present or just created through the FORMAT program, it will allow you to install FreeDOS using the installation program. The installation program is intuitive to use, though you should type in a pathname (C:\FDOS for example) instead of a drive/driveletter (C:). If you specify the latter, all files end up in the root of the drive, instead of its own directory. We recommend to opt for a destination directory on drive C:, to have the FreeDOS system files and the rest of the files on one single partition. Be aware that DOS numbers partitions in a different order than other operating systems. Also only FAT(12/16/32) filesystems are recognized and accessible through an assigned driveletter, not NTFS/HPFS/EXT2, etc.. All selected files are copied to the selected installation directory, the core components installed (kernel - c:\kernel.sys ; shell - c:\command.com) and several startup files are created. See following chapter for that. All is done now, you have installed FreeDOS to harddisk and can start using it. We recommend to reboot your system though for best use. Also remove any installation discs to make sure you boot from harddisk. If booting from harddisk fails, then a critical piece of program code called the 'boot sector' was not (properly) written to harddisk. In that case, boot from your installation disc, select a clean boot, and enter the following command (followed by pressing ENTER): A:\FREEDOS\SYS C: C: /BOOTONLY --------------------------------- V - Post-installation disk/RAM layout and configuration files This chapter references the layout of both files and memory layout, on diskette, cdrom and the harddisk installed FreeDOS distribution. Feel free to skip this chapter immediately or after the harddisk disk layout and conventional memory layout. * Memory layout (below 1MB) when maximizing free conventional memory, using the FreeDOS EMM386 driver. Layout obtained from "MEM /C /P" Name Total Conventional Upper Memory -------- ---------------- ---------------- ---------------- SYSTEM 16,192 (16K) 9,888 (10K) 6,304 (6K) HIMEM 2,480 (2K) 2,480 (2K) 0 (0K) EMM386 3,200 (3K) 3,200 (3K) 0 (0K) COMMAND 3,264 (3K) 2,944 (3K) 320 (0K) DISPLAY 11,648 (11K) 0 (0K) 11,648 (11K) KEYB 1,536 (2K) 0 (0K) 1,536 (2K) MOUSE 3,328 (3K) 0 (0K) 3,328 (3K) Free 693,296 (677K) 634,512 (620K) 58,784 (57K) * Harddisk layout for a fresh installed FreeDOS distribution: C:\ Root of active FreeDOS FAT partition | AUTOEXEC.BAT Bootup script, contents see below. | COMMAND.COM Shell (FreeCOM), translated if possible | CONFIG.SYS FreeDOS configuration file | FREEDOS.BSS Bootsector of drive C: stored in file | KERNEL.SYS FreeDOS kernel, version 2.0.35 or newer | \--FDOS FreeDOS directory | +--INSTBASE GUI installer logfiles | +--TEMP Directory for storing temporary files | +--APPINFO Contains the Linux Software Maps (LSM files). See below | +--BIN Contains FreeDOS programs and drivers | | +--CTMOUSE CuteMouse available in several languages | | \--KEY keyboard layout files for KEYB 2.0, zipped(!) | +--DOC Contains documentation for each program, in own directory | +--HELP Stores the help-files for freedos support program | | \--HHSTNDRD called HELP. Files support a subset of the HTML format | +--NLS contains localized help text for some programs | \--CPI International CodePages for FreeDOS, in compressed format Many DOS operating systems use the files c:\autoexec.bat and c:\config.sys Therefore FreeDOS will, if another DOS-based operating system is detected, use other system files instead: c:\fdconfig.sys instead of c:\config.sys fdauto.bat in your FreeDOS installation directory, instead of c:\autoexec.bat If FreeDOS SETUP detected WindowsNT/2K/XP/2K3, then C:\BOOT.INI will contain a menu entry to startup FreeDOS. If a DOS based operating system was detected, then file METAKERN.SYS will be in your root directory of C:. It contains the entry for booting your other DOS, and an entry to boot FreeDOS. The LSM files can be found through http://www.freedos.org/freedos/software/ example: http://www.freedos.org/freedos/software/lsm.cgi?q=v&a=base/kernel.lsm * Created Config.sys bootup file (c:\config.sys or c:\fdconfig.sys): ( "!" means always execute, ";" is a comment, "123?" is menu implementation) ( our cdrom driver is disabled, as we recommend the VIDE-CDD.SYS from BENQ ) !SET dosdir=C:\FDOS !SET lang=NL ;for help on commands, see file config.sys in your FreeDOS directory ;www.benq.com/ss_download/drivers/storage/cd-rom/drivers/dos/apicd214.exe ;below is a demonstration of the FreeDOS multi-configuration menu system. !LASTDRIVE=Z !BUFFERS=20 !FILES=40 !DOS=UMB !DOSDATA=UMB !set dircmd=/ogn !MENUCOLOR=7,0 MENUDEFAULT=1,5 MENU 1 - Load FreeDOS with maximum RAM free, using EMM386 MENU 2 - Load FreeDOS including HIMEM XMS-memory driver MENU 3 - Load FreeDOS without drivers 1?DOS=HIGH 12?DEVICE=C:\FDOS\BIN\HIMEM.EXE 1?DEVICE=C:\FDOS\BIN\EMM386.EXE VDS NOEMS X=TEST ;1?DEVICE=C:\FDOS\bin\atapicdd.sys /D:FDCD0001 12?SHELL=c:\command.com /K c:\autoexec.bat 3?SHELL=c:\command.com /D /K set path=C:\FDOS\bin (note that cdrom driver has been disabled. Remove the ;REM part from atapicdd, or download the VIDE_CDD.sys file from above named APICD214.exe link) * Created Autoexec.bat bootup file (c:\autoexec.bat or \freedos\fdauto.bat), including basic sound support and drivers for keyboard, cdrom and mouse: (display driver configuration is an example, and commented out by default) (at the end you see some text in Dutch, to demonstrate localized parts) @echo off set PATH=%dosdir%\bin set NLSDIR=%dosdir%\NLS set temp=%dosdir%\temp set tmp=%dosdir%\temp SET BLASTER=A220 I5 D1 H5 P330 Shsucdx /D:?FDCD0001 /D:?FDCD0002 /D:?FDCD0003 LH DISPLAY CON=(EGA,,1) MODE CON CP PREP=((858) %dosdir%\cpi\EGA.CPI) MODE CON CP SEL=858 LH KEYB US,,C:\FDOS\bin\KEY\US.KL echo typ HELP om ondersteuning te verkrijgen over opdrachten en navigatie echo. echo FreeDOS heet u welkom. echo. MOUSE * FreeDOS downloadable Bootdisk RAM contents (Modules using memory below 1MB): (note that EMM386 is not enabled by default, as EMM386 settings are specific to each individual computer system) Name Total Conventional Upper Memory -------- ---------------- ---------------- ---------------- SYSTEM 17,600 (17K) 12,480 (12K) 5,120 (5K) HIMEM 2,112 (2K) 2,112 (2K) 0 (0K) EMM386 2,608 (3K) 2,608 (3K) 0 (0K) UDMA 624 (1K) 624 (1K) 0 (0K) COMMAND 3,984 (4K) 0 (0K) 3,984 (4K) SHSUCDX 6,656 (7K) 0 (0K) 6,656 (7K) ELTORITO 3,104 (3K) 0 (0K) 3,104 (3K) CDRCACHE 6,016 (6K) 0 (0K) 6,016 (6K) Free 792,464 (774K) 637,136 (622K) 155,328 (152K) * FreeDOS downloadable Bootdisk image file contents: (identical to FDBOOT.IMG used on this disk and cdrom) A:\ Root of diskette(-image) | README.TXT FreeDOS readme document | METAKERN.SYS FreeDOS bootmanager | LDLINUX.SYS Syslinux bootloader | SYSLINUX.CFG Syslinux configuration file | MT86v140 Memtest+ version 1.40 (www.memtest.org) | SBM.CBT Smart Boot Manager compiled as Syslinux module | MEMDISK Syslinux RAMDISK DISK-image loader | FDBOOT.IMG 360KB FreeDOS bootimage for MEMDISK | KERNEL.SYS FreeDOS kernel/core, development release | COMMAND.COM FreeDOS command interpreter / shell (FreeCOM) | FDCONFIG.SYS FreeDOS bootup configuration file | +--FREEDOS Directory containing freedos applications | APPEND.EXE Mounts drive + contents into empty directory | CHOICE.EXE Required for menu options | FDAUTO.BAT Bootup script, called from fdconfig.sys | FDISK.EXE The "Fixed Disk" partitioning program | FDISK.INI Configuration file for Fdisk | FORMAT.EXE Creates FAT (FAT12/FAT16/FAT32) filesystem | GETARGS.COM Detects if Iso/Sys-Linux was loaded with Memdisk | HDD.BAT Wrapper for textmode diskette installation | INIADD.COM Adds a line of text if keyword is not found in INI-file | LOCALIZE.COM CATS implementation for displaying text from file | LOCATE.COM Finds the FreeDOS directory | META-ALL.BIN MetaKern bootloader primary stub | METABOOT.BOT MetaKern bootloader freedos kernel loader | OSCHECK.COM Detects populair already installed operating systems | SYS.COM Transfers FreeDOS core files and makes disk bootable | +--DRIVER contains FreeDOS drivers | ATAPICDD.SYS cdrom driver, alpha-status | CDRCACHE.SYS cdrom caching module | DEVLOAD.COM Commandline device driver loading utility, UMB support | ELTORITO.SYS Bart Lagerweij's boot-from-cdrom cdrom-driver | HIMEM.EXE XMS driver for 386 and newer, up to 2048MB RAM | LBACACHE.COM XMS read-cache for harddisks and physical floppy drives | SHSUCDHD.EXE Mounts an ISO file as if it was a physical cddrive+disk | SHSUCDX.COM Provides driveletter to each cdrom drive (MSCDEX) | UDMA2.SYS Speed up harddisks by using UDMA and background transfers ***** Other tools in the directory called SPECIAL: ***** | GPL.COM The General Public License as self-displaying document | XCOPY.EXE Copies files and directories | LABEL.EXE Sets the label of a disk partition (11 characters max) | PG.EXE advanced textfile viewer (without optional plugins) | EDIT.EXE textfile editor (optional plugins omitted though) | MEMTEST.EXE Memtest version 1.30, loadable from DOS | LOADLIN.EXE Allows to start Linux from DOS. | ATTRIB.COM (Re)sets file and directory attributes | CALLVER.COM Fakes DOS version for a specific file you load | COPYBS.COM Dumps bootsector, just like OSCHECK, but unconditionally | FDXMS286.SYS For 286 (and newer), max 16 mb (on 386 64 mb) ram | ATAPICD2.SYS Incomplete newer test version of ATAPICDD.sys | EMM386.EXE Memory optimizing driver providing UMB and EMS | CTMOUSE.EXE CuteMouse serial/PS2 mouse driver | TICKLE.COM Data prefetch program for floppy disks, for LBACACHE * CDROM image contents [CDROM] | BOOT.CAT MKISOFS's El-Torito Boot Catalogue | AUTORUN.INF auto-launch file for Windows | +--FREEDOS FreeDOS specific files | +--3RDPARTY (Freeware/GPL) third party addons | +--DOCS Various important documents | | | | | +--LICENSES useful License Stuff | | +--MOREINFO additional documents covering advanced topics. | | | +--PACKAGES installable programs | | +--BASE FreeDOS basic components | | | +--DISK01 disk#1 up to and including disk#8 | | | | | \--SRC_BASE Sourcefiles for basic components | | +--DISK01 Sourcefiles for kernel | | +--DISK02 Sourcefiles for FreeCOM | | +--DISK03 Sourcefiles for Defrag | | +--DISK04 Sourcefiles for FreeDOS programs | | +--DISK05 (up to 12) Disk#5 up to disk#12 | | | | | \--SETUP | +--BATCH | | AUTORUN.BAT FreeDOS batch logic for menu's | | BOOTDISK.BAT Creates a FreeDOS bootdisk | | MENU1.BAT Handles user output for menu 1 | | MENU2.BAT Handles user output for menu 2 | | TEXTMENU.BAT Handles Fdisk/Format/Installer | | | +--ODIN FreeDOS programs usable without installing first | | | | | +--KEY Keyboard layouts for non-US keyboards | | +--CPI Contains some compressed international codepages | | | +--INSTALL | | | INSTALL.EXE Graphical User Interface installer, | | | INSTALL.INI by Sergej Kozlovich | | | INSTALL.MIN specify which disksets to present | | | INSTALL.TXT required by GUI installer | | | LICENCE.TXT required by GUI installer | | | TEXTINST.EXE Textmode (fallback) installer, JeremyD | | | in case GUI fails to create \fdconfig.sys | | | or for (8086/186/286) systems without cdrom | | | | | +--DE Translated text-files, German | | +--EN Translated text-files, English | | +--ES Translated text-files, Spanish | | +--IT Translated text-files, Italian | | \--NL Translated text-files, Dutch | | | +--LANGUAGE Long installation textfiles, | | +--DE translated into German, | | +--EN English | | +--ES Spanish | | \--NL Dutch | | | \--NLS Translated texts for batchfile use | \--ISOLINUX Isolinux bootloader (isolinux.zytor.com) | ISOLINUX.CFG Isolinux menu configuration file | MAKEISO.BAT ISO9660 creation batchfile for Windows | ISOLINUX.BIN Isolinux non-emulation mode bootloader | +--DATA | BOOTMSG.TXT Welcome screen if booting from cdrom | F1_HELP.TXT Tells user which keys to press | F2_LICEN.TXT Tells user FreeDOS distributed under GPL | FDBOOT.IMG FreeDOS bootup disk image, 360KB | F_ABOUT.TXT About FreeDOS | LOGO.LSS Splashscreen you see when booting cdrom | MEMDISK RAMDISK Loader for (diskette) image files | +--BUILDCD | COMMAND.COM FreeCOM, DOS/Win9x shell too limited | PARAMS.TXT Contains additional required MKISOFS options | MKISOFS.EXE MKISOFS cdrom image creation program, DOS DJGPP/CWSDPMI/386+ --------------------------------- VI - Using FreeDOS We must assume you are familiar with the DOS operating system. This README document is not the place to explain that. You can get help in the following ways: *HELP *programname /? *HELP programname *FASTHELP programname *read documents located in the DOC subdirectory of your installation directory if that's not enough to help you, feel free to submit your problem or question to the FreeDOS user's list. See end of this document for the email address. --------------------------------- VII - Updates and help -If you would like to see what software parts need improvements, have a look at http://fdos.org/ripcord/fdos_1_0/official/todos.htm -A newer FreeDOS distribution may be found at www.freedos.org/freedos/files/ -Updated software is available from http://www.freedos.org/freedos/software/ -The FreeDOS kernel may be updated by replacing C:\KERNEL.SYS with a newer version, which can be obtained from: [official release] http://sourceforge.net/project/showfiles.php?group_id=5109 [weekly from CVS ] http://fdos.org/bootdisks/ [daily from CVS ] http://fdos.org/kernel kwc8632.dev.zip or compiled (use OpenWatCom 1.3 for example) from sources: [daily CVS source ] www.fdos.org/kernel ( kernel.UNSTABLE.zip ) -Bugs may be reported at the FreeDOS bug database [ http://www.freedos.org/bugs/bugzilla/ ], or at the developer's mailinglist [ read: http://sourceforge.net/mailarchive/forum.php?forum=freedos-devel ] [ subscribe to: http://www.freedos.org/freedos/lists/ ] [ send message: freedos-devel@lists.sourceforge.net ] for general help please consult the FreeDOS user mailinglist, [ read: http://sourceforge.net/mailarchive/forum.php?forum=freedos-user ] [ subscribe to: http://www.freedos.org/freedos/lists/ ] [ send message: freedos-user@lists.sourceforge.net ] IRC chat is also provided (irc.i7c.org , channels #fd-user and #freedos ), use a IRC client (Mozilla, mIRC, etc) to connect to the IRC chat. thank you for reading this lengthy document, and enjoy FreeDOS :) Bernd Blaauw, 2004-11-30