Have an idea how to make KryoFlux even better? Let us know...
Does this mean it's not possible for us to make flux-level identical copies of floppies ourselves? It must be converted to IPF first? We can't (eventually) write stream/DRAFT files?
Copy-protected software was always duplicated with well designed patterns and methods of writing from analysed and fully understood data - duplicators simply refused to duplicate anything that was not possible to script properly. Simply put, what you write is not necessarily what you read, one good example of that is weak bits, but there are other examples too. An IPF file is a simplified script describing how to generate the disk data, generated from higher level scripts describing the structure of the data - which is not part of an IPF file as it's no longer needed at this stage. In other words, it enables writing or generating data for emulation.Malvineous wrote:Does this mean it's not possible for us to make flux-level identical copies of floppies ourselves? It must be converted to IPF first? We can't (eventually) write stream/DRAFT files?
So... This will mostly work for data that comes out as being written. E.g. long track protections can be copied easily, even from STREAM or DRAFT. What will be problematic is mastering data that was obfuscated to fool the drive, e.g. weak / flakey bits. These bit patterns were written in a way that they change with every revolution read. Now writing such data back to disk will save a static pattern, not a changing one, so the software will be able to tell it's a copy. For instances like these, you'll need to describe how the data needs to be written. Either by making a software that will allow you to alter the STREAM data (so you can save patterns that will generate changing output when read back), or by using an IPF made by us.
I hope that resembles it correctly. IFW will correct me if necessary.