I can get color in the other bit-depths, but those run slooooow (as documented). When I select any other 8-bit display size, I only get grayscale (no color display). Other discussions in other forums indicate that Mac-handler will mount the Mac system disk as a folder in Workbench, but when I try that I get the message "device 'Mac:' is already mounted." It seems like Shapeshifter is using the same HDF files as the Amiga, so maybe that's why, but what other way could I access the Mac drives?Ģ. How can I transfer files into the Mac volumes? I can see the CH1 and CH2 hard files from Amiga Workbench, but I have no idea how to access their contents. I have two questions that I can't seem to figure out, maybe someone here already knows the answer:ġ. Wow, this is an amazing project, and was really pretty easy for me to get up and running- thanks meauxdal! In the case of the Mac image, has anyone tried manually setting the device (vice), unit (1 if 2nd device on 1st channel, 2 or 3 for the 2nd channel), and then firstsector=0, number of sectors = (filesize/512) - or mounting it as a ShapeShifter filedisk accessed over the shared filesystem, instead of as an Amiga drive? The hardfiles that no longer work aren't images of complete hard drives, they're images of partitions. That's why the MaxTransfer problem cropped up with real hard drives, and (presumably) the new IDE subsystem isn't mimicking ATA-1 behaviour so it's happening again now. (It's not forbidden, just no longer mandated). ![]() Unfortunately that behaviour changed with ATA-2, and on command completion the taskfile doesn't have to contain the CHS address any more. The problem is in how it does that:Īfter the first set of blocks has completed, vice assumes that the hard drive's taskfile registers will contain the CHS address of the last block read (as per the ATA-1 spec), increments them by one and starts the next transaction. The IDE command set allows a maximum of just shy of 128k (0x1fe00) bytes to be transferred in a single command, so if MaxTransfer is higher than that, and you're accessing a chunk of a file that's larger than that, *and* your filesystem's not fragmented, so there are more bytes than that in a contiguous lump, then vice will read the data in two consecutive IDE commands. It's not that MaxTransfer's ignored or obeyed by anything - MaxTransfer is nothing more than the maximum number of bytes vice will attempt to transfer in a single transaction. Toastboy wrote: ↑ Sat 9:19 ammaxtransfer used to be ignored by the old minimig disk subsystem, but now it's obeyed, even if it's a silly value.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |