#Imgmount dosbox windows
I try to create 8gb hard drive image with Windows 98, but without success.ġ. Therefore I'd suggest using internal imgmake for images <8GB (or partitioning the image with a program that creates compatible partition table). I assume images over 8GB (0xC partition type) are fine since they're using LBA and not CHS addressing. While this may seem fine at first (the 7GB image created this way passed all md5sum checks) doing something like 'sys a: c:' will corrupt the filesystem! DOS & W9x officially need all partitions aligned to cylinder boundary (except the first and every logical which should be track +1).
#Imgmount dosbox windows 7
I've added support for mounting empty (no mbr, unformatted) VHD images so they can be partitioned later in the booted system, and added geometry translation for 1023cyl VHD images (fixes the problem mentioned in the above post).īUT, here's a WARNING: Windows 7 Disk Manager no longer aligns partitions to cylinder boundary. It creates partitions larger than disk (partition end cylinder is the same as disk geometry, but should be c-1 as cylinder count is zero based the same as heads) and that certainly can't be good 😀Īside from that, I've fixed imgmake to take parameters in any order (after creating an image named '-t' during my tests 😀). I wasn't really planning on working on this much more, but I found a pretty serious bug in the original hal's imgmake command. Why VHD? Because it can be natively mounted by Win7 & 8.Linux users? Tough luck 😀 (altough it still a valid raw image with the 512b footer at the end, kpartx will handle it just fine 😁) I use raw2vhd program for that and the functionality is now incorporated into imgmake.
What is little known is that any "raw" image (such as the ones dosbox uses) can be converted to VHD with just writing the 512b footer. Such image cannot be used as it exceeds 1023 cyl limit.
For the 7GB image, it used only 16 heads and some 14000+ cylinders. Creating 8GB image takes some time, be patient.Īt first, I created the VHD with Win7 Disk Manager. So far, a larger image can be mounted but Windows will most probably return "Error reading sector" as it tries to access data beyond the 1023 cyl. More would require working IDE emulation (edit: it seems extended int13/42h would also work). Only images up to 8GB are supported (1023/255/63). ran md5sum and checked that all files are OK inside dosbox, the FAT32 volume will not be visible, but Windows can be booted off another disk and will see the FAT32 volume copied almost 8GB of large files to the image and created md5sum of the files initialized disk, created 1 partition and formatted it FAT32 mounted the VHD using Windows 7 Disk Manager created a new 8GB VHD image with imgmake c:\dosbox\dosbox.vhd -t hd_8gig (the disk will not be formatted, only images <2GB will be formatted by imgmake as it cannot handle FAT32) I also added the ability to read (fixed size, not dynamic) VHD images. Since I've been doing something similar, I merged both patches + hal's megabuild imgmake.
#Imgmount dosbox Patch
Ykhwong's patch is somewhat too aggressive as it changes all fopen functions (you won't need 2gb+ for reading conf, hopefully 😀), but lacking some other fixes (while 4GB might work, 4GB+ probably won't).
0 kommentar(er)
