Professional Documents
Culture Documents
Word Count:
499
Summary:
Tech support tells me to type 'regedt32' as opposed to 'regedit' to access the
registry from the command line (Start > Run). I question the use of 'regedt32,' but
he says to do it anyway. Whenever I use the registry editor, I recall this incident
and never look up the tale of the two regs... until now.
Keywords:
registry editor, regedit, reged, windows, microsoft windows, computer, pc
Article Body:
Tech support tells me to type 'regedt32' as opposed to 'regedit' to access the
registry from the command line (Start > Run). I question the use of 'regedt32,' but
he says to do it anyway. Whenever I use the registry editor, I recall this incident
and never look up the tale of the two regs... until now.
"You cannot set the security for registry keys. You cannot view, edit, or search
the value data types <>REG_EXPAND_SZ and <>REG_MULTI_SZ. If you try to view a
<>REG_EXPAND_SZ value, Regedit.exe displays it as a binary data type. If you try to
edit either of these data types, Regedit.exe saves it as <>REG_SZ, and the data
type no longer performs its intended function. You cannot save or restore keys as
hive files."
In WinXP and Server 2003, the two have been replaced by a new version of regedit
that has features from both. Try typing 'regedit' and 'regedt32' to see what
happens. They're the same. To prove it, while in 'regedit,' select 'edit' and
you'll see 'permissions.' This is a feature that was only available in the old
'regedt32' and not 'regedit.'
Now I remember that tech support was checking to see if the permissions were
properly set and that was why we used 'regedt32.' However, someone forgot to update
the script or tell him that it didn't matter anymore when a user had WinXP. Tech
support always asks what operating system at the beginning of the call, so he knew.