Hi, Eric!
PA is short for Pennsylvania in the USA
I sure will send bug reports and help out! Will try
jemm386 on my test system and let you know....
What went wrong with install and such?? Some examples as I
had no problem running from LiveCD:
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.
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. I
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. I
then manually added anything additional that I wanted after
that.
3) No path was set to fdos\bin and I had to figure out
where the external commands were. No biggie, saw "bin"
subdirectory and knew they were there. Many people I know
don't know to look there.
4) I wiped all clean at one point and tried a FAT16 hard
drive install after using MS-DOS fdisk and format. All
seemed okay... ran chkdsk which of course ran under FAT16
but told me that files which I knew were okay were too
small... Chkdsk reported that one 91k file was supposed to
be over 4000k! No good!
Other stuff:
"Edit" drove me nuts with forced saves until a user here
pointed out to use "Y" and "N" keys -- that works... I
forget that I don't use a mouse with DOS, only keyboard ...
my principle DOS application doesn't use a mouse... only key
combinations for commands and menu navigation.
The installer forces a FAT32 file system yet installs
"chkdsk" and "defrag" which don't work with FAT32. This
threw me at first until I dug into the help system. I
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.
It does its intitial check of the drive and then seems to
hang up on checking for bad clusters. I let it run for an
hour. I tried installing FreeDOS on another PC, an old
Compaq deskpro C400 that I had laying around. DOSFSCK did
run fine on that system's hard disk. The difference between
the two? The old Compaq has IDE hard drive, while SATA
drives are in the system that failed.
Tried loading CWSDPMI.EXE as a TSR -- the "help" file says
"-p" for the permanent TSR load but it's really "-r"
instead. Thinks like that which make you go back and edit
stuff.
I'll post more as I find it but I cannot run FreeDOS until
I can work out a functional file system check and repair
utility.
-------------------------------------------------------------------------
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
