RegSnap

[Gordon Smith \(eMVP\)]

Has anyone else run into bugs with RegSnap? I downloaded it recently to
handle creating a .reg file for an application that adds about 1033 registry
keys. The html report generated by RegSnap seems perfectly accurate, but
the .reg file created by it doesn't seem to reflect everything in the
report.

Is it bugged or am I?

 

[KM]

Gordon,

I've been using RegSnap v3.1 without problems. The reg files seemed to be
correct (Undo and Redo).
What exactly bugs do you see there?

Also, please keep in mind there is a bug in MS CD about importing .reg
file - loosing spaces in reg key paths. This gets especially hard to fix
when you have got a bunch of reg keys to integrate in to your image.

 

[Landon Cox]

Yes, as a matter of fact I just posted this this morning on another RegSnap
thread earlier. I have 1.4.1 (latest stuff off the lastbit.com site)

This is a repeat of my post of my experience with it:

I bought RegSnap based on this recommendation as it really seemed like
it had what would be needed - a registry diff ability to write out a .reg
file of the differences.

I have found two pretty horrendous bugs with it. One, regardless of my
comparison settings for generating .reg files from the comparison (redo and
undo .reg files) to include keys and values, only keys are generated in the
..reg files. This completely defeats the ability to pull registry diffs out
in any semblance of useful format. It generates HTML reports which are
correct, but obviously not usable for importing/restoral.

Secondly, if I export a RegSnap .rsnp file as a .reg file, many times keys
will have a redundant 'leaf' on the key name that is not there in the
original registry. ie: [HKEY_LOCAL_MACHINE\SOFTWARE\TOC\TOC] when the
origional registry only had: [HKEY_LOCAL_MACHINE\SOFTWARE\TOC]

So, if you were to restore the registry with this .reg file, it would be
completely hosed up.

I've tried contact LastBit software by both email and phone. NO response by
email and their phone seems to be permanently hooked to a FAX.

This software is so close but yet so far. Thought people might like to know
this.

Landon

 

[KM]

Landon,

The latest version of the RegSnap seems to be 4.1.1224. Is it the one you
are referring to?

 

[Landon Cox]

Yes, sorry I transposed my version digits.

My help about box says v4.1 (build 1224)

I downloaded it and bought it from their site yesterday. The trial won't
save so some of these problems can't be seen before purchase.

Landon

 

[Gordon Smith \(eMVP\)]

I guess I should look for an old version somewhere. The new version isn't
quite working correctly. Not all of the keys make it to the .reg file and
few (but some) of the values make it there.

 

[KM]

I've just downloaded and try the 4.1.1224 version (Evaluation). I am not
able to repro the first problems you mentioned - the reg values are in the
Undo and Redo files.

However, the second problem, exporting a .reg file from a snapshot seems to
produce redundant keys.
Anyway.. this feature is not very useful for XPe integration. You will
probably need only snapshot comparison feature.

--
KM,
BSquare Corporation

Landon,

The latest version of the RegSnap seems to be 4.1.1224. Is it the one you
are referring to?

--
KM,
BSquare Corporation

Yes, as a matter of fact I just posted this this morning on another RegSnap
thread earlier. I have 1.4.1 (latest stuff off the lastbit.com site)

This is a repeat of my post of my experience with it:

I bought RegSnap based on this recommendation as it really seemed like
it had what would be needed - a registry diff ability to write out a ..reg
file of the differences.

I have found two pretty horrendous bugs with it. One, regardless of my
comparison settings for generating .reg files from the comparison (redo and
undo .reg files) to include keys and values, only keys are generated in the
.reg files. This completely defeats the ability to pull registry diffs out
in any semblance of useful format. It generates HTML reports which are
correct, but obviously not usable for importing/restoral.

Secondly, if I export a RegSnap .rsnp file as a .reg file, many times keys
will have a redundant 'leaf' on the key name that is not there in the
original registry. ie: [HKEY_LOCAL_MACHINE\SOFTWARE\TOC\TOC] when the
origional registry only had: [HKEY_LOCAL_MACHINE\SOFTWARE\TOC]

