Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Aethereal]

Hi all
sorry for the probably "newbie" problem, but I am unable to use the windows compile of aMuleGUI.

The problem:
I run aMuleGUI
a dialog box appear asking for host, port and password of the aMuled to connect to
I fill the required info
the windows disappear and nothing happens
amulegui.exe is listed on active processes in Task Manager (CPU=0) but no user interface is shown (very disappointing, being having a GUI the very target of all this...)

The environment:
Windows XP sp2, all critical updates
Dial-up internet connection (not firewalled)

I had the same problem on 2 different PCs with:
- Pre-compiled amulegui from CVS 22-09-2005 found in forum
- locally built amulegui from CVS 30-09-2005
- locally built amulegui from CVS 26-10-2005

the amuled I was trying to connect to runs on a Gentoo and is built from CVS 30-09-2005

Any Ideas? I am clueless...

[stefanero]

well 1st of all, you always need SAME cvs date for core and remote-gui

can you maybe try to run amulegui.exe from inside mingw console and look at teh output?

is there any info abour EC-connect in the amuled-log?

[Aethereal]

Originally posted by stefanero
well 1st of all, you always need SAME cvs date for core and remote-gui

I know, that's why I tried to build on Win the same CVS used on Gentoo.
I tried the latest just to see if the problem was consistent (I suppose I should receive at least an "unable to connect" dialog if amulegui is working correctly)

I am in the process of updating the gentoo-side too at the moment, so I'll be able to check with version-consistent amuled-amulegui

Originally posted by stefanero
can you maybe try to run amulegui.exe from inside mingw console and look at teh output?

is there any info abour EC-connect in the amuled-log?

even running from mingw I get the same behaviour, nothing is written on console. I am rebuilding just now amulegui with the options

./configure --disable-monolithic --disable-ed2k --enable-amule-gui

so to have a debug-enabled version (previously I added a --disable-debug, just to see if there was any difference)

Yes, in the logfile there is a reference to a client amule-remote 0x0001 being rejected for Incorrect EC version ID, so I suppose there are no network/comunication problems.

I'll post later when the gentoo CVS finish to compile (old PIII...)  

[lfroen]

Few notes:

Dial-up internet connection (not firewalled)

If you connecting amulegui to core over slow network: most chances that it will not work at all. Amuleweb is suited better for such environment.

there is a reference to a client amule-remote 0x0001 being rejected for Incorrect EC version ID

As stefanero say - you need same cvs date for core and remote.

[Aethereal]

Update:

Now that both amuled and amulegui are the same version, it looks like working.
I still don't understand why it didn't while both amuled and amulegui were CVS 30-09-2005, anyway with today CVS 26-10-2005 version it works.

I plan to use amuled on the same network, the dial-up was only for doing the tests right now, while I am away from the server (I usually use amuleweb for this kind of remote control)

As a side note, it still puzzles me that a failed connection will result in the program running (well, doing nothing actually) in background without any error message, having the user to manually kill the process. Is this due to the still "Experimental" status of amulegui?

Anyway, thanks a lot for your help, it was really appreciated.

[lfroen]

it still puzzles me that a failed connection will result in the program running

No, it should fail with error message and return to logic dialog

But, being as "experimental"  it still have things that not working as should