CompuServe Thread

#GOMF V3.0

12 messages in this thread
#77739From: Wayne ColeDec 8, 1989 12:18 AM
Andrew, Forget GOMF3.0 .. It is a time bomb that crashes your system in ever shorter times after every reboot until the point where it won't allow a rebot to complete. Then you have to turn the machine off and then back on again followed by a quick edit job to get it out of your startup-sequence. ANd the company will laugh at your problem…they get your money and that is all they are interested in. Stay away from the non-PD version of GOMF. wmc
#77785From: RON TROYDec 8, 1989 12:12 PM
Wayne, I've had enough problems with gomf3, but never system crashing like you describe. Ron
#77787From: Mike SchillerDec 8, 1989 12:31 PM
Wayne: Do your comments apply to GOMF 2.2 as well? I've had some problems with random guru's (that apparently slipped by v2.2) but now i'm wondering if it didn't cause them itself. Any help you might be would be appreciated. -Mike
#77789From: Steve AhlstromDec 8, 1989 12:40 PM
With 2.2, some gurus get by, but, with 3.0, I'm convinced it generates it's own gurus just for something to do.
#77806From: Mike SchillerDec 8, 1989 2:12 PM
So is 2.2 better than 1.0? or is 1.0 better than 2.2? -Mike
#77812From: Philip PriceDec 8, 1989 2:30 PM
I avoid GOMF. Had numerous problems with it. (My system always acted flackey when I had gomf around. Older gomfs also dislike being brought up in your startup-sequence. ie. they go even more flackey if your startup-sequence finishes before gomf puts up all it's notices. Phil
#77893From: Mike SchillerDec 9, 1989 1:23 AM
Phil: GOMF2.2 is the first (or maybe second) command in my Startup-Sequence, and as such it gets through with all it's messages well before the SS stops. It's also possible that some of the problems I've had are related to varying line voltages, and dips that the local electric company here (Florida Power & Light) also known as Florida Flicker & Flash – supplies. For instance I have a disproportionate amount of read/write errors on the hard disk as well as various other miladies. I might try removing GOMF from the SS and seeing if the system gets any more reliable though. -Mike
#77914From: RON TROYDec 9, 1989 9:43 AM
When starting gomf you need to make sure that NOTHING else executes till gomf is finished starting up (either with waits or waitforport). Using it otherwise makes it much more unlikely to work properly according to their people many months ago. Ron
#77800From: Roy S. LauferDec 8, 1989 1:45 PM
Wayne, GOMF's writers are not the most responsible in the field. They originally wrote the device driver for a penlight product that was a misery to use and buggy as hell. The Pen light company had to find another company to do it right. I thought GOMF 1.0 had potential, but 3.0 is another example of a buggy useless piece of software. No self respecting retailer should sell the stuff. Even the writer doesn't have the nerve to try to sell anyone a 4.0 version. I went for the 3.0 button and all – got me no where fast. I soon deleted it from my startup-sequence. It was a good idea, but some companies are known for well running bug free software and others, well… you get the idea! -RSL-
#77874From: RON TROYDec 8, 1989 10:50 PM
I think everyone concluded that the button was more harm then good, but most of the time gomf 3 behaves ok, except with very buggy software, where it goes nuts, and when whap freaks out. Ron
#77918From: Roy S. LauferDec 9, 1989 11:42 AM
Ron, The button is useless, but then the software never helped me either. I just got tired with the problems it was causing and yanked GOMF off my machine. If you find it useful, so be it. I hope it helps you, it didn't help me! -RSL-
#77833From: Andrew J. RichardsonDec 8, 1989 5:45 PM
Bill, Thanks for that advice…think I'll stick with V1.0 that i found here! Andrew