boinc client, port 1043, and alternate port


log in

Advanced search

Questions and Answers : Windows : boinc client, port 1043, and alternate port

Author Message
Profile Doris and Jens
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 21 Nov 99
Posts: 362
Credit: 1,065,561
RAC: 549
Germany
Message 201872 - Posted: 3 Dec 2005, 7:55:12 UTC - in response to Message 201856.

I originally selected (during installation) the recommended option of running only for my login. I tried again by selecting for when anybody logs in. I didn't not want to run as a service because I like the screensaver. So -- I'm easily amused...


When BOINC Manger should start the BOINC client (boinc.exe) -as in single or share mode - it has a problem when other applications use the for BOINC reserved port. Then it failes. This is not a issue when the BOINC client (boinc.exe) starts before BOINC Manager , as in service mode.

If you can not stop the other program to use the BOINC port, then service mode is the only real work around at the moment. Possible you may want to start boinc.exe in a DOS window and then start BOICN Manager. This must work too.

I hope the developers will fix this issue soon, but I don't know how long this will need.

There is a possibility to see the screen saver in servcie mode too. It is not really the secure solution but if some one may accept the risk ... I personl use the screen saver in service mode on some of my hosts.

You only need to change the service after the install in the way that it is starting with system account and not with the user named in the installation. The service must be restarted then.

____________
Greetings from Bremen/Germany
Jens Seidler (TheBigJens)

hbamford
Send message
Joined: 15 Mar 03
Posts: 5
Credit: 9,564,547
RAC: 5,457
United States
Message 201772 - Posted: 3 Dec 2005, 3:58:57 UTC

Greetings,

I also have been having the problem with connecting to the boinc client problem. I did the poking around suggested in other messages and discovered that there is indeed another program starting up, CLI.exe, that uses this port. I cannot get rid of it as it is part of the ATI graphics board stuff. No point in a fancy screen saver if there is no screen!

However, when I start the boinc client from a DOS box by hand, I get the complaint about 1043 and using the alternate port. And then I can start boincmgr.exe and everything works.

So. What is different about the way boincmgr starts boinc that means I have to do this by hand? Is the boinc manager use an undocumented option to FORCE 1043 when it (apparently) is not necessary?

For now, I just manually start boinc -redirectio, kill the window (which leaves boinc.exe running) and then start boincmgr.exe and every runs OK. Just a pain.

Any (polite) suggestions? :-)
____________

Profile Ageless
Avatar
Send message
Joined: 9 Jun 99
Posts: 12456
Credit: 2,688,798
RAC: 1,220
Netherlands
Message 201779 - Posted: 3 Dec 2005, 4:07:03 UTC

CLI.exe, the Command Center for the ATI cards... well. I am using one, I can reboot, I don't have any trouble with either CLI or Boinc.

Might be because I am using the newer .NET software. The 2.0RC version.

Keep it pouring in, let's see if this is part of the problem. And thanks for the first part. :)

____________
Jord

Fighting for the correct use of the apostrophe, together with Weird Al Yankovic

1mp0£173
Volunteer tester
Send message
Joined: 3 Apr 99
Posts: 8423
Credit: 356,897
RAC: 0
United States
Message 201783 - Posted: 3 Dec 2005, 4:11:22 UTC

However, when I start the boinc client from a DOS box by hand, I get the complaint about 1043 and using the alternate port. And then I can start boincmgr.exe and everything works.

When you aren't starting it by hand, how should it be starting? As a service? In the start-up group?

Does CLI.EXE also start as a service? In your start-up group?


____________

Profile Ageless
Avatar
Send message
Joined: 9 Jun 99
Posts: 12456
Credit: 2,688,798
RAC: 1,220
Netherlands
Message 201791 - Posted: 3 Dec 2005, 4:22:17 UTC - in response to Message 201783.

Does CLI.EXE also start as a service? In your start-up group?

Funny... neither.

I just checked it. It starts up twice, both as the same thing:
CLI.exe as ATICCC is the Command Line Interface application.


HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\Notify

+ ATICCC CLI Application (Command Line Interface) ATI Technologies Inc. C:\\Program Files\\ATI Technologies\\ATI.ACE\\CLI.exe

+ ATI CATALYST System Tray.lnk CLI Application (Command Line Interface) ATI Technologies Inc. C:\\Program Files\\ATI Technologies\\ATI.ACE\\CLI.exe

____________
Jord

Fighting for the correct use of the apostrophe, together with Weird Al Yankovic

1mp0£173
Volunteer tester
Send message
Joined: 3 Apr 99
Posts: 8423
Credit: 356,897
RAC: 0
United States
Message 201794 - Posted: 3 Dec 2005, 4:30:49 UTC - in response to Message 201791.

Does CLI.EXE also start as a service? In your start-up group?

Funny... neither.

I just checked it. It starts up twice, both as the same thing:
CLI.exe as ATICCC is the Command Line Interface application.


HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\Notify

+ ATICCC CLI Application (Command Line Interface) ATI Technologies Inc. C:\\Program Files\\ATI Technologies\\ATI.ACE\\CLI.exe

+ ATI CATALYST System Tray.lnk CLI Application (Command Line Interface) ATI Technologies Inc. C:\\Program Files\\ATI Technologies\\ATI.ACE\\CLI.exe

My question (to hbamford) is about the order in which programs start and bind to various sockets.

As a general rule, I try to keep things out of the tray. I've got an ATI card, but I'm not running ATICCC or CLI.EXE.

Clearly, if CLI.EXE gets started first, and BOINC later tries to bind port 1043, it moves to the traditional 31416.

I don't know what CLI.EXE does if port 1043 is in use when it starts.

... and that may be different if you're running a newer version.
____________

Profile Ageless
Avatar
Send message
Joined: 9 Jun 99
Posts: 12456
Credit: 2,688,798
RAC: 1,220
Netherlands
Message 201797 - Posted: 3 Dec 2005, 4:40:47 UTC

Use Autoruns.

It will tell. :)
____________
Jord

Fighting for the correct use of the apostrophe, together with Weird Al Yankovic

hbamford
Send message
Joined: 15 Mar 03
Posts: 5
Credit: 9,564,547
RAC: 5,457
United States
Message 201855 - Posted: 3 Dec 2005, 6:38:41 UTC - in response to Message 201797.

Use Autoruns.

It will tell. :)


It certainly tells me a lot! Wow! Good tip!

OK, more details. Up until a few days ago, I didn't have this problem. Something got updated or installed or whatever and the problem appeared. It would seem that the order of execution changed. I have been seeing 2 instances of CLI.exe for years so that isn't new.

As to why some ATI users don't have these calls, perhaps it is related to the builtin TV tuner and associated stuff. I dunno.

I do not know enough about this stuff to force a re-order of execution and even if I did, it apparently can get re-ordered as the result of otherwise benign actions. Anybody have tips on that?

Anyway, it doesn't answer the original question of how does my manual invocation of boinc.exe differ from the automatic invocation by boincmgr.exe? And is there something that can be done to boincmgr.exe to "fix" this?

Thanks for all your help!

-- Harold

____________

hbamford
Send message
Joined: 15 Mar 03
Posts: 5
Credit: 9,564,547
RAC: 5,457
United States
Message 201856 - Posted: 3 Dec 2005, 6:41:01 UTC - in response to Message 201783.

However, when I start the boinc client from a DOS box by hand, I get the complaint about 1043 and using the alternate port. And then I can start boincmgr.exe and everything works.

When you aren't starting it by hand, how should it be starting? As a service? In the start-up group?

Does CLI.EXE also start as a service? In your start-up group?



I originally selected (during installation) the recommended option of running only for my login. I tried again by selecting for when anybody logs in. I didn't not want to run as a service because I like the screensaver. So -- I'm easily amused...

____________

hbamford
Send message
Joined: 15 Mar 03
Posts: 5
Credit: 9,564,547
RAC: 5,457
United States
Message 201876 - Posted: 3 Dec 2005, 8:12:39 UTC - in response to Message 201872.

