can't change screen resolution?

[blanning]

I'm using 3.1 on a 2000.  I went into ScreenMode in the prefs window.  I changed it from 640x200 to 640x400 interlace, then clicked use.  Nothing happened.  Still in 640x200.  What's going on?

Maybe it's mui related?  I just installed mui.  Its programs seem to be able to change resolution just fine.  But the workbench can't.  Am I doing something wrong?

brian

[blanning]

I still can't change the resolution.  Screenmode seems to let me change and save the resolution.  It will show me 640x400, but the resolution isn't interlaced.  The overscan tool can tell it's only 640x200 though.  

This is driving me nuts.  I can't open trident because it needs a higher resolution.

brian

[blanning]

If I had to guess, I'd say that mui takes over handling screen resolutions switches, but since this is an unregistered version of mui, it's preventing the interlaced screen resolutions now.  I'd love to uninstall this to test it, but I'm not sure how to go about doing that.  And since trident requires mui, I guess I'm stuck.

All this to get a deneb working.  This sucks.

brian

[blanning]

AmigaMance wrote:
Can you change the screen mode to a lower resolution or is it stuck to 640x200 only? Can you change other system preferences like the WB patterns?
 I don't think that MUI is related to the problem.. Perhaps.. Try to run MUI prefs -> System -> Press "Call inspector". If there is a WorkBench entry, delete it, save and reboot.

Workbench is stuck in 640x200, but mui's demo programs can change the resolution.  I haven't tried other settings.  I'll try that in a minute.  Call inspector didn't seem to do anything.  There is a workbench entry.  I'll try deleting that also.

brian

[blanning]

Patterns and lower resolutions don't work either.  I deleted the workbench entry, but no effect.

The display tab in PSI shows no displays and everything is ghosted out.  Not sure what that means.

brian

[blanning]

AmigaMance wrote:
2 things that you should do.
- Launch a system monitor like Scout or the Who command and see if there is an « IPrefs » task, active in memory

- Open a CLI window, type
List env:sys/
and paste the output here.

Ah!  The startup script complains that iprefs can't be found.  This was the error message I was talking about earlier, the one that's quickly covered up by the workbench.  Sounds like a winner.  I'll investigate further later today.

brian