Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!dogie.macc.wisc.edu!indri!polyslo!usc!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Determining Window Border Widths
Message-ID: <16998@usc.edu>
Date: 3 May 89 21:12:40 GMT
References: <2816@cps3xx.UUCP> <6704@medusa.cs.purdue.edu>
Sender: news@usc.edu
Reply-To: papa@pollux.usc.edu (Marco Papa)
Organization: Felsina Software, Los Angeles, CA
Lines: 23

In article <6704@medusa.cs.purdue.edu> wolff@cs.purdue.EDU (Robert M. Wolff) writes:
>From article <2816@cps3xx.UUCP>, by usenet@cps3xx.UUCP (Usenet file owner):
>> What is a viking monitor?(with a gfx card too i would assume)

>The viking monitor is a 1008x800 display monitor that (as far as I know)
>needs *NO* extra graphics cards. If the software is written properly, then
       ^^^^^^^^^^^^^^^^^^^^^^^^^
>it will show up properly on the viking.
>The viking is only 2 bitplanes though... :-(

Wrong! I have one.  It needs a separate video card that goes in the A2x00
video slot (only the first one is used, so it will work even with old "german"
A2000s, unlike the flickerFixer that uses BOTH video slots and therefore
will work only on B2000s).  So the Viking 1 cannot be used with A1000s and 
A500s. The CBM A2024, on the other hand, has the circuitry all inside the
monitor and therefore it will work on ALL Amigas (with some gotchas due to
the memory required on an A1000).  The A2024 is not available, though.

-- Marco Papa 'Doc'
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
uucp:...!pollux!papa       BIX:papa       ARPAnet:pollux!papa@oberon.usc.edu
 "There's Alpha, Beta, Gamma and Diga!" -- Leo Schwab [quoting Rick Unland]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=