rodney@solar.card.inpu.oz.au (Rodney Campbell) (03/06/91)
Can someone PLEASE HELP ME...
I have an Amiga 3000UX and I have decided (much to my detriment) to try
the overscan feature in an attempt to get some more screen space.
I am running Sys5 R4 Beta3j of the OS and in the Manual 'Using Amiga Unix'
on page 176 is a section which describes the following:
'If your monitor has overscan, and you want these extra pixels, modify the
file /etc/rc2.d/S70sioc. Near the end of this short startup file is a
commented out line that sets the overscan for each of the four screen
edges.
Now I did this and it sort of worked but it was a little too much so I
thought I might just reduce the number of extra pixels and the offset
again and reboot. Now here is where the problems began.
After Reboot all of the virtual screens were garbled and just producing
flashing out of sync blocks of colour. Since then I have been rlogin into
the machine and editing the file and rebooting. After many retries I can
often get the screen back to some semblence of normality but if I then
reboot again it is stuffed again. It seems that whatever this line:
sioc setdisplayadjust -offsetx -offsety overscanx overscany
does is cumulative and thus it offsets and overscan amounts are
continually cycling past the displayable area.
If anyone knows if this is true and how to get the damn thing to return to
the original state I would be most appreciated. Does someone at Commodore
have any ideas, please.....
Rodney....
_______________________________________________________________________________
Rodney Campbell - Telecom Aust |MHSnet: rodney@solar.card.inpu.oz.au
Integrated Network Products |Snail : 8th Floor, 91 York Street, Sydney 2000.
Customer Applications Research | or PO Box A226, Sydney South 2000, Australia.
& Development |Phone : +61 (0)2 364 3346 Fax: +61 2 262 3813ford@amix.commodore.com (Mike "Ford" Ditto) (03/07/91)
rodney@solar.card.inpu.oz.au (Rodney Campbell) writes: > I have an Amiga 3000UX and I have decided (much to my detriment) to try > the overscan feature in an attempt to get some more screen space. [ ... ] > Now I did this and it sort of worked but it was a little too much so I > thought I might just reduce the number of extra pixels and the offset [ ... ] > After Reboot all of the virtual screens were garbled and just producing > flashing out of sync blocks of colour. In the current software, only certain specific horizontal adjustment settings work correctly. This limitation will be removed in the future. When the documentation was written, we didn't know this limitation would be present. Some settings that should work include: Horizontal offset can be 0, -8, or -16. Horizontal overscan can be 0, 16, or 32. There are no such peculiar limitations in the vertical direction. Some functional settings are: 0 0 0 0 # 640 x 400, (no overscan) -16 0 16 16 # 672 x 432 -16 0 32 32 # 704 x 464 The example in S70sioc that shows horizontal offset -12 doesn't work on all systems and will be changed in future releases. > It seems that whatever this line: > sioc setdisplayadjust -offsetx -offsety overscanx overscany > does is cumulative and thus it offsets and overscan amounts are > continually cycling past the displayable area. No, this is not true and must have been an illusion. > If anyone knows if this is true and how to get the damn thing to return to > the original state I would be most appreciated. The original state, of course, would be achieved by commenting out the line, as it was shipped, and rebooting. I hope one of the above examples also works for you to give you the overscan you want. -=] Ford [=- "The term most often used in this (In Real Life: Mike Ditto) manual is `implementation-defined'." ford@amix.commodore.com - SVR4 Programmer's Guide: POSIX uunet!cbmvax!ditto ford@kenobi.commodore.com