ProE and Windoze Registry question

[ptc-113113]

I was trying to clean PTC entries out of my registry today when I
noticed an over abundance of clones of the following key :

Key Name:
HKEY_CLASSES_ROOT\CLSID\{02B56CD4-088B-3E27-BEEC-A12517977D2B}\InprocSer
ver32
Class Name: <no class=">
Last Write Time: 6/19/2006 - 1:11 PM
Value 0
Name: <no name=">
Type: REG_SZ
Data: D:\PTC\PROEWI~1\i486_nt\lib\pfcscom.dll <<<this is<br="/>a path into my proe load point>>>

One or two references to this would not peak my interest, but there are
about 100 cloned entries for this key, where the only thing that seems
to be different is the CLSID itself. So another way to explain it is,
there are around 100 copies of this key that are identical, except the
hexadecimal names are different for each one.

Questions:
Would a tool like "reg clean" ( or equivalent ) clean this and all its
clones out of my registry?

What does Proe use pfcscom.dll for?

What is InprocServer32?

"InProcServer32
The registry key 'HKEY_CLASSES_ROOT\CLSID\{16-byte
ID}\InProcServer32' holds the full path to a DLL if the COM object is
implemented as a library. If this key does not exist then it is assumed
that the COM object is managed by a separate process, with LocalServer32
holding the full path name of the executable." ref.
http://www.cryer.co.uk/glossary/i/inprocserver32.htm
huh???


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[MarcMettes]

That DLL exposes the COM interface for WebLink. There are
many entries because there are many entry points into the
API for that DLL.

If you remove the registry entries, WebLink will probably
not work. Even worse, they will most likely be recreated
later on, perhaps when ProEngineer is restarted. Depends
on the value of the config.pro setting WEB_ENABLE_JAVASCRIPT.

For WF1 and WF2, WebLink is the closest things to a freely
available, lightweight, platform independent scripting
language for ProEngineer. While it does introduce some
awkward hurdles to overcome (i.e. web browser security
settings), apps can be created, with slick HTML-based GUIs,
very quickly.


Marc

[unknown1]

A COM object is a means of communication with software using
programming. http://en.wikipedia.org/wiki/Component_Object_Model
Judging by the many pfc entries in the ProE manual, in this case we are
dealing with the J-Link interface.

Inprocserver: Microsofts description is shorter: "Registers a 32-bit
in-process server and specifies the threading model of the apartment the
server can run in." In other words it is a process that provides the COM
interface with some default environment.

If I'm not mistaken tools like regclean checks for references to absent
files and deletes the references if the files are found to be absent.

Perhaps next time you should try uninstalling Pro/E using the tools
provided for that purpose? 😉

Cheers,
Patrick

Andrew Amsden wrote:
> I was trying to clean PTC entries out of my registry today when I
> noticed an over abundance of clones of the following key :
>
> Key Name:
> HKEY_CLASSES_ROOT\CLSID\{02B56CD4-088B-3E27-BEEC-A12517977D2B}\InprocServer32
>
> Class Name: <no class=">
> Last Write Time: 6/19/2006 - 1:11 PM
> Value 0
> Name: <no name=">
> Type: REG_SZ
> Data: D:\PTC\PROEWI~1\i486_nt\lib\pfcscom.dll <<<this is=" <br="/>> a path into my proe load point>>>
>
> One or two references to this would not peak my interest, but there are
> about 100 cloned entries for this key, where the only thing that seems
> to be different is the CLSID itself. So another way to explain it is,
> there are around 100 copies of this key that are identical, except the
> hexadecimal names are different for each one.
>
> Questions:
> Would a tool like "reg clean" ( or equivalent ) clean this and all its
> clones out of my registry?
>
> What does Proe use pfcscom.dll for?
>
> What is InprocServer32?
>
> "InProcServer32
>
> The registry key ‘HKEY_CLASSES_ROOT\CLSID\{16-byte
> ID}\InProcServer32’ holds the full path to a DLL if the COM object
> is implemented as a library. If this key does not exist then it is
> assumed that the COM object is managed by a separate process, with
> LocalServer32 holding the full path name of the executable." ref.
> _http://www.cryer.co.uk/glossary/i/inprocserver32.htm_
>
> huh???
>
>