So, if you were to restore the registry with this .reg file, it would be
completely hosed up.

I've tried contact LastBit software by both email and phone. NO

response

by
email and their phone seems to be permanently hooked to a FAX.

This software is so close but yet so far. Thought people might like to know
this.

Landon

 

[Gordon Smith \(eMVP\)]

RegSnap is a download-to-evaluate-then-enter-a-licence key product. Would
you happen to have the download-to-evaluate package from 3.1 that you could
make available? 4.1 seems buggy.

Landon,

The latest version of the RegSnap seems to be 4.1.1224. Is it the one
you are referring to?

Yes, as a matter of fact I just posted this this morning on another
RegSnap thread earlier. I have 1.4.1 (latest stuff off the
lastbit.com site)

This is a repeat of my post of my experience with it:

I bought RegSnap based on this recommendation as it really seemed
like
it had what would be needed - a registry diff ability to write out a
.reg file of the differences.

I have found two pretty horrendous bugs with it. One, regardless of
my comparison settings for generating .reg files from the comparison
(redo and undo .reg files) to include keys and values, only keys are
generated in the .reg files. This completely defeats the ability to
pull registry diffs out in any semblance of useful format. It
generates HTML reports which are correct, but obviously not usable
for importing/restoral.

Secondly, if I export a RegSnap .rsnp file as a .reg file, many
times keys will have a redundant 'leaf' on the key name that is not
there in the original registry. ie:
[HKEY_LOCAL_MACHINE\SOFTWARE\TOC\TOC] when the origional registry
only had: [HKEY_LOCAL_MACHINE\SOFTWARE\TOC]

So, if you were to restore the registry with this .reg file, it
would be completely hosed up.

I've tried contact LastBit software by both email and phone. NO
response by email and their phone seems to be permanently hooked to
a FAX.

This software is so close but yet so far. Thought people might like
to know this.

Landon

 

[Gordon Smith \(eMVP\)]

Nevermind - I found it using google. I'll try 3.1 to see if it works
correctly.

RegSnap is a download-to-evaluate-then-enter-a-licence key product.
Would you happen to have the download-to-evaluate package from 3.1
that you could make available? 4.1 seems buggy.

Landon,

The latest version of the RegSnap seems to be 4.1.1224. Is it the one
you are referring to?

Yes, as a matter of fact I just posted this this morning on another
RegSnap thread earlier. I have 1.4.1 (latest stuff off the
lastbit.com site)

This is a repeat of my post of my experience with it:

I bought RegSnap based on this recommendation as it really seemed
like
it had what would be needed - a registry diff ability to write out a
.reg file of the differences.

I have found two pretty horrendous bugs with it. One, regardless of
my comparison settings for generating .reg files from the comparison
(redo and undo .reg files) to include keys and values, only keys are
generated in the .reg files. This completely defeats the ability to
pull registry diffs out in any semblance of useful format. It
generates HTML reports which are correct, but obviously not usable
for importing/restoral.

Secondly, if I export a RegSnap .rsnp file as a .reg file, many
times keys will have a redundant 'leaf' on the key name that is not
there in the original registry. ie:
[HKEY_LOCAL_MACHINE\SOFTWARE\TOC\TOC] when the origional registry
only had: [HKEY_LOCAL_MACHINE\SOFTWARE\TOC]

So, if you were to restore the registry with this .reg file, it
would be completely hosed up.

I've tried contact LastBit software by both email and phone. NO
response by email and their phone seems to be permanently hooked to
a FAX.

This software is so close but yet so far. Thought people might like
to know this.

Landon

 

[Gordon Smith \(eMVP\)]

3.1 works ***MUCH*** better.

My .reg file with 3.1 is 194k.
My .reg file with 4.1 is 35k.

The difference between those was important to me at least.... if not to
RegSnap 4.1. ;-)

--Gordon

Nevermind - I found it using google. I'll try 3.1 to see if it works
correctly.

RegSnap is a download-to-evaluate-then-enter-a-licence key product.
Would you happen to have the download-to-evaluate package from 3.1
that you could make available? 4.1 seems buggy.

Landon,

The latest version of the RegSnap seems to be 4.1.1224. Is it the
one you are referring to?


