Eric Auer schreef:
DEFRAG was taken off the list, because so many freeware / shareware /
commercial defraggers exist - or because many people run FreeDOS in a
DOS emulator like VMWare or DOSemu, and defraggers aren't needed...
Jim means defraggers for DOS? FreeDOS may still aim at the embedded
market. Proof for this was Lucho working on the kernel :)
Reasonably modern computers (Pentium and newer) might be able to run
ReactOS in due time and run win32 defraggers. However built-in defrag
program for DOS is still usefull for very small or very basic systems.
I'm glad that on the next FreeDOS distro all you would need to use an
ancient PC is a diskette drive and an internet connection.
This would allow abandoned systems to be in use so fast..
no need to transfer files to the harddisk, no need to burn an ISO and
then find out the old cdrom drive cannot read any (burned) CD/DVD.
'Compatibility' is mainly a matter of getting KERNEL, HIMEM and EMM386
working quite a lot like in MSDOS. To a lesser extent having FreeCOM
emulating other popular shells like MS COMMAND.COM, and the one from
DRDOS, and last but not least 4DOS. Not each of them 100% ofcourse, as
4DOS can be a memory hog :)
http://wiki.fdos.org/Main/Todo_1_0
- can somebody name a few tools for which the wrong errorlevels are
returned? I assume it would not be too hard to fix them. Which EL are
used by DYNALOAD, by the way? http://wiki.fdos.org/Main/ExitCodes
http://home.earthlink.net/~rlively/MANUALS/INDEX.HTM
seems like a nice and usefull template.
Also the FDOS wiki should have a section on current popular DOS software
and how to get it working on a bootdisk.
Arachne, NTFS4DOS, maybe Supaplex or Stunts or so, Mark's radio program,
etc..
- are there still tools which display DATE/TIME without using COUNTRY
settings, or fail to do COUNTRY stuff for alphabetic sorting and upcase
or downcase (except EDIT 0.7d "upcase/downcase block" functions ;-))?
I know, we also ask for COUNTRY-defined NUMBER formatting, but we would
already know a lot if we know that ONLY NUMBER formatting is still TODO.
How should people know? There's still no official NLS-aware FreeDOS
subsystem released.
-no official released kernel has support for KERNEL.SYS
-country.sys is still only available at Jeremy's site, for development
kernel.
-nlsfunc 0.0.1 doesn't generate errorlevels, my received binary 0.0.2(?)
does so.
-new DISPLAY, KEYB and MODE aren't released officially yet.
-CHCP is included in the FreeCOM 0.84(pre), also not released yet.
- Jeremy, any ATAPICDD news? :-)
I'm using WGET to obtain the VIDE-CDD.SYS driver, but a true public
domain or GPL cdrom-driver would be better.
- Aitor has bold plans with KEYB, as usual
- do we really need local buffers for SHSUCDX? Or is CDRCACHE enough?
No buffers needed, see Jason's notes in the SHSUCDX package.
/M:nn is accepted though by SHSUCDX, but no inner working.
If you feel like transforming CDRCACHE into a patch for adding XMS
buffers into SHSUCDX, go ahead. I'm pretty sure Jason will accept it if
you release it as public domain (shsucdx is freeware).
- What are experiences with Jason's RAMDISK, good enough to drop TDSK and
even stop using the closed source XMSDSK? Former definitely, but latter?
for DOS uses, Jason's diskdriver will be fine instead of XMSDSK.
For cooperation with Windows9x, and even installing Windows9x on the
ramdrive, I don't know how reliable Jason's driver is.
- DEFRAG, what happened to Imre?
- FDISK, I assume Brian and Jeremy are working on the repair?
- FORMAT, please report any remaining bugs.
no working bootsector installed. MS format *does* write a bootsector
which can start IO.SYS. No more SYS needed :)
FreeDOS FORMAT relies on (FreeDOS) SYS for bootsector stuff.
There's no way to pass arguments to FORMAT so it will instruct SYS to
behave in another way.
- SYS, bugs will usually be related to BIOS drive number and 8086 compat?
-fat16 and fat32 bootsector not working.
-cannot check current directory for which file is actually a valid
kernel file.
-copies %COMSPEC% to diskette even if it's WIN32 CMD.EXE/COMMAND.COM
- MEM, good that David is working on it :-).
Yes, though no idea what he's planning to change/add
- SETVER, not same as CALLVER, but nobody seems to have any copies of
the FREEVER binary left? We already know that the sources are lost.
disassembling a binary which is the result of viewing leaked MS sources?
FREEVER should be inside FreeCOM, or completely independent of it.
PS: Note that the 1.0 list does not ask for Weitek support in EMM386 :-).
Bernd
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
