GOMF- what good is it?
10 messages in this thread
Karl,
I agree. Wait 'till you get GOMF3.0. I'm still experimenting there to get a
reasonably stable configuration. BTW – DMCS doesn't like either GOMF at all and
generally crashes my machine upon exit, although the program runs fine. I
always NUKE GOMFx.x before using it.
David
David,
I did change my startup-sequence recently to kill the Runback I had to
invoke GOMF, and later that session (after rebooting), GOMF awoke for the first
time in months. That tempts me to conclude that it is incorrect to runback it,
but something or someone pursuaded me that it was correct to do so when I
installed it, and you say that you use Runback to invoke it. Now I'm really
confused. BTW, I have the same problem you do with DMCS.
Are you saying that you now have GOMF3.0? Are you having better luck with
it if so? What are the REAL reasons to upgrade (i.e., is there really an
improvement)?
You said you Nuke'd GOMF before starting DMCS; what are the steps YOU use
to do that?
Karl
Karl,
I've had GOMF3.0 for about a month now, although I wasn't using it much because
I had problems with it in my system configuration. (I also got the GOMF button,
but have not put it in yet. I like to change only one thing at a time whenever
possible 8). I couldn't find in the new manual any mention of a wait command
after invoking GOMF3.0, although it definitely say to RUN >NIL: GOMF3.0 for
WB1.3 or RUNBACK GOMF3.0 for WB1.2 in the manual (pp 21 & 22). I couldn't get a
stable configuration without adding a Wait 5 statement immediately after the
RUN commmand. (I always try to start out by following the instructions, and
then, if it doesn't work, anything that appears to work goes! 8). I may have to
change it to a longer wait period. Possibly the faster autoboot start-up (it is
a real _joy_, BTW) makes a longer startup wait necessary.
As far as reasons to upgrade to 3.0 – 1) It is supposed to catch more errors
than 2.2. 2) It is supposed to be more compatable with HD's (I think). 3) The
manual is _much_ better. 4) The NUKE command has a "task selector" that makes
it much easier to use. 5) It supports the GOMF button – if you're brave enough
to install it. 6) I try to make it a general rule to upgrade to the "latest and
greatest" version of software for continuing support and any bug fixes and
enhancements. (i.e. general response to first trouble call – "You need to
upgrade to the latest version. If you still have trouble, call back.")
<continued>
<continuation>
To NUKE any task, including GOMF2.2, do the following:
1) open a CLI and expand it to full screen (for convenience).
2) type NUKE ! <CR> to get a task listing
3) note the EXACT, case sensitive task name that GOMF2.2 is running under. It
will be something like "c:GOMF2.2" or "System/GOMF2.2".
4) Assuming you want to remove "c:GOMF2.2", type in the command: NUKE c:GOMF2.2
<CR>
5) if everything goes according to plan, you should see a sign-off message from
GOMF similar to the startup message.
Note that there are certain transient task conditions that can cause NUKE not
to find a task as you're trying to NUKE it. If, while trying to get rid of
GOMF, you don't get the sign-off message, GOMF is still there. Just do the same
command again. (Under GOMF3.0, you just double-click the NUKE icon, select
GOMF3.0 and then the NUKE gadget.)
Note that there are errors that cannot be trapped. (The system lockup that
occurs after exiting from DMCS is one of them.) Supposedly, the GOMF button is
for those lockup occaisions. I have experienced GURUs that lead to HD reboots,
so I guess that there are some things that GOMF3.0 still cannot
<continued>
<continuation>
pick up.
Sorry for the long winded reply, but I hope that it helps you.
David
David,
Thanks for the comlete reply; it helps a lot.
You've mentioned several times that you have difficulties that force you
to do a Wait. Just what are these symptoms? Does the boot process suffer in
some way? I was Runbacking GOMF for a month or more on the hard-drive and it
seemed to work OK. After removing the Runback, per Ron Troy, GOMF has awakened
twice in two days (whereas I hadn't seen it in a month while runbacking), and
it still loads fine, but of course ties up the machine while it installs
itself.
I understand that what GOMF is attempting is no small feat, and am
willing to put up with some inconvenience in order to get it to work, as long
as I can figure out what to do! You've helped. I've forgotten; what's the
upgrade method for 3.0?
Karl
Karl,
Glad to be of some help.
The problems I was seeing showed up as keyboard or modem strangeness, even
though boot-up appeared to go OK. For example, I'd open a Shell, then type
'endcli', only the 'e' could not be typed, leaving 'ndcli' (strange, no 8).
Sometimes it also happened on 'a' or 'y'. I tried executing SetMap from the
icon, but that was not the problem. Does this sound familiar at all?
Did you send in your warranty card? I received an upgrade order form from
Hypertech/Silicon Springs and just sent it in and waited. If you haven't sent
it in, I'd just send it to them in an envelope and a letter requesting the
upgrade, along with some method of payment. I believe that the upgrade notice
doubled as the order form, so I don't have it to refer to for you. As I recall,
the upgrade cost w/ the GOMF button was $35 US.
David
David.
I have never noticed the problems you encountered with the keyboard or
modem.
I sent in the warranty card, but have not received anything else
resembling an upgrade order form. I did, however, misplace the warranty card
for awhile and sent it in in November, so maybe they haven't gotten around to
it yet.
You have repeatedly said that 3.0 expects either Run or Runback to start
GOMF; did you do that with 2.2 also? My manual says just GOMF2.2 to execute.
Just curious. I'm still having better luck with it without Runbacking like I
was. Strange.
Thanks,
Karl
Karl,
Whatever works in your configuration is fine. The GOMF2.2 manual says that
Runback is not required for GOMF2.2 (on pp 16 & 17). The GOMF3.0 manual says
that RunBack(WB1.2) or Run >NIL:(WB1.3) _IS_ required for GOMF3.0 (pp 21 & 22).
The problems that I was describing with DMCS and the keyboard occurred with
GOMF3.0 installed as per the manual.
When I was first experimenting with GOMF2.2 many months ago, I couldn't get it
to work properly for a reason that I can't remember at this time. I then tried
starting it with RunBack and was able to get it to work. I'd be the last one to
advise ignoring the printed instructions, I just was making the point that I
solved _my_ problem that way. Keep in mind that my problem could have just as
well have been something else and not GOMF2.2. I'm not really in a position to
recreate it (since I had KS1.2 then), although I'll try it with 1.3 and let you
know.
Good luck with it. You'll probably be getting your upgrade notice eventually.
If you want it faster, I'd just call them and order it. If they received your
warranty card they should accept a phone order.
David
David,
Thanks for the continued info. It's interesting that they've changed how
it's invoked from one version to the next. I'm keeping all your notes in case I
have trouble with 3.0, but understand your points about being just one case.
Karl