#C=1950 Monitor Help
3 messages in this thread
To Anyone,
I need some help trouble shooting problems with a used C=1950 multiscan
monitor that I recently purchased. I am unable to get an acceptable signal to
the monitor through the RGB port of my A2000, however when I connect to the RGB
port of the A2300 genlock installed in the Video slot the monitor functions
properly. This seems odd to me since my old monitor (ThompsonRGB) was able to
use both ports with no problem. Does the presence of the genlock change the
signal in the original RGB port? If it does, is their a cable or hardware fix?
Also, I cannot get the Preferences ScreenMode program to acknowledge the
precence of the Multiscan monitor driver that I have placed in the
Devs/Monitors dir, so I am unable to choose any of the screen modes that that
driver provides. Has anyone else had this problem with OS 3.1? If you have,
how did you resolve it?
My system has the ECS chips so I should be able to access this driver. Any
help would be greatly appreciated.
Kapryan Kennedy
Have you tried removing the genlock? Also what do you mean by an acceptable
signal? My a1200 produces a picture so dark on my monitor it is unusable ( but
then it was free and it works fine on my a500 ).
Phill
Phill,
<<Have you tried removing the genlock?>>
Not yet. I am hoping that someone else has had a similar exprience that could
help me narrow down the problem without having to dissassemble my whole system.
Meanwhile there are some good people at Redmond Cable looking into this problem
for me, though they seemed mystified by it as well.
<< Also what do you mean by an acceptable signal?>>
Well I assume that the signal coming from my the A2000 RGB port is unacceptable
to the 1950 monitor because it produces a scrambled image with interference
lines running all over the screen. However my old monitor works fine on the
same port as does my DCTV.
As it is my system is quite usable, but I feel quite fortunate to have had a
genlock already installed or this 1950 monitor would have been entirely uselss
to me. Either the problem is in the adapter cable or in the A2000 RGB port
since the specs for the monitor indicate that it should be able to connect to
the Amiga RGB port. If the genlock is producing the problem then I suppose I
can live with it since it is just a hardware bug, and I know what is causing
it. Finding out will help me decide wether to send my Amiga to the shop for
repairs (a costly event), or if I just need a new adapter cable ( much more
reasonable).
BTW: Do you have any thoughts on my monitor driver problem?
Many Thanks,
Kapryan Kennedy