Yes, as a matter of fact I just posted this this morning on another
RegSnap thread earlier. I have 1.4.1 (latest stuff off the
lastbit.com site)

This is a repeat of my post of my experience with it:

I bought RegSnap based on this recommendation as it really seemed
like
it had what would be needed - a registry diff ability to write out
a .reg file of the differences.

I have found two pretty horrendous bugs with it. One, regardless
of my comparison settings for generating .reg files from the
comparison (redo and undo .reg files) to include keys and values,
only keys are generated in the .reg files. This completely
defeats the ability to pull registry diffs out in any semblance of
useful format. It generates HTML reports which are correct, but
obviously not usable for importing/restoral.

Secondly, if I export a RegSnap .rsnp file as a .reg file, many
times keys will have a redundant 'leaf' on the key name that is not
there in the original registry. ie:
[HKEY_LOCAL_MACHINE\SOFTWARE\TOC\TOC] when the origional registry
only had: [HKEY_LOCAL_MACHINE\SOFTWARE\TOC]

So, if you were to restore the registry with this .reg file, it
would be completely hosed up.

I've tried contact LastBit software by both email and phone. NO
response by email and their phone seems to be permanently hooked to
a FAX.

This software is so close but yet so far. Thought people might
like to know this.

Landon

 

[Landon Cox]

I've just downloaded and try the 4.1.1224 version (Evaluation). I am not

able to repro the first problems you mentioned - the reg values are in the
Undo and Redo files.

Wonder what the difference is. Is it related to type? My test was simple -
I added one key and one DWORD value. The value never showed up in the .reg
redo file, only the key even though I requested both keys and values.

However, the second problem, exporting a .reg file from a snapshot seems to
produce redundant keys.
Anyway.. this feature is not very useful for XPe integration. You will
probably need only snapshot comparison feature.

The only reason I looked at this was to see if any .reg they produced was
getting it right - in this case the value was there but the key was wrong.
There is no winning with this version.

I likewise will try to find 3.1.

Maybe you guys could ping LastBit as well - I've already done it and have
received no response.

Thanks,

Landon

 

[Landon Cox]

Maybe you guys could ping LastBit as well - I've already done it and have

received no response.

As a data point, I just now got a response from LastBit suggesting I
download 4.1 - which of course is the problem. I've responded to them again
with the version I have and issues. We'll see how long it takes to turn
this into a workable version.

 

[KM]

Landon,

I've just performed the same test (adding a value) you did and it worked
just fine with 4.1... version.
The second but is still there. As I don't see the bug on earlier versions
I'd suggest you to get and switch to 3.1. version.

 

[KM]

Gordon,

They seem to have gotten rid of the "Windows NT options" in 4.1 version in
"Save snapshot" dialog. I guess they now make a snapshot in "user mode" only
instead of having an option to grab everything as it was (is) in 3.1.
version.

--
KM,
BSquare Corporation

3.1 works ***MUCH*** better.

My .reg file with 3.1 is 194k.
My .reg file with 4.1 is 35k.

The difference between those was important to me at least.... if not to
RegSnap 4.1. ;-)

--Gordon

Nevermind - I found it using google. I'll try 3.1 to see if it works
correctly.

RegSnap is a download-to-evaluate-then-enter-a-licence key product.
Would you happen to have the download-to-evaluate package from 3.1
that you could make available? 4.1 seems buggy.

KM wrote:
Landon,

The latest version of the RegSnap seems to be 4.1.1224. Is it the
one you are referring to?


Yes, as a matter of fact I just posted this this morning on another
RegSnap thread earlier. I have 1.4.1 (latest stuff off the
lastbit.com site)

This is a repeat of my post of my experience with it:

I bought RegSnap based on this recommendation as it really seemed
like
it had what would be needed - a registry diff ability to write out
a .reg file of the differences.

I have found two pretty horrendous bugs with it. One, regardless
of my comparison settings for generating .reg files from the
comparison (redo and undo .reg files) to include keys and values,
only keys are generated in the .reg files. This completely
defeats the ability to pull registry diffs out in any semblance of
useful format. It generates HTML reports which are correct, but
obviously not usable for importing/restoral.

