Hi,
it's risky to guess CHS geometry from the MBR, because partitions
don't necessarily end at cylinder boundaries.
Using CHS internally means to use int13 calls to read/write sectors
using CHS values (which Linux does not do). For those the only values
that make sense and are safe are the ones
More tests: http://jafile.com/uploads/dos386/perftest.txt
unless dos386 describes what program(s) he used on what hardware
to produce these results, the data are useless :(
...you can try first writing some dummy data at where the file
will end, then close it and re-open (without truncate of
- write 1 byte of data at this place
Shouldn't it be sufficient to seek to the desired size (as offset), then
do a write with length zero there? (Writing with length zero extends or
truncates the file to the current seek offset.)
- close the file
- open file for writing (no truncate)
I would
Hi Christian,
- write 1 byte of data at this place
Shouldn't it be sufficient to seek to the desired size (as offset), then
do a write with length zero there? (Writing with length zero extends or
truncates the file to the current seek offset.)
Possibly, but I wanted to keep things simple
Is it possible to have the FreeDOS kernel start with driveletter
assignment from specific interfaces, or are we stuck with what BIOS
offers us?
When booting from USB, I've got multiple options:
1) syslinux + memdisk + floppy image
2) syslinux + memdisk + ISO file
3) syslinux + chain.c32 +
