Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: DiamondScan & Productivity Mode
Message-ID: <17996@cbmvax.commodore.com>
Date: 24 Jan 91 00:33:21 GMT
References: <91022.115050LDSHANER@MTUS5.BITNET>
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA
Lines: 33

In article <91022.115050LDSHANER@MTUS5.BITNET> LDSHANER@MTUS5.BITNET (Leon D. Shaner) writes:
>I own a Mitsubishi DiamondScan (AUM1381A) and have been using it with a cable
>made by Redmond Cable, that uses the monitors NTCS compatible inputs...
>
>A friend of mine has an A3000 and I decided to see how this monitor and cable
>fared with productivity mode - it didn't!!!  It seemed to be sync'ed "okay"
>enough, but the contrast and brightness was so dark that things were barely
>readable...  The worst problem was severe distortion and multiple ghosted
>images....
>
>Is this a problem with the choice of cables???  I realize that if I did get
>an A3000, I would want to get a cable that takes advantage of the monitor's
>multi-scan capabilities, but I'm thinking along the lines of 'How will the
>monitor look on my 2000 when I get ECS and 2.0???'

	Did he install the VGA monitorspec in the monitors drawer?

	Is he running version 2.02 KS and WB?

	It sounds like a problem where the monitor thinks it should be
digital RGB instead of analog.  I think it was solved by something in the
VGA monitorspec, or it might be a cabling issue (I forget exactly, maybe
Andy remembers).

	Long-term, of course, he should get a 15-pin cable and hook up to the
31Khz video port.

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com  BIX: rjesup  
The compiler runs
Like a swift-flowing river
I wait in silence.  (From "The Zen of Programming")  ;-)