Bobcat, "keep it running" memory hack.


 When Bobcat bombs because it runs out of memory in a session you can use
 this trick to finish.

When you run out of memory, do a ^A  to load a spawned fresh lynx
showing a page summary of the last address which caused you to run out of
memory. You may then load your URL again with more space.

You will have to exit each session opened in turn , in order to hangup, but
although inconvenient, it is a lot better than not being able to continue.


If you changed your directory names it may not work. But try it anyway.


You must turn on history.htm file logging in lynx.cfg. Since it defaults to
TRUE, the following will work. ( comment out the LOG_URLS line or remove it
completely ) #LOG_URLS:FALSE

LOG_URLS:TRUE for some reason does not work.

I have also modified my lynx.cfg to allow action which is similar to
lynx386 where a manual spawn is called by "." ( period)

KEYMAP:.:EXTERN         # MAP "period" to run External.bat

This addition allows one to use "." to call any external programs manually
which are not defined under auto_extern. ( same as ^A)

Note:
If you are using "share" Bobcat cannot be loaded in a shell from Bobcat.
However lynx386 and Arachne can.

VE3LGS April 19 1998