Folks,
I've run across an interesting bug in the FreeDOS kernel.
In order to prevent on-screen noise in the event of critical DOS errors, my
DOS application hooks the critical error handler (Int24h), records the
error that pops out, and always returns with AL == 3 to fail the operation.
Folks,
The DI1000DD.SYS ASPI drive mapper, which also offers extended Int13
support, fails under FreeDOS kernels (2032 and 2034) but runs fine under
various versions of MS-DOS.
If you have a motherboard with a USB chipset, the USBASPI.SYS driver should
install ASPI support for it. If not,
Hi Folks,
Using the 2034 kernel and fdxms.sys, I have two systems where FDXMS.SYS
refuses to load because it mistakenly detects that VDISK is present.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented
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 +
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 if
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 +
Hi Jim,
Yes, something is wrong.
I tried the only updating the boot sector using FreeDOS' SYS and got;
D:\Download\FreeDOSsys X: BOOTONLY
FreeDOS System Installer v2.9, Sep 24 2003
Processing boot sector...
Reading old bootsector from drive X:
Divide overflow
WinXP throws up an error message
