#Monitor Modes Missing
10 messages in this thread
Try opening the DEVS:Monitors drawer from Workbench, and double-click the PAL
monitor. Now open the ScreenMode preferences. Is PAL still not there? Open
the Overscan Preferences. Is PAL there?
Ian:
I will have him try that tomorrow. I've been a bit swamped the past
couple of days and haven't had a chance to follow through.
Clint <Chaocity>
Ian:
Tried having him double click on the various monitor icons in the
Devs/Monitors drawer and then check with the ScreenMode prefs. It didn't change
anything. He reinstalled the entire OS and it still doesn't change anything. He
tried with and without VGAOnly in the drawer. The paths all seem to be OK all
the way through startup. I think that is has to do with his Syquest (using
DataFlyer SCSI), as it stopped working after he installed it.
Clint <Chaocity>
Clint,
I was reading this thread and realized that I also have this problem with
monitor drivers and the ScreenMode prefs. I have a GVP8up+120HD with a MAXTOR
drive installed, 3.01 OS, 030/882 accellerator, megachip, and 12meg of fast RAM
running on an A2000.
Recently I purchased a 1950 multyscan monitor and tried to load the
Multiscan driver into the Devs/monitors drawer. Previously the NTSC driver was
the only driver in use. Although I tried the double click trick, rebooted,
re-assigned, nothing would make the selector in ScreenMode prefs recognize any
driver other that NTSC (I tried some of the other drivers with the same
results). I do have a A2300 genlock installed in the Video slot, and DCTV is
also installed, I don't know if they could affect or limit choices in
ScreenMode, stranger things have happened.
If you or some one else can come up with an answer to this I would be most
appreciative as I suspect would quite a few others. My personal suspesion is a
bug in OS3.01.
Many thanks.
Kapryan Kennedy
Kapryan:
I have the same problem on my 3000 under 2.1, but I assumed that it had to
do with having the EGS chipset rather than the AGA chipset. That's why I
suspect a bad library somewhere for my user who is having problems. If he had
an old pre-AGA library somewhere then it may not know how to deal with Monitor
types. So far no luck with finding the problem though. <sigh>
Clint <Chaocity>
Clint, –<sigh>– You sound weary. Hope you can get some R&R before getting
engulfed in VP4.0. I see you responding to many users concerns on the Amiga
forums. I'd like to say I appreciate your spirit and am glad that you're still
around to answer questions and help out.
I have been contemplating the problem with monitors and the ASL requester,
and realized that I had recently installed MUI and a recent unofficial upgrade
to the asl.library from AmigaTech called ASLV42.lha. Could MUI of this new
library have something to do with it?
Many thanks.
Kapryan Kennedy
Kapryan:
Actually, programming _is_ my R&R. <grin> The order filling, tech support,
product manufacturing, newsletter writing side of things takes up most of my
time, so getting a chance to program is a relief.
It is definitely possible that MUI or the ASL library could have some
impact. The only way to tell is to de-install them and see if the problem goes
away. I don't have MUI on my 3000 and I am using the released version of
asl.library, so that is not the cause here. My friend is pretty much of a
novice, and I don't think that he has installed anything other then commercial
packages, but some of them have been known to change libraries.
Clint <Chaocity>
Clint,
I'm going to try de-installing MUI and ASL as soon as possible. If that yields
results it may be because I'm still running the demo version of MUI wich is
somewhat save crippled, and since ASL42 is MUI dependent that may be the
problem. I'll let you know how that turns out.
I'm glad to hear that you have something to do for fun. :^) VP is one of my
favorite programs, I'm always looking forward to the next version. Many thanks.
Kapryan Kennedy
Clint,
I have an A3000 that had a similar problem with the ScreenMode prefs. I
found that it was due to a defective IV24 board which when removed, the missing
screen modes magically showed up. I think you may be right about it having
something to do with the addition of a defective or conflicting piece of
hardware. I don't know if this helps, good luck.
David (75714,2776)
Waiting just "two more weeks" <G> for my 060/A4000T
David:
Thanks for the info. Unfortunately, I don't know the internals of how the
Amiga decides which modes to display, but it does sound like some hardware
changes confuse it.
Clint <Chaocity>