Is there any reason why you would need to use Warp? It only reads from trackdisk.device, you could use any ADF creator to replace it.
UnWarp runs on Kick 3.1, so there is no risk to start a disk-validator virus when writing to DF0. BTW, I just tried Warp on 3.1 and it worked without problems.
Disk-Validator is not limited to DF0. It will run from/for RAD, too.
Thanks Thomas.
Warp does seem to work on KS3.1 but at the end of compression it freezes. If not, could you please tell me filesize/version of Warp you're using?
I have a lots of duplicates in my 'collection':.adz/.dms/.wrp/.dsq. The idea is to convert all (or most) of them to .adf, rename and then use 7z solid packing with large dictionary size. But, I'd like to do it so the process is reversible, to be able one day to reconstruct original files. It's hard because of different buggy versions, file_id.diz, algorithms, and so on. Some data needs to be saved separately (headers/footers). So far, I've managed dms and dsq (well mostly). Its probably a bit pointless task, but at least I'm learning perl and bash.