Access Connections stalling my startup

Message

defjux · #1 Post by **defjux** » Fri Apr 07, 2006 7:26 pm

I love Access Connections, but 4.11 is a piece of garbage when it comes to integration. I switched from Intel's connection manager to AC and my startup time increased from about 20 secs to three minutes. It sounds picky, but I think I paid enough for the machine to expect IBMs own software to behave properly on it. Is this problem abnormal, or do the engineers over at IBM just code bad software? If so, is there a fix?

christopher_wolf · #2 Post by **christopher_wolf** » Fri Apr 07, 2006 7:32 pm

I have 4.11 and have cold-boot times that are always around or under 37 seconds (and they didn't increase with AC 4.11); sometimes less depending on what I setup for system services last time. I wouldn't be so quick to call it a badly coded software app. If you like Access Connections before 4.11 then stick with those.

#3 Post by **jdhurst** » Fri Apr 07, 2006 8:24 pm

Agree - It is not delaying my startup. My total startup is longish (2.5 minutes) what with HD Protection, Power Manager, Card Eject, Two NIC's, DU Meter, Cache Sentry (15 seconds right there), Symantec Client Security, Intellisync, Deskmenu, Netscreen VPN, Task Manager, Access Connections, plus another 50 odd services.

JD Hurst

DIGITALgimpus · #4 Post by **DIGITALgimpus** » Fri Apr 07, 2006 8:40 pm

Indeed... mine is rather long... but I don't see AC taking that long.

It does slow down my comp in the following case:

when using the wired lan (it doesn't effect wifi), it seems to hestiate before connecting, causing other network-based apps to hang a bit, waiting for a connection.

Also noticed coming out of standby with wifi is very smooth, but with a wired lan, it connects, disconnects, then connects for real. Not sure why.

#5 Post by **bill bolton** » Fri Apr 07, 2006 9:53 pm

defjux wrote:to expect IBMs own software to behave properly on it.

As ineed it does on all my T4 x systems.

You mentioned you had been using the Intel Connection Manager. Are you using the IBM supplied device drivers with Access Connection or the Intel supplied drivers? If you are using Intel supplied device drivers, you should replace them with the IBM supplied device drivers!

Cheers,

Bill

#6 Post by **GomJabbar** » Sat Apr 08, 2006 12:21 am

This can happen when Access Connections tries to make a wireless or perhaps wired connection on Windows startup, and such a connection is not available. I had Access Connections working fine at home, but when I went to another location, I experienced long boot times like you are describing. Try leaving your wireless radio off when you shutdown. Also try disabling Location Switching, and uncheck box to Allow wireless connection at Windows logon.

christopher_wolf · #7 Post by **christopher_wolf** » Sat Apr 08, 2006 12:27 am

Interesting...I go all around the campus to various access points and haven't encountered long boot up times.

davidspalding · #8 Post by **davidspalding** » Sat Apr 08, 2006 9:28 am

defjux wrote:I love Access Connections, but 4.11 is a piece of garbage when it comes to integration. I switched from Intel's connection manager to AC and my startup time increased from about 20 secs to three minutes. It sounds picky, but I think I paid enough for the machine to expect IBMs own software to behave properly on it. Is this problem abnormal, or do the engineers over at IBM just code bad software? If so, is there a fix?

Do you have it connecting at logon ("allow wireless connection at windows logon (requires restart)")? I tried that - ONCE. It made it take twice as long for logging in to take place. Check your global options, and deselect that if enabled.

FWIW, I leave my radio on for shutdown, and use location switching ... no problems on startup. Though ... lots of IBM utilities loading up make boot times a bit laborious. < 2 minutes, usually.

christopher_wolf · #9 Post by **christopher_wolf** » Sat Apr 08, 2006 2:19 pm

davidspalding wrote:
defjux wrote:I love Access Connections, but 4.11 is a piece of garbage when it comes to integration. I switched from Intel's connection manager to AC and my startup time increased from about 20 secs to three minutes. It sounds picky, but I think I paid enough for the machine to expect IBMs own software to behave properly on it. Is this problem abnormal, or do the engineers over at IBM just code bad software? If so, is there a fix?
Do you have it connecting at logon ("allow wireless connection at windows logon (requires restart)")? I tried that - ONCE. It made it take twice as long for logging in to take place. Check your global options, and deselect that if enabled.

FWIW, I leave my radio on for shutdown, and use location switching ... no problems on startup. Though ... lots of IBM utilities loading up make boot times a bit laborious. < 2 minutes, usually.

Seriously, this is the only way I have found, thus far, that significantly impedes startup. Added on an easy 10 seconds or more.

#10 Post by **GomJabbar** » Sat Apr 08, 2006 5:41 pm

christopher_wolf wrote:Interesting...I go all around the campus to various access points and haven't encountered long boot up times.

I may be barking up the wrong tree here, but I did have the extra long boot-up times after one of my Access Connection upgrades. I did not experience this at home, but when I went to work where I had no WiFi signal at all, this is when it happened. My solution at the time was to temporarily disable Access Connections at work. When I got home, I enabled it again. Since this episode occurred, I have updated Access Connections again. With the settings mentioned above, I have not noticed any appreciable difference in boot-up times regardless of my location.

Edit: I said I disabled Access Connections. Actually, I think I disabled my wireless adapter when away from home.

Access Connections stalling my startup

Access Connections stalling my startup

Re: Access Connections stalling my startup

Re: Access Connections stalling my startup

Re: Access Connections stalling my startup

Who is online