#GOMF- what good is it?
15 messages in this thread
Ron,
GOMF3.0 requires a "run > nil:" or a "runback" 'cause, unlike GOMF2.x, it
won't otherwise detach from its startup CLI. I'm personally very curious as to
why this is so…it seems like kind of a step backward. GOMF2.x also paused
execution of the startup-sequence while it installed itself, grabbed all
necessary vectors, etc. GOMF3.0 doesn't do that, thus the need to follow it
with a "wait" (not mentioned in the manual, BTW). Actually, the best thing to
do (for those of us with ARexx) is to follow the "run > nil: gomf3.0" with a
"waitforport GOMF3.0Port"; this not only eliminates drive thrashing but also
speeds up the start-seq.
I was gonna install the GOMF Button this week (along with the 1.3 ROM, my
HD, and controller) but I'm a bit leery now after reading David's message about
GOMF3.0 and KS1.3. Think I'll wait awhile….
-Dave
It is very strange. BTW, what is/where do you get this waitforport?
Ron
Ron,
Waitforport is a short program that Bill Hawes put on the ARexx disk. I
don't recall offhand which directory/sub-directory it's located in, but it's
somewhere on the disk. Of course, you also need a monitor program of some sort
to determine the port names of programs like GOMF. I use a program I found on
an old AMnews disk.
-Dave
I found it. Thanks. And amon (though it is still somewhat unstable) can find
the port.
Ron
Ron,
I received version 1.05 of WShell today in the USnail; the WShell disk now
also contains WaitForPort. I'm not familiar with AMon, tho I assume it's
similar to the monitor program I use (which, BTW, behaves rather strangely-it
redraws its entire screen every second or so, and it's also a CPU hog).
GOMF3.0 seems to be working quite well. The only thing it hasn't caught is
a curious (and seemingly random) crash that I've occasionally been experiencing
with Access! I'll be zipping away here, capturing messages at 2400 bps (it's
never happened at a slower rate), and all of a sudden the program will fall
thru the floor, straight to the GURU. The last time it happened I clicked the
left mouse button just like the GURU says to, the machine rebooted, I opened
the Access! drawer, started the program, and–surprise, surprise!!–I was
_still_ online. That's never happened before. 8^)
-Dave
David, where in your startup are you running gomf3? Amigamonitor is not cpu
heavy, but does have some flaky spots, like when I exited out after showing
ports, it crashed, and a little while later the machine hung in whap. As for
still being online, that has happened to me at times.
Ron
Ron,
"run > nil: GOMF3.0" is the second command in my startup-sequence, right
after "setpatch." The GOMF manual vaguely warns of possible problems which
could be caused by using both GOMF and SetPatch, but I haven't noticed anything
unusual. (The Access! crashes, BTW, predate both GOMF3.0 and SetPatch…I
suspect Access! and something else in my system are occasionally running into
each other and creating havoc; it happens so rarely that I haven't taken the
trouble to track the problem down.)
I meant in my last message to say that the monitor program I use (also
called Amiga Monitor, I think) redraws its _window_ every second or so, not its
_screen_. I was going to mention something about the program opening its own
1-bitplane custom screen, but the message ended up a bit garbled. That's what
I get for composing "live" at 2400 bps with the online clock in my wallet
ticking very loudly. <grin>
-Dave
Yeah, I keep learning not to 'compose' online. Its not worth it. You do run
the program early enough. I assuming you're using the setpatch that cbm
provides on the 1.3 wb disk. I wonder why gomf whould have a problem with that
– all its doing is fixing some screwed up code. Maybe they would suggest
running gomf 2nd, but since the error handling is part of what is screwed up
that wouldn't make sense to me. I wish we could get a straight answer.
Ron
David,
If you have WaitForPort, it also means you have ARexx, and you can get a list
of all ports from ARexx by typing (in a WShell),:
"say showlist('p')
If you don't have WShell, you can make a small script called something like
'ports.rexx', with the above command in it, and call it with the 'rx' command.
-larry
Larry,
I do indeed have ARexx (and WShell as well…received the V1.05 update
yesterday). Thanks for reminding me about showlist(). Time to chalk up
another one for ARexx…'tis bloody useful. 8^)
-Dave
Dave,
Thanks for the port id. It's going into my startup-sequence as soon as I end
this Whap! session.
David
David,
You're quite welcome. The WaitForPort ought to smooth things over
considerably. Remember, tho, that the messageport names are case-sensitive;
"GOMF3.0Port" and "gomf3.0port" are not the same.
Good luck.
-Dave
David,
I have had 1.3 WB/Roms for a while now as well as the GOMF 3.0 /button in
my system with no problems.Now my biggest problem is that I haven't had any
problems to test it out on! Oh-well, it gives people something to ask what that
little red button under the drive is for.
Kurt L.
Kurt,
Thanks for that info. Ok, I'll be "daring" <chuckle> and install the Button
along with the 1.3 ROM. So you've put the button under a disk drive, eh? I
still don't know exactly where I'm gonna put mine. Decisions, decisions….
-Dave
Ya David,
Right under the disk ejector. It hasn't been in my way yet.The cable
is short enough.<Grin>
Kurt L.