usenet@cps3xx.UUCP (Usenet file owner) (09/06/89)
Two simple questions to those in the know:
1: I have asked this twice before, but I have not seen it
answered as yet.
Will ScrollRaster() be fixed in respect to SIMPLE_REFRESH???????
A simple yes/no answer from CATS would be nice.
2: The ECS I have heard will allow for 400 line display modes
non-interlaced. THis is fine if you have a multisync.
What happens if you have a standard NTSC compatible monitor,
and some whizbang software opens up a 400 lines non-interlace
screen??
I have heard that if you do this you will actually destroy or
damage many monitors.
If so, there should be a hardware toggle switch to prevent
such displays from being used if you only have a regular
monitor, no?
REAL NAME: Joe Porkka jap@frith.cl.msu.edubaird@ditsyda.oz (John Baird) (09/07/89)
in article <4463@cps3xx.UUCP>, usenet@cps3xx.UUCP (Usenet file owner) says: > Two simple questions to those in the know: > >.....Stuff..... > > 2: The ECS I have heard will allow for 400 line display modes > non-interlaced. THis is fine if you have a multisync. > What happens if you have a standard NTSC compatible monitor, > and some whizbang software opens up a 400 lines non-interlace > screen?? > >.....More stuff..... > > REAL NAME: Joe Porkka jap@frith.cl.msu.edu What about those of us lucky enough to have PAL Amigas? Does the ECS support 320 x 256 and 640 x 512 , or are we stuck with NTSC screen sizes? John ________ John Baird CSIRO Information Technology - Knowledge-Based Systems Engineering PO Box 1599 baird@ditsyda | North Ryde NSW baird@ditsydb | CSIROs opinions are under review, 2113 Australia baird@ditsydd | so these must be my own. Ph: 02-887-9384 baird@ditmelb |
mks@cbmvax.UUCP (Michael Sinz - CATS) (09/08/89)
In article <4463@cps3xx.UUCP> porkka@frith.egr.msu.edu () writes: > >Two simple questions to those in the know: > > 1: I have asked this twice before, but I have not seen it > answered as yet. > Will ScrollRaster() be fixed in respect to SIMPLE_REFRESH??????? > A simple yes/no answer from CATS would be nice. The answer is:.... Yes > > 2: The ECS I have heard will allow for 400 line display modes > non-interlaced. THis is fine if you have a multisync. > What happens if you have a standard NTSC compatible monitor, > and some whizbang software opens up a 400 lines non-interlace > screen?? > > I have heard that if you do this you will actually destroy or > damage many monitors. > If so, there should be a hardware toggle switch to prevent > such displays from being used if you only have a regular > monitor, no? There will be majic... /----------------------------------------------------------------------\ | /// Michael Sinz -- CATS/Amiga Software Engineer | | /// PHONE 215-431-9422 UUCP ( uunet | rutgers ) !cbmvax!mks | | /// | |\\\/// When people are free to do as they please, | | \XX/ they usually imitate each other. | \----------------------------------------------------------------------/
jms@tardis.Tymnet.COM (Joe Smith) (09/09/89)
In article <2179@ditsyda.oz> baird@ditsyda.oz (John Baird) writes: > What about those of us lucky enough to have PAL Amigas? Does the ECS >support 320 x 256 and 640 x 512 , or are we stuck with NTSC screen sizes? >2113 Australia baird@ditsydd | so these must be my own. They say there will be a single Agnus for both NTSC and PAL machines. The "1-meg Agnus" can be switched from 60Hz 200 lines to 50Hz 256 lines under software control if you know which registers to change. (I haven't seen the actual details yet.) -- Joe Smith (408)922-6220 | SMTP: JMS@F74.TYMNET.COM or jms@tymix.tymnet.com McDonnell Douglas FSCO | UUCP: ...!{ames,pyramid}!oliveb!tymix!tardis!jms PO Box 49019, MS-D21 | PDP-10 support: My car's license plate is "POPJ P," San Jose, CA 95161-9019 | narrator.device: "I didn't say that, my Amiga did!"
ahh@glyph.UUCP (Andy Heffernan) (09/11/89)
In article <7855@cbmvax.UUCP> mks@cbmvax.UUCP (Michael Sinz - CATS) writes: >In article <4463@cps3xx.UUCP> porkka@frith.egr.msu.edu () writes: >> >> I have heard that if you do this you will actually destroy or >> damage many monitors. > > There will be majic... > Preferences!
usenet@cps3xx.UUCP (Usenet file owner) (09/11/89)
In article <477@glyph.UUCP> ahh@glyph.UUCP (Andy Heffernan) writes: _>In article <7855@cbmvax.UUCP> mks@cbmvax.UUCP (Michael Sinz - CATS) writes: _>>In article <4463@cps3xx.UUCP> porkka@frith.egr.msu.edu () writes: _>>> _>>> I have heard that if you do this you will actually destroy or _>>> damage many monitors. _>> _>> There will be majic... _>> _> _> Preferences! It *must* switch not under complete control of the computer to prevent malicious (sp?) programs from blasting unsuspecting monitors away. REAL NAME: Joe Porkka jap@frith.cl.msu.edu
cmcmanis@sun.Eng.Sun.COM (Chuck McManis) (09/12/89)
In article <4463@cps3xx.UUCP> porkka@frith.egr.msu.edu () writes:
->Two simple questions to those in the know:
-> 1: I have asked this twice before, but I have not seen it
-> answered as yet.
-> Will ScrollRaster() be fixed in respect to SIMPLE_REFRESH???????
-> A simple yes/no answer from CATS would be nice.
I guess I must have missed the original problem. What is broken about it?
I've used it on S_R windows (and hence SIMPLE layers) and it seemed to
work as advertised. (It flashes of course when you have lots of bit planes
but that isn't ScrollRaster's fault per se.)
-> 2: The ECS I have heard will allow for 400 line display modes
-> non-interlaced. THis is fine if you have a multisync.
-> What happens if you have a standard NTSC compatible monitor,
-> and some whizbang software opens up a 400 lines non-interlace
-> screen??
->
-> I have heard that if you do this you will actually destroy or
-> damage many monitors.
-> If so, there should be a hardware toggle switch to prevent
-> such displays from being used if you only have a regular
-> monitor, no?
Actually, it won't hurt your monitor. But the picture will look weird.
The problem with damaging monitors comes from setting up a scan rate that
is *much* faster than the monitor is designed for. This causes lots of
Hsyncs to be sent to the monitor and keeps the Horizontal driver transistor
on more often than it should be. This has two effects:
1) The H Transistor is designed for a small duty cycle, lots of
hsyncs cause it to be "on" more often and that can overheat it.
After overheating it can burn out and leave you with a dead monitor.
2) The rapid fire hsyncs are what are feeding the flyback transformer
in some monitors, and by changing the frequency and "shape" of the
signal you can cause the flyback to burn out as well.
Now all the ECS does is double the scan rate. This will stress your monitor
but it isn't enough to damage it.
--
--Chuck McManis
uucp: {anywhere}!sun!cmcmanis BIX: cmcmanis ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses. But you knew that, didn't you.c162-de@zooey.Berkeley.EDU (David Navas) (09/12/89)
In article <124439@sun.Eng.Sun.COM> cmcmanis@sun.UUCP (Chuck McManis) writes: >In article <4463@cps3xx.UUCP> porkka@frith.egr.msu.edu () writes: >-> Will ScrollRaster() be fixed in respect to SIMPLE_REFRESH??????? >-> A simple yes/no answer from CATS would be nice. > >I guess I must have missed the original problem. What is broken about it? >I've used it on S_R windows (and hence SIMPLE layers) and it seemed to >work as advertised. (It flashes of course when you have lots of bit planes >but that isn't ScrollRaster's fault per se.) Okay, It doesn't work so well when there are layers residing above the S_R layer to scroll. In fact, it doesn't blank the correct spots in your S_R layer. I'm not sure whether there is reliable way to determine which parts of your layer need to be updated either. I do a simple check to see if the layer I'm about to scroll is the foremost layer. If it is I use ScrollRaster, otherwise I blank the whole window and redraw the layer. This stinks as far as performance is concerned. David C. Navas c162-de@zooey
usenet@cps3xx.UUCP (Usenet file owner) (09/12/89)
-In article <124439@sun.Eng.Sun.COM> cmcmanis@sun.UUCP (Chuck McManis) writes: ->In article <4463@cps3xx.UUCP> porkka@frith.egr.msu.edu () writes: ->->Two simple questions to those in the know: ->-> 1: I have asked this twice before, but I have not seen it ->-> answered as yet. ->-> Will ScrollRaster() be fixed in respect to SIMPLE_REFRESH??????? ->-> A simple yes/no answer from CATS would be nice. -> ->I guess I must have missed the original problem. What is broken about it? ->I've used it on S_R windows (and hence SIMPLE layers) and it seemed to ->work as advertised. (It flashes of course when you have lots of bit planes ->but that isn't ScrollRaster's fault per se.) Try this: Make a S_R window. Drag another window on over the top portion of the S_R window. Now ScrollRaster the S_R window towards the bottom of the screen and try to handle refresh intelligently. The only reasonable solution is to repaint the whole window in JAM2, or clear then fill with JAM1. Both yeild excessive amounts of flickering. It does not update the damage lists to account for the obscured (sp?) portion of the S_R. Thanks for the monitor-damage details. REAL NAME: Joe Porkka jap@frith.egr.msu.edu