Path: utzoo!attcan!uunet!mcvax!ukc!eagle.ukc.ac.uk!icdoc!tgould!iwm From: iwm@amvax3.ic.ac.uk (Ian Moor) Newsgroups: comp.sys.amiga Subject: GOMF (was Can Amiga reach for the Sun?) Message-ID: Date: 3 Nov 88 19:09:28 GMT References: <6526@xanth.cs.odu.edu> <41435@linus.UUCP> <5170@cbmvax.UUCP> Sender: news@doc.ic.ac.uk Organization: Dept. of Computing, Imperial College Lines: 24 In-reply-to: jesup@cbmvax.UUCP's message of 2 Nov 88 04:45:46 GMT Posting-Front-End: GNU Emacs 18.45.10 of Tue Jan 12 1988 on amvax3 (berkeley-unix) jesup@cbmvax.UUCP (Randell Jesup) says: > GOMF is a neat hack. It can be a useful tool for a developer, >or even a sophisticated user. It's DEADLY DANGEROUS to a generic or >novice user! > GOMF may seem to recover you from a situation, but other important >things may have been trashed. What can go wrong ? I guess anthing that was in RAM - resident programs, RAM: contents, other tasks (disk drivers aargh!). I am using PDC from Fish Disk 110 which tends to guru when it finds C that it cant cope with - now that I know what these are its not so bad, but until I got GOMF things were slow and painful. I'm using GOMF 1.0 from a disk `free' with a magazine, is GOMF 2 or 3 that much better given the price (#20 in the UK) ? My main complaint is that locks created by the program that blows up seem to stay (or at least thats what seems to be going on, if `PDC foo.c' crashes, there is no foo.s but I cant create foo.s until a reboot. -- Ian W Moor. Department of Computing Imperial College London SW7 UK