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_DEVIC
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 describ
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 d
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 fullhear
