Archive

Posts Tagged ‘remove’

Manually Removing a Windows XP Application

August 30th, 2005

If you found this page, I’m going to assume that you have a problem
with a particular piece of software and you’d like to remove it from
your system. I’m also going to assume you’re familiar with Windows
Explorer, RegEdit, and the dangers of deleting something when you don’t
know what it is. If you don’t know these things, or are in the least
uncomfortable doing something that could seriously mess up your
computer, please don’t attempt to do what you read about here.

The
right way to remove it is to go to the Start Menu, to Control Panel, to
Add or Remove Programs, select “Change or Remove Programs”,
locate the program in the list, and click the “Remove”
button.

Sometimes, though, an application simply refuses to
uninstall when you want it to. In those cases, you will need to remove
it manually. Some people will tell you that it is enough to simply
delete the program’s files from “C:\Program Files” and move
on. In a very small number of cases (maybe 1 in 50) that might be true,
but most programs’ installers make any number of changes, such
as:

  • Create a directory under “C:\Program Files”
    named to match the application and/or its manufacturer, then fill it
    with additional files and subdirectories.
  • Create a directory
    somewhere other than “C:\Program Files” (such as one directly
    under “C:\” and populate that with files and
    subdirectories.
  • Place files and subdirectories under
    “C:\Documents and Settings\All Users” and “C:\Documents
    and Settings\Default User” to ensure that all users of a computer
    can see that the program is available for use, to store temporary data
    files, etc.
  • Place files in “C:\Windows\All Users” to
    make them available to all users.
  • Create or modify one or more
    INI files on the system.
  • Add an entry to the Registry to tell
    the “Add or Remove Programs” control panel where to find the
    application’s uninstaller.
  • Add entries to the Registry to tell
    the Windows Explorer to associate this application with specific kinds
    of files (e.g., “.doc” to Microsoft Word, as well as
    “.rtf”).
  • Add entries to the Registry that store the
    application’s preferences, such as what font you like to use in an
    editor, where you last saved a file, where to place the application’s
    window on the screen, etc.
  • Add DLLs and other files to the
    Windows directory.

The installer might do other things,
depending on what kind of an installer it is. For example, a screen
saver installer might put some “.SCR” files in
“C:\Windows\system32″. A device driver installer might put
items in the System Tray (which it does by creating Registry entries). A
resume package might add templates to Microsoft Word
directories.

Because of all this variation, there’s no single set
of instructions I can give you that will get every file an application
might have installed 100% of the time. However, if you follow the
instructions I provide later in this article, you have a good chance of
being able to remove the bulk of the application. If you want to get rid
of ALL of it, one thing that might work for you is to follow my
instructions, then try reinstalling the application and using its own
uninstaller to remove it. That would theoretically get everything you
missed. (I have to warn you that some applications’ uninstallers don’t
remove everything they installed, either because they’re trying to keep
you from losing data you created yourself, because they’re buggy and
incomplete, or because they are cautious and trying to leave behind
files that other applications from the same manufacturer might be
using.)

Read more…

admin Windows Support , , ,

OS X System Cache Cleaning Script

June 3rd, 2005

As part of its normal operation, OS X creates a number of cache files
that allow it to speed up its operations.  Like any files, these
cache files can become corrupted, fragmented, or otherwise
damaged.  This can cause the system to slow down, crash, or behave
erratically.

To prevent such problems, I developed the following
script to delete the system cache files on the computer each night and
force a reboot to maintain the system’s integrity (since deleting a
cache file the OS is using would be “a bad
thing”).

While I’ve tested this script on Mac OS X 10.3.x and
10.4 and believe that it functions as designed, I can’t promise that it
will work on earlier or later OS X releases and provide no warranty or
support.  As with all my scripts, this one is provided “as
is”.  If you are able to make use of it and derive value from
it, great!  If not, you assume all responsibility and liability for
what happens to your system if you choose to use or modify this
script.

This script can be executed from the command line or via a
cron task.

Read more…

admin Mac Support , , , , , , , , , , , ,

OS X Local Cache Cleaning Script

June 3rd, 2005

As you use your Macintosh, OS X creates a number of cache files in
your home directory under “/Users”.  These cache files
are intended to speed up or otherwise improve system performance. 
However, like any files, they can become damaged or corrupted. 
When this happens, the system will behave erratically and perhaps crash
or lock up.

The script below will automatically delete all the
cache files for all the users on the system and attempt to force the
system to reboot (so that the now-missing cache files don’t cause a
crash).

While I’ve tested this script on several OS X 10.3.x and
10.4 systems and have not suffered any problems as a result of using it,
I provide it “as is” and without any warranty of any
kind.  If you use it and it works well for you, great!  If it
doesn’t work or it causes you any kind of problem or loss, you agree
that you assumed that responsibility and liability when you tried to use
the script.

This script can be run from the command line or as a
cron task.

Read more…

admin Mac Support , , , , , , , , , , , ,

OS X Font Cache Cleaning Script

June 3rd, 2005

As part of its normal operation, Mac OS X creates “font
cache” files that help it to speed up the display of fonts on the
screen.  Unfortunately, as with many types of cache files, OS X
font cache files can become corrupted or damaged.  When this
happens, strange font display problems, application crashes, or system
crashes may occur.  It’s a good idea to periodically delete the
font cache files, which OS X will dutifully rebuild on the next reboot
with clean non-corrupted copies.

Font cache files are stored in
“/System/Library/Caches” in a variety of files with different
names.  Those names all follow specific patterns, so we can easily
build a script to look for files with those names and delete them
automatically.

This script has been tested and to the best of my
knowledge appears to work on OS X 10.3.x and 10.4.  It may or may
not work with earlier or later versions of OS X.  As with all my
scripts, I provide it “as is” without warranty or support of
any kind.  If you choose to try this script, you accept all
responsibility for any damage it does to your computer or
data.

This script can be executed from the command line or a cron
task.

Read more…

admin Mac Support , , , , , , , , , , , , , , , , , , , , , , ,

OS X Internet Cache Cleaning Script

June 3rd, 2005

As you use your Macintosh to browse the web, your web browser begins
storing “cache” files on your computer’s hard disk drive in
order to make browsing faster.  For example, if you were looking at
Ford’s web site, trying to decide what new car to buy, your browser
might cache a copy of the Ford logo on your Mac.  Each time you
look at a new page, instead of asking Ford’s web server for another copy
of the Ford logo, your Mac uses the file in its cache (which it can read
much faster than it can get a new copy from Ford’s server).  This
is generally a good thing.

But like any other cache files, these
Internet cache files can become corrupted.  When this happens, the
web browser may crash, behave strangely, or even refuse to run at
all.  In an attempt to prevent this problem, I took some time to
try to determine where the different Mac web browsers we use store their
cache files.  Then I wrote the script below to automatically clear
out those caches each night.

As with all my scripts, this one was
tested with OS X 10.3.x and 10.4 and the web browsers and versions
we use at my place of employment.  While I believe that this script
works as intended and that it won’t wipe out your hard drive or cause
you some other problem, I can’t warranty that.  If you choose to
use this script on your Macintosh, you assume all liability and
responsibility for what happens to your computer as a result.  If
the script works for you, great!  If not, I’m sorry and I hope you
didn’t lose anything important – but there’s nothing I can do for
you.

This script can be executed from the command line or a cron
task.

Read more…

admin Mac Support , , , , , , , , , , , , ,