Guld wrote: ↑Sat Oct 09, 2021 12:18 am
brightcaster wrote: ↑Fri Oct 01, 2021 10:54 am
Your parameter line doesn't work that way! Just to quote the manual:
IMPORTANT NOTE on command line parameters order:
The following settings are “image local” and therefore must appear before the image type and would affect only the first image type specified after the parameter. Their values automatically revert to the default after an image type setting (ie once they get used).
Correct: DTC.exe -ffilename.ext -v360 -z3 -i4
Wrong: DTC.exe -ffilename.ext -i4 -v360 -z3
So your parameter line should be
dtc -ftest.img -v300 -e41 -oe39 -i4 -ffilename -i0
dtc -ftest.img -i4 -i0 -v300 -oe39 -e41
Still, a raw flux dump would be handy to examine for the bad sectors you get...
Ah, okay, thanks for the clarification, I wasn't aware of the argument ordering requirements.
I was able to determine that the disk I was testing with has got an issue now that it didn't used to have even on the original system, so that might explain some of the issues. I'll have to switch to another known good disk to continue testing. I'll post some raw flux dumps if I still have issues. Hopefully I can give it another go this weekend sometime.
Thanks for all the pointers David!
Alright, I'm back to trying to resolve this issue again. I've got known good disks now and I'm using the exact same drive connected to Kryoflux as I am in the target system itself.
The drive is a Qume Qumetrak 142 (5 1/4" DSDD). It works perfectly in the target system and I've checked that it is running the correct RPM.
I have also been successfully able to write a Kryoflux stream to the disk and use it in the target system just fine (after degaussing the disk, etc.)
However, no matter what I do, Kryoflux seems completely unable to read disks back from this DSDD drive. It wasn't even able to read the disk which I wrote with Kryoflux, which is really odd. As a reminder, the exact same disk works perfectly in the target system using the exact same drive. I've also done some binary-diffs on the files on the disk vs. the ones that were on the original it was copied from and all the ones I checked matched exactly.
When I attempt to read the disk in Kryoflux, I get repeated errors about bad sectors, and the preservation stream coming back does not look good either.
Command line arguments used:
'dtc -ftest.img -v300 -e41 -oe39 -i4 -ftest\test -e41 -i0'
I will note that I do see that Kryoflux is reporting errors of XX.X "Drive speed problem detected". I have also tried pulling a preservation stream with the 300 RPM specified and it does not help. The Qumetrak 142 drive does of course run at 300 RPM.
As another test, I put the same disk in my Teac FD-55GFR (5 1/4" DSHD - 360 RPM), and it pulls a great looking stream and image. So by all accounts that I can tell, the disk is good and was written well.
Any ideas on why Kryoflux seems to have issues reading from the Qume drive even though it successfully wrote the image?