[comp.sys.apple2] Bouncing Bluster problems

twb5024@rigel.tamu.edu (BOTTING, TYE WILLIAM) (12/08/90)

	Does anyone know if Bouncing Bluster is supposed to have 
problems with a ROM 03 //gs?  I just got it off the ftps and unpacked
it (with no problem, according to GSHK and BinSCII), but the dang
thing just sends me back to the finder when I try to run it.  Is
this normal?  It sounds like a problem someone else was having a
while ago with having wierd INITs, but I booted off the System
Disk 5.0.2 and the same thing keeps a-happening...  Help?

System:  ROM 03 GS, 3.125 MB RAM, Sider D20, Zip GSX (which hasn't
                                                      had any other
                                                      compatibility
                                                      probs yet and
                                                      runs great!)

-----------------------------------------------------------------------
TWB5024@tamu.venus.edu          Warlock           BOTTING@tamu.comp.edu
                              Tye Botting
-----------------------------------------------------------------------

kimbrennan@gnh-starport.cts.com (Kim Brennan) (12/11/90)

Bouncing Bluster consists of three disks. The third disk is the editor.
However, the first two are critical as Bouncing Bluster uses GS/OS4.0 and will
NOT run under 5.0x. You MUST Boot the BB disk to get it to run, you can NOT run
it or launch it from your hard drive if you have 5.0x on your hard drive.
INET: /\_/\  kimbrennan@gnh-starport.cts.com
     / o o \ America Online: KimBrennan
     (  v  ) ______
     /// \\\       \\
      (          / /\\
      | || |\___/ /  ))
     /// ///   ///   ((
                     ))
                     ~

AABENSON@MTUS5.BITNET (12/12/90)

Hmmm... Well if it has all those problems, it better be one FANTASTIC program.
I don't think we should really have to put up with that kind of crap.
If developers would follow the RULES just once in a while, these types of
problems wouldn't happen (unless, of course, it's a memory problem).

On the other hand, Apple doesn't follow their own rules (gee -- MORE
hipocracy), so I'm not surprised that nobody else does either.

                                                     - Andrew.

Internet: aabenson@balance.cs.mtu.edu
Junk-net: AABENSON@MTUS5.BITNET

(Please email responses to aabenson@balance.cs.mtu.edu, if possible.)