| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: User Profile Hive Cleanup Service, Bravo! |
From: "Rich"
This is a multi-part message in MIME format.
------=_NextPart_000_003F_01C76B08.32133B20
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
REGEDIT doesn't save binary. You sound like you seeing Unicode =
(UTF-16). REGEDIT switched to Unicode at some point because it is =
required to support the registry which is Unicode. The reason the older =
versions of REGEDIT weren't Unicode was that it was a Windows 95 =
component and Windows 95 had an ANSI registry. REGEDT32 was the Windows =
NT tool. REGEDT32 was removed when Unicode support and other =
functionality was folded into REGEDIT.
Rich
"Gary Britt" wrote
in message =
news:46005ded{at}w3.nls.net...
It certainly looks like ascii, but I can tell you from personal =
experience=20
when I view a non-ascii version 5 registry file with the built in file =
viewer that comes with ZtreeWin it looks exactly like ascii and like =
what=20
you've shown below. Fooled me into thinking it was really ascii until =
when=20
something wasn't working right for me in trying edit or do something =
with=20
the file, I finally figured out it was really a binary, non-ascii, =
file that=20
I was viewing. If it says its version 5 at the top of the file, then =
it=20
ain't really ascii. If it says version 4 at the top of the file than =
it=20
really is ascii (probably ).
Gary
Frank Haber wrote:
> I call this stuff ASCII. The mounted hives are compressed, and half =
> this size...
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D
>=20
>=20
> =
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{b4fe65aa-f9e9-4b13-bd79-a9491=
02c5294}\TypeLib]=20
>=20
> {at}=3D"{E891EE9A-D0AE-4cb4-8871-F92C0109F18E}"
>=20
> =
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{b4fe65aa-f9e9-4b13-bd79-a9491=
02c5294}\VersionIndependentProgID]=20
>=20
> {at}=3D"Photoshop.PathPointInfo"
>=20
> =
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B50F5260-0C21-11D2-AB56-00A0C=
9082678}]=20
>=20
> {at}=3D"Compress Files Cleaner"
>=20
> =
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B50F5260-0C21-11D2-AB56-00A0C=
9082678}\DefaultIcon]=20
>=20
> =
{at}=3Dhex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74=
,00,25,\=20
>=20
> =
00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,41,0=
0,\=20
>=20
> =
54,00,41,00,43,00,4c,00,45,00,4e,00,2e,00,44,00,4c,00,4c,00,2c,00,32,00,0=
0,\=20
>=20
> 00
------=_NextPart_000_003F_01C76B08.32133B20
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
REGEDIT
doesn't save =
binary. You=20
sound like you seeing Unicode (UTF-16). REGEDIT switched to = Unicode at=20
some point because it is required to support the registry which is=20
Unicode. The reason the older versions of REGEDIT weren't Unicode
= was that=20
it was a Windows 95 component and Windows 95 had an ANSI registry. =
REGEDT32 was the Windows NT tool. REGEDT32 was removed when = Unicode=20
support and other functionality was folded into REGEDIT.
Rich
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)SEEN-BY: 633/267 5030/786 @PATH: 379/45 1 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.