1. I do not want to install xshell on my internal memory (do not want to take a chance to brick my iliad, even if iva an unbreakable one...), I have installed it on my CF and I am wondering what I might be missing doing that?

My installer about as safe as you can get, and it modifies no system files. Your concern seems to stem from my ambiguous usage of the term "internal memory." I don't mean the root filesystem where the sensitive files live. Instead I'm referring to a separate internal "storage filesystem" (located at /mnt/free). It behaves like a hardwired 128MB CF card, and functions as such when no external memory is attached. No sensitive files live there.

You use this, and everything else on this forum, at your own risk. For the above reasons, xshell/mrxvt is relatively quite safe.

Quote:

Originally Posted by Dabon

2. with the previous mrxvt software we did not have to install anything, do we have to install the Xshell software before using the software??? what is the instalation really for?? and can I just install on the CF and not the internal memory?? all my other software are installed on the CF?

You do not have to install to use. As Wallcraft pointed out, "Run standalone" will run mrxvt for you.

The "installation" allows you to easily run text-based programs like elinks from the iLiad's menu system. Otherwise you must perform a more advanced procedure. (I will post to the elinks thread.)

I set the default to "internal storage memory" because I want xshell to be accessible even if the iLiad's CF card reader pins get bent. I anticipate someday soon an interactive version of "unbrickable" that may require xshell on internal memory. For this reason I'm reluctant, but I could easily add an option for installing to the CF card if that makes people feel more comfortable.

Quote:

Originally Posted by Dabon

3. What steps should I take (installation, launching...) before installing the elinks text-based web browser that I want to use so much....

I installed xshell and, although it starts and is functional, it creates a file errors.txt in the _xshell\mrxvt directory. This happens with both the installed and the standalone versions (in different mrxvt directories obviously).

The problem has disappeared... I noticed a few other forum topics where problems disappeared the next day, but I guess I can add one to that list. I did reboot a few times to no avail, waiting untill the next day did the trick. Mysterious...

To complete the issue, I did change the shellscript upon your request, this is the new errors.txt: