bro@eunomia.rice.edu (Douglas Monk) (11/06/90)
The version of mtools I got would not work as compiled because it only wrote one copy of the FAT area. IBM's could read such disks, but my ST could not. Goofy behavior resulted. The solution was to compile the file init.c with the DUP_FAT #define set. This makes the code that writes the FAT update both copies. Remember: like all IBM formatted disks, these disks will not have a serial number, so your ST can get confused and write back the wrong FAT and directory information to them in some circumstances. I recommend using them as read-only disks unless you know EXACTLY what is going on. Doug Monk (bro@rice.edu) Disclaimer: These views are mine, not necessarily my organization's.
ralph@laas.fr (Ralph P. Sobek) (11/08/90)
The DUP_FAT #define is not the only patch necessary for MTOOLS to be compatible with an ST. By default MTOOLS writes out an ALL-BLANKS volume id, which makes the Gulam shell not be able to read that floppy. I've already posted my simple patch to comp.sys.sun and maybe even this newsgroup. I am sure that other small bugs are lurking in MTOOLS. Ever try to abort in the middle of an MTOOLS operation? Cheers, -- Ralph P. Sobek Disclaimer: The above ruminations are my own. ralph@laas.fr Addresses are ordered by importance. ralph@laas.uucp, or ...!uunet!laas!ralph If all else fails, try: sobek@eclair.Berkeley.EDU =============================================================================== Reliable software should kill people reliably! -Andy Mickel, Pascal News #13,78