Unsolved

This post is more than 5 years old

34674

July 27th, 2005 11:00

Newest drivers for my 8600 gives error message on boot up

Following some intermittant and annoying breakdowns in connectivity with my Wanadoo Livebox, I downloaded the latest drivers for my 1350 wireless card and WLAN Utility (new version 3.120.28.0)
 
Now, when I boot up, I'm given an error message "notification.dll has not been registered, program will not work".  As soon as I cancel/acknowledge the message, the WLAN utility loads and works normally.
 
Any ideas would be very welcome?

2 Intern

 • 

12K Posts

July 28th, 2005 05:00

Have you tried to uninstall and reinstall the application?

August 15th, 2005 20:00

I found following event in log:

The System Event Notification service depends on the following nonexistent service: EventSystem

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

August 15th, 2005 20:00

I tried to start the service manually, I got:

Could not start System Event Notification service on Local Computer
Error 1075: The dependency service does not exist or has been marked for deletion

August 15th, 2005 20:00

I have same problem with clean new XP Pro setup. I uninstalled, installed, the problem still persists. What is notification.dll? Should I install some more soft? It is not original Dell setup.

August 15th, 2005 22:00

I tried to install .NET Framework 1.1 but the problem still persists.

Message Edited by rostro on 08-15-2005 06:09 PM

August 18th, 2005 15:00

I just updated my WLAN 1350 from the Dell download area and am getting the same thing - "Notification dll has not been registered, program will not work correctly." What program? My wireless network is working fine! And I'm not running any program.

I think Dell or their supplier may have supplied a faulty update?

2 Posts

August 23rd, 2005 00:00

I have a 5100 notebook -- just installed the latest Wireless driver, and I get that same error message about not registering the notification.  Does anyone know how to ask someone at Dell what to do?  Has anyone fixed the problem?  I rolled back the driver, and the problem persisted.  Acck.
 

August 23rd, 2005 02:00

I talked to Dell and they had me roll back my system to a check point prior to my upgrade. The message continued. So then they had me run a chkdsk/r which did find some errors that were fixed. But now I couldn't boot my system because ntfs.sys was missing or corrupt. :smileymad: So I used the recovery console to copy the file off the CD twice and my system still complained about ntfs.sys. :smileymad::smileymad: Now I wished that I just left the error messages be as at least I had a system that was functioning! Next I reinstalled XP using the repair option. This finally gave me a bootable system. It was a pain as I had to reinstall all the updates to XP - BUT I HAD A WORKING SYSTEM! The messages about wireless configuration are still there, but I don't care. :smileysad:

August 26th, 2005 17:00

I´ve got workaround :-))))
If you change anything in Add or Remove Programs / Add/Remove Windows Components, the COM+ system is repaired automatically. I removed Windows Messenger for example. The missing COM+ Event System service is so configured again and the problem disappears.

Sooooooo simple ;-)
Enjoy

2 Posts

August 26th, 2005 19:00

I'll try it!  I suspect you are a genius!  :-D
 

4 Posts

September 19th, 2005 17:00

Hi, the answer to this issue is to register an unregistered .dll file, two of them to be precise.  The actual error message doesn't read "notification.dll", it reads "notification dll".  Ideally it would read "Notification:  dll has not been registered."
 
Regardless of the poor punctuation in the error message (on behalf of the programmers, not you), the solution is extremely easy:
 
Click Start -> Run and type in "regsvr32 atl.dll" (without the quotes), click OK
Click Start -> Run and type in "regsvr32 wltrynt.dll" (without the quotes), click OK
 
Enjoy the absence of that very annoying error message!

2 Posts

September 17th, 2006 13:00



@iherrick wrote:

Hi, the answer to this issue is to register an unregistered .dll file, two of them to be precise.  The actual error message doesn't read "notification.dll", it reads "notification dll".  Ideally it would read "Notification:  dll has not been registered."

 

Regardless of the poor punctuation in the error message (on behalf of the programmers, not you), the solution is extremely easy:

 

Click Start -> Run and type in "regsvr32 atl.dll" (without the quotes), click OK

Click Start -> Run and type in "regsvr32 wltrynt.dll" (without the quotes), click OK

 

Enjoy the absence of that very annoying error message!





This did not work for me. Neither di the other suggestion to remove Windows Messenger. Anybody else??

1 Message

January 29th, 2007 01:00

I fixed this by starting (setting to automatic) the two COM+ services (control panel > administrative tools > component services > services).
 
Cheers.
No Events found!

Top