CompuServe Thread

Dennis, It looks like some of your message is missing…but I think I got the idea. When you create a JLink'ed file…you open and create just that…a file. If you have a system crash, or forget to unlink that file when you shut down for the night…then the creation is "incomplete" in that the AmigaDOS file wasn't properly closed, so it's length wasn't properly set. By filling that file (JLink'ed disk) and then unlinking it…you both create the file full sized right off the bat…but you also properly close it so the creation is "complete" and it's length is properly set. Once that is done…all JLink does is "play" with the data inside the file…it doesn't change the length of the file and thus all the AmigaDOS pointers are always valid. That means you can't crash the JLinked file by forgetting to unlink before you shutdown or re-set. You only have to do it ONCE…when you first create the file. You do not have to do it each time you link the file. Yes…disk access will be slow. There's a lot of conversion that needs to be done, you're going thru the Janus Interface and software, and finally…you're dealing with a *file* that emulates a disk drive, not an actual hard disk drive (even if that file is on a hard disk drive). Because it's a file…your data can be scattered all over your drive itself. Access must be done thru AmigaDOS, not thru a hardware controller. However, slow and quirky as it is…it's far better than not being able to use the HD at all for MS-DOS work. Don