Arachne system files description
Main configuraton file ARACHNE.CFG
Expected in: .\ARACHNE.CFG
when not found there: [arachne directory]\ARACHNE.CFG
written always to: [already existing file]
The configuration file can be changed using user friendly
setup pages, but for experienced PC user it must be
self-explaining ;-)
Following information is only for The Inner Circle ;-)
ARACHNE.BAT, CORE.EXE
Expected in: .\
when not found there: [system path]\
these files are never overwritten by Arachne
CORE.EXE is main executable file of Arachne. It cannot be run standalone,
it must be run from inside of ARACHNE.BAT. Command line arguments
of ARACHNE.BAT will be passed to CORE.EXE.
Command line arguments:
| URL | Start with desired document (default protocol is file:)
| | -o | Start in online mode (eg. with Connection @PPP.EXE ...)
|
| -x [URL] | Start in fullscreen mode [and display desired document]
|
| -s | User have to select video adapter, then go to SETUP.HTM. SETUP.BAT does this.
|
| -c | Continue offline browsing
|
| -cg | Continue offline browsing without reseting graphics mode (only for internal use of Arachne !)
|
| -r | Continue online browsing (eg. with Connection @PPP.EXE ...)
|
| -rg | Continue online browsing without reseting graphics mode (only for internal use of Arachne !)
|
| -f | Create new font information (FONTINFO.BIN)
|
| -u | Unload packet driver (ARACHNE.BAT only)
|
Plug-in configuration file MIME.CFG
Expected in: .\MIME.CFG
when not found there: [arachne directory]\MIME.CFG
this file is never overwritten by Arachne
You must manualy update MIME.CFG each time when you
need to add some plug-in to ARACHNE (for example Java interpreter, VRML
browser, or so ;-). If you want to write your own
DGI application, your installation program should ask
for path to MIME.CFG and update it automaticaly (like other programs are
updating for example AUTOEXEC.BAT and CONFIG.SYS).
...and following lines can be understood only by the Very Highest Council
of the secret C geeks and adepts of free masonry ;-)
Cache index file
User definable filename and location, usually: [arachne directory]\TOHLEUZ.MAM
Cache Index is binary file with following structure:
BinaryRecord
BinaryRecord
BinaryRecord
...
BinaryRecord
BinaryRecord has following structure:
int itemlength;//in this file, always 0x01A8
struct HTTPrecord cacheitem;
And this is prototype of HTTPrecord:
#define URLSIZE 256
struct HTTPrecord
{
char URL[URLSIZE];// "" - zaznam neni platny
unsigned x;
long y; // odkud byl naposled zobrazeny
long size; // v bajtech
char knowsize; // znam vubec velikost ?
char mime[40]; // mime typ
char locname[80]; // full local file name
char httpresponse[30]; //nakonec vyuziju asi jinak
int handle; // file handle
long lastseen; // last seen time
char postflag; // slo o vysledek operace POST
};
The Other *.CFG files
usually: [arachne directory]\*.CFG
These are the other configuration files. Their usage usually depends
on ARACHNE.CFG. Don't change them if you don't know what you are doing.
History file
User definable filename and location, usually: [arachne directory]\TADYJSEM.BYL
Plain text file - each line contains one URL. First line must be for some
reasons (mysterious even to the author) empty. Index of current URL is located
in ARACHNE.PCK file.
Runtime configuration file ARACHNE.PCK
Expected in: .\ARACHNE.PCK
when not found there: [arachne directory]\ARACHNE.PCK
written always to: .\ARACHNE.PCK
Run SETUP.BAT if you want to ignore this file and reset Arachne.
This file contains hardware dependent information about your video card !
struct ArachnePick
{
char graphics[16];//last video mode
char GUIstyle; //0-menu vpravo, 1-menu nahore
char language[9]; //*.MSG File name
long cachesize; //velikost HTTP cache
int history; //ukazatel do souboru TADYJSEM.BYL
};
Icon files
Expected always in: [arachne directory]\
Files with extension *.IKN are Arachne icons.
On Arachne online homepage, there is available package MORE_IKN.
It is collection of various *.IKN files, which
can be useful for different file extensions on your hard disk.
This format was originaly used in IBASE image databes.
It's advantage against Windows *.ICO format is, that it contains colour
pallette. All 60x60 *.IKN files were created by me sometimes between
1991 and 1996 for IBASE "Command Center". I included some of them to
Arachne because I had no other idea how to use them ;-)
I don't recomend to publish them on WWW. It's dead file format.
However, it can be used in your Intranet *.HTML file, if you decide to
use Arachne as intranet client.
GIFIKN utility will allow you to customize Arachne toolbar.
It is available to owners of commercial multilicense
(see file REGISTER.HTM.
Font files
Expected always in: [arachne directory]\
FONTINFO.BIN and *.FNT files
are files used by X_LOPIF graphics library.
Currently, there is available free utility TFONTY to convert *.TTF
fonts to *.FNT format (for Windows) and FEDIT utility to edit
*.FNT files (for DOS).
After modifying Arachne FNT files, you have to run arachne -f
to create new font information (file FONTINFO.BIN).
See also details about distribution X_LOPIF
graphics library for C language.
The waste
Can be found on diffent places
Files like *._$b, *.TMP or $roura$.bat are temporary
and can be deleted when they stay on your hard disk (it can happen when
Arachne crashes).
Return to main help page.