When BOINC Manger should start the BOINC client (boinc.exe) -as in single or share mode - it has a problem when other applications use the for BOINC reserved port. Then it failes. This is not a issue when the BOINC client (boinc.exe) starts before BOINC Manager , as in service mode.

If you can not stop the other program to use the BOINC port, then service mode is the only real work around at the moment. Possible you may want to start boinc.exe in a DOS window and then start BOICN Manager. This must work too.

I hope the developers will fix this issue soon, but I don't know how long this will need.

There is a possibility to see the screen saver in servcie mode too. It is not really the secure solution but if some one may accept the risk ... I personl use the screen saver in service mode on some of my hosts.

You only need to change the service after the install in the way that it is starting with system account and not with the user named in the installation. The service must be restarted then.


As I don't have to restart my machine that often (NOW I've said it...) I'll just start boinc and then boincmgr by hand. If I could figure out which of the many places programs can be started happened in which order, I might put boinc in one and boincmgr in another. Or not.

Thanks for your help.
____________

Shaitan
Send message
Joined: 29 Nov 05
Posts: 2
Credit: 17,032
RAC: 0
Hungary
Message 210224 - Posted: 11 Dec 2005, 12:31:40 UTC - in response to Message 201855.

Hi,

I had the same problem as you and I've also using ATI card.
But I found a cure for this problem. I've started to use Omega ATI driver (www.omegadrivers.net) and Boinc is working fine with it.
You should give a try.

have a nice day,
Shaitan


Use Autoruns.

It will tell. :)


It certainly tells me a lot! Wow! Good tip!

OK, more details. Up until a few days ago, I didn't have this problem. Something got updated or installed or whatever and the problem appeared. It would seem that the order of execution changed. I have been seeing 2 instances of CLI.exe for years so that isn't new.

As to why some ATI users don't have these calls, perhaps it is related to the builtin TV tuner and associated stuff. I dunno.

I do not know enough about this stuff to force a re-order of execution and even if I did, it apparently can get re-ordered as the result of otherwise benign actions. Anybody have tips on that?

Anyway, it doesn't answer the original question of how does my manual invocation of boinc.exe differ from the automatic invocation by boincmgr.exe? And is there something that can be done to boincmgr.exe to "fix" this?

Thanks for all your help!

-- Harold

hbamford
Send message
Joined: 15 Mar 03
Posts: 5
Credit: 9,564,547
RAC: 5,457
United States
Message 211155 - Posted: 12 Dec 2005, 4:43:28 UTC - in response to Message 210224.

I had the same problem as you and I've also using ATI card.
But I found a cure for this problem. I've started to use Omega ATI driver (www.omegadrivers.net) and Boinc is working fine with it.
You should give a try.


What are omega drivers and why wouldn't I want to use the ATI drivers?

Also, I know that everytime I update the ATI drivers, I wind up spending several days getting things fully operational again. Thus, I am reluctant to touch them!

____________

Shaitan
Send message
Joined: 29 Nov 05
Posts: 2
Credit: 17,032
RAC: 0
Hungary
Message 211252 - Posted: 12 Dec 2005, 8:11:04 UTC - in response to Message 211155.

Omega drivers are a little different from the original catalyst drivers but they are based on it. Every time an ATI catalyst driver came out soon there is an Omega driver based on the same catalyst version. But for Omega driver there is no need for .NET and probably they are using different port because BOINC is working perfectly with it.


I had the same problem as you and I've also using ATI card.
But I found a cure for this problem. I've started to use Omega ATI driver (www.omegadrivers.net) and Boinc is working fine with it.
You should give a try.


What are omega drivers and why wouldn't I want to use the ATI drivers?

Also, I know that everytime I update the ATI drivers, I wind up spending several days getting things fully operational again. Thus, I am reluctant to touch them!

Questions and Answers : Windows : boinc client, port 1043, and alternate port

Copyright © 2014 University of California