CompuServe Messages

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