Timeline for Why is QEMU cutting off the last cylinder of the disk image?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 29, 2021 at 14:23 | comment | added | user3840170 | @Justme It relates to retrocomputing because the 16-bit ROM BIOS and CHS addressing is an old interface, and even a modern implementation thereof is heavily constrained by the design parameters of retro hardware and compatibility with retro software (e.g. the 256 heads bug). | |
| Aug 29, 2021 at 14:17 | vote | accept | Joshua | ||
| Aug 29, 2021 at 13:46 | history | became hot network question | |||
| Aug 29, 2021 at 8:09 | history | edited | user3840170 |
edited tags
|
|
| Aug 29, 2021 at 8:05 | comment | added | user3840170 |
Tangentially, dd if=/dev/null of=hd.img bs=512 count=0 seek=$(( 16 * 63 * 0xf8 )) would have been faster, as it creates a sparse file instead of copying small blocks of zeroes (and avoids spawning a subprocess for the calculation).
|
|
| Aug 29, 2021 at 8:02 | history | edited | user3840170 |
edited tags
|
|
| Aug 29, 2021 at 7:54 | answer | added | user3840170 | timeline score: 13 | |
| Aug 29, 2021 at 2:27 | comment | added | Leo B. | You can find out the answer by doing the following: Create an image of the size which QEMU recognizes as the desired HD configuration, write a unique pattern into each sector using a program run from within QEMU, then look at the image from the host OS to find out which areas of the image were not touched. | |
| Aug 28, 2021 at 22:11 | history | edited | Joshua | CC BY-SA 4.0 |
more bad keyin
|
| Aug 28, 2021 at 19:53 | history | edited | Joshua | CC BY-SA 4.0 |
edited body
|
| Aug 28, 2021 at 19:25 | history | asked | Joshua | CC BY-SA 4.0 |