"APPINIT_DLLS=" error and ".wll" error

Ok first off I have no knowledge of registry problems or how to fix them.
With that said I have been trying to get some help for a long time with two
errors I keep getting. It all started after installing a update from windows
update and up until now they had always been helpfull. I keep getting moved
around and forwarded to different people and they have not been able to help
me fix the errors so I am asking for help from anyone who can help. I would
prefer help from someone who has had these issues and fixed them, but at this
point I would greatly appreciate any help because error messages really
bother me, even if it has not caused a problem yet.

These are the errors I have got :
1. ' AppInit_DLLs=' this one has two errors that show up.

1st error message: "Cannot find the file ' AppInit_DLLs=' ( or one of it's
components). Make sure the path and filename are correct and that all
required libraries are available."

2nd error message "Could not load or run ' AppInit_DLLs=' specified in the
registry. Make sure the file exists on your compoter or remove the referance
to it in the registry."

This is what I have found about this but it is of no use to me because it
does not provide me with a "fix" that I can do.


ARTICLES FROM MICROSOFT ABOUT ERROR:

Working with the AppInit_DLLs registry value
View products that this article applies to.
Article ID : 197571
Last Review : February 19, 2005
Revision : 4.0
This article was previously published under Q197571
SUMMARY
The AppInit_DLLs value is found in the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Windows

All the DLLs that are specified in this value are loaded by each Microsoft
Windows-based application that is running in the current log on session.
MORE INFORMATION
Note This feature may not be available in future versions of the Windows
operating system.

The AppInit DLLs are loaded by using the LoadLibrary() function during the
DLL_PROCESS_ATTACH process of User32.dll. Therefore, executables that do not
link with User32.dll do not load the AppInit DLLs. There are very few
executables that do not link with User32.dll.

Because of their early loading, only API functions that are exported from
Kernel32.dll are safe to use in the initialization of the AppInit DLLs.

We do not recommend that applications use this feature or rely on this
feature. There are other techniques that can be used to achieve similar
results. For additional information, click the following article number to
view the article in the Microsoft Knowledge Base:
134655 (http://support.microsoft.com/kb/134655/) AppInit_DLLs registry value
and Windows 95
The AppInit_DLLs value has type "REG_SZ." This value has to specify a
NULL-terminated string of DLLs that is delimited by spaces or by commas.
Because spaces are used as delimiters, do not use long file names. The system
does not recognize semicolons as delimiters for these DLLs.

Typically, only the Administrators group and the LocalSystem account have
write access to the key that contains the AppInit_DLLs value.

--------------------------------------------------------------------------------

APPLIES TO
• Microsoft Win32 Application Programming Interface (API), when used with:
the operating system: Microsoft Windows NT 4.0
Microsoft Windows 2000 Standard Edition
the operating system: Microsoft Windows XP


Back to the top

Keywords: kbdll kbinfo kbkernbase kbregistry KB197571

AppInit_DLLs Registry Value and Windows 95
View products that this article applies to.
Article ID : 134655
Last Review : March 1, 2005
Revision : 3.2
This article was previously published under Q134655
SUMMARY
Windows 95 does not support the loading of a DLL into a process's address
space through the use of the AppInit_DLLs registry value. In Windows NT, for
every process executed, Windows NT loads the DLLs listed in the AppInit_DLLs
registry value into the process' address space. For similar functionality in
Windows 95, you can implement a system-wide hook. This article shows by
example how to do it.
MORE INFORMATION
To implement a system-wide hook, you must ensure that the hooked function
(callback function) exists in a DLL. Then, when the this function is called,
the operating system maps the hooked DLL into the target application's
address space. The actual hooked function then operates as part of the target
application's process.

There are essentially two steps involved in creating a system-wide hook: 1.
Create a DLL with an exported function that is used as the hooking function.
In the sample function that follows, the callback function is modeled after a
callback function required to implement a WH_KEYBOARD system-wide hook:
// Trap keyboard messages
__declspec(dllexport) LRESULT CALLBACK HookFunction(
int code,
WPARAM wParam,
LPARAM lParam)
{
char szVCode[50];

//display the virtual key code trapped
sprintf(szVCode, "Virtual Key code: %lx", wParam);
MessageBox(NULL, szVCode,"Key stroke", MB_OK);
:
:
}

The associated .def file for this DLL might resemble this:

LIBRARY HOOK

EXPORTS
HookFunction


2. Install the system-wide hook. To install the hook, the DLL must be
loaded, the hook function's address retrieved, and SetWindowsHookEx called
with the function's address. Here's an example: // add system-wide hook
hHookDll = LoadLibrary("hook");
hHookProc = (HOOKPROC) GetProcAddress(hHookDll, "HookFunction");

// Install keyboard hook to trap all keyboard messages
hSystemHook = SetWindowsHookEx(WH_KEYBOARD,hHookProc,hHookDll,0);

Once the application has finished with the system-wide hook, be sure to undo
the hooking process as follows: // Remove the hook and unload the DLL
used for the hooking process
UnhookWindowsHookEx(hSystemHook);
FreeLibrary(hHookDll);




--------------------------------------------------------------------------------

APPLIES TO
• Microsoft Win32 Application Programming Interface (API), when used with:
Microsoft Windows 95 Service Pack 1
Microsoft Windows 98 Standard Edition
Microsoft Windows Millennium Edition


Back to the top

Keywords: kbcode kbkernbase kbregistry KB134655

Sorry that was so long but I hope if I give all information I have someone
might be able to help.

The second error I get is when I run Nortin WinDoctor invalid file
extension. This error is very problematic and once again I can find no "real"
help on fixing it. This is what is stated by windoctor:

Missing or Invalid Key: ".wll"
The file extensions, ".wll", referes to an invalid identifier,
"Word.Addin.8" it tries to delete the registry entry but fails everything I
have tried has failed there seems to be now information from microsoft about
this and all the message boards I have been to could not help me fix this
issue.

My OS is Windows2000 Professional

---Evil
.