Re: determining #ram slots and # of slots currently in use

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"Lisa" wrote in <news:u71YT9PzIHA.2184@xxxxxxxxxxxxxxxxxxxx>:

You don't uninstall ActiveX controls, you delete them.

Please do tell us the EXACT process to do that which is the SAME for
every AX object installed.

I didn't realize that "regsrv32.exe" was a "delete" operation. regsvr32
does not delete "them" (files). Or maybe "delete" was some larger
procedure that you didn't bother to define. You think using Windows
Explorer to select the AX *description* at "C:\Windows\Downloaded
Program Files" (a "special" folder and why Windows Explorer doesn't show
the actual files) will let you delete all AX files? The Adobe PDF AX
control is over in C:\Program Files\Common
Files\Adobe\Acrobat\ActiveX\AcroPDF.dll. The AX installer can put the
file anywhere. Not all AX objects are recorded with an Uninstall key
entry so they show up in the Add/Remove Programs applet for easy removal
(but often results in incomplete removal).

How is the user to know what to delete? If the AX control is inside a
shared DLL, will the user know that and realize that the file should not
be deleted if other functionality is still needed? Not all AX controls
are containing within an .ocx file. How are you going to delete one AX
object (entry point) from msxml without lossing the entire library which
means losing other AX controls that you did not intend to remove? Are
YOU going to make yourself immediately available all day and every day
to provide guidance to the user on how to *properly* remove one AX
control and do so without affecting other functionality or leaving
remnants in the registry?

- You need to deregister them. Otherwise, they remain in the registry
and the user may end up seeing errors when they are called but the path
reference in the registry points to a file and entry point that no
longer exist.

- You need to delete the files, yes. Windows Explorer will not show you
the files. It shows you the object definition when you visit the
"special" directory that holds them (once you determine which folder
that is). I have deleted AX objects this way and I have ended up with
some remnant files for that AX object. Not a lot of users are really
comfortable with using a command shell to ensure that they delete ALL
files (there may be more than 1 for an AX control). When you are using
the DOS shell so you can actually see the *files*, how do you know which
..ocx, .dll, .inf, and other files comprise a particular AX object? They
may be similarly named. They may not.

Removing an AX control is only easy and simple if the developer made it
that way. Unfortunately, even with enterprise-level software,
developers are not keen on spending time on how to remove their
products. Their goal is to get them into your system, not out of it.

Here's an example. You go to Symantec and install their AX control for
their online scan. In Windows Explorer, you see the following AX
objects when you navigate Windows Explorer to C:\Windows\Downloaded
Program Files:

Symantec AntiVirus Scanner
Symantec RuFSI Utility Class

Which do you "delete" (right-click, remove) using Windows Explorer? One
is obvious. Remove the scanner AX object does not remove the RuFSI AX
object. What is RuFSI used for? Should you delete it, too? Is having
to do web research part of that simplistic "delete" scheme that you
didn't define? If you used their online scanner and then remove the
Symantec AntiVirus Scanner AX object, did that get rid of all the files
for it simply because the entry in Windows Explorer disappeared? No.
Now use a DOS shell to go delete the virscan*.dat file in that folder.
Don't go deleting all *.dat files because some were created by other AX
objects. What about the zdone.dat file? Was it for the Symantec
scanner AX object? You can't tell. Looks like a candidate, though.
There are some other .dat files in that folder so you'll have to use
notepad or a hex editor to make a guess as to whether they should be
deleted after removing the Symantec scanner AX object.

Yeah, oh, it is so simple to "delete" and AX object. If you have the
expertise, initiative, and stubbornness to fully extract an AX control
from your system and without causing interdependency problem then, yes,
the AX object can be "deleted" from your system. For the vast majority
of users, however, the AX object continues to pollute their system.
.

Relevant Pages

  • UserControl and CreateObject
    ... I have a UserControl that encapsulates a MSCOMM object. ... This control is being used in an MDI project. ... test situations where a computer does not have the Bluetooth scanner ... Run-Time error '429': ...
    (microsoft.public.vb.general.discussion)
  • Re: UserControl and CreateObject
    ... > I have a UserControl that encapsulates a MSCOMM object. ... This control is being used in an MDI project. ... > test situations where a computer does not have the Bluetooth scanner ... ran it on a test machine. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB Applications with Barcode Scanners
    ... IMHO when a input device like a barcode scanner (unlike for instance a ... control, I can not see why that should be so difficult. ... Dick Grier explained that you could not make a keyboard wedge scanner to ...
    (microsoft.public.vb.general.discussion)
  • EEYE: BitDefender Online Scanner 8 Double Decode Heap Overflow
    ... BitDefender Online Scanner 8 Double Decode Heap Overflow ... BitDefender Online Anti-Virus Scanner 8.0 released on May 24th 2006. ... control from being initialized outside of an authorized domain. ... A remote vulnerability lies within a malformed request sent to ...
    (Bugtraq)
  • Re: Is there any way to start (and later quit) an EXE file.
    ... Since I didn't have VNC.exe to test on, the subroutine ... regain complete control of XP and lose barcode scanner control. ... You can use the Shell function to launch an executable file but you don't ...
    (microsoft.public.excel.misc)