Hi Eric and the rest, Simply four coments about this (Eric, sorry to reply in public here).
(1) For the KEYB roadmap: there's just one important feature that I want for the final FD-KEYB 2.0, and it is the sound alert (beep) for these three cases: - COMBI where the combination is not possible for current codepage(e.g. ' + B ) - Buffer is full (the secondary buffer used with Strings, as for most of the cases I simply call BIOS to fill the primary buffer, so I guess BIOS will beep for me) - Beep command is issued. There was another feature that I wanted for FD-KEYB 2.0, and it would be to do the same trick you do for the CPX files, but applied to KEYBOARD.SYS and friends, so that many more space is saved (please Eric feel free to write to me a few lesson, I still don't understand how the CPX game works). About XT compatibility: this is actually done already in 2.0pre4, but as I haven't been able to test myself yet, I haven't updated the to-do list (if someone manages to report FD-KEYB 2.0pre4 working on PC/XT class machines, please let me know). However, you could consider overall that FD-KEYB is mature enough to be launched with FreeDOS 1.0. I am currently working on patching a couple of things on KC/KLIB (2) About DISPLAY/NLSFUNC et al. I am just finishing DISPLAY 0.13, the last version of this "driver" before it becomes a new driver (ver 1.0). It has all the changes planned for it before 1.0: many new changes (including a hard code re-structure, and new specs for writing specific codepage management sub-drivers), and some command-line changes, but there are few external changes. Eric, as I announced long time ago, there won't be interface changes in versions up to 0.99. Could you please produce a new MODE that admits version 0.13? (same behaviour as for 0.12). Both Henrique and I would be grateful for testing DISPLAY 0.13. I don't know the current status of NLSFUNC, but I think it is now using the same interface as MODE, which is good: for the final, the same kind of Generic IOCTL calls should be issued to ALL character device drivers (and not through the DISPLAY interrupt). (3) I see you are promoting some cleaning of the 1.0 to-do list, but I am a bit less optimistic: regardless of the features, there are still the bugs, that as far as I see, haven't in the majority being fixed/looked into. I would like to re-view re-post the list I published some months ago about it. (4) My 2€-c about 4DOS: there were some clains of it's being distributed under Open Source license, what's about that? Until this happens, I am for placing it into a 3rd party software. I am still dubious if it is convenient to include non-open source in the official distributions, regardless how useful it might be. Regards, Aitor PS: By the way, Eric, the NANSI bug is still open, and when DISPLAY 1.0 comes to light it might prevent DISPLAY.SYS and NLSFUNC to work properly. I reproduced the bug with MS-DOS. 2006/5/25, Eric Auer <[EMAIL PROTECTED]>:
Hi, I have the impression that the http://freedos.sourceforge.net/freecom/FreeCOM.html#-status page is far too pessimistic: Even 0.82pl3 does support - wildcard rename - swap to XMS without helper app - supports redirect / pipe in the XMS swap version - did I miss other issues? So the only remaining missing 1.0 feature is: - int 2e support (run shell commands by sending them to the master shell through the int 2e interface, so you do not have to start a new shell instance) Plus some 1.0 wishes: - use own I/O library - optimize for size, improve modularization and code sharing between modules, do strict _doserrno error handling... - LFN support... - load parts of the shell to HMA (if I understand "DOS=HIGH support" right) Comments please - I would like to update the FreeCOM.html file when I can find the time, so please send me suggestions about what should be changed. Thanks! Eric PS: I think we should add 4DOS to the distro - it is not open source but it is distrobutable and free as far as I can tell. And I hope it supports int 2e... Does it...? PPS: We would also need somebody who can add some smaller bug really useful bugfixes to FDISK and DEFRAG and SYS, anybody? ^-- but (I hope MEM and NLSFUNC will be okay... maybe somebody even does PRINT(Q)?) ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642 _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
