#GOMF- what good is it?
14 messages in this thread
Ron,
If memory serves me correctly, I had to RunBack -5 GOMF2.2 because the AmigaDOS
window would not close otherwise. (I could be wrong and can't try it out right
now.) The GOMF3.0 manual actually instructs using RunBack on WB1.2 and RUN
>NIL: for WB1.3. Again, I couldn't get a stable system without the Wait 5
statement immediately after the RUN >NIL: GOMF3.0 statement. This configuration
works reasonably well, but I actually find that I have more system problems
with GOMF installed than without. I _strongly_ suspect that my problems with it
are that I switched to KS1.3 with an autoboot HD on my A500. I suppose that if
I really got curious I could try the system with the HD turned off, but that's
kind of a pain now that I'm used to autoboot. One of these days I'll get around
to writing a letter about it.
BTW – the new NUKE command is really nice. You can run it from the WB (or from
the CLI) and you get a very nice "Task Selector" requester to use. It's a great
improvement over the CLI only NUKE command.
David
Odd. I run gomf2.2 without any run or runback command, both under ks1.2 and
1.3 (now that I've finally put the rom in). If you use a run or runback you
must delay all that follows long enough for gomf to get settled in, or you will
have a mess. I find no problems related to gomf being in. As for the new
nuke, I had finally gotten taskctl – the good question – which came first,
taskctl or the new nuke! I have ordered 3.
Ron
Ron,
My philosophy has always been to follow the manual first, then, if problems
persist, anything that appears to work, goes 8). I'm not saying that I couldn't
have been mistaken about having to RUNBACK it, but GOMF2.2 has always worked
for me with that configuration. Do you use DMCS at all? If so, keep GOMF
active, load and play one of the demos, then exit. Then just click somewhere on
the WB screen. Usually (but for some reason, not always) you'll get the mouse
changing into "zzz" wait-for-disk access balloon and then all you can do is
move the mouse. AmigaDOS will not recognize any disk insertions or do anything
else.
David
I don't use dmcs, have had no trouble with gomf2.2 run the way I described. The
only thing I'm certain about is that one needs to run it as close to the
beginning of the startup as possible – I've found that running it later leads
to a less stable environment.
Ron
I've been using GOMF 2.2, with DMCS, and have not observed the problems you
have described (not that DMCS hasn't got serious problems 😉
Jeff,
How, exactly, do you invoke GOMF in your startup-sequence? I'm curious as
to how you are avoiding the problem with DMCS. Also, are you using KS and
WB1.3?
Karl
Do you let the WB close when DMCS runs? Closing the WB is one of my pet
peeves. I almost always leave a window open on the WB when I start DMCS so
that it can't close the screen. I think that might be the difference (i.e.,
the crash occurs when DMCS tries to reopen the WB).
Jeff,
I'm not sure it's possible to "let the WB close". If you mean closing the
current window, I don't believe I've done that prior to running DMCS, but it's
an interesting point: I'll try that immedieately. Thanks!
Karl
DMCS tries to close the Workbench screen. Try Left Amiga-N from DMCS. If the
Workbench screen doesn't appear DMCS has closed it. If you are running a
program that opens a window on the Workbench (other than a drawer window.
something like a CLI) DMCS can't close the Workbench screen. I always have a
clock running on the Workbench. I though that this might be why DMCS doesn't
crash for me. Apparently there is more to it.
Jeff,
Interesting. Which Amiga do you have? I've got an A500 and had the problem
before and after upgrading to KS1.3 and before and after my HD addition. DMCS
works fine, itself, problems just occur after exiting.
I also find that choosing a CANCEL gadget in the file requester causes problems
on exit. I try to avoid CANCEL operations at all cost. You might try CANCELing
something and then exiting, just to see what happens. I'd be interested in
hearing.
David
I have a B2000, with 1Meg. I'm running KS1.2 and WB1.3 (with a bit of ARP
lying around). I use an interlaced overscan WB, and run MachII. Because the
MachII window is open, the WB doesn't close when DMCS starts. I think that
this is the significant difference. I haven't time to try it out right now.
Give it a shot.
Jeff,
Thanks, I'll try it, although I seem to remember trying something similar
before with similar results. Let you know how it comes out.
David
Jeff,
Update… I tried opening a shell and then ran DMCS. I checked and made sure WB
wasn't shut down and then played the DMCS Bach demo piece. The piece played OK
and then I exited… INSTANT LOCKUP.
This is w/ GOMF3.0 started with RUN >NIL: GOMF3.0.
Well, I tried anyway 8).
David