I am changing the HeapDecommitFreeBlockThreshold on a Exchange 2003 server and having problems in the registry

The solution to this is so simple, yet so difficult. i came across this possible issue in the documentation on the MS website. i dutifully proceeded to open the registry editor and created the DWord value. No Problem. However when I try to change the value from the default "0" to the recommended "0x00040000" the editor does not allow me to type the little "x" in the second character position for the Hex value. I have tried putting the value in in decimal, "262144" and then clicking on "Hex", but that gives me a Hex value of "40000" which I believe has the same meaning as "0x00040000" but it looks different and I'm hesitant to the point of not willing to click out of it and reboot. I have seen similar issues posted hear on EE and they all get pointed to the article on MS Tech Net or the KB article which never mention anything but the "0x00040000" value with the 'x" in it. Could someone please give me some advice about the small "x". and not being able to enter it in the registry editor?
dwielgoszAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rakeshmiglaniCommented:
please check the following microsoft atricles.

The "HeapDecommitFreeBlockThreshold" registry key
http://support.microsoft.com/kb/315407/en-us

How to optimize memory usage in Exchange Server 2003
http://support.microsoft.com/kb/815372/en-us

How to troubleshoot virtual memory fragmentation in Exchange Server 2003 and Exchange 2000 Server
http://support.microsoft.com/kb/325044/en-us
0
dwielgoszAuthor Commented:
So what are you saying, to just set it with the decimal number and not worry about the inability to enter the number in hex?
0
rakeshmiglaniCommented:
yes..  the following KB has the steps defined

The "HeapDecommitFreeBlockThreshold" registry key
http://support.microsoft.com/kb/315407/en-us
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dwielgoszAuthor Commented:
OK, I get it. By virtue of the fact that the instructions are referring to using the decimal equivalent it can be safely assumed that it's OK to use the decimal, even though the article (nor any that I have found) have not addressed the small "x" part of the hex number being entered. haha Just wanted 'proof" because I have a "nice" exchange server that's running smoothly and I didn't want to create any problems. There's always enough issues without creating any new ones. Thanks for the help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.