Skip to main content

Timeline for Floppies backup on non-floppies

Current License: CC BY-SA 3.0

8 events
when toggle format what by license comment
Jan 31, 2013 at 15:34 comment added Steve I stand corrected.
Jan 31, 2013 at 15:30 comment added Kitet Floppy anti-piracy features include reading sector that is beyond normal formatted space and reading data from it. So I could format 1.44 floppy as custom size and put somewhere after that a sector that contained something only I know. Then there's BAD sector protection - i could MAKE bad sector on a floppy and test if it exist at specified place with my program. If you CAN read it - no game. And so on and so on. So copying file-by-file COULD work, but it also COULD NOT, @Steve.
Jan 31, 2013 at 14:47 comment added AlexV @Steve Yeah I know you can put each floppy in it's own folder but by doing so it will render most of the old installer unusable (often they search for the data on the root of the current drive and don't offer you to search for missing files).
Jan 31, 2013 at 14:32 comment added Keltari @steve in same cases what you say is true, but in other it wasnt the contents of the filesystem, but how the disk was written to the floppy. Copying the filesystem would not work.
Jan 31, 2013 at 14:29 comment added Steve Folder1 = Disc1 folder2 = Disc2 @Keltari, normally they were interested in a flopy being in the drive that had a certain filename, this can be gotten around with the use of path.
Jan 31, 2013 at 14:26 comment added AlexV @Steve Yeah I know but in some cases the installer was span on multiples floppies and 2 floppies could have the same file name so I can't always do this...
Jan 31, 2013 at 14:26 comment added Keltari thats not true at all. Many floppy based programs had anti-piracy features that required the floppy to be in the drive.
Jan 31, 2013 at 14:15 history answered Steve CC BY-SA 3.0