KryoFlux Support Forums

The board thought that every hard-sector linked pulse was the end of a revolution, and as a result dumped only 5 sectors. Could you try dtc -ffilename -i0 -i5 -r85 ? Incidentally, the log is interesting. 5760rpm is 360rpm*16, i.e. it sees every sector hole as a full revolution. When it says 7200rpm ...

IFW wrote:IPF ID please?

I don't have the original zip, but the header says release 3187, revision 1 credit 2010-06-12 1:16:24.671

OG.

Hi guys, I happen to have Chase HQ ST handy (sha1 ce4d71db6789b07b35297d4e22284ff8a7350424). On track 0 head 0, the last block is a little weird, with only the second gap stream present. This would end up with a splice position at the end of that gap, or in other words in the first bits of the first...

IFW wrote:We have very un-rainy days recently due to the amount of work going towards C64 and now even Atari-8 bit preservation...

I'll take care of the mess support

Damn, our amiga core needs a friggin' overhaul, and don't get me started about the atari one...

OG.

No, but as IFW outlined such behaviour is controlled via scripts. There are scripts for most weak bit protections that can be applied. IFW can go into detail if needed. Well, I'm obviously interested. The support is Mess requires to be able to regenerate exactly what was on the floppy from the ipf ...

DrCoolZic wrote:Not to mention "No flux reversal areas" that also produce fuzzy bits.

Not that many, cf. Turrican and friends.

OG.

Isn't there a more generic way of handling fuzzy bits that would apply to more copy protection schemes? There is, but DM is the only game with this type of protection so deserves to be stored correctly. You mean all the amiga games with weak bits do it through unformatted or out-of-alignment zones?...

Xelok used on Silent Service ST is a tricky protection btw. and is based on having two write splices - actually one is just simulated to fool copiers. Nice :-) Looking at the read track output, I see that the gap between the under-the-index sector and the first sector is divided in multiple parts: ...

But when reproducing a disk I do not see what is the problem??? If you are working with a non tempered disk you should not even see this problem, and if the disk to reproduce has been already re-written then the copy should have the same problem as the original. And in fact if you are clever you mi...

I do not consider multiple revolution as an annoyance but as a mandatory feature. This is a must to find out things like fuzzy bits. If you do not want multiple revolutions to be stored just ask the DTC program to only record one. Depends on what you want to do with the result. For dumping, I compl...