Open GoogleCodeExporter opened 9 years ago
Addition to "What is the expected output? What do you see instead?"
What I see: After the forced reboot after partitioning and booting from the
Workbench Install Disk again, I get an error message regarding checksum errors
in Blocks 882-890. The Disk boots fine, but it's directory is empty. The
partitions in the hard file can be formatted, no problem on that side. I
checked the exact same disk images on WinUAE doing the exact same steps, even
using the same labes for Disk manufacturer etc. The error does not show up on
WinUAE.
Original comment by LSerraM...@gmail.com
on 17 Apr 2015 at 5:45
[deleted comment]
It seems that the MiST is somewhat unreliable when writing to the disks. My
Cloanto images worked first, but after copying a few files to the image, it
started to throw checksum errors again (block 1100 and up).
I tested with another SD card from a differend brand, same issue.
Original comment by LSerraM...@gmail.com
on 17 Apr 2015 at 9:05
I could recreate this problem on my MiST. Also did get the CRC Problems after
using this ESCOM Install 3.1 Disk. After pressing Cancel some times the MiST
did freeze and after an additinal reset the MiST blinks red and the Filesystem
of the SD-Card is totally corrupted :( On the PC the SD seems then to be
unformated.
Original comment by guido.le...@gmail.com
on 17 Apr 2015 at 4:59
Attachments:
Somewhat good news: I tried to copy the floppy image using Xcopy via the
BAMCOPY+ method. According to DMS-Workshop, both files have the same CRC32 - so
the writing engine is not generally broken.
However, still no clue why it seems that the MiST overwrites some parts of the
disk instead of stopping when the disk is full.
It also seems that MiST is not that accurate in the emulation of the floppy
disk speed. I tested the MiST with the "Ami..Alignment System" test disk and
get an average 320RPM instead of the 300RPM the drive should have according to
Wikipedia. WinUAE averages at 303-305RPM. Read and write speeds also differ:
MiST: 6631 bytes/s write, 19944 bytes/s read
WinUAE: 4922 bytes/s write, 13900 bytes/s read
MiST and WinUAE use the same configuration and run on the same Kickstart
versions. Of course I set WinUAE to highest accuracy and disabled the drive
turbo in MiST. I'm emulating a PAL OCS A500.
I know that WinUAE is not a proper way to get reference measurements for
hardware specific stuff, but I think we can see that there's quite a difference
between the emulator and MiST.
Original comment by LSerraM...@gmail.com
on 19 Apr 2015 at 8:02
Bug also appears on minimig AGA beta core.
Original comment by LSerraM...@gmail.com
on 20 Apr 2015 at 5:11
Original issue reported on code.google.com by
LSerraM...@gmail.com
on 17 Apr 2015 at 5:36Attachments: