[Freedos-user] re: re: FreeDOS Post-1.0 todo list

2005-10-04 Thread Eric Auer
Hi Brolin, > As far as I know, you could not write a generic AC97 driver, because > AC97 only defines a standard for audio codecs to conform to... Good point. I just had a quick look at /usr/src/linux-2.6.11.4-20a/sound/{oss/ac97*.?,pci/ac97/*.?} (9k lines of C in 12 files) and it seems that muc

Re: [Freedos-user] re: FreeDOS Post-1.0 todo list

2005-10-04 Thread Brolin
Eric Auer wrote: "future DOS" - things for modern hardware and modern OS compatibility. Examples: long file names, PCMCIA, USB (drives, mice, keyboards...), AC97->SB16 virtual soundcard generic driver As far as I know, you could not write a generic AC97 driver, because AC97 only defines a

[Freedos-user] re: re: FreeDOS Post-1.0 todo list

2005-10-04 Thread Eric Auer
Hi Michael! > >"soon please" - would be nice to have that soon after FreeDOS 1.0, e.g. > > before 2.0, for example: several EMM386 / HIMEM features... > aka, none. EMM386 is quite deliberately versioned at 2.x because it's > moved beyond what is needed and necessary for a FreeDOS 1.0+ relea

Re: [Freedos-user] re: FreeDOS Post-1.0 todo list

2005-10-04 Thread Aitor Santamaría Merino
Hi, Eric Auer escribió: Hi, I would suggest an extra column for the tables in the post 1.0 TODO list: Level / State of the wish. Example values: [ http://wiki.fdos.org/Main/Post_1_0_Todo ] I seem to like the idea of the categories , although I'd personally review what anyone puts anywhere.

Re: [Freedos-user] Forensic FreeDOS version determination?

2005-10-04 Thread Arkady V.Belousov
Hi! 4-Окт-2005 17:16 [EMAIL PROTECTED] (Andre Tertling) wrote to freedos-user@lists.sourceforge.net: AT> Ah! I already saw the UPX! signature but didn't find the usual header. AT> Is the kernel using a customized upx engine? No. But kernel image customized after upx to make it .sys-able. Bu

Re: [Freedos-user] re: FreeDOS Post-1.0 todo list

2005-10-04 Thread Michael Devore
At 01:11 PM 10/4/2005 +0200, Eric Auer wrote: "soon please" - would be nice to have that soon after FreeDOS 1.0, e.g. before 2.0, for example: several EMM386 / HIMEM features aka, none. EMM386 is quite deliberately versioned at 2.x because it's moved beyond what is needed and necessary

Re: [Freedos-user] Forensic FreeDOS version determination?

2005-10-04 Thread Arkady V.Belousov
Салям! 4-Окт-2005 17:10 [EMAIL PROTECTED] (Robert Riebisch) wrote to freedos-user@lists.sourceforge.net: >>You can't, because kernal image along with all textial information >> inside it is packed (by UPX). RR> He could check sum the files and compare these with some predefined RR> values

Re: [Freedos-user] Forensic FreeDOS version determination?

2005-10-04 Thread Andre Tertling
Ah! I already saw the UPX! signature but didn't find the usual header. Is the kernel using a customized upx engine? At least it is UPX and no proprietary algorithm. :) How does the data get packed at compilation/linking time? Regards, Andre Arkady V.Belousov wrote: Hi! 4-Окт-2005 16:44 [EM

Re: [Freedos-user] Forensic FreeDOS version determination?

2005-10-04 Thread Robert Riebisch
"Arkady V.Belousov" wrote: >You can't, because kernal image along with all textial information > inside it is packed (by UPX). He could check sum the files and compare these with some predefined values. Of course a lot work, because he has to know nearly *every single* kernel version for

Re: [Freedos-user] Forensic FreeDOS version determination?

2005-10-04 Thread Arkady V.Belousov
Hi! 4-Окт-2005 16:44 [EMAIL PROTECTED] (Andre Tertling) wrote to Freedos User Mailinglist : AT> I am in the odd situation that I need to determine the FreeDOS version AT> of a given bootdisk without booting it. I already found that FreeCom can AT> display the version, but only if FreeDOS is runni

[Freedos-user] Forensic FreeDOS version determination?

2005-10-04 Thread Andre Tertling
Hi everybody, I am in the odd situation that I need to determine the FreeDOS version of a given bootdisk without booting it. I already found that FreeCom can display the version, but only if FreeDOS is running. So I guess it retrieves the version information from the FreeDOS kernel. So where c

Re: [Freedos-user] re: FreeDOS Post-1.0 todo list

2005-10-04 Thread Bernd Blaauw
Eric Auer schreef: Hi, I would suggest an extra column for the tables in the post 1.0 TODO list: Level / State of the wish. Example values: Category "deprecated" you mean? That would mean the functions are not implemented. With or without commandline compatibility? (parameter accepted but no

[Freedos-user] re: FreeDOS Post-1.0 todo list

2005-10-04 Thread Eric Auer
Hi, I would suggest an extra column for the tables in the post 1.0 TODO list: Level / State of the wish. Example values: [ http://wiki.fdos.org/Main/Post_1_0_Todo ] "legacy" - MS DOS had it, but nobody needs it anymore. For example: DRIVER / DRIVPARM (for tape drives, for forcing "disk change

Re: [Freedos-user] FreeDOS Post-1.0 todo list

2005-10-04 Thread Bernd Blaauw
Michael Devore schreef: No way I can see to discuss a page so that I can record a comment, for example, that notes most of the remaining EMM386 option to-do list is unnecessary, superseded, or no longer applicable. Not appropriate to just yank them out of there unilaterally. And pretty much

Re: [Freedos-user] FreeDOS Post-1.0 todo list

2005-10-04 Thread Michael Devore
At 11:19 PM 10/3/2005 -0700, Blair Campbell wrote: Hi. Just wanted to let everyone know that I've copied the Post-1.0 todo list to the FreeDOS wiki so that everyone can view and edit the list of items. It is available at: http://wiki.fdos.org/Main/Post_1_0_Todo No way I can see to discuss a

Re: [Freedos-user] FreeDOS Post-1.0 todo list

2005-10-04 Thread [EMAIL PROTECTED]
Many thanks, Blair. Just one word on the list: I know what some people may be thinking of some of the items there. I would like to suggest that the list be used to track the features that are not available in FreeDOS and are not to be implemented in FreeDOS in a short time or even never (e.g. D