On Sun, 14 Jan 2001, Michael Polak wrote:

> If you are not using SVGAlib, you can delete arachne-svgalib completely,
>  it is not required by arachne-ggi.

  Yes, I know... I deleted arachne-svgalib some time ago.  ;-)

> There are some SVGAlib emulators which run on top of X, which use GGI as
> kind of glue layer, but arachne-svgalib doesn't run very good with that
> emulator.

  That must be what I was thinking of...  :-/

> >   Using those default numbers, you can drive your monitor at
> > 800x600 @ 60 Hz or 640x480 @ 72 Hz.  If you want higher resolutions
> > and/or higher refresh rates, and your monitor can support them, then
> > you need to look in your monitor specs and put those in there.
> 
> Easiest way is to copy apropriate lines from your XF86Config to
> libvga.config - syntax of so-called "modelines" is same for both files.

  Except that I don't think Clarence is using X.

> I just copied all modelines
> from Xf86Config, as my X11 configured by Xconfigurator work well... I
> think default libvga.config should include them, as they are universal 
> for all monitors and cards,

  Not really...  Using default X modelines, my image would be way 
off to the left of the screen, even to the point of "echoing" back.  
Some of them worked "all right," but I adjusted all my modelines 
after exploring xvidtune in order to not have to fiddle with monitor 
knobs every time I change resolution.
  For libvga.config, I only changed the horizontal sync range, and
all modes work fine.
  I guess how much fiddling you need to do really depends on your
exact card and monitor.

> > do NOT use any of those numbers if you're not sure your monitor
> > can support them.  Overdriving your monitor can damage it.
> 
> I think uncommenting modelines is safe, as long as you don't exceed your
> maximum vertical refresh rate, and even in that case, I haven't damaged
> monitor...well... to be true, one of my monitors is now being repaired
> ;-) So maybe these experiments were the reason ;-)

  It could be... Not too long after I exceeded my monitor's
capabilties on an old .56 dp monitor, I had to repair the
high-voltage transformer (black automotive, non-acetic silicone
rubber makes a good high-voltage insulator ;-).  Like you, I'm not
*positive* my experimenting was the cause of the transformer 
housing developing a hairline crack, but since then I'm very wary 
of trying to overdrive a monitor.
  
> There are some hardcoded image size limits in Arachne ,but I thought  
> these are
> at least 2000 pixels... Arachne is limited by available DOS memory, red
> boxes were results of maximum image width hardcoded to wide...

  I just created a 2500x60.gif, and both Arachne-GGI and Arachne-SVGA 
1.66 display the entire thing just fine... 
  I tried to display the same gif in DOS Arachne 1.69 and I get a 
stack overflow error.

 - Steve


Reply via email to