regsvr32 shell32.dll

I tried to run regsvr32 shell32.dll but I got the following message "shell32
was loaded, but theDIIRegisterSever entry point was not found. What does
this mean?
Sol

S1L1Y1 wrote:

I tried to run regsvr32 shell32.dll but I got the following message
"shell32 was loaded, but theDIIRegisterSever entry point was not
found. What does this mean?

The only thing regsvr32 does is calling a function in the provided dll. The
dll is supposed to register itself. This function is called
'DllRegisterServer', and obviously your shell32.dll doesn't export such a
function.

Have you tried it with the /i switch?

regsvr32 /i shell32.dll

--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.net/
http://dts-l.net/goodpost.htm


"S1L1Y1" wrote in message
...
I tried to run regsvr32 shell32.dll but I got the following message "shell32
was loaded, but theDIIRegisterSever entry point was not found. What does
this mean?
Sol

On Fri, 18 Jan 2008 14:34:25 -0500, "glee"
put finger to keyboard and composed:

Have you tried it with the /i switch?

regsvr32 /i shell32.dll

Sorry to hijack this thread, but what exactly does the regsvr32
command actually do, ie what does "registering" a .dll file involve?

All I have been able to find is an explanation such as ...

"This command-line tool registers .dll files as command components in
the registry."

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

"Explanation of Regsvr32 usage and error messages"
http://support.microsoft.com/kb/249873/en-us

HTH

Mart


"Franc Zabkar" wrote in message
...
On Fri, 18 Jan 2008 14:34:25 -0500, "glee"
put finger to keyboard and composed:

Have you tried it with the /i switch?

regsvr32 /i shell32.dll

Sorry to hijack this thread, but what exactly does the regsvr32
command actually do, ie what does "registering" a .dll file involve?

All I have been able to find is an explanation such as ...

"This command-line tool registers .dll files as command components in
the registry."

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

Franc, you might find some further insight in the Win98 Resource Kit (on the
Win98 CD) in Section 31 - Windows 98 Registry, sub-section Working with the
Registry Keys.

Don't know if that helps or not, but it's the best I can find.

Mart


"Mart" wrote in message
...
"Explanation of Regsvr32 usage and error messages"
http://support.microsoft.com/kb/249873/en-us

HTH

Mart


"Franc Zabkar" wrote in message
...
On Fri, 18 Jan 2008 14:34:25 -0500, "glee"
put finger to keyboard and composed:

Have you tried it with the /i switch?

regsvr32 /i shell32.dll

Sorry to hijack this thread, but what exactly does the regsvr32
command actually do, ie what does "registering" a .dll file involve?

All I have been able to find is an explanation such as ...

"This command-line tool registers .dll files as command components in
the registry."

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

On Sat, 19 Jan 2008 01:53:52 -0000, "Mart"
put finger to keyboard and composed:

Franc, you might find some further insight in the Win98 Resource Kit (on the
Win98 CD) in Section 31 - Windows 98 Registry, sub-section Working with the
Registry Keys.

Don't know if that helps or not, but it's the best I can find.


Thanks, I looked but couldn't find any pertinent information.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

On Sat, 19 Jan 2008 01:28:07 -0000, "Mart"
put finger to keyboard and composed:

"Explanation of Regsvr32 usage and error messages"
http://support.microsoft.com/kb/249873/en-us

HTH

Mart

Thanks, I had already seen that, but the problem is that I'm not a
programmer and therefore have no idea what registering a .dll file
means. My understanding is that a .dll file contains a library of
functions which can be accessed by any program that knows how to call
it. Therefore I would have thought that merely placing the .dll file
in the Windows\System directory (or wherever is applicable) would
satisfy the calling program. Otherwise what more information is made
available via the registration process?

"Franc Zabkar" wrote in message
.. .
On Fri, 18 Jan 2008 14:34:25 -0500, "glee"
put finger to keyboard and composed:

Have you tried it with the /i switch?

regsvr32 /i shell32.dll

Sorry to hijack this thread, but what exactly does the regsvr32
command actually do, ie what does "registering" a .dll file involve?

All I have been able to find is an explanation such as ...

"This command-line tool registers .dll files as command components in
the registry."

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.


- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

... Otherwise what more information is made
available via the registration process?

Dunno - but I have certainly seen the effect of an 'unregistered' .dll

viz. - REGSVR32 THUMBVW.DLL in particular

