Re: Modifying the Registry for NTP Access(Authoritative)--Doesn't Look Right

Tech-Archive recommends: Fix windows errors by optimizing your registry

rdgentry1_at_cablelynx.com
Date: 01/11/05 

Date: 10 Jan 2005 17:14:41 -0800

W. Watson wrote:
> Win XP Pro.
> This <http://support.microsoft.com/default.aspx?scid=kb;en-us;314054
> shows steps to
> modify the registry to use NTP as an external source. Step 3 asks
that
> SpecialPolInterval be changed to TimeInSeconds. The current value is
binary.

Something sounds off here -- this is not a "binary" value. See below.

>I have a limited knowledge of the use of regedit, but this looks
wrong.

Sure does ... [:-(

> BTW, before attempting to modify the registry I exported it. I made a
mistake early,
> and decided to import the file. It looks like it did this
successfully, but gave me a
> message at the end that said something like it could not restore all
values because
> they were in use. Close to that wording. What's that about. I had no
windows open.

It's a registry check so that it's not hacked (among other reasons).
"In use" means there is _some_ part of the system that is monitoring it
for changes -- like when you are editing ;-) I usually save the
sub-key folder I'm editing, make edits, open the reg file to check I
haven't just pooped on the registry, then close regedit when I'm
comfortable.

In fact, for what you were doing, I would probably have saved the
sub-key folder
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\ and just
edited the values by hand, then imported it.

But, back to Step 3 ...
c.
In the Edit DWORD Value dialog box, under Value data, type
'TimeInSeconds', and then click OK.

A DWORD should present you a dialog with an edit field and two radio
buttons: 1) decimal 2) hex. Check decimal and just enter 900 (or
whatever you want to try). "900 Decimal" means that the only valid
keystrokes are "decimals", ie., 0-9. Base 16 hex valid keystrokes are
0-9, a-f, A-F. 900 decimal in hex is 0x384 -- that's what the hex key
on the desktop calculators is for ;-)

In step 6 the instructions are more specific:
b.
In the right pane, right-click MaxPosPhaseCorrection, and then click
Modify.
c.
In the Edit DWORD Value dialog box, under Base, click Decimal.
d.
In the Edit DWORD Value dialog box, under Value data, type
TimeInSeconds, and then click OK.

Same should apply for step 3.

But when you look at step 5 they use hex for the # one, ie., 0x1. Not
that this would matter as 1=0x1. Somebody in doc creation is messin'
with your head? Click the radio button to tell registry how you are
entering the data, ie., decimal or hex, and it will interpret what you
enter.

Binary values present you with a hex editor and if you've not used one
before (or even if you have) you have to be sure you're editing the
correct nybbles (the individual digits). The "value" may contain a
number of discrete pieces of data of different sizes.

That's why this DWORD value presenting itself as binary sounds like
something is not right with the XP world. It makes perfect sense that
# of seconds be a DWORD integer -- none that it be binary. Besides,
it's been declared DWORD since W2K or even NT.

Are you being presented with the hex editor for binary values? It
looks like a small, scrollabe window with hex numbers in neat, numbered
rows on the left and a column of gobbled characters -- some words mixed
with junk on the right.

I don't recall MS ever publishing a registry edit that involved a
binary value -- usually they just provide a reg file for that. If you
are getting the binary hex editor for a DWORD, something is broke.

hth,
prg
email above disabled

PS Here's the links for firewall stuff:
http://www.microsoft.com/technet/community/columns/cableguy/cg0104.mspx#EHAA
http://www.microsoft.com/technet/community/columns/cableguy/cg0204.mspx
http://support.microsoft.com/default.aspx?scid=kb;en-us;886185
the Critical Update :(

Quantcast