On Fri, 16 Apr 2004, Steve Gibson wrote:
> 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
Hi Bart,
> 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 + B
Folks,
Could someone briefly explain the function of the kernel's "FORCELBA"
option? The command shown by sys.com is "Always use LBA if possible". So
I suppose I'd like to understand why or when the kernel would not use LBA
when it's available?
Is it, for example, a matter of not using LBA i
On Sat, 17 Apr 2004, Steve Gibson wrote:
> Could someone briefly explain the function of the kernel's "FORCELBA"
> option? The command shown by sys.com is "Always use LBA if possible". So
> I suppose I'd like to understand why or when the kernel would not use LBA
> when it's available?
If a par
Hi Bart,
> Could someone briefly explain the function of the kernel's
> "FORCELBA" option? The command shown by sys.com is "Always
> use LBA if possible". So I suppose I'd like to understand
> why or when the kernel would not use LBA when it's available?
If a partition isn't marked as "LBA" (wit
FreeDOS kernel 2034 is released at the usual place. Since no new
critical problems were found with 2034rc it is the same as kernel 2034rc
except for the updated history.txt and the version string.
Some important user visible changes (full log in history.txt):
Memory savings: saved ~1100 bytes of
