[Discussion] screen frequency

[Michael]

Michael wrote:
> Woke up early this morning with an idea and it worked. 
> I looked through all my junk and changed the video card :)
> 
> The card that I had problem with was Sis 6326. It worked fine with all other systems.
> The card I just put in is:
> Manufacturer:    ATI
> Chipset:         3D Rage II+
> Memory:          2048 Kb
> DAC:             ATI Mach64 Internal 24 bit DAC
> Clock:           ATI Mach64 Internal Clock
> Driver Revision: Build 10
> Driver Build:    Jul 28 2000
> 
> I go from 8 megs ram to 2 megs ram. Oh well, it works for now :)
> 
> Now to answer some of the questions:
> 
> ** Reply to note from Thomas Clayton <topcatdrc at yahoo.com> Sat, 12 Apr 2008 00:24:42 -0700 (PDT)
>>   
>> Michael,
>>   
>> My thoughts are:
>>   
>> Monitors (analogue) "traditionally" start up at 720x400 @ 70(not 60) Hz
>> V. Refresh (This is a /text/ mode!)
>>   
>> When the system BOOTs do you see memory counts and other text OK?
>>   
> 
> Just splash screen for partial boot-up, then the "out of range" screen. When the WPS finally
> loads,I then have good looking screen.
> 
>>   
>> Standard VGA is 640x480 @ 60Hz V. refresh (Definitely 'Graphics mode' -
>> or, IF you're an old time IBMer (many on this list are), A.P.A. = All
>> Points Addressable).
>>   
>> When you installed Warp4 did you see graphics OK? (I'd guess "Yes".)
> 
> For the initial installation, yes, but as soon as the system rebooted for first time (during
> install), no. 
> 
>>   
>> There are two ways (things) that have to 'sync' with each other: the
>> Video Display Adapter and the monitor.
>>   
>> Let's atart with the monitor. IF it has (as I think is does have) an 
>> On-Screen Display (OSD) of settings, LOOK thru them to /make sure/ that
>> there isn't a setting already set that causes the monitor to start up
>> in a particular (NON-standard) mode. (Some of these can start up in
>> 800x600 graphics but nothing "less" - and they are NOT fixed
>> frequency.)
>>   
>>   
>> BTW, What EXACTLY is the model number of your monitor (KDS ????)?
>> We can look it up with that info.
> 
> vs-7e "17 Multiscan Color Monitor"
>       
>> Uh, ANY 'bent' pins on the cable connectors? (A passing thought.)
> 
> All pins are/were good :)
>    
>>   
>> Now, as for the video display card (VDC):
>>  we've got possible HW settings - ('jumpers') - unlikely BUT possible; 
>>   
>>  video ROM programming by the manufacturer
>> (Does it work with other OSes OK?)
> 
> Yes, it worked great with other systems: M$, linux, *bsd
>    
>> and, of course, the card's drivers and THEIR default setting(s). 
>> THIS is THE most likely culprit! 
>>   
>> When you installed Warp4 did you CHOOSE a video driver (other than
>> "plain old VGA")? (It is USUALLY best to INITIALLY 'go with' VGA and,
>> only later, install a particular ("BETTER") video driver. Also, SciTech
>> and IBM GradD IIRC /require/ fixpaks to be applied to the base system 
>> /before/ they'll install.)
> 
> I *always* install with VGA ;) I generally (for my own system(s)), do a very basic install and
> then add sound, printer, video, network, etc.
> After the install, I used WarpUP to add fp15, device drivers, and video. 
> 
>> I just typed the IIRC abreviation and I've forgoten what
> it means! :-( > (I'm not sure I used it correctly!)
>>   
>>   
>> It's late. 'nough for now. Let us know how things go - or DON'T.
>>   
> 
> Thanks for your time and effort :)    I'll just mark the SiS as not for OS/2 :( 
> Again, thank-you all that took the time and effort to help. 
> Now that the system is up and running,  I can get on to other things.
> 
> Michael
> 
>> Sincerely,
>>   
>> Thomas Clayton
>>   
>>   
>> --- Michael <bsd4me at cableone.net> wrote:
>>   
>>> Hi all.
>>> Just joined having been away from OS/2 for some time due to hd crash
>>> and then cpu burn-up.
>>> Any way, I got Warp 4 installed on a computer, but during bootup or
>>> even trying to use a OS/2 Full Screen window, I get the "out of
>>> range" screen. My monitor is a 17" KDS with 30-70 horizontal freq,
>>> but OS/2 tries to use 27.8. 
>>> Even if using vga mode, I get the same thing. 
>>> The system did it while installing OS/2 and still does it with fp15. 
>>> The most serious problem with this is that during startup, the system
>>> doesn't like something and waits for me to interact (by hitting the
>>> enter key) with it. 
>>> Is there something I can do/edit to fix this problem? I searched
>>> google for the phrase "out of range", but didn't see anything for
>>> this.
>>>
>>> Thanks
>>>
>>> Michael
>>>

This is in case anybody wants more info on the booting OS/2 with the old 
card (SiS 6326).
When pressing Alt-F2, I had a screen till I saw "os2dasd.dmd". That 
showed for maybe 1/2 second and then the "out of range" screen popped up 
till OS/2 fully booted and then I could see my desktop.

Michael


> _______________________________________________
> Discussion mailing list
> Discussion at lists.possi.org
> http://lists.possi.org/mailman/listinfo/discussion
>