T43 slow startup

[kidpaprika]

Hi

I recently bought a 2nd-user t43. I decided to start with a clean Windows installation as it seemed to boot up a little slowly. I formatted and reinstalled Windows and bootup was super-fast.

I then installed the drivers.

From then on, whenever Windows booted, it seemed to hang for quite a few seconds (maybe 30?) on the welcome screen. The wireless light flashed during this time.

I uninstalled the WiFi drivers and the problem went away. Reinstalled and it happened again.

Any ideas?

[lithium726]

Its trying to connect to a wireless network. Annoying, i know, but I dont know of any way around it... you could turn off the wireless antenna so it doenst find anything, or juts hybernate instead of shutdown...

[Supporter]

Its trying to connect to a wireless network. Annoying, i know, but I dont know of any way around it... you could turn off the wireless antenna so it doenst find anything, or juts hybernate instead of shutdown...

If you are using access connections then it has an option inside preferences to try and connect on start up.

However if you are using a windows based connection method.. try the following.

Find the latest driver on our website for the wireless card.

Remove any instance of WIRELESS from add or remove programs. Intel wireless or IBM wireless. Also remove INTEL SEBRING if is a intel based wireless card.

Upon removal restart. If the found new hardware wizard comes up close it.

Install the latest driver being sure to follow the installation instructions exactly. Reboot.

If problem persists let me know.

[rcrooks]

I have the same problem plus a little something else.

Every 10th boot or so itll boot me up and sit there with the background and a cursor, and when I alt ctrl del it I have about 25 processes running instead of the usual 55.

It usually takes about 30 seconds and then the rest of them start to boot up. I have no idea why it takes so long and what makes it do this on what seems like 10% of bootups

[kam_]

The problem on the welcome screen is with ACNotify.dll (access connections). If you turn on verbose messaging you can see windows hang for a minute while loading that dll. It's actually not got anything to do with it searching for connections but a bug in the dll.

[Turn on verbose messaging - very handy for debugging!]

Go to Start/Run/Regedit and navigate to this key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
To enable verbose status messages create a new DWORD value called "verbosestatus" and set it to "1".

An additional value called "DisableStatusMessages" forces status messages to be disabled, make sure this value does not exist or is set to "0".

Restart Windows for the change to take effect.

Use software installer to downgrade to Access Connections < 4.11a. Right now i'm using 3.71 which is working fine.

The problem of half the processes loading and then the rest after 30 seconds to a minute has had me baffled for a long time.
I first thought it was a problem with the order of startup programs - this can't be set manually as it depends on the the way the registry hive gets compacted. However its not startup processes but some windows service hanging.

I would suggest you disable windows services a few at a time to see which one is causing the problem. If you figure it out please let me knoe!

[rcrooks]

Well, Ive never had this problem with any computer before with booting up halfway.. so Ive got to naturally suspect an IBM preload...

Ill do some sleuthing and see what I can find.

[ashleys]

I've also had the problem with ACNotify.dll waiting for 1 minute during startup.

You can significantly reduce the wait time by running it asynchronously. This allows the rest of the startup sequence to finish whilst ACNotify is still running. I only have a 5-10 second delay now at the end of my startup before Access Connections (who is waiting for the ACNotify to finish) comes up.

To run it asynchronously find the ACNotify key in the registry. It's under (on my Windows 2000 system)

My Computer\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\ CurrentVersion\Winlogon\Notify\ACNotify

In that key you'll find the DllName which should be ACNotify.dll.
You will also see an asynchronous REG_DWORD which is set to 0. Set the asynchronous REG_DWORD to 1 and re-boot.

If you have the verbose message setting on (as described in an earlier post) you will see no ACNotify.dll message at all. Startup will continue normally but you probably will see a small delay at the end of start up before Access Connections starts.

[nyc]

Hello,

I was having the same problem after I did a clean install of XP SP2 along with all the drivers on my T42 with Thinkpad b/g wireless.

There was a long delay, at the logon screen, after I had logged on. Then there was more delay after the desktop loaded until the wireless card was up and running.

Without going into details here's what I found. Access connection is not the culprit, it seemed like it but it's actually the Thinkpad b/g wireless card itself(or the driver) which in turn caused Access Connection's delay.

I tested my system with 3 most recent softwares for the wireless driver and the Access Connection software.

Even without the Access Connection software there was a delay at logon or at desktop until the wireless was up and running.



Solution:

I found this on an old post and I would like to thank the users "Porsche" and "Kenn" for the solution. The post title was "ACK! Delayed bootup due to Wireless Card?"

The solution, which was quite simple(for me at least), was to turn on Wireless Zero Configuration. You do this by setting the Wireless Zero Configuration service to start automatically.

I think I had my system set to Disabled or manual. The long hang/delay was completely gone when I rebooted after I changed it to start automatically.

No other changes were necessary.

I'm using the latest driver(5.3.035) and Access Connection software(4.41), without any delays now. My system used to hang for about 2-3 minutes, not anymore.

Once again, big thanks to Porsche and Kenn!