Hi. Arkady V.Belousov wrote:
Hi!
19-Июл-2004 22:11 [EMAIL PROTECTED] (tom ehlert) wrote to "Arkady V.Belousov" <[EMAIL PROTECTED]>:
te> do you really think a new kernel that breaks all installed FreeCOM's te> in the wild is an improvement ?
Workaround for current bug in FreeCOM is easy, this is question of two lines in main.c before p_0(): "if (empty environment) CmdSet("A=B");". But this works only when FreeCOM called through SHELL=, this not helps for INSTALL= - neither in orignal 2035, nor in my edition; also, if some application with empty environment tries to call FreeCOM, FreeCOM again wrong. And again, notwithstanding if this workaround is present (and eats extra memory in each following environment) or not, bug anyway should be fixed.
Work around in the kernel is wrong. FreeCom should be fixed.
te> Do you really want to force everyone to update to a new freecom? te> (people often update only one component)
FreeCOM executable included into package with kernel executable.
Yes!
te> Do you really want to see all the te> 'updated to new kernel, now freecom doesn't work anymore'
It work, unless config.sys defines no enivoronment (no menu and no SETs).
If there is a problem with FreeCom, Fix it don't hack the kernel. Silence has been deafening to me, B^\ James
------------------------------------------------------- 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_idG21&alloc_id040&op=click _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
