Re: [Freedos-kernel] Re: FreeCOM
I vote for it, please... Alain In other words: Only for non-multiconfig we would waste 4 bytes per environment for the sake of being compatible to all programs! I think we *must* pay this price, even though mathematical logics tell use the programs *should* accept \0c:\freecom.com\0 after all. Please re-add such a workaround (old string was PATH=.\0 I think) instead of forcing us to upgrade all versions of FreeCOM and possibly also other programs. I think saving four bytes of kludge RAM are not worth forcing us all to upgrade FreeCOM. Eric --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: FreeCOM
Hi! 22--2004 21:44 [EMAIL PROTECTED] (Alain) wrote to [EMAIL PROTECTED]: A I vote for it, please... Please re-add such a workaround (old string was PATH=.\0 I think) If you will read letters here carefull, you will see, that I already do this. --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_idG21alloc_id040op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] Re: FreeCOM
Hi, even though you now have an (0.82pl3w? Testing, unstable!)
FreeCOM, you STILL should waste those FEW BYTES in the environment
to maintain FreeCOM compatibility!
There is TRANSLATED FreeCOM, STABLE FreeCOM, DEBUGGING FreeCOM,
NON XMS SWAP FreeCOM, and possibly many other reasons why people
cannot upgrade to the FIXED FreeCOM. Still they want to be able
to test your kernel, even with F5 mode!!!
Problem:
some=var\0other=var\0\0c:\freecom.com
- works with BOTH smartdrv and all FreeCOM versions
\0c:\freecom.com
- BREAKS FreeCOM and possibly also FDAPMs Am I run from INSTALL=?
detection: FreeCOM erroneously searches for \0\0 as marker to
find c:\freecom.com string, and FDAPM (and possibly several
other programs!) searches for \0\0 as marker to where it can
stop looking for COMSPEC (if no COMSPEC found, FDAPM assumes
that it is being run from INSTALL). In FreeCOM this means CRASH
but in FDAPM this only crashes if there is no \0\0 before the
scan reaches environment:0x offset.
Correct behaviour:
pointer = start of environment
while (*pointer) {
copy string at pointer, including the trailing \0, and
update pointer to point after that trailing \0
}
pointer++; /* skip over the end of variables \0 which we found */
string at pointer (possibly empty) up to and including the trailing \0,
is the name of the program
However, COMMON behaviour is:
do {
copy string at pointer, including the trailing \0 ...
(or skip over it)
} until (!*pointer);
pointer++;
string at pointer is ...
Or in other programs, which are not interested in environment variables:
while (pointer[0] || pointer[1]) pointer++;
The BUG in this common behaviour: The two consecutive \0 are only an
artifact of end of an environment variable string being right before
\0 which marks upcoming name-of-program string. Result:
\0c:\freecom.com\0 is only understood by CORRECT programs like SMARTDRV
\0\0c:\freecom.com\0 is only understood by BUGGY but COMMON programs like FreeCOM
*but*
A=B\0\0c:\freecom.com\0 is understood by ALL programs, I dare to say.
So Arkady has optimized away 4 wasted bytes in environment, but we *need*
them to make ALL programs work! The A=B\0 is, however, ONLY needed for
SHELL/INSTALL lines and ONLY if there are no SET events before and if there
is no CONFIG=7 or anything in the environment anyway.
In other words: Only for non-multiconfig we would waste 4 bytes per environment
for the sake of being compatible to all programs! I think we *must* pay this
price, even though mathematical logics tell use the programs *should* accept
\0c:\freecom.com\0 after all.
Please re-add such a workaround (old string was PATH=.\0 I think)
instead of forcing us to upgrade all versions of FreeCOM and possibly also
other programs. I think saving four bytes of kludge RAM are not worth
forcing us all to upgrade FreeCOM.
Eric
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: FreeCOM
Hi! 20--2004 17:09 [EMAIL PROTECTED] (Eric Auer) wrote to [EMAIL PROTECTED]: EA Hi, even though you now have an (0.82pl3w? 0.82pl3v EA Testing, unstable!) FreeCOM, Same for 2035a - it _called_ unstable (bad name, BTW), but it includes optimizations, fixes and features. Thus, fixed kernel plus fixed FreeCOM - very good. EA \0c:\freecom.com - BREAKS FreeCOM and possibly also FDAPMs Am I run from INSTALL=? 1. MS-DOS-style mean two \0 and 2035a produces two \0. 2. There are no reliable/portable way how to detect if you run from config.sys. Suggesting empty environment as indicator of INSTALL= is wrong: you may be called with empty environment at any time. And vice versa: INSTALL= (now!) may be called with non-empty environment, if there is menu or SETs in config.sys. BTW, why FDAPM should suggest INSTALL=? EA Correct behaviour: EA pointer = start of environment I already explain all of this for Steffen, but patch from tom was prepared much earlier. EA \0c:\freecom.com\0 is only understood by CORRECT programs like SMARTDRV Wrong. Smartdrv expects \0\0. EA \0\0c:\freecom.com\0 is only understood by BUGGY but COMMON programs like EA FreeCOM Wrong. FreeCOM (was) expects one \0, smartdrv - two \0\0. EA So Arkady has optimized away 4 wasted bytes in environment, 6. --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_idG21alloc_id040op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: FreeCOM
- BREAKS FreeCOM and possibly also FDAPMs Am I run from INSTALL=? 1. MS-DOS-style mean two \0 and 2035a produces two \0. EA So Arkady has optimized away 4 wasted bytes in environment, 6. PLONK. tom --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: FreeCOM bug reporting (was: kernel progress)
On Tue, 13 Jul 2004, Eric Auer wrote: Hello Eric, thanks for the list. What is it to tell me? Reporting bugs is nice, but fixing them is better. I already spend far too Yes, and reporting via Bugzilla is better than sending mails. This is what I wanted to say. And sending already reported bug reports again won't raise my interest, but annoys me. Bye, -- Steffen Kaiser --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: FreeCOM bug reporting (was: kernel progress)
Hi! 13--2004 16:10 [EMAIL PROTECTED] (Eric Auer) wrote to [EMAIL PROTECTED]: EA FreeCOM has 18 registered bugs at the moment: EA - MEM aborts with UMB corruption - FreeCOM 0.82pl3e+ (I have patches EA for MEM to make it more forgiving, I hope Bart can find the time to apply) May you send it for me? I wish to look at it. (And I hope, that my MEM doesn't have such bug). EA [FreeCOM might assume /P if it finds itself being the master shell] This issue is under question. MS-command.com doesn't assume /p (almost not need, MS-DOS triest to automatically start/restart command.com in case of errors in shell= or if previous shell exits), NDOS/4DOS tries to assume /p. I think, this is low priority issue, if at all. EA And in kernel 2035a, it sometimes runs out of history space forever, i.e. EA you have to reboot or you will get an out of history space message every EA time you enter a command, and history will be dysfunctional. How kernel affects this (especially most my changes are in init, transient part)? --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
