Hi Aitor!
> I have to agree with Arkady. Two things why I feel it could be inconvenient:
> - the extra few bytes it takes
> - the fact that, being unique to MS-DOS 4.0...
Well... it was my idea to move this functionality from a FreeDOS-only
function number to an MS-DOS-4.00-only function number.
Hi,
Arkady V.Belousov escribiÃ:
And we even don't may prove this or check how those MS-DOS editions
support this function.
LG> From what I tested, it's only in MS-DOS 4.0 indeed. But I've said I won't
LG> remove it, period.
But why you add it?!
I have to agree with Arkady. Two things
Hi!
12-Сен-2004 12:41 [EMAIL PROTECTED] (Kenneth J. Davis) wrote to
[EMAIL PROTECTED]:
KJD> So the options are:
KJD> 1) current
KJD> Cons: if one needs compatibility with other boot sectors or
KJD> has a buggy value passed to the boot sector, one must
KJD> explicitly provi
Hi!
12-Сен-2004 17:47 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
LG> +++ nls.c 12 Sep 2004 17:47:21 - 1.19.2.4
LG> @@ -490,7 +518,7 @@
LG> -printf("%c", str[c] > 32 ? str[c] : '.');
LG> +printf("%c", ((char FAR *)str)[c] > 32 ? ((char FAR *)str)[c] : '.')
Hi Tom,
On Sun, 12 Sep 2004, tom ehlert wrote:
> the only real solution that comes to my mind is to undo the
> alloc_fnode() change, even if that costs a few byte in low memory;
> if you don't have UMB's, it even saves a few byte (the memory used by
> the 2 near_fnodes)
If you undo the change th
Hi!
12-Сен-2004 18:06 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
>> Therefore I vote for a SYS option which lets you decide whether or not
>> the 0x80 in the boot sector will be used. The DEFAULT should be, in my
>> opinion, to accept the value from the boot manager / MBR /
Hi!
12-Сен-2004 16:55 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
LG> Hallo Tom,
"D:"==second disk? Second disk is a 81h value.
>>> Only 0 and 80 are used by MS-DOS. All other values are "FreeDOS
>>> extensions" ;-)
>> are you SURE ?
Strange, I not seen letters wi
Hi!
12-Сен-2004 17:45 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
>>> RBIL is not very clear how!
LG> RBIL is correct that it's only for MS-DOS 4.0.
I mean, that it not explains, that "zero value should restore original
version", that "changed version affects only INT2
Hi!
12-Сен-2004 18:42 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
>>> unsigned char check_handle_break(struct dhdr FAR **pdev)
>>> {
>>> - unsigned char c;
>>> + unsigned char c = 0;
>>>if (ctrl_break_pressed() ||
>>> (c = (unsigned char)ndr
Hola, Eduardo!
This patch adds DBCS support to DOS-65-23 (Determine if a character
represents yes/no response) as specified by RBIL, and fixes DOS-63-00
(Get Double Byte Character Set lead-byte table.) It now returns the DBCS
table from the active NLS package, not the harcoded one. Applies to
u
Hi Jeremy, I vote for 2)
- use 0 or 80 only in the boot sector (or really any value the
user wants, but default to 0 or 80)
- the boot sector code has at a fixed location
useBIOSorNotFixedLocation:
mov [drive], dl
- SYS is then responsible for determining if BIOS pro
So the options are:
1) current
- use 0xFF in BPB.drive to indicate to boot code to use BIOS provided
drive in DL, otherwise use value in BPB.drive
- the boot sector code can be anywhere and is similar to:
cmp [BPB.drive], 0xFF
jmp dont_use_bios
mov [BPB.drive], dl
don
unsigned char check_handle_break(struct dhdr FAR **pdev)
{
- unsigned char c;
+ unsigned char c = 0;
if (ctrl_break_pressed() ||
(c = (unsigned char)ndread(&syscon)) == CTL_C
||
*pdev != syscon && (c = (unsigned char)ndread(pdev))== CTL_C)
{
hand
Hi,
This patch adds DBCS support to DOS-65-23 (Determine if a character
represents yes/no response) as specified by RBIL, and fixes DOS-63-00
(Get Double Byte Character Set lead-byte table.) It now returns the DBCS
table from the active NLS package, not the harcoded one. Applies to
up-to-date CVS
Hallo Tom,
at least I know the problem - and described it when publishing the patch.
Do you mean
http://www.mail-archive.com/[EMAIL PROTECTED]/msg01070.html
(It doesn't contain other comments but those in the patch.) If you
confirm, I can apply it.
it happens if a int24 handler returns to itsel
Hallo,
Therefore I vote for a SYS option which lets you decide whether or not
the 0x80 in the boot sector will be used. The DEFAULT should be, in my
opinion, to accept the value from the boot manager / MBR / BIOS for
harddisks. For floppy, 0 will be in the boot sector, and the DEFAULT
should pr
Hallo Eric,
we already do have 622k low DOS RAM free in a quite straightforward
configuration (in DOSEMU, where HIMEM / EMM386 take almost no memory,
even 627k), and I never met any program which really needed more than
590k, so this is only about bragging.
Exactly. I have 629 KB free in FreeDOS
Hi!
11-Сен-2004 15:52 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
LG> Log Message:
LG> break.c:check_handle_break() return type was undefined if no Ctrl-break
LG> +++ break.c 11 Sep 2004 15:52:56 - 1.17.2.2
LG> @@ -53,7 +53,7 @@
LG> unsigned char check_handle_b
RBIL is not very clear how!
RBIL is correct that it's only for MS-DOS 4.0.
And we even don't may prove this or check how those MS-DOS editions
support this function.
From what I tested, it's only in MS-DOS 4.0 indeed. But I've said I won't
remove it, period.
-
Hi!
> > Only 0 and 80 are used by MS-DOS. ...
> I remember a BIOS that had the option to boot from 2'nd drive.
> this only makes sense if DOS then boots from 0x81.
Therefore I vote for a SYS option which lets you decide whether or
not the 0x80 in the boot sector will be used. The DEFAULT should
Hi, after PTS-DOS, the DR-DOS enhancement people have added an
option to put more data structures of DOS into UMB (I guess this
time we are talking about LoL / SDA). That way they get 626k of
640k low DOS RAM free after loading HIMEM/EMM386.
If you want to keep up with the game, we could add such
Hallo Tom,
"D:"==second disk? Second disk is a 81h value.
Only 0 and 80 are used by MS-DOS. All other values are "FreeDOS
extensions" ;-)
are you SURE ?
Just checked that, and now I'm even more sure.
I remember a BIOS that had the option to boot from 2'nd drive.
this only makes sense if DOS then b
Hi!
12-Сен-2004 14:28 Arkady V.Belousov wrote to
[EMAIL PROTECTED]:
>>> And what about INT2F/122F?
LG>> Although only MS-DOS 4.0 had it, I won't remove it
AVB> Let me ask reverse question: why you add this _another FreeDOS
AVB> specific
AVB> function, which duplicates another specific functi
Hello Luchezar,
>> and removes (parts? of) tom's patch.
> As you wrote youself, it's better to have the whole patch than parts of
> it. And even better is to solve entirely the problem which this kludge
> solves partially. But we don't know the problem :-(
at least I know the problem - and desc
Hello Luchezar,
>> "D:"==second disk? Second disk is a 81h value.
> Only 0 and 80 are used by MS-DOS. All other values are "FreeDOS
> extensions" ;-)
are you SURE ?
I remember a BIOS that had the option to boot from 2'nd drive.
this only makes sense if DOS then boots from 0x81.
tom
Hola, Eduardo!
OK, done again. New patch in:
http://perso.wanadoo.es/samelborp/country3.zip
It also adds complete NLS info for (de,at)/(850,858,437), and keeps the
entry for tr/850, but makes tr/857 the default.
Thanks! Just applied it, tested, uploaded the 7K binary to my page, and
committed t
I don't understand this. SYS writes 0/FF only into its own images,
builtin into SYS executables. And, if _after_ SYS someone will change
boot loader, then 0/FF value also will be replaced. Where is trouble?
The trouble is that most SYSes don't bother to set this value - they just
copy the whole
Здравствуйте, Аркадий!
Show this, please.
See it in the CVS, along with the nice additions of Eduardo.
Let me ask reverse question: why you add this _another FreeDOS specific
function, which duplicates another specific function_, whereas only some
version probably support this function (and RBIL
Hi!
10-Сен-2004 10:50 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
>> above shown MASM/TASM style, when _text_ with delimiters (spaces and/or
>> comas) enclosed into brackets (<99h,0,0,0,0>). This allows to pass
>> enclosed content as one argument. This is need, because list
Hi!
15-Авг-2004 20:24 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
>> - lr.BH = OEM_ID;
>> - lr.CH = REVISION_MAJOR; /* JPP */
>> - lr.CL = REVISION_MINOR;
>> - lr.BL = REVISION_SEQ;
>> + lr.BX = (OEM_ID << 8) | REVISION_SEQ;
>> + lr.CX = 0; /* seri
Hi!
10-Сен-2004 20:05 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
LG> "brain-dead" BIOSes if the boot drive is A: (but not if it's C:), the FF
LG> value written to by SYS causes a compatibility problem. What happens if
LG> someone decides to overwrite our boot sector later w
Hi!
15-Авг-2004 21:59 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
BO> BC isn't a target for freedos optimizations; there's one and only one
BO> target to optimize for : WATCOM.
BO> so BC specific optimization is a waste of time (ours and yours)
BO> This just being tom's opini
Arkady V.Belousov wrote:
... (I'm reading his question from the archive, never getting it myself) ...
http://freedos.sourceforge.net/kernel.UNSTABLE.tgz
will be http://freedos.sourceforge.net/kernel/kernel.UNSTABLE.tgz
and updated regulary once sourceforge reenables cronjobs,
currently it and /kern
33 matches
Mail list logo
