Hi Chris (please use plain text, non-html email), thanks for the feedback!
> 1) The options to create a bootable floppy disk from in the > install program didn't work. No command.com or kernel.sys > were copied. I could make a working bootable floppy disk > from the hard drive install. Maybe Bernd knows more about this...? > 2) I found no way to exit the install process when I was > done with installing a package series. It kept wanting me > to install packages that I had not selected, like games. It asks one series after another, but there are less than 10 series so it should not be too annoying that you have to do the selection for all screens...? > finally found it easier to use a base installation and > unzip all of the packages manually. I tried the installer > again, asking for a minimal install, and that worked fine. Using a base / minimal install should be the same as unzipping all base packages. Apart from the fact that unzipping is not the whole story - there is also stuff like SYSing and creating a config and autoexec for you. > I then manually added anything additional that I wanted That definitely works. If you use fdpkg instead of unzip, you also get dependency checks, but I myself prefer plain unzip, too ;-). > 3) No path was set to fdos\bin and I had to figure out > where the external commands were. Probably because you aborted / bypassed the installer. > small... Chkdsk reported that one 91k file was supposed to > be over 4000k! No good! That is a known bug in chkdsk - the files are actually okay, at least that is what dosfsck will tell you. Somehow chkdsk thinks that the files are 4 GB minus a multiple of 32 kB, at least this is what another user reported on the list 19dec2006. He reported the following sizes: 4 GB minus 1, 1.5, 3, 8.5, 9 and 14 times 64 kB, which is 2, 3, 6, 17, 18 and 28 times 32 kB. > "Edit" drove me nuts with forced saves until a user here > pointed out to use "Y" and "N" keys -- that works... Which key combinations did you try before using y and n? > The installer forces a FAT32 file system yet installs > "chkdsk" and "defrag" which don't work with FAT32. They are still useful because people are used to them and the tools can be used for diskettes and other disks, like usb drives... The installer does not force a particular fat file system, it just uses the fat partitions it finds. > can't get DOSFSCK to work on a SATA hard disk. I set it to > run with verbose switch so I could see what was going on. Did you try version 2.11b from my page? > Tried loading CWSDPMI as a TSR That should not be necessary... Note that somebody had the idea of including hdpmi of hxrt and renaming it to cwsdpmi which can be confusing :-(. Eric PS: Newest Defrag is supposed to work on fat32 but it is way too slow and easily runs out of courage before it gets the work fully done. At least it does so safely, afair... ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