I believe they (.dll's) need to be registered for 'system global' purposes,
i.e. so they can be called (via their registered path?) by any application
(wherever located) requiring them, from any installed location (usually
windows\systemxx). Merely placing them there may not be enough. But then I'm
not a programmer either.

Perhaps this site *might* give further insight:-
http://consumer.installshield.com/kb.asp?id=Q108199

Hmm.. see also:-
http://www.kbdedit.com/manual/file_r..._dll_file.html

Mart


"Franc Zabkar" wrote in message
...
On Sat, 19 Jan 2008 01:28:07 -0000, "Mart"
put finger to keyboard and composed:

"Explanation of Regsvr32 usage and error messages"
http://support.microsoft.com/kb/249873/en-us

HTH

Mart

Thanks, I had already seen that, but the problem is that I'm not a
programmer and therefore have no idea what registering a .dll file
means. My understanding is that a .dll file contains a library of
functions which can be accessed by any program that knows how to call
it. Therefore I would have thought that merely placing the .dll file
in the Windows\System directory (or wherever is applicable) would
satisfy the calling program. Otherwise what more information is made
available via the registration process?

"Franc Zabkar" wrote in message
. ..
On Fri, 18 Jan 2008 14:34:25 -0500, "glee"
put finger to keyboard and composed:

Have you tried it with the /i switch?

regsvr32 /i shell32.dll

Sorry to hijack this thread, but what exactly does the regsvr32
command actually do, ie what does "registering" a .dll file involve?

All I have been able to find is an explanation such as ...

"This command-line tool registers .dll files as command components in
the registry."

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.


- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

"Franc Zabkar" wrote in message
...
On Fri, 18 Jan 2008 14:34:25 -0500, "glee"
put finger to keyboard and composed:

Have you tried it with the /i switch?

regsvr32 /i shell32.dll

Sorry to hijack this thread, but what exactly does the regsvr32
command actually do, ie what does "registering" a .dll file involve?

All I have been able to find is an explanation such as ...

"This command-line tool registers .dll files as command components in
the registry."

Well, that's what it does.....the particular file contains the information for
self-registering, which means to add its needed entries into the Registry. Each
component is specific to the file that is registered, and what those components are
is known by the programmer.

Some can be searched online.....for example, go he
http://www.mvps.org/serenitymacros/repair.html

Expand the first heading:
Repairing your File Associations from Winzip

Scroll down and you will see an example where, if you've installed Compressed
Folders from Plus!98, the file zipfldr.dll is registered, and you can effect a
repair if it stops working correctly by re-registering it with regsvr32.

That action adds the following entries to the Registry:

[HKEY_CLASSES_ROOT\.zip]
"Content Type"="application/x-zip-compressed"
@="CompressedFolder"
[HKEY_CLASSES_ROOT\.zip\ShellNew]
"NullFile"=""
[HKEY_CLASSES_ROOT\CompressedFolder]
@="Compressed Folder"
[HKEY_CLASSES_ROOT\CompressedFolder\CLSID]
@="{E88DCCE0-B7B3-11d1-A9F0-00AA0060FA31}"
[HKEY_CLASSES_ROOT\CompressedFolder\DefaultIcon]
@="C:\\WINDOWS\\SYSTEM\\ZIPFLDR.DLL"
[HKEY_CLASSES_ROOT\CompressedFolder\Shell]
[HKEY_CLASSES_ROOT\CompressedFolder\Shell\Explore]
[HKEY_CLASSES_ROOT\CompressedFolder\Shell\Explore\C ommand]
@="explorer /e,/root,{E88DCCE0-B7B3-11d1-A9F0-00AA0060FA31},%L"
[HKEY_CLASSES_ROOT\CompressedFolder\Shell\Open]
[HKEY_CLASSES_ROOT\CompressedFolder\Shell\Open\Comm and]
@="rundll32.exe zipfldr.dll,RouteTheCall %L"
[HKEY_CLASSES_ROOT\CompressedFolder\ShellEx]
[HKEY_CLASSES_ROOT\CompressedFolder\ShellEx\Context MenuHandlers]
[HKEY_CLASSES_ROOT\CompressedFolder\ShellEx\Context MenuHandlers\{E88DCCE0-B7B3-11d1-A9F0-00AA0060FA31}]
@="Compressed Folder Menu"
[HKEY_CLASSES_ROOT\CompressedFolder\ShellEx\DropHan dler]
@="{E88DCCE0-B7B3-11d1-A9F0-00AA0060FA31}"
[HKEY_CLASSES_ROOT\CLSID\{E88DCCE0-B7B3-11d1-A9F0-00AA0060FA31}]
@="CompressedFolder"
[HKEY_CLASSES_ROOT\CLSID\{E88DCCE0-B7B3-11d1-A9F0-00AA0060FA31}\DefaultIcon]
@="C:\\WINDOWS\\SYSTEM\\ZIPFLDR.DLL"
[HKEY_CLASSES_ROOT\CLSID\{E88DCCE0-B7B3-11d1-A9F0-00AA0060FA31}\InProcServer32]
@="C:\\WINDOWS\\SYSTEM\\ZIPFLDR.DLL"
"ThreadingModel"="Apartment"
[HKEY_CLASSES_ROOT\CLSID\{E88DCCE0-B7B3-11d1-A9F0-00AA0060FA31}\ProgID]
@="CompressedFolder"
[HKEY_CLASSES_ROOT\CLSID\{E88DCCE0-B7B3-11d1-A9F0-00AA0060FA31}\ShellFolder]
"Attributes"=hex:a0,01,00,20
[HKEY_CLASSES_ROOT\CLSID\{E88DCCE0-B7B3-11d1-A9F0-00AA0060FA31}\Implemented
Categories]
[HKEY_CLASSES_ROOT\CLSID\{E88DCCE0-B7B3-11d1-A9F0-00AA0060FA31}\Implemented
Categories\{00021490-0000-0000-C000-000000000046}]

Every self-registering .dll or .ocx file can have anywhere from a few to dozens or
hundreds of entries....it depends on what the programmer built into the file.

Hope this helps....
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.net/
http://dts-l.net/goodpost.htm