![]() ![]() For floppy disk, I usually don't bother and simply make a copy outside the emulator. I find this extremely useful for hard disks. You can subsequently either remove the cow image (to roll back all changes) or you can commit the changes from the PCE monitor interface: If you configure a COW image like this:Īll changes to the disk images will be written to "w", "myimage.qed" won't be touched. * For floppy disks, use Disk Copy 4.2 images if the images are 400K, 800K, 720K or 1440K. QED images are sparse, while raw images are more compatible. * For hard disks, use either QED or raw images. All emulators share the same disk handling code, and while on the Mac you can get by perfectly fine using only block images, for the other emulators (particularly the Atari ST), storing disk images at a lower level is extremely important (mostly to handle copy protected disks). One reason for this complexity is the other emulators supported by PCE. I'm aware that is is all more complex than it should be. In PCE you can use block images and sector images interchangeably (in object oriented parlance: sector images are a subclass of block images). # New 800K image in Disk Copy 4.2 format: Here are some simple commands to create new images and to convert existing images: This program has '''a lot''' of options to modify the images. There are very few differences between the two). The PCE tool to handle sector images is now called psi (it used to be called pfdc, I recently renamed it as well as the file format of the same name. In PCE they are read into memory completely, modified there and then written back as a whole. These images are mostly useful for floppy disks. These store individual sectors along with various degrees of meta data, such as the order of sectors on disk, CRC errors, different sector sizes and so on. To get a list of all options and commands. (here the output file type is determined by looking at the extension. Or, if you don't care about the geometry, just the size: $ pce-img create -g 1024 4 17 newimage.pimg The PCE tool to handle block images is pce-img. pimg | PCE disk image (raw disk image with a short header) | ![]() These images are mostly used for hard disks (though not necessarily, they are just most useful for this purpose). If the file format does not provide a geometry, PCE takes a guess. In PCE they also have a (regular) disk geometry associated with them. These represent a sequence of 512 byte blocks. PCE supports two basic types of disk images: = What type of disk images does PCE recognize and what tools does PCE provide for creating disk images? = Hampa was commenting specifically on the standalone PCE distribution, so you should download it if you wish to create disk images for this web-based version. What follows is a conversation I had with Hampa Hug, the creator of PCE, about disk images. To create disk images, you should download a stand-alone copy of PCE from. You can copy files inside the running emulator, but all disk images are stored in RAM and your changes will be lost when you refresh the web page. This webapp does not currently allow you to create or modify disk images. As an interim fix, my code will detect and patch these disk images before presenting them to PCE. PCE does not currently read such format natively. The vMac emulator uses DiskCopy 4.2 images that have been stripped of their headers. ![]() = Special handling for vMac 400k and 800k disk images = QED images are sparse and are useful for making hard disks with free space for distribution over the web. Hard drive images can only be mounted before the emulator starts up. The web interface will allow you to mount floppy disk images at any time. The emulated computer supports the same types of disk images that are supported by the underlying PCE emulator, such as raw block images or DiskCopy 4.2 images (see below for others). ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |