|
|
Hi:
I have a question about Registry back up and restore that hopefully
someone can give me a reliable answer.
If you do a complete Export of your Registry and save it to your Desktop
and then do an application update that causes problems can you Import it
back and it will do away with all the Registry entries created by the App
update?
I feel the last Java Runtime update caused problems for my computer and
using System Restore and also uninstalling it afterwards did not resolve the
problem. Luckily I had my system backed up on another HD and reverted to it.
However now I before I try another Java update can I do as described above
with a complete Registry Export and Import if I do have problems as
previously. While I feel it was the Java update that caused my problems I am
not totally sure, but I just want to have a Registry back up in case.
Again my main question is if I do a complete Export, install the Java
update and it does cause problems again, can I Import the Registry back and
it will void any Registry entries the update caused?
Thanks
|
|
ColTom2 wrote:
[Quoted Text] > Hi:
>
> I have a question about Registry back up and restore that hopefully
> someone can give me a reliable answer.
>
> If you do a complete Export of your Registry and save it to your Desktop
> and then do an application update that causes problems can you Import it
> back and it will do away with all the Registry entries created by the App
> update?
>
> I feel the last Java Runtime update caused problems for my computer and
> using System Restore and also uninstalling it afterwards did not resolve the
> problem. Luckily I had my system backed up on another HD and reverted to it.
>
> However now I before I try another Java update can I do as described above
> with a complete Registry Export and Import if I do have problems as
> previously. While I feel it was the Java update that caused my problems I am
> not totally sure, but I just want to have a Registry back up in case.
>
> Again my main question is if I do a complete Export, install the Java
> update and it does cause problems again, can I Import the Registry back and
> it will void any Registry entries the update caused?
>
> Thanks
>
>
I will not address most of your questions, but I would suggest you
search for ERUNT to obtain a free and more complete registry backup
program. It is a great program that saved me several times.
|
|
ColTom2 wrote:
[Quoted Text] > I have a question about Registry back up and restore that hopefully
> someone can give me a reliable answer.
>
> If you do a complete Export of your Registry and save it to your
> Desktop and then do an application update that causes problems can
> you Import it back and it will do away with all the Registry
> entries created by the App update?
>
> I feel the last Java Runtime update caused problems for my
> computer and using System Restore and also uninstalling it
> afterwards did not resolve the problem. Luckily I had my system
> backed up on another HD and reverted to it.
>
> However now I before I try another Java update can I do as
> described above with a complete Registry Export and Import if I do
> have problems as previously. While I feel it was the Java update
> that caused my problems I am not totally sure, but I just want to
> have a Registry back up in case.
>
> Again my main question is if I do a complete Export, install the
> Java update and it does cause problems again, can I Import the
> Registry back and it will void any Registry entries the update
> caused?
- ERUNT as someone else already suggested.
- Your issues may not have anything to do with the regitry.
- How are you 'updating' JAVA. My suggestion is to never do the update that
is suggested by the application itself when it comes to JAVA - but to go
into Control Panel --> Add or Remove Programs and remove all previous
versions of JAVA and reboot. Then download the Offline installer (comes
with less baggage lately) and use it to install the latest version (JRE 6
Update 11 I believe.)
--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
|
|
First, system restore includes a copy of your registry. So, if it did not
fix your problem, then I would look outside of the registry for answers.
You already have a full system backup, which a great idea, and so you have
protection against bad installs/uninstalls, etc.
But, I assume that you would like something less drastic, and maybe quicker,
to use on some occasions?
As far as the registry goes, there are a number of programs that can do
backups and restores. Some, like ERUNT, are free. But, that program
requires that XP be installed on a FAT32 partition, since its way of
handling an unbootable PC is to boot from a floppy disk containing DOS. DOS
can not see NTFS partitions. However, one could run it from a bootable CD
based on XP, such as Windows PE or Bart's PE.
Other options can be found at:
http://www.majorgeeks.com/downloads15.html
Just be sure that any you pick have some way to run, in cases XP will not
boot.
"ColTom2" <noemailaddress[ at ]nomail.com> wrote in message
news:eWSgpw2YJHA.1188[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] > Hi:
>
> I have a question about Registry back up and restore that hopefully
> someone can give me a reliable answer.
>
> If you do a complete Export of your Registry and save it to your Desktop
> and then do an application update that causes problems can you Import it
> back and it will do away with all the Registry entries created by the App
> update?
>
> I feel the last Java Runtime update caused problems for my computer and
> using System Restore and also uninstalling it afterwards did not resolve
> the
> problem. Luckily I had my system backed up on another HD and reverted to
> it.
>
> However now I before I try another Java update can I do as described
> above
> with a complete Registry Export and Import if I do have problems as
> previously. While I feel it was the Java update that caused my problems I
> am
> not totally sure, but I just want to have a Registry back up in case.
>
> Again my main question is if I do a complete Export, install the Java
> update and it does cause problems again, can I Import the Registry back
> and
> it will void any Registry entries the update caused?
>
> Thanks
>
>
|
|
*Bonjour Bob Harris * !
<news:#jEpwl3YJHA.2620[ at ]TK2MSFTNGP02.phx.gbl>
[Quoted Text] > First, system restore includes a copy of your registry. So, if it did not
> fix your problem, then I would look outside of the registry for answers.
> You already have a full system backup, which a great idea, and so you have
> protection against bad installs/uninstalls, etc.
> But, I assume that you would like something less drastic, and maybe quicker,
> to use on some occasions?
> As far as the registry goes, there are a number of programs that can do
> backups and restores. Some, like ERUNT, are free. But, that program
> requires that XP be installed on a FAT32 partition, since its way of handling
> an unbootable PC is to boot from a floppy disk containing DOS.
?????????????????????????
Please read erunt.txt ==>
http://www.larshederer.homepage.t-online.de/erunt/erunt.txt
Restoring the registry with ERDNT - Emergency Scenario II
1. Bart's PE Builder
2. The Windows Recovery Console (Windows 2000 and higher)
No need to be FAT32 !!!
--
Regards, Jean-François
|
|
you can export the complete
registry, but you cannot import
the complete registry.
the export and import feature
is best for individual keys or
branches.
--------------
the best method would be to simply
copy your registry hive into a
safe and easily accessible
folder on the root "or" in
the windows system folder.
then if you have to restore
that copy, you would do it
via the windows cd
repair/recovery console.
system restore would be
a better and easier option,
as it can be executed via
safemode in the event
normal mode becomes
corrupted or unstable.
--
db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces
"ColTom2" <noemailaddress[ at ]nomail.com> wrote in message news:eWSgpw2YJHA.1188[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] > Hi:
>
> I have a question about Registry back up and restore that hopefully
> someone can give me a reliable answer.
>
> If you do a complete Export of your Registry and save it to your Desktop
> and then do an application update that causes problems can you Import it
> back and it will do away with all the Registry entries created by the App
> update?
>
> I feel the last Java Runtime update caused problems for my computer and
> using System Restore and also uninstalling it afterwards did not resolve the
> problem. Luckily I had my system backed up on another HD and reverted to it.
>
> However now I before I try another Java update can I do as described above
> with a complete Registry Export and Import if I do have problems as
> previously. While I feel it was the Java update that caused my problems I am
> not totally sure, but I just want to have a Registry back up in case.
>
> Again my main question is if I do a complete Export, install the Java
> update and it does cause problems again, can I Import the Registry back and
> it will void any Registry entries the update caused?
>
> Thanks
>
>
|
|
<snipped>
<entire conversation>
http://groups.google.com/group/microsoft.public.windowsxp.basics/browse_frm/thread/d82cd25c5e5cb58f/c021d9dde8b2b3c8#c021d9dde8b2b3c8
<end entire conversation>
JF wrote:
<quote from Bob Harris>
[Quoted Text] >> As far as the registry goes, there are a number of programs that
>> can do backups and restores. Some, like ERUNT, are free. But,
>> that program requires that XP be installed on a FAT32 partition,
>> since its way of handling an unbootable PC is to boot from a
>> floppy disk containing DOS.
<end quote from Bob Harris>
>
> ?????????????????????????
> Please read erunt.txt ==>
> http://www.larshederer.homepage.t-online.de/erunt/erunt.txt
> Restoring the registry with ERDNT - Emergency Scenario II
> 1. Bart's PE Builder
> 2. The Windows Recovery Console (Windows 2000 and higher)
>
> No need to be FAT32 !!!
Please read the entire message that you responded to... ;-)
The sentence you conveniently cut off the paragraph you quoted to make your
point...
"However, one could run it from a bootable CD based on XP, such as Windows
PE or Bart's PE."
So - your quote to respond to could (some would argue 'should') have been:
Bob Harris wrote:
> As far as the registry goes, there are a number of programs that
> can do backups and restores. Some, like ERUNT, are free. But,
> that program requires that XP be installed on a FAT32 partition,
> since its way of handling an unbootable PC is to boot from a floppy
> disk containing DOS. DOS can not see NTFS partitions. However,
> one could run it from a bootable CD based on XP, such as Windows PE
> or Bart's PE.
Given the last sentence of the paragraph (conveniently removed from your
response) would have asserted what you re-asserted in your response.
Redundancy is good, snipping the parts of the previous post that make your
response redundant and claiming the original response (or more directly, the
original responder) was mis-informed - bad form...?
--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
|
|
ColTom2-
I use ERUNT to run automatic daily registry backups.
http://www.larshederer.homepage.t-online.de/erunt/
According to the "README":
Note: The "Export registry" function in Regedit is USELESS (!) for
making a complete backup of the registry. Neither does it export the
whole registry (for example, no information from the "SECURITY" hive
is saved), nor can the exported file be used later to replace the
current registry with the old one. Instead, if you re-import the file,
it is merged with the current registry without deleting anything that
has been added since the export, leaving you with an absolute mess of
old and new entries.
*As far as the program "requiring XP to be installed on FAT32" it goes on to say:
Supported operating systems
---------------------------
- Windows NT 3.51
- Windows NT 4.0
- Windows 2000
- Windows 2003
- Windows XP
- most likely, all future Windows versions based on the NT kernel
(So I don't know where Bob came up with that "requirement"-It's called
ERU*NT*-Emergency Recovery Utility NT)
I even did a restore via Safe Mode w/command prompt when Windows wouldn't
successfully boot, by entering C:/Windows/ERDNT.EXE (if I remember correctly) & I was
able to boot from then on with no problems.I had deleted a key from the ROOT that I
thought had belonged to an uninstalled program,& I was in a panic!
To get it to do a daily AuotBackup & remove the previous days backup just go to
Start/All Programs/Startup & right click on ERUNT AutoBackup & in the Target add a
space at the end then "/days:1".(without the quotes)
It should look like this then: "C:\Program Files\ERUNT\AUTOBACK.EXE"
%SystemRoot%\ERDNT\AutoBackup\#Date# /noconfirmdelete /noprogresswindow /days:1
You should also create a manual backup when you first install it & allow it to create
the ERDNT folder in Windows. Then you can create a manual backup whenever you want &
they will always be there. It only takes a few seconds & then it's done.
~Gary
"Bob Harris" <rharris270[SPAM][ at ]hotmail.com> wrote in message
news:%23jEpwl3YJHA.2620[ at ]TK2MSFTNGP02.phx.gbl...
[Quoted Text] > First, system restore includes a copy of your registry. So, if it did not fix your > problem, then I would look outside of the registry for answers. > > You already have a full system backup, which a great idea, and so you have > protection against bad installs/uninstalls, etc. > > But, I assume that you would like something less drastic, and maybe quicker, to use > on some occasions? > > As far as the registry goes, there are a number of programs that can do backups and > restores. Some, like ERUNT, are free. But, that program requires that XP be > installed on a FAT32 partition, since its way of handling an unbootable PC is to > boot from a floppy disk containing DOS. DOS can not see NTFS partitions. However, > one could run it from a bootable CD based on XP, such as Windows PE or Bart's PE. > > Other options can be found at: > > http://www.majorgeeks.com/downloads15.html> > Just be sure that any you pick have some way to run, in cases XP will not boot. > > "ColTom2" <noemailaddress[ at ]nomail.com> wrote in message > news:eWSgpw2YJHA.1188[ at ]TK2MSFTNGP05.phx.gbl... >> Hi: >> >> I have a question about Registry back up and restore that hopefully >> someone can give me a reliable answer. >> >> If you do a complete Export of your Registry and save it to your Desktop >> and then do an application update that causes problems can you Import it >> back and it will do away with all the Registry entries created by the App >> update? >> >> I feel the last Java Runtime update caused problems for my computer and >> using System Restore and also uninstalling it afterwards did not resolve the >> problem. Luckily I had my system backed up on another HD and reverted to it. >> >> However now I before I try another Java update can I do as described above >> with a complete Registry Export and Import if I do have problems as >> previously. While I feel it was the Java update that caused my problems I am >> not totally sure, but I just want to have a Registry back up in case. >> >> Again my main question is if I do a complete Export, install the Java >> update and it does cause problems again, can I Import the Registry back and >> it will void any Registry entries the update caused? >> >> Thanks >> >> > >
|
|
|
[Quoted Text] > Hi:
>
> I have a question about Registry back up and restore that hopefully
> someone can give me a reliable answer.
>
> If you do a complete Export of your Registry and save it to your
> Desktop and then do an application update that causes problems can
> you Import it back and it will do away with all the Registry entries
> created by the App update?
If you mean by using Regedit, no, you cannot. Well, you could, but do
not do it<g>. The Import will simply add the exported settings to waht
you already have and everything will be doubled, or worse.
Usual Ways to back up the Registry:
-- Create a Restore Point.
-- Use ntBackup.exe to save the System State. This also backs up
additional files needed at boot time and is the most complete method.
-- Use a 3rd party app. Personally I avoid them when I can if XP
already has a way of doing the same thing already, which it does. Ymmv
of course.
-- As part of a complete OS backup.
>
> I feel the last Java Runtime update caused problems for my computer
> and using System Restore and also uninstalling it afterwards did not
> resolve the problem. Luckily I had my system backed up on another HD
> and reverted to it.
>
> However now I before I try another Java update can I do as described
> above with a complete Registry Export and Import if I do have
> problems as previously. While I feel it was the Java update that
> caused my problems I am not totally sure, but I just want to have a
> Registry back up in case.
No, do not do that. Regedit was not intended for that purpose and you
could end up with a mess.
See the usual ways to create a backup above and use one of those
instead. Creating Restore Points is quick & simple, usually works,
saving the System State is more thorough and is always going to work
when you Restore it.
>
> Again my main question is if I do a complete Export, install the Java
> update and it does cause problems again, can I Import the Registry
> back and it will void any Registry entries the update caused?
No. See the preceding comments.
You know, I don't really see the tie-in to the registry having a problem
here. Are you getting error messages or what? I'm wondering why you
are concerned with the registry to rephrase the question so many times.
It's entirely possible the reigstry isn't part of whatever problem you
think you have?
Perhaps a further clarification of the issues at hand might be a good
idea.
HTH
Twayne
>
> Thanks
|
|
Twayne wrote:
[Quoted Text] >>Hi:
>>
>> I have a question about Registry back up and restore that hopefully
>>someone can give me a reliable answer.
>>
>> If you do a complete Export of your Registry and save it to your
>>Desktop and then do an application update that causes problems can
>>you Import it back and it will do away with all the Registry entries
>>created by the App update?
>
>
> If you mean by using Regedit, no, you cannot. Well, you could, but do
> not do it<g>. The Import will simply add the exported settings to waht
> you already have and everything will be doubled, or worse.
Importing or merging files to the registry does not create duplicate
registry entries. Importing into the registry will not double
everything, what you are claiming is absolutely impossible to do. You
should refrain from giving "advice" about things that you obviously know
nothing of.
John
|
|
John John (MVP) wrote:
[Quoted Text] > Twayne wrote:
>>> Hi:
>>>
>>> I have a question about Registry back up and restore that hopefully
>>> someone can give me a reliable answer.
>>>
>>> If you do a complete Export of your Registry and save it to your
>>> Desktop and then do an application update that causes problems can
>>> you Import it back and it will do away with all the Registry entries
>>> created by the App update?
>>
>>
>> If you mean by using Regedit, no, you cannot. Well, you could, but do
>> not do it<g>. The Import will simply add the exported settings to waht
>> you already have and everything will be doubled, or worse.
>
> Importing or merging files to the registry does not create duplicate
> registry entries. Importing into the registry will not double
> everything, what you are claiming is absolutely impossible to do. You
> should refrain from giving "advice" about things that you obviously know
> nothing of.
>
> John
Right. Actually, importing a registry ".reg" file MERGES its contents with
what is in the registry already. It does not "double or duplicate"
entries, or any other such nonsense.
|
|
Didn't you read the post? He/she asked for a reliable answer.
"Twayne" <nobody[ at ]devnull.spamcop.net> wrote in message
news:Oc%23nOd%23YJHA.1528[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] >> Hi:
>>
>> I have a question about Registry back up and restore that hopefully
>> someone can give me a reliable answer.
>>
>> If you do a complete Export of your Registry and save it to your
>> Desktop and then do an application update that causes problems can
>> you Import it back and it will do away with all the Registry entries
>> created by the App update?
>
> If you mean by using Regedit, no, you cannot. Well, you could, but do not
> do it<g>. The Import will simply add the exported settings to waht you
> already have and everything will be doubled, or worse.
>
> Usual Ways to back up the Registry:
> -- Create a Restore Point.
> -- Use ntBackup.exe to save the System State. This also backs up
> additional files needed at boot time and is the most complete method.
> -- Use a 3rd party app. Personally I avoid them when I can if XP already
> has a way of doing the same thing already, which it does. Ymmv of course.
> -- As part of a complete OS backup.
>
>>
>> I feel the last Java Runtime update caused problems for my computer
>> and using System Restore and also uninstalling it afterwards did not
>> resolve the problem. Luckily I had my system backed up on another HD
>> and reverted to it.
>>
>> However now I before I try another Java update can I do as described
>> above with a complete Registry Export and Import if I do have
>> problems as previously. While I feel it was the Java update that
>> caused my problems I am not totally sure, but I just want to have a
>> Registry back up in case.
>
> No, do not do that. Regedit was not intended for that purpose and you
> could end up with a mess.
> See the usual ways to create a backup above and use one of those instead.
> Creating Restore Points is quick & simple, usually works, saving the
> System State is more thorough and is always going to work when you Restore
> it.
>>
>> Again my main question is if I do a complete Export, install the Java
>> update and it does cause problems again, can I Import the Registry
>> back and it will void any Registry entries the update caused?
>
> No. See the preceding comments.
>
> You know, I don't really see the tie-in to the registry having a problem
> here. Are you getting error messages or what? I'm wondering why you are
> concerned with the registry to rephrase the question so many times. It's
> entirely possible the reigstry isn't part of whatever problem you think
> you have?
>
> Perhaps a further clarification of the issues at hand might be a good
> idea.
>
> HTH
>
> Twayne
>
>>
>> Thanks
>
>
>
|
|
The date and time was Sunday, December 21, 2008 6:25:38 AM, and on a
whim, Shenan Stanley pounded out on the keyboard:
[Quoted Text] > ColTom2 wrote:
>> I have a question about Registry back up and restore that hopefully
>> someone can give me a reliable answer.
>>
>> If you do a complete Export of your Registry and save it to your
>> Desktop and then do an application update that causes problems can
>> you Import it back and it will do away with all the Registry
>> entries created by the App update?
>>
>> I feel the last Java Runtime update caused problems for my
>> computer and using System Restore and also uninstalling it
>> afterwards did not resolve the problem. Luckily I had my system
>> backed up on another HD and reverted to it.
>>
>> However now I before I try another Java update can I do as
>> described above with a complete Registry Export and Import if I do
>> have problems as previously. While I feel it was the Java update
>> that caused my problems I am not totally sure, but I just want to
>> have a Registry back up in case.
>>
>> Again my main question is if I do a complete Export, install the
>> Java update and it does cause problems again, can I Import the
>> Registry back and it will void any Registry entries the update
>> caused?
>
> - ERUNT as someone else already suggested.
>
> - Your issues may not have anything to do with the regitry.
>
> - How are you 'updating' JAVA. My suggestion is to never do the update that
> is suggested by the application itself when it comes to JAVA - but to go
> into Control Panel --> Add or Remove Programs and remove all previous
> versions of JAVA and reboot. Then download the Offline installer (comes
> with less baggage lately) and use it to install the latest version (JRE 6
> Update 11 I believe.)
>
Word of caution here. Some programs use a particular build of Java and
may not work if the version the program was written for is removed.
Three weeks ago I removed Java version 5.11 from a server and installed
6.11. Blackberry Professional would no longer work. Go figure.
And finally with version 6.11, Java will remove prior versions after
6.10. Earlier versions will still have to be removed manually.
--
Terry R.
***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.
|
|
|
[Quoted Text] > Twayne wrote:
>>> Hi:
>>>
>>> I have a question about Registry back up and restore that hopefully
>>> someone can give me a reliable answer.
>>>
>>> If you do a complete Export of your Registry and save it to your
>>> Desktop and then do an application update that causes problems can
>>> you Import it back and it will do away with all the Registry entries
>>> created by the App update?
>>
>>
>> If you mean by using Regedit, no, you cannot. Well, you could, but
>> do not do it<g>. The Import will simply add the exported settings
>> to waht you already have and everything will be doubled, or worse.
>
> Importing or merging files to the registry does not create duplicate
> registry entries. Importing into the registry will not double
> everything, what you are claiming is absolutely impossible to do. You
> should refrain from giving "advice" about things that you obviously
> know nothing of.
>
> John
Give it a try; I have it right here next to me on a sandbox machine.
Full of duplicates. It does not merge properly.
|
|
"Twayne" <nobody[ at ]devnull.spamcop.net> wrote:
[Quoted Text] >> Twayne wrote:
>>>> Hi:
>>>>
>>>> I have a question about Registry back up and restore that hopefully
>>>> someone can give me a reliable answer.
>>>>
>>>> If you do a complete Export of your Registry and save it to your
>>>> Desktop and then do an application update that causes problems can
>>>> you Import it back and it will do away with all the Registry entries
>>>> created by the App update?
>>>
>>>
>>> If you mean by using Regedit, no, you cannot. Well, you could, but
>>> do not do it<g>. The Import will simply add the exported settings
>>> to waht you already have and everything will be doubled, or worse.
>>
>> Importing or merging files to the registry does not create duplicate
>> registry entries. Importing into the registry will not double
>> everything, what you are claiming is absolutely impossible to do. You
>> should refrain from giving "advice" about things that you obviously
>> know nothing of.
>>
>> John
>
>Give it a try; I have it right here next to me on a sandbox machine.
>Full of duplicates. It does not merge properly.
That's because you've fouled up your machine by constantly using a
registry cleaner, doofus.
|
|
Twayne wrote:
[Quoted Text] >>Twayne wrote:
>>
>>>>Hi:
>>>>
>>>>I have a question about Registry back up and restore that hopefully
>>>>someone can give me a reliable answer.
>>>>
>>>>If you do a complete Export of your Registry and save it to your
>>>>Desktop and then do an application update that causes problems can
>>>>you Import it back and it will do away with all the Registry entries
>>>>created by the App update?
>>>
>>>
>>>If you mean by using Regedit, no, you cannot. Well, you could, but
>>>do not do it<g>. The Import will simply add the exported settings
>>>to waht you already have and everything will be doubled, or worse.
>>
>>Importing or merging files to the registry does not create duplicate
>>registry entries. Importing into the registry will not double
>>everything, what you are claiming is absolutely impossible to do. You
>>should refrain from giving "advice" about things that you obviously
>>know nothing of.
>>
>>John
>
>
> Give it a try; I have it right here next to me on a sandbox machine.
> Full of duplicates. It does not merge properly.
There cannot be duplicate entries in the registry! It is an *absolute
impossibility*! What you are saying is just plain impossible to do, why
you insist on spreading this lie is rather baffling to say the least!
There cannot be duplicate Subtrees (Root keys) in the registry!
There cannot be duplicate Keys in a Subtree!
There cannot be duplicate Subkeys in a Key!
There cannot be duplicate values in a Key or Subkey!
You cannot export the whole registry and then try to re-import or merge
it back, it will throw an error, but it will not create duplicate entries.
John
|
|
"ColTom2" <noemailaddress[ at ]nomail.com> wrote in message
news:eWSgpw2YJHA.1188[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] > Hi:
>
> I have a question about Registry back up and restore that hopefully
> someone can give me a reliable answer.
>
> If you do a complete Export of your Registry and save it to your Desktop
> and then do an application update that causes problems can you Import it
> back and it will do away with all the Registry entries created by the App
> update?
>
> I feel the last Java Runtime update caused problems for my computer and
> using System Restore and also uninstalling it afterwards did not resolve
> the
> problem. Luckily I had my system backed up on another HD and reverted to
> it.
>
> However now I before I try another Java update can I do as described
> above
> with a complete Registry Export and Import if I do have problems as
> previously. While I feel it was the Java update that caused my problems I
> am
> not totally sure, but I just want to have a Registry back up in case.
>
> Again my main question is if I do a complete Export, install the Java
> update and it does cause problems again, can I Import the Registry back
> and
> it will void any Registry entries the update caused?
>
> Thanks
>
>
Backup system state would get the job done. This is a function of ntbackup.
Jim
|
|
John John (MVP) wrote:
[Quoted Text] > Twayne wrote:
>
>>> Twayne wrote:
>>>
>>>>> Hi:
>>>>>
>>>>> I have a question about Registry back up and restore that hopefully
>>>>> someone can give me a reliable answer.
>>>>>
>>>>> If you do a complete Export of your Registry and save it to your
>>>>> Desktop and then do an application update that causes problems can
>>>>> you Import it back and it will do away with all the Registry entries
>>>>> created by the App update?
>>>>
>>>>
>>>> If you mean by using Regedit, no, you cannot. Well, you could, but
>>>> do not do it<g>. The Import will simply add the exported settings
>>>> to waht you already have and everything will be doubled, or worse.
>>>
>>> Importing or merging files to the registry does not create duplicate
>>> registry entries. Importing into the registry will not double
>>> everything, what you are claiming is absolutely impossible to do. You
>>> should refrain from giving "advice" about things that you obviously
>>> know nothing of.
>>>
>>> John
>>
>>
>> Give it a try; I have it right here next to me on a sandbox machine.
>> Full of duplicates. It does not merge properly.
>
> There cannot be duplicate entries in the registry! It is an *absolute
> impossibility*! What you are saying is just plain impossible to do, why
> you insist on spreading this lie is rather baffling to say the least!
Because he doesn't really understand it? It's not really that "amazing".
> There cannot be duplicate Subtrees (Root keys) in the registry!
> There cannot be duplicate Keys in a Subtree!
> There cannot be duplicate Subkeys in a Key!
> There cannot be duplicate values in a Key or Subkey!
>
> You cannot export the whole registry and then try to re-import or merge
> it back, it will throw an error, but it will not create duplicate entries.
>
> John
Exactly.
|
|
|
[Quoted Text] > John John (MVP) wrote:
>> Twayne wrote:
>>
>>>> Twayne wrote:
>>>>
>>>>>> Hi:
>>>>>>
>>>>>> I have a question about Registry back up and restore that
>>>>>> hopefully someone can give me a reliable answer.
>>>>>>
>>>>>> If you do a complete Export of your Registry and save it to your
>>>>>> Desktop and then do an application update that causes problems
>>>>>> can you Import it back and it will do away with all the Registry
>>>>>> entries created by the App update?
>>>>>
>>>>>
>>>>> If you mean by using Regedit, no, you cannot. Well, you could,
>>>>> but do not do it<g>. The Import will simply add the exported
>>>>> settings to waht you already have and everything will be doubled,
>>>>> or worse.
>>>>
>>>> Importing or merging files to the registry does not create
>>>> duplicate registry entries. Importing into the registry will not
>>>> double everything, what you are claiming is absolutely impossible
>>>> to do. You should refrain from giving "advice" about things that
>>>> you obviously know nothing of.
>>>>
>>>> John
>>>
>>>
>>> Give it a try; I have it right here next to me on a sandbox machine.
>>> Full of duplicates. It does not merge properly.
>>
>> There cannot be duplicate entries in the registry! It is an
>> *absolute impossibility*! What you are saying is just plain
>> impossible to do, why you insist on spreading this lie is rather
>> baffling to say the least!
>
> Because he doesn't really understand it? It's not really that
> "amazing".
>> There cannot be duplicate Subtrees (Root keys) in the registry!
>> There cannot be duplicate Keys in a Subtree!
>> There cannot be duplicate Subkeys in a Key!
>> There cannot be duplicate values in a Key or Subkey!
>>
>> You cannot export the whole registry and then try to re-import or
>> merge it back, it will throw an error, but it will not create
>> duplicate entries.
Question: Have you tried it? Go ahead and try it. It can indeed be
accomplished.
Twayne
>>
>> John
>
> Exactly.
|
|
ColTom2 wrote:
[Quoted Text] > If you do a complete Export of your Registry and save it to your
> Desktop and then do an application update that causes problems can
> you Import it back and it will do away with all the Registry
> entries created by the App update?
<snipped>
> Again my main question is if I do a complete Export, install the
> Java update and it does cause problems again, can I Import the
> Registry back and it will void any Registry entries the update
> caused?
Twayne wrote:
> If you mean by using Regedit, no, you cannot. Well, you could, but
> do not do it<g>. The Import will simply add the exported settings
> to [what] you already have and everything will be doubled, or worse.
<snipped>
John John (MVP) wrote:
> Importing or merging files to the registry does not create duplicate
> registry entries. Importing into the registry will not double
> everything, what you are claiming is absolutely impossible to do. You
> should refrain from giving "advice" about things that you
> obviously know nothing of.
Twayne wrote:
> Give it a try; I have it right here next to me on a sandbox machine.
> Full of duplicates. It does not merge properly.
John John (MVP) wrote:
> There cannot be duplicate entries in the registry! It is an
> *absolute impossibility*! What you are saying is just plain
> impossible to do, why you insist on spreading this lie is rather
> baffling to say the least!
> There cannot be duplicate Subtrees (Root keys) in the registry!
> There cannot be duplicate Keys in a Subtree!
> There cannot be duplicate Subkeys in a Key!
> There cannot be duplicate values in a Key or Subkey!
>
> You cannot export the whole registry and then try to re-import or
> merge it back, it will throw an error, but it will not create
> duplicate entries.
Bill in Co. wrote:
> Because he doesn't really understand it? It's not really that
> "amazing".
<in reference to the "There cannot be duplicate" listing>
> Exactly.
Twayne wrote:
> Question: Have you tried it? Go ahead and try it. It can indeed
> be accomplished.
Okay. I'll try anything on a computer once - particularly my virtual
machines.
Let's just do a simplistic test.
I used RegEdt32 (habit) to create the following registry values:
HKEY_LOCAL_MACHINE\SOFTWARE\Twayne\Test
"TestEntryOne" (String) = "TestValue1"
"TestEntryTwo" (DWORD) = 1
I exported said values into a Registry Export file:
<copy below this line>
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Twayne\Test]
"TestEntryOne"="TestValue1"
"TestEntryTwo"=dword:00000001
<copy above this line>
Called that file "TwayneTest.reg".
I then double-clicked on said file. The "Registry Editor" window appeared
and asked, "Are you sure you want to add the information in
C:\TwayneTest.reg" to the registry?" [Yes] [No].
I chose [Yes] and the new "Registry Editor" window appeared telling me,
"Information in C:\TwayneTest.reg has been successfully entered into the
registry.".
So I checked. Yep - there it was. The same entries - still in there just
once. Perhaps I needed to refresh... So I pressed F5 with the root of the
registry selected. No change. So I closed the registry editor and
re-opened to check. Still only the single entries. So I closed it and
merged again and rebooted for good measure. When I logged back in and
checked - still only the single entries.
I am unsure how far to go - but I decided to make the "TEST" key so only
"SYSTEM" had permissions to change it. I selected it, EDIT --> PERMISSIONS,
Advanced -> Unchecked the inheritance and copied the current permissions to
it. I then removed everything but "SYSTEM" from those who have permissions
to do anything to it. Not surprisingly, the String and DWORD values
'disappeared' from view instantly ("TestEntryOne" and TestEntryTwo".)
Replacing the owner I did not do.
So I tried to import again... This time I received a new message when I
told it I was sure I wanted to merge. That message was in a "Registry
Editor" error window and said, "Cannot import C:\TwayneTest.reg: Not all
data was successfully written to the registry. Some keys are open by the
system or other processes."
So I thought... Maybe it's because I still have the RegEdt32 window open.
Closed it.
Tried the import again...
Nope - same error.
Okay - rebooted.
Tried the import again.
Same error.
Checking each time - the values were still 'hidden' from my view (I did not
have perms to them after all) and no duplicates had appeared elsewhere.
I added my perms back. I tried the import again.
It imported successfully now that I had permissions to it. But no duplicate
values of any sort.
Now - all I can figure is that you are doing some much larger export/import?
Although I cannot fathom how that would make any difference. This
small-scale test shows that existing values - well - they exist and cannot
be duplicated.
It's like a file system directory structure (because that is what it is.)
If I have C:\Documents and Settings\Shenan\ --> I can have that path *once*.
If the file "test.txt" exists in that directory (C:\Documents and
Settings\Shenan\test.txt) and I try to create a file with the same name and
extension there - it will tell me I cannot.
Can you explain more fully what test would replicate what you are claiming?
Oh - in case it matters - this was all done on a fully updated Windows XP
Professional machine - SP3, IE7, etc.
--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
|
|
Twayne wrote:
[Quoted Text] >>John John (MVP) wrote:
>>
>>>Twayne wrote:
>>>
>>>
>>>>>Twayne wrote:
>>>>>
>>>>>
>>>>>>>Hi:
>>>>>>>
>>>>>>>I have a question about Registry back up and restore that
>>>>>>>hopefully someone can give me a reliable answer.
>>>>>>>
>>>>>>>If you do a complete Export of your Registry and save it to your
>>>>>>>Desktop and then do an application update that causes problems
>>>>>>>can you Import it back and it will do away with all the Registry
>>>>>>>entries created by the App update?
>>>>>>
>>>>>>
>>>>>>If you mean by using Regedit, no, you cannot. Well, you could,
>>>>>>but do not do it<g>. The Import will simply add the exported
>>>>>>settings to waht you already have and everything will be doubled,
>>>>>>or worse.
>>>>>
>>>>>Importing or merging files to the registry does not create
>>>>>duplicate registry entries. Importing into the registry will not
>>>>>double everything, what you are claiming is absolutely impossible
>>>>>to do. You should refrain from giving "advice" about things that
>>>>>you obviously know nothing of.
>>>>>
>>>>>John
>>>>
>>>>
>>>>Give it a try; I have it right here next to me on a sandbox machine.
>>>>Full of duplicates. It does not merge properly.
>>>
>>>There cannot be duplicate entries in the registry! It is an
>>>*absolute impossibility*! What you are saying is just plain
>>>impossible to do, why you insist on spreading this lie is rather
>>>baffling to say the least!
>>
>>Because he doesn't really understand it? It's not really that
>>"amazing".
>>
>>>There cannot be duplicate Subtrees (Root keys) in the registry!
>>>There cannot be duplicate Keys in a Subtree!
>>>There cannot be duplicate Subkeys in a Key!
>>>There cannot be duplicate values in a Key or Subkey!
>>>
>>>You cannot export the whole registry and then try to re-import or
>>>merge it back, it will throw an error, but it will not create
>>>duplicate entries.
>
>
> Question: Have you tried it? Go ahead and try it. It can indeed be
> accomplished.
Yes I have, just now again, and many times before! I have exported the
*whole* registry, *whole% hives or just select keys/subkeys and I have
then attempted to import them back into the registry. The attempted
imports had various results, either the operation failed completely
(trying to import the whole registry) or it succeeded but with errors
(when importing whole hives it imported some keys but could not import
them all) or the operation was completely successful. In all cases
there were no duplicate entries created, there were none because what
you say is not true, it is impossible to created duplicate entries in
the registry!
I have just now tested this on Windows XP and on Windows 2000 and on
both machines the results were the same. I had no qualms doing this on
production (home) machines because I have backups and I know all too
well that there can be no harm in importing identical entries in the
registry, it changes nothing in the registry. I also know that due to
the ACID nature of the registry when imports fail it will not allow the
creation of meaningless entries in the registry. In my 12+ years of
using NT operating systems I have exported/imported and merged files to
the registry countless times and I have *never* seen duplicate entries
in the registry, what you are saying is pure and simply bunk!
Anyone can easily and fairly safely test this by doing the following:
1- Create a Restore Point.
2- Create a new dummy test user account.
3- Log on to the new user account to allow the system to create the
user's profile hive. Log off to ensure that the profile hive is
properly created and stored.
4- Log back on to the new user account and use the registry editor and
export the whole HKEY_CURRENT_USER subtree, and then (while still logged
on as the same new user!) try to import or merge the exported HKCU file
back to the registry and observe the results.
As mentioned by Shenan in his post, this is akin to creating duplicate
paths or folders/files with duplicate names in the same path, it is
impossible to do! In the case of Windows Explorer, by default it will
simply assign a new, slightly different name to the file system object
(FileName (2), FileName (3)...). Other utilities may use different
methods such as adding or appending to the object name (Copy of
ObjectName, Copy2 of ObjectName...). Native Windows registry utilities
do not use these methods to rename registry entries, for starters those
newly renamed entries would be completely meaningless and useless, they
would serve absolutely no purpose. Adding or merging an entry to the
registry is an all or nothing proposition, either it works or it fails,
there is no in between and on failure the registry tools do not create
duplicate entries!
So that brings us to your claims that importing files into *your*
registry leaves it "Full of duplicates"! If this is happening then we
can only surmise or offer possibilities such as:
1- Your Windows installation is completely borked, probably brought
about by the indiscriminate use of worthless registry cleaners!
2- Your machine has a severe virus infection.
3- You are using a useless third party registry utility to import or
merge the files to the registry and the utility is using a renaming
scheme as described above to rename entries.
If, as you claim, your registry is "Full of duplicates" could you give
use the full details of some those duplicate entries? What are the
names of these duplicates?
John
|
|
Hi Shenan Stanley,
[Quoted Text] > ColTom2 wrote:
>> If you do a complete Export of your Registry and save it to your
>> Desktop and then do an application update that causes problems can
>> you Import it back and it will do away with all the Registry
>> entries created by the App update?
> <snipped>
>> Again my main question is if I do a complete Export, install the
>> Java update and it does cause problems again, can I Import the
>> Registry back and it will void any Registry entries the update
>> caused?
>
....
>
> Twayne wrote:
>> Question: Have you tried it? Go ahead and try it. It can indeed
>> be accomplished.
>
> Okay. I'll try anything on a computer once - particularly my virtual
> machines.
> Let's just do a simplistic test.
>
> I used RegEdt32 (habit) to create the following registry values:
I don't think it matters whether it's redegit32 or regedit. IIRC I read
somewhere that regedit32 is actually a front end to start regedit.
Something I've never looked into though. Point is, you end up with the
same app running, I think.
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Twayne\Test
> "TestEntryOne" (String) = "TestValue1"
> "TestEntryTwo" (DWORD) = 1
>
> I exported said values into a Registry Export file:
>
> <copy below this line>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Twayne\Test]
> "TestEntryOne"="TestValue1"
> "TestEntryTwo"=dword:00000001
> <copy above this line>
>
> Called that file "TwayneTest.reg".
>
> I then double-clicked on said file. The "Registry Editor" window
> appeared and asked, "Are you sure you want to add the information in
> C:\TwayneTest.reg" to the registry?" [Yes] [No].
>
....
> It imported successfully now that I had permissions to it. But no
> duplicate values of any sort.
>
> Now - all I can figure is that you are doing some much larger
> export/import? Although I cannot fathom how that would make any
> difference. This small-scale test shows that existing values - well
> - they exist and cannot be duplicated.
>
> It's like a file system directory structure (because that is what it
> is.) If I have C:\Documents and Settings\Shenan\ --> I can have that
> path *once*. If the file "test.txt" exists in that directory
> (C:\Documents and Settings\Shenan\test.txt) and I try to create a
> file with the same name and extension there - it will tell me I
> cannot.
> Can you explain more fully what test would replicate what you are
> claiming?
> Oh - in case it matters - this was all done on a fully updated
> Windows XP Professional machine - SP3, IE7, etc.
>
> --
> Shenan Stanley
> MS-MVP
Tthat's similar to what I mean. Only the OP wanted to use Export to
export the entire registry to a file and then Import the entire registry
in order to fix a problem in it. I left his original question at the
top of this post.
I can do exactly what you did; export a key or whatever and then
reimport it, and it'll merge fine. In fact, I do it fairly often
relatively speaking. I have no idea why it's so, but importing a
complete exported registry will create the issues.
Since you're running a VM, I think you should be able to try that,
too.
Just for grins I restored my System state on the sandbox to get it
running well again, and this time imaged with XP Home SP2; the last one
was SP1, which I'd forgotten at first. It's SP2 with MSO, TurboCad and
some graphic manipulation programs, Norton, OO.o, Audacity & a bunch of
other open source stuff, AV, ZoneAlarm several spyware detectors and a
host of test utilities and a couple .NET frameworks besides a bunch of
simple 'net util apps that are mostly VB6 which don't use the registry.
The drive images are kept on an external drive, not normally connected
to the machine and it has not been connected to the 'net in the recent
past; I think two images ago. Whenever I start to use it, I re-image it
because it's sometimes left in a pretty bad state when Iv'e been playing
with things. I use Ghost14 for imaging. Two physical drives, NTFS, 80
Gig and 160 Gig.
I can only get into Safe Mode with it after Importing the entire
Registry, that was exported; it will not completely boot otherwise. Or
maybe it will, but I cut off boots at 6+ minutes. Normally it's around
3 minutes for that machine so beyond 6 minutes indicates to me something
substantially changed and historically won't repair itself with further
boots. .
I don't think the version of XP matters, nor does the Service Pack
level but I haven't actually compared results from only SP1 2 or 3. I
don't know much about, or use, VMs, but AFAIK there is very little
difference in the way an OS operates because it's in a VM.
If you have the time to fiddle, I'd be very interested in hearing what
happens when you used regedit to Export the entire registry, restart it
two or more times, or a Cold Boot, run a program or two, but not
purposely messing with the registry and then Import back in the same
Exported registry file. If I'm wrong and have some words to eat, I'll
do so, but I really feel this isn't just my particular system doing
this. This is the first time I've had anyone dispute the matter and I
have read similar experiences in other groups, though not here i don't
think.
I'm guessing and have never taken the time to check, but I think,
since the registry is constantly being rewritten as applications and the
OS are being exercised, that it'll end up with some duplicate entries
with different values to them, and with the new values actually being
the "old" ones, which can give the OS a rather strong stomach ache.
I've seen the duplicate entries and also noted that the symptoms of
importing an entire registry vary with time, and I've never ended up
with a healthy machine. But then I've only done it a handful of times,
too. I hate waiting, even for just a re-image and a boot.
I'd be interested in your own results of exporting/importing a complete
registry all in one piece.
Regards,
Twayne
|
|
Your lead-in just doesn't sound believable; sorry. And even so, you
haven't covered the situation the OP was discussing and how/what he
would have expoted/imported vs time passing.
....
[Quoted Text] >>
>>
>> Question: Have you tried it? Go ahead and try it. It can indeed be
>> accomplished.
>
> Yes I have, just now again, and many times before! I have exported
> the *whole* registry, *whole% hives or just select keys/subkeys and I
> have then attempted to import them back into the registry. The
> attempted imports had various results, either the operation failed
> completely (trying to import the whole registry) or it succeeded but
> with errors (when importing whole hives it imported some keys but
> could not import them all) or the operation was completely
> successful. In all cases there were no duplicate entries created,
> there were none because what you say is not true, it is impossible to
> created duplicate entries in the registry!> I have just now tested
> this on Windows XP and on Windows 2000 and on
> both machines the results were the same. I had no qualms doing this
> on production (home) machines because I have backups and I know all
> too well that there can be no harm in importing identical entries in
> the registry, it changes nothing in the registry. I also know that
> due to the ACID nature of the registry when imports fail it will not
> allow the creation of meaningless entries in the registry. In my 12+
> years of using NT operating systems I have exported/imported and
> merged files to the registry countless times and I have *never* seen
> duplicate entries in the registry, what you are saying is pure and
> simply bunk!
> Anyone can easily and fairly safely test this by doing the following:
I wouldn't recommend this on production machines, but it should be OK.
I've only had it result in an unbootable machine one time.
>
> 1- Create a Restore Point.
>
> 2- Create a new dummy test user account.
That won't set you up to export the whole registry. You'll need Admin
privileges.
>
> 3- Log on to the new user account to allow the system to create the
> user's profile hive. Log off to ensure that the profile hive is
> properly created and stored.
>
> 4- Log back on to the new user account and use the registry editor and
> export the whole HKEY_CURRENT_USER subtree, and then (while still
> logged on as the same new user!) try to import or merge the exported
> HKCU file back to the registry and observe the results.
>
> As mentioned by Shenan in his post, this is akin to creating duplicate
> paths or folders/files with duplicate names in the same path, it is
> impossible to do! In the case of Windows Explorer, by default it will
> simply assign a new, slightly different name to the file system object
> (FileName (2), FileName (3)...). Other utilities may use different
> methods such as adding or appending to the object name (Copy of
> ObjectName, Copy2 of ObjectName...). Native Windows registry
> utilities do not use these methods to rename registry entries, for
> starters those newly renamed entries would be completely meaningless
> and useless, they would serve absolutely no purpose. Adding or
> merging an entry to the registry is an all or nothing proposition,
> either it works or it fails, there is no in between and on failure
> the registry tools do not create duplicate entries!
>
> So that brings us to your claims that importing files into *your*
> registry leaves it "Full of duplicates"! If this is happening then we
> can only surmise or offer possibilities such as:
>
> 1- Your Windows installation is completely borked, probably brought
> about by the indiscriminate use of worthless registry cleaners!
>
> 2- Your machine has a severe virus infection.
>
> 3- You are using a useless third party registry utility to import or
> merge the files to the registry and the utility is using a renaming
> scheme as described above to rename entries.
>
> If, as you claim, your registry is "Full of duplicates" could you give
> use the full details of some those duplicate entries? What are the
> names of these duplicates?
>
> John
|
|
Now you're back peddling, it doesn't surprise me, that is your usual MO.
You spread FUD and when taken up on it you try to weasel your way out
of your lies.
Anyone can try this if they want, it won't hurt their Windows
installation, they can export the *whole* registry and then try to
import it again, they will get the same results as I did.
A top of doing this with Windows 2000 and Windows XP I have just now
done the same thing with Regedit on my NT 4.0 box and guess what? I got
an error message stating that I was attempting to tamper with the
registered product type, (License violation), (that is because there is
a key that cannot be touched or replaced while Windows is up and
running) and then the system continued its attempt to import the whole
file and then failed with another error message. And sure enough, on my
NT4 installation, as on my other installations, there are no duplicate
entries in the registry! Your FUD has been exposed, importing files
into the registry *never* creates duplicates!
And you haven't told us which entries were duplicated in your registry,
I wonder why? The only thing unbelievable in this whole thread is that
you still cling to your incorrect statements and still try to pass your
FUD as facts.
John
Twayne wrote:
[Quoted Text] > Your lead-in just doesn't sound believable; sorry. And even so, you
> haven't covered the situation the OP was discussing and how/what he
> would have expoted/imported vs time passing.
>
>
> ...
>
>>>
>>>Question: Have you tried it? Go ahead and try it. It can indeed be
>>>accomplished.
>>
>>Yes I have, just now again, and many times before! I have exported
>>the *whole* registry, *whole% hives or just select keys/subkeys and I
>>have then attempted to import them back into the registry. The
>>attempted imports had various results, either the operation failed
>>completely (trying to import the whole registry) or it succeeded but
>>with errors (when importing whole hives it imported some keys but
>>could not import them all) or the operation was completely
>>successful. In all cases there were no duplicate entries created,
>>there were none because what you say is not true, it is impossible to
>>created duplicate entries in the registry!> I have just now tested
>>this on Windows XP and on Windows 2000 and on
>>both machines the results were the same. I had no qualms doing this
>>on production (home) machines because I have backups and I know all
>>too well that there can be no harm in importing identical entries in
>>the registry, it changes nothing in the registry. I also know that
>>due to the ACID nature of the registry when imports fail it will not
>>allow the creation of meaningless entries in the registry. In my 12+
>>years of using NT operating systems I have exported/imported and
>>merged files to the registry countless times and I have *never* seen
>>duplicate entries in the registry, what you are saying is pure and
>>simply bunk!
>>Anyone can easily and fairly safely test this by doing the following:
>
>
> I wouldn't recommend this on production machines, but it should be OK.
> I've only had it result in an unbootable machine one time.
>
>>1- Create a Restore Point.
>>
>>2- Create a new dummy test user account.
>
>
> That won't set you up to export the whole registry. You'll need Admin
> privileges.
>
>>3- Log on to the new user account to allow the system to create the
>>user's profile hive. Log off to ensure that the profile hive is
>>properly created and stored.
>>
>>4- Log back on to the new user account and use the registry editor and
>>export the whole HKEY_CURRENT_USER subtree, and then (while still
>>logged on as the same new user!) try to import or merge the exported
>>HKCU file back to the registry and observe the results.
>
>
>
>>As mentioned by Shenan in his post, this is akin to creating duplicate
>>paths or folders/files with duplicate names in the same path, it is
>>impossible to do! In the case of Windows Explorer, by default it will
>>simply assign a new, slightly different name to the file system object
>>(FileName (2), FileName (3)...). Other utilities may use different
>>methods such as adding or appending to the object name (Copy of
>>ObjectName, Copy2 of ObjectName...). Native Windows registry
>>utilities do not use these methods to rename registry entries, for
>>starters those newly renamed entries would be completely meaningless
>>and useless, they would serve absolutely no purpose. Adding or
>>merging an entry to the registry is an all or nothing proposition,
>>either it works or it fails, there is no in between and on failure
>>the registry tools do not create duplicate entries!
>>
>>So that brings us to your claims that importing files into *your*
>>registry leaves it "Full of duplicates"! If this is happening then we
>>can only surmise or offer possibilities such as:
>>
>>1- Your Windows installation is completely borked, probably brought
>>about by the indiscriminate use of worthless registry cleaners!
>>
>>2- Your machine has a severe virus infection.
>>
>>3- You are using a useless third party registry utility to import or
>>merge the files to the registry and the utility is using a renaming
>>scheme as described above to rename entries.
>>
>>If, as you claim, your registry is "Full of duplicates" could you give
>>use the full details of some those duplicate entries? What are the
>>names of these duplicates?
>>
>>John
>
>
>
>
|
|
Good grief. Did you run a registry cleaner on your brain? It's as scrambled
as your registry must be.
"Twayne" <nobody[ at ]devnull.spamcop.net> wrote in message
news:O9XL2dgZJHA.1532[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > f'ups adjusted back
>
>> Now you're back peddling, it doesn't surprise me, that is your usual
>> MO. You spread FUD and when taken up on it you try to weasel your
>> way out of your lies.
>
> Nope, I am saying the same exact thing I said before. You have a very poor
> handle on any of this and think you can bluff your way along; you can't.
> I can't help your disability in the comprehension areas.
> Using your own methodology, since you chose to not refute my suspicion
> that you hadn't actually tried out what you said you did, then I'll chalk
> that one up as the lie I thought it was.
> There is a very simple reason why you didn't catch me in a lie too, BTW:
> Unlike you, I do not lie. Period. Nothing can be gained by it, it's a
> waste of time to do, and it defines the only group of people I have any
> sort of actual prejudice against: Liars.
>
>>
>> Anyone can try this if they want, it won't hurt their Windows
>> installation, they can export the *whole* registry and then try to
>> import it again, they will get the same results as I did.
>
>>
>> A top of doing this with Windows 2000 and Windows XP I have just now
>> done the same thing with Regedit on my NT 4.0 box and guess what? I
>> got an error message stating that I was attempting to tamper with the
>> registered product type, (License violation), (that is because there
>> is a key that cannot be touched or replaced while Windows is up and
>> running) and then the system continued its attempt to import the whole
>> file and then failed with another error message. And sure enough, on
>> my NT4 installation, as on my other installations, there are no
>> duplicate entries in the registry! Your FUD has been exposed,
>> importing files into the registry *never* creates duplicates!
>
> Ahh, another blatant attempt at misdirestion which you favor so strongly:
> You are the first to bring NT4 into this. Shall we also discuss NT1, CP/M
> and DOS operating systems like win98/95/3? Hell, you can't even figure
> out which newsgroup you want to post in so you start adding your own.
> That is a clear indication of what your intents actually are. But it'll
> still only get read one time, if it's read at all. Even I only read them
> for the entertainment value.
>
>>
>> And you haven't told us which entries were duplicated in your
>> registry, I wonder why?
>
> You didn't ask perhaps? Or maybe I have no reason to? There is nothing to
> make me want to do so? You're grabbing at straws? You know and want to
> see if I really do? All the above? None of the above? Since you've
> actually duplicated (you claimed) the OPs propsed actions, in their
> entirety, then you can easily know anyway. There was a time I'd have
> answered you had you asked, but now that you've been relegated to the nut
> bin, that time is well past. Especially when you can actually do it
> yourself, which you have not done yet.
>
> The only thing unbelievable in this whole
>> thread is that you still cling to your incorrect statements and still
>> try to pass your FUD as facts.
>
> Since your allegation is untrue, than can I construe the above sentence to
> mean that all else is believable? Good; not that I care. It's accurate;
> believability is your problem.
>
> You are even less believable now than you were; it seems your age
> regresses with each post, actually. When I stop responding to you, you'll
> know that I've relegated you to the ignorable troll bin. Be sure to hold
> your breath.
>
> Twayne
>
>>
>> John
>>
>> Twayne wrote:
>>
>>> Your lead-in just doesn't sound believable; sorry. And even so, you
>>> haven't covered the situation the OP was discussing and how/what he
>>> would have expoted/imported vs time passing.
>>>
>>>
>>> ...
>>>
>>>>>
>>>>> Question: Have you tried it? Go ahead and try it. It can indeed
>>>>> be accomplished.
>>>>
>>>> Yes I have, just now again, and many times before! I have exported
>>>> the *whole* registry, *whole% hives or just select keys/subkeys and
>>>> I have then attempted to import them back into the registry. The
>>>> attempted imports had various results, either the operation failed
>>>> completely (trying to import the whole registry) or it succeeded but
>>>> with errors (when importing whole hives it imported some keys but
>>>> could not import them all) or the operation was completely
>>>> successful. In all cases there were no duplicate entries created,
>>>> there were none because what you say is not true, it is impossible
>>>> to created duplicate entries in the registry!> I have just now
>>>> tested this on Windows XP and on Windows 2000 and on
>>>> both machines the results were the same. I had no qualms doing this
>>>> on production (home) machines because I have backups and I know all
>>>> too well that there can be no harm in importing identical entries in
>>>> the registry, it changes nothing in the registry. I also know that
>>>> due to the ACID nature of the registry when imports fail it will not
>>>> allow the creation of meaningless entries in the registry. In my
>>>> 12+ years of using NT operating systems I have exported/imported and
>>>> merged files to the registry countless times and I have *never* seen
>>>> duplicate entries in the registry, what you are saying is pure and
>>>> simply bunk!
>>>> Anyone can easily and fairly safely test this by doing the
>>>> following:
>>>
>>>
>>> I wouldn't recommend this on production machines, but it should be
>>> OK. I've only had it result in an unbootable machine one time.
>>>
>>>> 1- Create a Restore Point.
>>>>
>>>> 2- Create a new dummy test user account.
>>>
>>>
>>> That won't set you up to export the whole registry. You'll need
>>> Admin privileges.
>>>
>>>> 3- Log on to the new user account to allow the system to create the
>>>> user's profile hive. Log off to ensure that the profile hive is
>>>> properly created and stored.
>>>>
>>>> 4- Log back on to the new user account and use the registry editor
>>>> and export the whole HKEY_CURRENT_USER subtree, and then (while
>>>> still logged on as the same new user!) try to import or merge the
>>>> exported HKCU file back to the registry and observe the results.
>>>
>>>
>>>
>>>> As mentioned by Shenan in his post, this is akin to creating
>>>> duplicate paths or folders/files with duplicate names in the same
>>>> path, it is impossible to do! In the case of Windows Explorer, by
>>>> default it will simply assign a new, slightly different name to the
>>>> file system object (FileName (2), FileName (3)...). Other
>>>> utilities may use different methods such as adding or appending to
>>>> the object name (Copy of ObjectName, Copy2 of ObjectName...). Native
>>>> Windows registry utilities do not use these methods to
>>>> rename registry entries, for starters those newly renamed entries
>>>> would be completely meaningless and useless, they would serve
>>>> absolutely no purpose. Adding or merging an entry to the registry
>>>> is an all or nothing proposition, either it works or it fails,
>>>> there is no in between and on failure the registry tools do not
>>>> create duplicate entries! So that brings us to your claims that
>>>> importing files into *your*
>>>> registry leaves it "Full of duplicates"! If this is happening then
>>>> we can only surmise or offer possibilities such as:
>>>>
>>>> 1- Your Windows installation is completely borked, probably brought
>>>> about by the indiscriminate use of worthless registry cleaners!
>>>>
>>>> 2- Your machine has a severe virus infection.
>>>>
>>>> 3- You are using a useless third party registry utility to import or
>>>> merge the files to the registry and the utility is using a renaming
>>>> scheme as described above to rename entries.
>>>>
>>>> If, as you claim, your registry is "Full of duplicates" could you
>>>> give use the full details of some those duplicate entries? What
>>>> are the names of these duplicates?
>>>>
>>>> John
>
>
>
|
|
You obviously have a cranium rectum inversion.
"Twayne" <nobody[ at ]devnull.spamcop.net> wrote in message
news:O9XL2dgZJHA.1532[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > f'ups adjusted back
>
>> Now you're back peddling, it doesn't surprise me, that is your usual
>> MO. You spread FUD and when taken up on it you try to weasel your
>> way out of your lies.
>
> Nope, I am saying the same exact thing I said before. You have a very poor
> handle on any of this and think you can bluff your way along; you can't.
> I can't help your disability in the comprehension areas.
> Using your own methodology, since you chose to not refute my suspicion
> that you hadn't actually tried out what you said you did, then I'll chalk
> that one up as the lie I thought it was.
> There is a very simple reason why you didn't catch me in a lie too, BTW:
> Unlike you, I do not lie. Period. Nothing can be gained by it, it's a
> waste of time to do, and it defines the only group of people I have any
> sort of actual prejudice against: Liars.
>
>>
>> Anyone can try this if they want, it won't hurt their Windows
>> installation, they can export the *whole* registry and then try to
>> import it again, they will get the same results as I did.
>
>>
>> A top of doing this with Windows 2000 and Windows XP I have just now
>> done the same thing with Regedit on my NT 4.0 box and guess what? I
>> got an error message stating that I was attempting to tamper with the
>> registered product type, (License violation), (that is because there
>> is a key that cannot be touched or replaced while Windows is up and
>> running) and then the system continued its attempt to import the whole
>> file and then failed with another error message. And sure enough, on
>> my NT4 installation, as on my other installations, there are no
>> duplicate entries in the registry! Your FUD has been exposed,
>> importing files into the registry *never* creates duplicates!
>
> Ahh, another blatant attempt at misdirestion which you favor so strongly:
> You are the first to bring NT4 into this. Shall we also discuss NT1, CP/M
> and DOS operating systems like win98/95/3? Hell, you can't even figure
> out which newsgroup you want to post in so you start adding your own.
> That is a clear indication of what your intents actually are. But it'll
> still only get read one time, if it's read at all. Even I only read them
> for the entertainment value.
>
>>
>> And you haven't told us which entries were duplicated in your
>> registry, I wonder why?
>
> You didn't ask perhaps? Or maybe I have no reason to? There is nothing to
> make me want to do so? You're grabbing at straws? You know and want to
> see if I really do? All the above? None of the above? Since you've
> actually duplicated (you claimed) the OPs propsed actions, in their
> entirety, then you can easily know anyway. There was a time I'd have
> answered you had you asked, but now that you've been relegated to the nut
> bin, that time is well past. Especially when you can actually do it
> yourself, which you have not done yet.
>
> The only thing unbelievable in this whole
>> thread is that you still cling to your incorrect statements and still
>> try to pass your FUD as facts.
>
> Since your allegation is untrue, than can I construe the above sentence to
> mean that all else is believable? Good; not that I care. It's accurate;
> believability is your problem.
>
> You are even less believable now than you were; it seems your age
> regresses with each post, actually. When I stop responding to you, you'll
> know that I've relegated you to the ignorable troll bin. Be sure to hold
> your breath.
>
> Twayne
>
>>
>> John
>>
>> Twayne wrote:
>>
>>> Your lead-in just doesn't sound believable; sorry. And even so, you
>>> haven't covered the situation the OP was discussing and how/what he
>>> would have expoted/imported vs time passing.
>>>
>>>
>>> ...
>>>
>>>>>
>>>>> Question: Have you tried it? Go ahead and try it. It can indeed
>>>>> be accomplished.
>>>>
>>>> Yes I have, just now again, and many times before! I have exported
>>>> the *whole* registry, *whole% hives or just select keys/subkeys and
>>>> I have then attempted to import them back into the registry. The
>>>> attempted imports had various results, either the operation failed
>>>> completely (trying to import the whole registry) or it succeeded but
>>>> with errors (when importing whole hives it imported some keys but
>>>> could not import them all) or the operation was completely
>>>> successful. In all cases there were no duplicate entries created,
>>>> there were none because what you say is not true, it is impossible
>>>> to created duplicate entries in the registry!> I have just now
>>>> tested this on Windows XP and on Windows 2000 and on
>>>> both machines the results were the same. I had no qualms doing this
>>>> on production (home) machines because I have backups and I know all
>>>> too well that there can be no harm in importing identical entries in
>>>> the registry, it changes nothing in the registry. I also know that
>>>> due to the ACID nature of the registry when imports fail it will not
>>>> allow the creation of meaningless entries in the registry. In my
>>>> 12+ years of using NT operating systems I have exported/imported and
>>>> merged files to the registry countless times and I have *never* seen
>>>> duplicate entries in the registry, what you are saying is pure and
>>>> simply bunk!
>>>> Anyone can easily and fairly safely test this by doing the
>>>> following:
>>>
>>>
>>> I wouldn't recommend this on production machines, but it should be
>>> OK. I've only had it result in an unbootable machine one time.
>>>
>>>> 1- Create a Restore Point.
>>>>
>>>> 2- Create a new dummy test user account.
>>>
>>>
>>> That won't set you up to export the whole registry. You'll need
>>> Admin privileges.
>>>
>>>> 3- Log on to the new user account to allow the system to create the
>>>> user's profile hive. Log off to ensure that the profile hive is
>>>> properly created and stored.
>>>>
>>>> 4- Log back on to the new user account and use the registry editor
>>>> and export the whole HKEY_CURRENT_USER subtree, and then (while
>>>> still logged on as the same new user!) try to import or merge the
>>>> exported HKCU file back to the registry and observe the results.
>>>
>>>
>>>
>>>> As mentioned by Shenan in his post, this is akin to creating
>>>> duplicate paths or folders/files with duplicate names in the same
>>>> path, it is impossible to do! In the case of Windows Explorer, by
>>>> default it will simply assign a new, slightly different name to the
>>>> file system object (FileName (2), FileName (3)...). Other
>>>> utilities may use different methods such as adding or appending to
>>>> the object name (Copy of ObjectName, Copy2 of ObjectName...). Native
>>>> Windows registry utilities do not use these methods to
>>>> rename registry entries, for starters those newly renamed entries
>>>> would be completely meaningless and useless, they would serve
>>>> absolutely no purpose. Adding or merging an entry to the registry
>>>> is an all or nothing proposition, either it works or it fails,
>>>> there is no in between and on failure the registry tools do not
>>>> create duplicate entries! So that brings us to your claims that
>>>> importing files into *your*
>>>> registry leaves it "Full of duplicates"! If this is happening then
>>>> we can only surmise or offer possibilities such as:
>>>>
>>>> 1- Your Windows installation is completely borked, probably brought
>>>> about by the indiscriminate use of worthless registry cleaners!
>>>>
>>>> 2- Your machine has a severe virus infection.
>>>>
>>>> 3- You are using a useless third party registry utility to import or
>>>> merge the files to the registry and the utility is using a renaming
>>>> scheme as described above to rename entries.
>>>>
>>>> If, as you claim, your registry is "Full of duplicates" could you
>>>> give use the full details of some those duplicate entries? What
>>>> are the names of these duplicates?
>>>>
>>>> John
>
>
>
|
|
|