Dale,
The problem wasn't with my viewer. The problem was that I was looking
specifically for VGA.something or VGA. Since I've a VESA card and have
things jacked up as high as they can go because of the Pentium I run on,
my Arachne.pck doesn't *start* with VGA anything. It starts with Hi16
But, if I did run a VGA card, I still couldn't have successfully edited
the file. It is one long single line and my editor only allows 255
characters per line, and I think that means the file, after editing,
would no longer be in the original format. Oh well ...
I still wonder why cache items end up in that file though.
l.d.
====
On Fri, 11 Feb 2000 16:33:50, Dale Mentzer wrote:
> On 11 Feb 00 at 4:14, L.D. Best wrote:
>>> I was curious, so went to see what was in my arachne.pck file. I had a bit
>>> of trouble, since when viewed as text by Arachne it was one single long
>>> line; trying to edit with Arachne gave the famous "long line blank screen."
>>> So I went to my personal editor, and found that the lines were too long for
>>> it also, and it didn't matter anyway cuz I couldn't find a first string that
>>> said VGA or VGA.something.
> The first thing in my arachne.pck file is the name of the driver I
> use (Trident). I used the viewer in Desktop2 and viewed it in HEX.
> You might want to try another HEX viewer/editor, L.D.
-- Arachne V1.60;b1, NON-COMMERCIAL copy, http://arachne.cz/
