|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Moving Novasoft SpamKiller from NT to XP
===Note: It may be illegal to transfer licensed software
=== to a machine not owned by the licensee.
I recently tried to execute an installer (SpamKiller276.exe, which I bought
from Novasoft six years ago) on a new XP machine. The installer would
start, show a blank full-screen "Installer" window for about 5 seconds,
then exit without showing any information at all.
In case someone else may want to do the same thing, here's how I moved
SpamKiller 2.76 from my NT system to my XP system without using the
installer:
Using the old regedit.exe program, I searched the NT4 machine's keys, data,
and values for "spamk". I found all of the matches under the following two
keys:
[HKEY_LOCAL_MACHINE\SOFTWARE\J. River\R2\1.2]
[HKEY_LOCAL_MACHINE\SOFTWARE\Novasoft]
I exported these two keys (including all subkeys) to the Desktop of the XP
machine, where I merged them into the XP machine's registry. I had first
ensured that no "spamk" matches existed in the XP registry.
On the NT machine, I searched all local drives for spamk*.* -- The only
folder found to contain Spamkiller-related files was C:\Program
Files\SpamKiller, which I copied to the XP machine (along with all the
subfolders and files it contained).
I ran ChangeOfAddress (COA) on the XP machine to update all references, but
it found nothing to change. (Although COA wasn't needed in this instance,
I've found it indispensable for re-organizing disk storage-- especially
after forgetting to override an installer's default target folder. See
http://www.pcmag.com/article2/0,1895,9505,00.asp )
Spamkiller 2.76 executed on the XP machine without a problem.
P.S. I went through this process because SpamKiller 2.76 had worked
flawlessly for six years on my NT machine, and I was reluctant to buy the
latest set of problems from McAfee. Like many experienced computer
professionals, I've found that software "upgrades" rarely justify the cost
of dealing with a new collection of bugs, design flaws, resource hogs,
intrusive interface elements, and other problems. Your own experience may
be different, but I like to keep working things working.
-- 2006mar03(17:29)-sls
|
|
|