World: r3wp

i just want, it works

it works with rebol

but not with Altme

i can't use Altme at my job

Then why don't you add a simple description of what you want to the 
item in the AltME Wishes checklist .


(In case, you haven't seen the checklists before click on the icon 
of a tick (check in the US) in the top left hand quadrant of the 
AltME window.

I don't think we should have proxy settings on the list.

the reason is that the proxy problem is with some proxy servers and 
occurs with all rebol applications.  In particular, I can point to 
squid.

I checked this by using a proxy that worked fine with rebol. I then 
switched to squid, and it failed.

Far out, I must have been still wonky when I wrote "End of Life" 
- I thought Henrik was talking about IE.

Graham, that's no reason for it not to be on the list. AltME might 
tackle this common user problem by linking to some documentation 
which explains the situation, problems and possibly automatically 
forwards a feature request for you to RT feedback.

Then RT might get a better idea of the numbers of people affected 
by this issue.

So is it possible to phrase the requirement better than "proxy"?

Is the requirement for an AltME client to access an AltME server 
from behind a firewall or proxy server?

Or is that two seperate wishes?

Does anybody want to run an AltME server from behind a firewall/proxyserver?

May be Safeworlds wants to offer a nifty http re-direction service 
from port 80 on a server?

No....we don't

At least that's one possible interpretation of "proxy" ruled out.

Anton, if the proxy only allows http packets .. then there is nothing 
that RT can do about this.

It's possible to tunnel through using http packets, isn't it ?

I'm running an altme server for family puposes on a Linux (debian) 
server at home. I would like it to start automatically, say after 
a power failure/reboot. I tried it under windows with command line 
options, but I did'nt get it to work.

Is this possible?

My present solution is to login remotly when I notice altme is gone, 
and leave a VNC created xsession up with altme restarted manually 
on it. But I prefer my computers trained to do things for me ;-)

I think command line driven altme servers are not free

If you want to use Altme at work, you could set up a ssl vpn at home 
using a Linksys rvl200 eg http://reviews.cnet.com/Linksys_4_Port_SSL_IPSec_VPN_Router_RVL200_router/4864-3243_7-32015900.html?ctype=msgid&messageSiteID=7&messageID=2349010&cval=2349010&tag=uolst

no, not at work. at home. was hoping to have it restart itself after 
a reboot for when I'm out.

Not vital since it's for family contacts only.

there is a (several?)  tool for windows which can generate events 
and select windows.  you could probably use that to simulate a manual 
login.

since all events are handled window wide (from the perspective of 
windows) It should be easy to trick rebol.  just record key sequence... 
put a few waits and you should be done :-)

denismx, if you're running debian thefile you want is probably  '/etc/init.d/rc.local' 
. Put your command in there and it will run after a reboot.

Maxim, I was thinking of a similar solution, some script that simulates 
keystrokes from the keyboard. I remember seing something like that 
under Windows. There's probably something like that under Xwindows.

Bobo: altme needs to have a world and password specified to start 
the local server. I tried command line parameters to do that, there 
are in fact parameters that can be passed to altme from the command 
line, but it did'nt start my world properly.

When and if that problem is solved, the solution script will indeed 
go into the init.d directory.

denismx: I have added "Launch  World on Start-up" to the AltME Wish 
List in the Checklists here. Please could you add a brief description.

denismx:  I'm not following very well.  Is your problem with the 
Debian server as I have this working for a family server hosted on 
a windows machine as I'm sure many people here do.  If you want to 
try again on a windows OS, place a shortcut in your startup folder. 
 In the target field the command should be similar to this...

physical path to altme

sorry

physical path to altme
 -s "WorldName" -p Port#

at one point I had three private worlds working this way.  Anytime 
the PC restarted the worlds were available.

i think the problem he has is that altme still needs X to be available

there is a "server only" altme, but it costs money.

I noticed a small but costly redraw issue (particularly when using 
AltME through remote desktop): When I am in this group and then click 
the checklist button and I then click on RebServices, AltME first 
redraws this group again and then draws the RebServices group. This 
takes 1-2 additional seconds to do.

I'm surprise "physical path to altme" -s "WorldName" -p Port# works 
for you on Windows, Brock. It did'nt for me - but it's been a very 
long time and I don't remember the details of that problem. I'm on 
Linux for my servers, Debian Sarge, now. Not going back.

What about the password, Brock? It's filled in automatically on your 
setup?

Well, well, I've just tried it under windows again, and it does seem 
to work, as Brock is saying. Didn't under some previous version I 
was running under. It just might work the same under Linux. Going 
there to try it. Will report back.

Well it now works under both windows and linux. Under linux you do 
a : "./altme -s Worldname" and it doen'nt even ask for the password 
! (?) - same for windows in fact. You can start any local world without 
the password from the command line.

So I'm wondering why the password is asked under the GUI?!

So I'll take this out of the wish list, PeterWood. Tks anyway.

:)

Yep, you only need passwords for starting the AltME user-client. 
 I believe the intent of the "Start a World" window is to create 
new worlds where you need a password for the world.  I don't see 
a need for a passord to start a world, you still need a client to 
communicate and access the data inside the world.