Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site mmintl.UUCP Path: utzoo!watmath!clyde!burl!ulysses!gamma!epsilon!zeta!sabre!petrus!bellcore!decvax!mcnc!philabs!pwa-b!mmintl!tedi From: tedi@mmintl.UUCP (Ted Ives) Newsgroups: net.micro.mac Subject: HardDisk20, HFS, Fortran Message-ID: <892@mmintl.UUCP> Date: Mon, 16-Dec-85 09:08:38 EST Article-I.D.: mmintl.892 Posted: Mon Dec 16 09:08:38 1985 Date-Received: Fri, 20-Dec-85 01:50:34 EST Organization: Multimate International, E. Hartford, CT Lines: 41 The Hard Disk 20 appears to have a fatal flaw; many (if not MOST) serious commercial applications just plain do not work with it. I gather the problem is not the Hard disk, but Finder 5.0 (i.e. HFS); since many applications seem to assume Finder 1.0 is being run, they just go south when they are installed on the hard disk. I went to a dealer who showed me a page-long list of applications that don't work, and I know from personal experience that this is true for Microsoft(i.e. Absoft ) MacFortran and for Assimilation Process' RamDisk. Fortran doesn't work at all, and the RamDisk will work with some cajoling, but can't be automatically created at startup. FLAME ON: I rather resent being used as a GUINEA PIG for Apple's new Finder. Nowhere in the manual for the disk drive did I find anything indicating that there might be problems with it. I suggest Apple stamp something on the box like " Warning : We recommend storing only TEXT FILES on this disk drive. anything else may cause all kinds of bad things to happen. " (What if when something 'goes south' it ruins things on my disk drive?) FLAME OFF. QUESTION : Does anybody know of any way to either make MacFortran compatible with Finder 5.0 OR (more likely) has anyone tried any other Hard Disk Software on their HD20 (i.e. MacBottom 20 software or Hyperdrive 20 or whatever). Also, does anyone know if Apple plans on making Finder 5.0 backward-compatible with Finder 1.0 so I can maybe use off-the-shelf software? - Thanks in advance, Ted Ives philabs!pwa-b!mmintl!tedi or in January, harvard!dartvax!tedi P.S. I called Microsoft LONG-DISTANCE and after being bounced around for 45 minutes I finally got ahold of someone who knew what I was talking about. This person said that the incompatibility is Apple's fault, not Microsoft's, and therefore Microsoft feels that it should be corrected by Apple. What a copout.