Re: [Freedos-kernel] kernel 2034rc for testing

2004-04-16 Thread tom ehlert
Bart,

ke2034rc compiled ok (386,fat32), and does MS networking - so it can't
be that bad ;)

one thing I don't understand:
MEM /F will show a 1K dataarea, between 2 FILES drivers, at ~2a6:0

this existed also in ke2033, and possibly before.

as it *seems* to be unused, what is it?

BTW: I fullheartily disagree with your efforts to move share_check()
into assembly, and I will never like #pragma aux, even if that saves a
few byte. IMO this is dos-C, and should be coded in C (which is
possible mostly)

tom




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] kernel 2034rc for testing

2004-04-16 Thread Bart Oldeman
On Fri, 16 Apr 2004, tom ehlert wrote:

> one thing I don't understand:
> MEM /F will show a 1K dataarea, between 2 FILES drivers, at ~2a6:0
>
> this existed also in ke2033, and possibly before.
>
> as it *seems* to be unused, what is it?

That would be the relocated EBDA. I should improve MEM to detect that one
properly.

> BTW: I fullheartily disagree with your efforts to move share_check()
> into assembly, and I will never like #pragma aux, even if that saves a
> few byte. IMO this is dos-C, and should be coded in C (which is
> possible mostly)

you'd have to be consistent. Most of the remote functions use assembly.
So why have just one using intr()? Either use intr() for all of them or
use external asm files for all of them. Since the resident code had only 4
or so intr() users it was easier to go for the external assembler. I left
all the intr()s in the init code as is though -- since it's the
predominant technique there.

As to #pragma aux, this helps the Watcom optimizer quite a bit (about
350 bytes for the asmsupt.asm interfaces) -- without it even a "memcpy" in
C would make a smaller kernel (but in the past you argued to do memcpy in
assembly). Ironically as soon as you throw a "normal" __cdecl or pascal
assembly function into the equation (whether intr() itself or anything
else) the whole optimizer chain collapses.

Bart



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] kernel 2034rc for testing

2004-04-16 Thread Arkady V.Belousov
Hi!

16-Апр-2004 20:30 [EMAIL PROTECTED] (tom ehlert) wrote to Bart Oldeman
<[EMAIL PROTECTED]>:

te> into assembly, and I will never like #pragma aux, even if that saves a
te> few byte.

 Let me disagree with you. This is most valid and effective way to
control compiler - in given case describe interface to (external) function.
IMHO, this is much more flexible and better than modifiers (like ASMPASCAL)
and cost only one additional line per each function in header file.

te> IMO this is dos-C, and should be coded in C (which is possible mostly)

 :) Some things (especially low level and which are complete in sense of
functionality) may (and should) be implemented in asm. Especially when we
talk about real OS, which may used as base for complex systems.




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


[Freedos-kernel] TDSK volume locking failure

2004-04-16 Thread Steve Gibson
Hi Guys,

Just a note that the 2032 kernel fails volume locking on the tdsk.exe 
turbodisk device.

mov bl, CurrentDosDevice; 1-based current device
xor bh, bh  ; lock level 0
mov cx, 084Ah   ; category / lock logical
mov ax, DOS_IOCTL SHL 8 + BLOCK_DEVICE_IO
int 21


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel