#reset workbench?
8 messages in this thread
After installing a Super Denise on my 2meg chip ram equipped 2000, I get a
requestor for trying to reset the workbench screen. Can anyone tell me
what this is and how to deal with it? At this point, the system does
appear to be running normally otherwise. I did have a lot of trouble at
first, though. I have not normally kept any monitors listed in the
devs:monitors directory, but now I have ntsc and pal. I run a 1084s.
I am using ados 2.1.
Thanks,
Ron
You have something in the Startup-sequence prior to IPREFS that outputs to
the screen. Find it and redirect the output to NIL:
(i.e. "XXXXXX >NIL:"). That will solve your problem.
//
-Karl \X/ Amiga and Autopilot: The *only* way to fly!
It seems to be gone now. Apparently when I was messing around with s-s to
get my system working after the denise upgrade I put in some echo's. The
actual problem was that I didn't have any 'monitor files' like NTSC and
the startup didn't like that one bit. It didn't matter with the old
denise. Once I put them in and restored my original startup I was fine.
Any suggestions on how to use the new modes of the super denise?
Thanks much,
Ron
Not really. I'm using a Flicker-Fixer, and they weren't compatible with
the ECS modes. So I'm stuck with high res interlaced. Of course, since
almost all programs support that mode, I would be using it most of the
time anyway. I have *seen* the ECS modes on other machines, though, and I
expect you will have to play with the fonts to get much use out of it.
//
-Karl \X/ Amiga and Autopilot: The *only* way to fly!
Understood. I suspect that I'll also have to find not just a different
font size but a different font. And its desire to reset everything each
time you make an adjustment seems to need a reboot to really work, so
these changes are a pain in the but. Thanks,
Ron
Ron,
if you are seeing the requester that asks to reset the Workbench
screen, then you have a program in your startup-sequence, prior to the
call to IPrefs, that is getting a lock on the screen. Doublecheck your
startup sequence to make sure that all programs prior to IPrefs have their
output sent to NIL: as well as input.
Brian
bjbart@watserv.ucr.edu
All cleaned up now. Thanks!
Ron
Ron,
your welcome. That problem drove me to distraction when it happened to
me.
Brian
bjbart@watserv.ucr.edu