Howard M. Harte
Howard M. Harte
Hello David, Thank you, I'll check it out this weekend! You are correct about how the encoder "worked" previously. It starts wrting at the Index pulse, and made sure the...
I’ve observed a similar issue with many of my Micropolis disks, and also need to go back and re-read them with the original machine to see if the disks are...
Hello David, Thank you for all the updates to FluxEngine lately. I had a chance to try the new decoder with the latest version of FluxEngine. Unfortunately, the latest version...
Thank you! I’ll give it a try. I saw the track 0 issue as well, I have a feeling this is how the CP/M disks were written originally. But now...
@ejona86 I found a clue as to what may be going on here. The sector SYNC pattern (00's followed by 0xFF) may be detected too "early" after the sector pulse....
A simpler fix that seems to work well is to seek forward about 500uS from the sector pulse before searching for the sync pattern.
PR #463 partially addresses the decode issues for some of the disks I have. Better hard sector ID'ing would also help somewhat, in cases where the sector ID encoded in...
Hello David, For the several hundred disks I've tried for all known operating systems on the Vector MZ (CP/M, MDOS, MZOS, OASIS) the sector IDs are in order. I do...
Thanks David for the tips above. I'll give those a try when I have a chance.
Writing .nsi files to disks should work. Please make sure to use a 300RPM 48TPI drive, and adjust the spindle speed to exactly 300RPM. Also make sure the FluxEngine hardware...