In message <
rh0mj8tg9n0s8hfl0...@4ax.com>, micky
<
NONONO...@bigfoot.com> writes:
>On Fri, 8 Mar 2013 20:40:34 +0000, "J. P. Gilliver (John)"
><
G6...@soft255.demon.co.uk> wrote:
>
>>
>>>I think I could register for a second skype account then compare the
>>>old r egistry with the new one to find what has been added, but I
>>>don't know how to compare the two r egistries without my going line by
>>>line.
>>
>>Which would take you for ever, I suspect (-:!
>
> Well, Norton Utilities came with a DOS utility called FC (file
I remember that old suite - lots of two-letter utilities, though there
was a menuing system that meant you didn't have to remember all the
pairs of letters. Quite good in its time; Norton was, then.
>compare) . It would compare binary files and when it found a byte
>that didnt' match, it would look ahead in each file to see if it
>started matching again. Then it would print out the part that was
>added or deleted (and the default was to not print everything that was
>the same) It worked excellently. I still have my Norton CD's and
>could** install that.
You might not need to. FC is a DOS command itself - I think even back in
'9x days; it's certainly there under XP. Open a command prompt (start,
run, enter "cmd", or find it under accessories), and enter
fc /?
(note the /b option). I imagine you can pipe it to more (
fc file.a file.b | more
) to get a page at a time - you can with most DOS commands.
>
>It or another version of Norton also had a windows program that was
>meant for t ext. It might have been called FileCompare. It did the
>same thing as FC but when it found differences, it formatted what it
>displayed as 80 column text. Good for comparing computer code and
>most text. Maybe it didnt' have to use 80. It too was excellent***.
>
>I guess I lost these when I upgraded my OS.
Unfortunately, I don't think this would be much use for tracking
registry changes anyway. I certainly wouldn't try to do it on the raw
.dat files, as you wouldn't have a clue what the varying strings of hex
mean; and the registry is being changed all the time, so trying to find
just the bits an install changed would be a thankless task. (Not to
mention that exporting the whole thing into text form [.reg files] would
take a Very Long Time [and just trying to select bits of it to text
would probably miss something]).
>
> **This brings up another question. What are the odds that software
>written for win3.1 or win98 will install in XP. I"m not talking
>about hardware for which drivers might be necessary.
It depends very much on the software. Sometimes it installs fine. (I'd
not bother with screensavers - they _are_ hard work.) On the whole, the
easiest thing is to just try! It doesn't _usually_ break anything,
though very occasionally something can, but XP is _reasonably_
self-protective. Note that anything from 3.1 days will use short
filenames (for files _and_ directories), as will a very few '9x things.
(You can usually tell this is going to be the case because the file
window - when you save or load anything in them - is the old one you
will recognise.)
Sometimes, it would run, but the installer won't. If an installer won't
run, you can always _try_ copying over the directory tree from a working
copy on the older system (or the hard disc from the older system if
you've kept it, or an image of it), and try running the main executable;
again, it's pot luck whether it will or won't. On the whole, if it
doesn't rely on registry entries having been made or files having been
put into the windows directory or one of its subdirectories, the chances
are it will run, though sometimes in an unexpected or limited manner
(and you may have to do something unusual, once or every time, to make
it run).
>
>(Although I'm curious, and might want to install old software someday,
>I guess it's too much work this time, especially since Skype will
>probably put the hammer down and make me change my password even where
>the old one works now.)
>
>***Another one of Norton Utilities would read the registry and find
>every instance of what I was loking for. So I didn't have to go along
>finding one at a time, so I had a good idea from the start how many
>hits there were. (If there were 200, I would probably change what I
>searched for.), so I'd know how close I was to being done. I
>suppose they've changed the name of the Registry by now, so a win98
>version won't be able to find it.
There are such things around - (pause) I thought I had one, but I seem
not to (maybe _I_ only have it on my '98 machine!). I did find I had
something called regshot, though, which sounds like it might interest
you:
"Regshot is a small,free and open-source registry compare utility that
allows you to quickly take a snapshot of your registry and then compare
it with a second one - done after doing system changes or installing a
new software product. The changes report can be produced in text or HTML
format and contains a list of all modifications that have taken place
between snapshot1 and snapshot2. In addition, you can also specify
folders (with sub filders) to be scanned for changes as well."
http://regshot.sourceforge.net/ - actual download (I think) on
http://sourceforge.net/projects/regshot/files/regshot/1.9.0/Regshot-1.9.0.7z/download
I'm sure other such utilities are available; this one's only 155k, so
can't be any good (-:
[]
>>YW. HIH.
[]
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf
"Mummy, Mummy, I'm 13 now can I wear a bra?"
"SHUT UP RALPH...."