Notices

I believe the opening of xterm twice is a problem that Personal Menu always has.

oh well...guess i just wont be able able to get it to launch from personal menu then

You can, you just get an extra XTerm, which you can close. In fact, I'm glad you asked about it and that TrueJournals had a useful answer, since it's how I now get to Tear Bookmarks Manager

id rather not use personal menu if its going to pop any windows open besides the program i want

If you're running a shell script, maybe try putting 'exec' in front of your command inside the shell script. It should take over the shell scripts process and thus no more shell. And maybe you'll want to redirect stdout and stderr. Should work.

For Personal Menu, the following worked for me. I created 2 scripts called hw.sh and top.sh in /home/user.
hw.sh:
top.sh:
I set permisions to 755:

chmod /home/user/hw.sh 755
chmod /home/user/top.sh 755

In Personal Menu, I set 'Command to execute' in one to:

'/usr/bin/osso-xterm /home/user/hw.sh'

and:

'/usr/bin/osso-xterm /home/user/top.sh'

in the other.

I did not select 'Run in terminal' for either.

When I started them from Personal Menu I got one shell each.

Dirty page, many ads and cookies.

Times are the best of several retries

Tear:
Loading the page without privoxy (after browser startup): takes 20 seconds to start rendering, 55 seconds to be fully loaded.
Loading the page without privoxy (several reloads): takes 18 seconds to start rendering, 37 seconds to be fully loaded.
Loading the page through privoxy (after browser startup): takes 17 seconds to start rendering, 40 seconds to be fully loaded.
Loading the page through privoxy (several reloads): takes 15 seconds to start rendering, 20 seconds to be fully loaded.

Microb (with flashblock):
Loading the page without privoxy (after browser startup): takes 10 seconds to start rendering, 35 seconds to be fully loaded (and cpu down to 0).
Loading the page without privoxy (several reloads): takes 5 seconds to start rendering, 23 seconds to be fully loaded
Loading the page through privoxy (after browser startup): 15 seconds to start rendering, 25 seconds to be fully loaded.
Loading the page through privoxy (several reloads): takes 6 seconds to start rendering, 13 seconds to be fully loaded.

Main computer:
Firefox 3.1: 15 seconds to be fully loaded (and cpu down to 0).
Firefox 3.1 +adblock: 10 seconds
Firefox 3.1+adblock+noscript: 2 seconds
Konqueror 3.5: 20 seconds

interesting then that i got maybe 9 seconds from starting browser to page loaded in microb. still, could be something left over in cache, even tho i tried to clear it before doing the timing.

with webkit i was seeing 2 min+...

and i do not bother with flashblock, i just switch the plugin of. simpler that way...

I did all timings after making sure that everything was cached in disk, so network didn't mattered too much.
The very first time I tryed to load the page (so nothing was cached) it took about 1 min 90 seconds in tear (without privoxy), and about 45-60 seconds in microb with privoxy.

well i cant see how network should result in a 2 min+ diff in load time.

and the basic page was clearly loaded, but webkit (in both tear and osso-browser) was having a hard time getting those images up there, and in that time making things unresponsive to any kind of input what so ever.