home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.misc
- Path: sparky!uunet!destroyer!gumby!wmu-coyote!22black
- From: 22black@sol.cs.wmich.edu (Martin Black)
- Subject: Re: WB 2.1 problems...
- Message-ID: <1992Dec13.162739.10825@sol.cs.wmich.edu>
- Organization: Western Michigan Univ. Comp. Sci. Dept.
- References: <1gevsrINNh1e@crcnis1.unl.edu>
- Distribution: usa
- Date: Sun, 13 Dec 1992 16:27:39 GMT
- Lines: 27
-
- tcampbel@unlinfo.unl.edu (thomas campbell) writes:
-
- >I just upgraded from WB 2.0 to 2.1, and I ran into a few problems:
- >
- >When I boot, several lines are printed on the CLI window:
- >
- >EXECUTE: Can't open T:M
- >object not found
- >
- >Also, I use VirusZ and an overscan screen. When booting, the system
- >doesn't get a chance to change from a 'normal' to an overscan screen
- >before the user-startup is executed. I've tried moving the location
- >of the user-startup execution within startup-sequence, and I've tried
- >putting waits before VirusZ is executed. Is there a solution? I'd
- >like to be able to run VirusZ automagically instead of having to do it
- >manually.
-
- Well make sure you put on every command executed in your startup-seq and
- user-startup a >nil: so nothing gets displayed.
- Something new is in the 2.1, that makes it so if there is never any
- output to your first screen, ie intro screen, then the screen won't
- show up, instead the workbench screens is the first and only window
- that opens.
-
- Martin
-
-
-