> Arachne-ggi actually runs on top of X... or I think more
> accurately, behaves as an interface to display an svga program
> on top of X. I'm not that well up on exactly what ggi is doing,
> but when you run an 800x600 Arachne-ggi in X, you stay in X.
arachne-ggi is standalone binary, linked against libggi instead of
libvga (SVGAlib).
If you are not using SVGAlib, you can delete arachne-svgalib completely,
it is not
required by arachne-ggi.
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.
> > It WAS set for VESA but the uncommented settings were for a *RANGE* of
> > Horsync and VertRefresh. (31.5-37.9 and 50-90) I didn't change that.
> > Am I supposed to pick specific numbers ?
Not, but you may have to change the range. Eg. older monitors won't
handle
50-90 range, I had to change that to 50-76 or even 50-60 for some types.
(Modern monitors on the other hand show exact refresh rate as part of
their onscreen menu, so you will see that actual value detected by
monitor is always within the
range you have specified in your setup...)
But you usually don't have to change Horizontal Sync.
> It depends. You probably want to allow svgalib to drive your
> monitor at the highest refresh rates possible to avoid eyestrain.
> Higher resolutions also require the higher Sync rates.
Exactly.
> 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.
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,
user just have to provide maximum vertical refresh rate, which is IMHO
the only number in which different monitor types vary (of course,
together with maximum X and Y resolution supported withou interlacing...
I think this has something to do with Hsync range, but I don't know
details).
> Otherwise, you can use the numbers in the commented lines, but
> do NOT use any of those numbers if you're not sure your monitor
> can support them. Overdriving your monitor can damage it.
> (If you ever plan on running X, keep those monitor specs handy
> because you'll want them then too.)
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 ;-)
> At least it sounds like you're making progress.
>
> > The Arachne screen is a total mess - nothing recognizeable at all - and
> > it doesn't reset or clear when I exit. I have to run blind. I guess my
> > card registers get screwed up. :(
>
> That happened to me the first time I tried to run svgalib
> Arachne too. It was long enough ago that I don't remember what
> I did to fix it, but I *think* what made the difference was
> upgrading libvga. (I'm running 1.4.1 now... I don't remember
> what I was running before)
The problem is, that resolution used by Arachne (800x600xHiColor) is far
beyond SVGAlib authors supposed users to use. Most games use only
320x200. But one of SVGAlib contributors is testing Arachne, so I hope
new releases of SVGAlib will be Arachne aware.
> Have Arachne use bootp. Then (this is the fun part)
> echo>\(arachne directory)\ppp.log
>
> That's right. A 0 byte ppp.log. As long as there's a file there, Arachne
> assumes it's online until it finds out otherwise.
Or you can RTFM and set connection variable to READY.
But PPP.LOG is needed for online time counter, that's right.
> Dear list:
> After fights at every step getting a colour image out of Protel
> schematic editor, the final disappointment was that Arachne wont display
> either the bmp (torn) the .gif (cropped) or the .png (torn)
>
> The final image after a weeks work was a 77Kb GIF with dimensions
> 1994 by 1341. It displays perfectly in windows 3.1 and GWSDOS which made
> it.
> The offending file is at http://www.nimnet.asn.au/~kali/download.htm
> "GIF of Downconverter Schematic"
> What are the image size limits for Arachne and what sets them?
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 got one too, blank return-path, two-part message, no subject, first part was
> text/plain but blank, second part was base64-encoded MKCCGENK.EXE. My ISP
> converts .EXE and .VBS in attachments to ~EXE and ~VBS to prevent a user from
> inadvertently running a viral or Trojan attachment. But about 8 days previous,
> I received another message
Yes, I am getting tons of this stuff too. It is virus, probably the one
called Hybris. I agree it is inconvenient to delete these messages all
the time, but it is the only damage this virus can do to me ;-)
--
Michael Polak - Arachne Labs. Online since 1994 (TM) Okrademe vas mene
(TM)
http://www.arachne.cz/ - Arachne Labs (WWW browser for DOS / Linux,
webhosting ...)
http://www.mp3records.cz/ - Free and 100% legal MP3 files by independent
musicians
http://www.vojna.cz/ - Kampan za zruseni povinne vojenske i civilni
sluzby v CR
