SDD compatible displays
Joe Negron
just two years, seven months ago!). When I turn it on, the green power
light flickers intermittently and the display never turns on.
In looking for a replacement, I figured I'd check the "Compatible
Hardware list" at www.os2warp.be. But, there's no mention of displays
at all. Neither at en.ecomstation.ru/hardware.php. And, the readme.txt
included in the snap-os2-3.1.8.exe installation package does not mention
compatible displays, only graphics cards.
So, where does one go to determine whether a display is compatible with
the SciTech driver?
--
------------------------------------------------------------------------
A holding company is a thing where you hand an accomplice the goods
while the policeman searches you.
--Will Rogers
War is good for business - invest your son.
--antiwar bumper sticker from the 1960s
------------------------------------------------------------------------
Joe Negron from Bensonhurst, Brooklyn, NY, USA
tho...@antispam.ham
> So, where does one go to determine whether a display is compatible with
> the SciTech driver?
You determine whether SDD is compatible with your video card. Because
you said nothing about it dying, we can assume that nothing has changed
there, so the compatibility remains. You then determine whether the
display can handle the output of the video card. Common modes like
800x600 are likely supported. Where you can run into problems is like
trying to run 1600x1200 through the DVI output. If the display can
handle the resolution, the video card might be able to do it only
through the analog output, not the digital output, assuming you have a
card that provides both.
Andreas Buchinger
> It looks like my ViewSonic LCD flat panel display has died (purchased
> just two years, seven months ago!). When I turn it on, the green power
> light flickers intermittently and the display never turns on.
>
> In looking for a replacement, I figured I'd check the "Compatible
> Hardware list" at www.os2warp.be. But, there's no mention of displays
> at all. Neither at en.ecomstation.ru/hardware.php. And, the readme.txt
> included in the snap-os2-3.1.8.exe installation package does not mention
> compatible displays, only graphics cards.
>
> So, where does one go to determine whether a display is compatible with
> the SciTech driver?
>
different resolutions. It's the graphic card and its driver which defines which
resolution is given out at its connectors (analog VGA connector or DVI port).
For LCDs/TFTs of course you should ever set the graphic card to the native
panels resolution and use DVI output. Although to some extend LCDs can zoom
other resolutions too, a good sharp pictures is only possible with the native
resolution (physically available pixels).
So questions are - which native resolution do you like to drive?
Which connector do you want to use - analog port or DVI (which is strongly
preferred with LCDs)?
Is your graphic card and driver capable to drive this resolution at the desired
port?
Percival P. Cassidy
>> It looks like my ViewSonic LCD flat panel display has died (purchased
>> just two years, seven months ago!). When I turn it on, the green power
>> light flickers intermittently and the display never turns on.
>>
>> In looking for a replacement, I figured I'd check the "Compatible
>> Hardware list" at www.os2warp.be. But, there's no mention of displays
>> at all. Neither at en.ecomstation.ru/hardware.php. And, the readme.txt
>> included in the snap-os2-3.1.8.exe installation package does not mention
>> compatible displays, only graphics cards.
>>
>> So, where does one go to determine whether a display is compatible with
>> the SciTech driver?
>>
> Why should any display be not compatible? A display is capable of
> displaying different resolutions....
... or maybe not: my new Samsung monitor blanks out after a minute or so
if it doesn't see a 1920x1280@60Hz signal -- which SNAP is capable of doing.
Perce
Andreas Buchinger
lower resolutions as the native one. Unfortunately they even zoom 4:3
resolutions to the wrong 16:10 full screen picture. But that's another story.
Andi
P.s: I suppose you meant 1920x1200, did you?
Percival P. Cassidy
>>> Why should any display be not compatible? A display is capable of
>>> displaying different resolutions....
>>
>> ... or maybe not: my new Samsung monitor blanks out after a minute or
>> so if it doesn't see a 1920x1280@60Hz signal -- which SNAP is capable
>> of doing.
> Hm, my Samsung 245B and all TFTs I've seen till now are capable of
> displaying lower resolutions as the native one. Unfortunately they even
> zoom 4:3 resolutions to the wrong 16:10 full screen picture. But that's
> another story.
>
> Andi
>
> P.s: I suppose you meant 1920x1200, did you?
Sorry. In fact I meant 1920 by 1080.
Perce
Andreas Buchinger
display other than the native resolution? What do you see during boot? Nothing?
I suppose VGA (640x480) works.
Percival P. Cassidy
>>>>> Why should any display be not compatible? A display is capable of
>>>>> displaying different resolutions....
>>>>
>>>> ... or maybe not: my new Samsung monitor blanks out after a minute
>>>> or so if it doesn't see a 1920x1280@60Hz signal -- which SNAP is
>>>> capable of doing.
>>> Hm, my Samsung 245B and all TFTs I've seen till now are capable of
>>> displaying lower resolutions as the native one. Unfortunately they
>>> even zoom 4:3 resolutions to the wrong 16:10 full screen picture. But
>>> that's another story.
>>>
>>> Andi
>>>
>>> P.s: I suppose you meant 1920x1200, did you?
>> Sorry. In fact I meant 1920 by 1080.
> So you have one of these "TV optimized" 16:9 devices. And it doesn't any
> more display other than the native resolution? What do you see during
> boot? Nothing? I suppose VGA (640x480) works.
While the machine is booting I see superimposed on the boot screen a box
informing me that the resolution is not optimum. The screen blanks after
less than a minute, but I can bring it back to life by toggling between
the analog and digital inputs.
I've never tried VGA resolution. The box does say "*up to* 1920x1080,"
but I've never tried anything else. The only documentation is on the CD
that came with the monitor. Quite possibly I would have needed to use
that CD and the driver that is on it if I wanted to use the monitor on a
Windozzze machine, but eCS "don't need no steenkin' driver" other than
the SNAP driver it includes already -- which retrieves the resolution
information directly from the monitor and adjusts the settings accordingly.
The monitor is a model 2233.
Perce
Andreas Buchinger
> Andreas Buchinger wrote:
>
>>>>>> Why should any display be not compatible? A display is capable of
>>>>>> displaying different resolutions....
>>>>>
>>>>> ... or maybe not: my new Samsung monitor blanks out after a minute
>>>>> or so if it doesn't see a 1920x1280@60Hz signal -- which SNAP is
>>>>> capable of doing.
>
>>>> Hm, my Samsung 245B and all TFTs I've seen till now are capable of
>>>> displaying lower resolutions as the native one. Unfortunately they
>>>> even zoom 4:3 resolutions to the wrong 16:10 full screen picture.
>>>> But that's another story.
>>>>
>>>> Andi
>>>>
>>>> P.s: I suppose you meant 1920x1200, did you?
>
>>> Sorry. In fact I meant 1920 by 1080.
>
>> So you have one of these "TV optimized" 16:9 devices. And it doesn't
>> any more display other than the native resolution? What do you see
>> during boot? Nothing? I suppose VGA (640x480) works.
>
> While the machine is booting I see superimposed on the boot screen a box
> informing me that the resolution is not optimum. The screen blanks after
> less than a minute, but I can bring it back to life by toggling between
> the analog and digital inputs.
capable to display VGA (during boot the graphic card outputs VGA resolution). I
assume it should be possible to deactivate this "box" and the "auto blank" in
the monitors menu. If not, it would be impossible to change setting in the mobos
bios f.i. For me this would be a major fault of a monitor.
Joe Negron
>Joe Negron writes:
>
>>So, where does one go to determine whether a display is compatible with
>>the SciTech driver?
>
>You determine whether SDD is compatible with your video card. Because
>you said nothing about it dying, we can assume that nothing has changed
>there,
The videocard (ATI Connect 3D Radeon 9550 SE AGP 8X) is fine. It's now
running my old Panasonic PanaSync/Pro C17P2P (CRT) monitor.
>so the compatibility remains. You then determine whether the
>display can handle the output of the video card. Common modes like
>800x600 are likely supported. Where you can run into problems is like
>trying to run 1600x1200 through the DVI output. If the display can
>handle the resolution, the video card might be able to do it only
>through the analog output, not the digital output, assuming you have a
>card that provides both.
This sounds simple, but how do you account for all the posts I read
about people having difficulties using their display with OS/2?
--
------------------------------------------------------------------------
Every man has a right to be wrong in his opinions. But no man has a
right to be wrong in his facts.
--Bernard Baruch
tho...@antispam.ham
> This sounds simple, but how do you account for all the posts I read
> about people having difficulties using their display with OS/2?
Compatibility between a video card and a display isn't strictly
an OS/2 issue. Problems can occur with any operating system.
ivan
wrote:
> On 2009-09-16, tho...@antispam.ham <tho...@antispam.ham> wrote:
> >Joe Negron writes:
> >
> >>So, where does one go to determine whether a display is compatible with
> >>the SciTech driver?
> >
> >You determine whether SDD is compatible with your video card. Because
> >you said nothing about it dying, we can assume that nothing has changed
> >there,
>
> The videocard (ATI Connect 3D Radeon 9550 SE AGP 8X) is fine. It's now
> running my old Panasonic PanaSync/Pro C17P2P (CRT) monitor.
>
> >so the compatibility remains. You then determine whether the
> >display can handle the output of the video card. Common modes like
> >800x600 are likely supported. Where you can run into problems is like
> >trying to run 1600x1200 through the DVI output. If the display can
> >handle the resolution, the video card might be able to do it only
> >through the analog output, not the digital output, assuming you have a
> >card that provides both.
>
> This sounds simple, but how do you account for all the posts I read
> about people having difficulties using their display with OS/2?
>
Joe, I think you will find that most, if not all, of those posts were
by people trying to either set up a resolution other than the default
for the display or the display wasn't playing nice and reporting what
it could do.
I have never had problems using a flat panel display with OS/2 and the
Scitech driver, and I've used some whacky displays to demonstrate on.
--
ivan
Joe Negron
By this I suppose you mean that there's some mechanism whereby the
display reports to the video driver what resolutions/colors/etc. it is
able to support?
How does one know which displays have this problem?
>I have never had problems using a flat panel display with OS/2 and the
>Scitech driver, and I've used some whacky displays to demonstrate on.
So, you think it's fairly likely that any widescreen display I'm likely
to get will work with SNAP and my ATI Connect 3D Radeon 9550 SE AGP
card?
--
------------------------------------------------------------------------
Difficulties strengthen the mind, as labor does the body.
--Seneca
ivan
wrote:
> On 2009-09-19, ivan <iva...@free.fr> wrote:
> >On Fri, 18 Sep 2009 20:35:17 UTC, Joe Negron <jne...@XsonicX.invalid>
> >wrote:
> >
> >>On 2009-09-16, tho...@antispam.ham <tho...@antispam.ham> wrote:
> >>
> >>>so the compatibility remains. You then determine whether the
> >>>display can handle the output of the video card. Common modes like
> >>>800x600 are likely supported. Where you can run into problems is like
> >>>trying to run 1600x1200 through the DVI output. If the display can
> >>>handle the resolution, the video card might be able to do it only
> >>>through the analog output, not the digital output, assuming you have a
> >>>card that provides both.
> >>
> >>This sounds simple, but how do you account for all the posts I read
> >>about people having difficulties using their display with OS/2?
> >
> >Joe, I think you will find that most, if not all, of those posts were
> >by people trying to either set up a resolution other than the default
> >for the display or the display wasn't playing nice and reporting what
> >it could do.
>
> By this I suppose you mean that there's some mechanism whereby the
> display reports to the video driver what resolutions/colors/etc. it is
> able to support?
Correct. look at page 2 of the screen settings, there you will see
what the driver has detected using a functioning DPMS. If not there
is the option to import the windows inf file.
>
> How does one know which displays have this problem?
Good question, I don't have an answer.
>
> >I have never had problems using a flat panel display with OS/2 and the
> >Scitech driver, and I've used some whacky displays to demonstrate on.
>
> So, you think it's fairly likely that any widescreen display I'm likely
> to get will work with SNAP and my ATI Connect 3D Radeon 9550 SE AGP
> card?
>
I don't see any reason why not, I have set up several wide screen
monitors on ATI Radeon 9200 SE AGP cards using the latest free snap
drivers.
--
ivan
Marty
Some OS's have workarounds built in for common issues, however. For
example, a non-standard widescreen native resolution on an LCD may not
be supported by your video card's BIOS, but a Windows driver would
program the video mode registers for it. OS/2 and SDD rely on the video
BIOS to support the video modes (or the user can program them too using
SDD if they know how).
--
Reverse the parts of the e-mail address to reply by mail.