mjl@ut-emx.UUCP (Maurice LeBrun) (02/25/89)
About a month ago, I asked about DiamondScan monitors and the cable, and thanks to all who posted or emailed suggestions. I ended up getting a DiamondScan for $500 mail order, and picked up a cable (made by Redmond Cable) from the Memory Location for around $25. As previously reported, the DiamondScan has excellent color saturation, and a pretty good dot pitch. It looks wonderful on top my A1000 -- I wish this had been the monitor I got with my machine. There have been several questions posted on the net re:monitors which I might be able to answer: 1) Why all the fuss about multiscan monitors? If you buy a FlickerFixer or intend to upgrade to the 1.4 chipset (I am planning on getting a 2000 eventually), you will need a multisync to take advantage of the new non-interlaced modes. Might as well start thinking about it now if you're in the market for a monitor, as I was. Also, multiscans generally tend to be of significantly higher quality than the 1080 or 1084. I am very happy with mine, even though I still use a non-interlaced Workbench screen. The black on this thing is a *real* black (at normal brightness levels), which persuaded me to switch to a light-char on black-background color scheme that looks quite nice. With my 1080, I couldn't quite tolerate this (and in fact used black chars on a light screen). 2) There were some questions about the inputs on a DiamondScan. It has three inputs: Standard composite video, RGB analog, and RGB TTL (IBM standard). The Amiga doesn't like one of the RGB analog signals which necessitates a special cable (available commercially, see above, also a schematic was posted to the net). The manual even claims some way to superimpose an Analog RGB image onto a Composite video one, but it looks like it might be messy (cut <-> cable <-> splice). Maurice LeBrun | "A computer is like a hole in the ground Institute for Fusion Studies | into which you pour money" University of Texas at Austin | Internet: | - some poor, mistaken person, mjl@fusion.ph.utexas.edu | obviously wrong :-)