Hi,
Commit 1705 renames a particular LoL field CPULevel and adds a comment
correctly claiming that MS-DOS sets this field to 1 on 386+ CPUs and to 0
otherwise. The commit however makes the boot loader store the detected CPU
level (0, 1, 2, or 3) there instead. I don't think it's necessary
Dear PerditionC,
UBYTE DiskTransferBuffer[MAX_SEC_SIZE];
wastes 3,5 KB low memory for *everybody*, not only when it's needed.
regarding how much time we have spend until we had 64 byte free
I think this is a bad idea
I also think that these experiments should NOT be in the stable
Hi Chris, Jeremy,
Commit 1705 renames a particular LoL field CPULevel and adds a comment
correctly claiming that MS-DOS sets this field to 1 on 386+ CPUs and to 0
otherwise. The commit however makes the boot loader store the detected CPU
level (0, 1, 2, or 3) there instead. I don't
On Tue, Feb 7, 2012 at 9:51 AM, Tom Ehlert t...@drivesnapshot.de wrote:
Dear PerditionC,
UBYTE DiskTransferBuffer[MAX_SEC_SIZE];
wastes 3,5 KB low memory for *everybody*, not only when it's needed.
regarding how much time we have spend until we had 64 byte free
I think this is a bad