![]() Tried dosbox-x-mingw-win64-20200101085603.zip unzipped and just ran it. Opened dosbox, typed: C:\>mount a /media/floppy0 OK, now, can I write to it? $ cp file /media/floppy0 dev/fd0 on /media/floppy0 type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro,user=username) dev/fd0 1.4M 87K 1.4M 7% /media/floppy0 $ mount | grep flo Inserted and clicked on the floppy in caja it seemed to mount ok. ![]() The permissions are a bit loose, but I am the only user of the machine: $ sudo mkdir /media/floppy0 ![]() Being lazy, I found one: Īdded the following line to /etc/fstab: /dev/fd0 /media/floppy0 auto rw,user,noauto,exec,umask=0,utf8 0 0 I suspect this is because there is no floppy line in /etc/fstab (file system table), so default user privileges are being applied - and for good reasons, default is r but not rw. Username lp dialout cdrom floppy sudo audio dip video plugdev netdev lpadmin scanner The files on the disk showed but I could only read, not write. I put the diskette in the drive, clicked on the disk icon in caja, the MATE file manager (Debian 11, 64 bit). So you can boot from the HDD image with the following commands instead.Why? Looking at old software, that sort of thing. This is because IMGMAKE always sets the partition type to type 6 (FAT 16), while DOS 3.3 expects type 4 (FAT 16 < 32M).Īs such you need to use the -NOFS switch like with earlier DOS versions and manually create a DOS partition and format it.Īfter you have created your image, due to the newer style partition layout, which DOSBox-X can autodetect, you do not have to specify the geometry to mount the image. Partitioned and formatted images created with IMGMAKE are not recognised by DOS 3.3. If you need multiple drives, you can create multiple images. Since DOSBox-X has only limited support for extended and logical partitions, it is recommended that you only create a single primary partition up to 32MB per HDD image. The maximum supported HDD size is now 504MB, but the maximum partition size is still only 32MB. You can create them, and when you boot your DOS image, you can access them.īut when you IMGMOUNT the image in DOSBox-X, the integrated DOS will only be able to access the primary partition. However, DOSBox-X has only limited support for extended and logical partitions. FDISK hangs with 32MBįormat error, and will fail to boot with 32MBĭOS 3.3 introduced the MBR partitioning scheme with primary, extended and logical partitions, that was used for all later DOS versions. Could read an HDD image created with PC DOS 2.10, but could not boot from it (after SYS), perhaps with HFORMAT which I could not easily locate…įails to boot from diskette, this can be circumvented by renaming CONFIG.SYS. In addition, the FDISK option to use the entire fixed disk for DOS gets confused if the drive is larger than 32MB, and depending on the DOS version will either overflow such that a 40MB HDD image becomes a 40-32=8MB partition, or it will create a drive that cannot be formatted. In effect, you will not be able to access the additional capacity from DOS, and it is therefore waisted space. While it is possible to use an HDD size larger than the maximum partition size, this is not recommended as these DOS versions only support a maximum of one DOS partition per HDD. For this reason the below examples will use 31MB for maximum compatibility between DOS versions. Other DOS versions are in practice limited to either 31MB, or their FDISK (or equivalent) tool is simply incompatible with DOSBox-X. For DOS 2.x, the maximum partition size depends on the OEM version, and should be 16 or 32MB using a FAT12 filesystem.įor DOS 3.00-3.21, the maximum partition size is supposed to be 32MB, using a FAT16 filesystem, but in reality this only appears to be the case for PC DOS 3.0 and 3.1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |