Thank you, Bart, for applying my patches, and reviewing the MAX_CDSPATH
use!
The following log comment is slightly incorrect:
prf.c
Log Message:
Borland C (unlike Turbo C) didn't like this pseudo register use.
Actually, *both* Turbo and Borland C didn't like it!
I mentioned a RAR32 bug
On Sun, 7 Mar 2004, Luchezar Georgiev wrote:
The following log comment is slightly incorrect:
prf.c
Log Message:
Borland C (unlike Turbo C) didn't like this pseudo register use.
Actually, *both* Turbo and Borland C didn't like it!
This is strange. The old code has been there for
On Sun, 7 Mar 2004 16:37:43 + (GMT), Bart Oldeman wrote:
Actually, *both* Turbo and Borland C didn't like it!
This is strange. The old code has been there for ages even when we
compiled with Turbo C by default.
Yes, but the bug didn't reveal until MENUCOLOR and the 8-bit strings it
allows
On 2004-02-27, Alain Mouette wrote:
True that once long time ago it was discussed that the rebooting
method of jumping to certain BIOS point wasn't safe in the sense
that wasn't portable across BIOSes, but it was s long time ago
that I may be wrong.
Thanks :)
Well, it _allways_ was
On 2004-03-02, Luchezar Georgiev wrote:
Now you can exit any primary shell that allows that (all I've tried
but 4DOS do) and specify another one.
Yup. Sometimes, in particular during testing and in embedded system
applications it is very convenient that you can safely EXIT the
primary shell.
On Sun, 7 Mar 2004, Luchezar Georgiev wrote:
EXACTLY! Now I see that put_unsigned() and put_string in prf.obj have a
CBW instruction that does just that! So, what do you suggest? I think that
we can just apologise to KR and change c in put_console() to char.
or cast to unsigned char. That's
On 2004-02-25, Arkady V.Belousov wrote:
There is such (current) order of source and target in SYS:
SYS {options} targetdrive:
SYS {options} sourcedrive: targetdrive: [bootsector.file]
SYS {options} sourcepath targetdrive: [bootsector.file]
But there also possible to handle
