LDSHANER@MTUS5.BITNET (Leon D. Shaner) (01/23/91)
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???' Could it be that the monitor doesn't like the scanning frequency used by productivity mode, or is it (gasp) something with his A3000 ??? Any insight, divine revelations, guesses, etc. greatly appreciated... Thanks... --Leon +--------------------------------+-----------------------------------+ | LEON D. SHANER <LDSHANER@MTUS5> :BBS: AMIGA BITSWAP CENTRAL DISPATCH: | OR <LDSHANER@MTUS5.CTS.MTU.EDU> : (906)482-8248 DIALOG PRO! BETA : | MICHIGAN TECHNOLOGICAL UNIVERSITY : FREE! :24 HOURS :80 MB :2 LINES!: +------------------------------------+-----------------------------------+
jesup@cbmvax.commodore.com (Randell Jesup) (01/24/91)
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") ;-)
troyb@pro-graphics.cts.com (Troy Barlow) (01/28/91)
In-Reply-To: message from jesup@cbmvax.commodore.com
I also have the Diamondscan. When I run it on my 2000 (with ECS chipset)
under WB 2.04 I get the same problems. The screen is sync'ed fine, but the
colors don't look ok, and I get ghosts. I also bought the cable from Redmond.
Redmond is sending me a new cable (the same cable, but no chip init), if it
works, they will exchange it with my old one.
When I run screenmode, it shows Productivity Mode's in the window, and they
work fine except for the bad colors/ghosts (looks like composite video!). I
should note that ALL the video modes look like this, not just productivity.
The computer is fine since the Amiga monitor works, the Diamondscan is also ok
since it works in VGA on my 386.
-Troy
-- Troy Barlow
Pro-Graphics BBS 908/469-0049 "It's better than a sharp stick in the eye!"
Internet: troyb@pro-graphics.cts.com
UUCP: crash!pro-graphics!troyb
ARPA: crash!pro-graphics!troyb@nosc.milandy@cbmvax.commodore.com (Andy Finkel) (02/22/91)
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... > There are two possible problem; one could be your cables. I'm not familiar with the exact set you have, but I've heard that some people with homemade cabless containing inverting buffers have had problems. The other could be that you just need a special monitor description for your monitor. The easy to create one for the Diamondscan is to make a copy of the productivity mode monitor, call it diamond, and add the following tooltype: BEAMCON0=0x1b88 Test the icon by adding it to the system by clicking on it; then bring up the ScreenMode editor and select it, and see if your colors are more like what you'd expect. andy -- andy finkel {uunet|rutgers|amiga}!cbmvax!andy Commodore-Amiga, Inc. "God was able to create the world in only seven days because there was no installed base to consider." Any expressed opinions are mine; but feel free to share. I disclaim all responsibilities, all shapes, all sizes, all colors.