Secondly, if I export a RegSnap .rsnp file as a .reg file, many
times keys will have a redundant 'leaf' on the key name that is not
there in the original registry. ie:
[HKEY_LOCAL_MACHINE\SOFTWARE\TOC\TOC] when the origional registry
only had: [HKEY_LOCAL_MACHINE\SOFTWARE\TOC]

So, if you were to restore the registry with this .reg file, it
would be completely hosed up.

I've tried contact LastBit software by both email and phone. NO
response by email and their phone seems to be permanently hooked to
a FAX.

This software is so close but yet so far. Thought people might
like to know this.

Landon

 

[Gordon Smith \(eMVP\)]

I got a reply back from them early this morning "We fixed the bug, please
upgrade to v4.2. I'm sorry for the inconvenience."

I haven't tried the newer version yet.

--Gordon

Gordon,

They seem to have gotten rid of the "Windows NT options" in 4.1
version in "Save snapshot" dialog. I guess they now make a snapshot
in "user mode" only instead of having an option to grab everything as
it was (is) in 3.1. version.

3.1 works ***MUCH*** better.

My .reg file with 3.1 is 194k.
My .reg file with 4.1 is 35k.

The difference between those was important to me at least.... if
not to RegSnap 4.1. ;-)

--Gordon

Nevermind - I found it using google. I'll try 3.1 to see if it
works correctly.

Gordon Smith (eMVP) wrote:
RegSnap is a download-to-evaluate-then-enter-a-licence key product.
Would you happen to have the download-to-evaluate package from 3.1
that you could make available? 4.1 seems buggy.

KM wrote:
Landon,

The latest version of the RegSnap seems to be 4.1.1224. Is it the
one you are referring to?


Yes, as a matter of fact I just posted this this morning on
another RegSnap thread earlier. I have 1.4.1 (latest stuff off
the lastbit.com site)

This is a repeat of my post of my experience with it:

I bought RegSnap based on this recommendation as it really seemed
like
it had what would be needed - a registry diff ability to write
out
a .reg file of the differences.

I have found two pretty horrendous bugs with it. One, regardless
of my comparison settings for generating .reg files from the
comparison (redo and undo .reg files) to include keys and values,
only keys are generated in the .reg files. This completely
defeats the ability to pull registry diffs out in any semblance
of useful format. It generates HTML reports which are correct,
but obviously not usable for importing/restoral.

Secondly, if I export a RegSnap .rsnp file as a .reg file, many
times keys will have a redundant 'leaf' on the key name that is
not there in the original registry. ie:
[HKEY_LOCAL_MACHINE\SOFTWARE\TOC\TOC] when the origional registry
only had: [HKEY_LOCAL_MACHINE\SOFTWARE\TOC]

So, if you were to restore the registry with this .reg file, it
would be completely hosed up.

I've tried contact LastBit software by both email and phone. NO
response by email and their phone seems to be permanently hooked
to a FAX.

This software is so close but yet so far. Thought people might
like to know this.

Landon

 

[Landon Cox]

I likewise got the reply and downloaded 4.2. Here are the results of my
testing:

Of the two problems, only one actually got fixed. The .reg file generated
on a registry compare now does contain values when both keys and values is
selected, so that part is good.

The other bug, exporting a .rsnp file to .reg file still unfortunately
contains duplicate leaf nodes on the end of the keyname.

I emailed them back again with this issue that's still outstanding.

Landon

 

[Landon Cox]

I reported to LastBit again that only one of the two bugs was fixed. I got
a mail from them after midnight (2/5) that they had uploaded the wrong
build. "Please download it once more, correct version has version
v4.2.1233".

I downloaded 4.2.1233 and tested it and I can finally say that they have
fixed both major issues that I saw with it: 1) values not making it into
the redo/undo reg files on compare and 2) redundant leaf nodes on key names.

So, give 4.2.1233 a download - I think they finally have it back up to
snuff.

Landon

 

[KM]

Landon,

Great! My guess they have fixed the bugs under your pressure
So, all XPe devs who use RegSnap will appreciate your efforts!