Wierd behaviourof "MORE" after the registry cleaning

  • Thread starter Thread starter Mazi
  • Start date Start date
M

Mazi

Hi There,

I just did some registry cleaning on my windows 2k3 Enterprise Server with
the "Tune-Up Utilities 2004". The Tune-Up did find lots of broken registries
and now my server is running more responsive. However, I do notice some
weird thing regarding the "more" piping utility. Usualy, if I executed "more
filename.txt" on a CMD console, I should be able to see/read the contents of
the filename.txt. After this Tune-Up, executing more filename.txt" on a CMD
console returns an error message "Too many arguments in command line.";
however, "type filename.txt | more" works just fine. I would appreciate if
anyone out here can help me out to fix this problem.

Thanks.
 
Mazi said:
Hi There,

I just did some registry cleaning on my windows 2k3 Enterprise Server with
the "Tune-Up Utilities 2004". The Tune-Up did find lots of broken registries
and now my server is running more responsive. However, I do notice some
weird thing regarding the "more" piping utility. Usualy, if I executed "more
filename.txt" on a CMD console, I should be able to see/read the contents of
the filename.txt. After this Tune-Up, executing more filename.txt" on a CMD
console returns an error message "Too many arguments in command line.";
however, "type filename.txt | more" works just fine. I would appreciate if
anyone out here can help me out to fix this problem.

Thanks.
Click to expand...

Allowing a tool to poke around in the registry is equivalent
to sticking needles into someone's brain to see what happens.
Scary stuff! And when you say that your server is "more
responsive", is this based on a tightly controlled measurement
or is it more a case of wishful thinking?

The fact is that the registry contains thousands of entries. My
server has 330,000 lines. Only the creator of these entries
knows exactly what each of them does. It's a bit like your DNA:
We know what's where but we don't have the faintest idea which
molecules are responsible for your surprising optimism.

Good luck!
 
Restore the registry from the backup you made, start a clean install, or
possible these may help.

How to Perform an In-Place Upgrade of Windows 2000
http://support.microsoft.com/support/kb/articles/Q292/1/75.ASP

What an In-Place Windows 2000 Upgrade Changes and What It Does Not Change
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306952

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Hi There,
|
| I just did some registry cleaning on my windows 2k3 Enterprise Server with
| the "Tune-Up Utilities 2004". The Tune-Up did find lots of broken
registries
| and now my server is running more responsive. However, I do notice some
| weird thing regarding the "more" piping utility. Usualy, if I executed
"more
| filename.txt" on a CMD console, I should be able to see/read the contents
of
| the filename.txt. After this Tune-Up, executing more filename.txt" on a
CMD
| console returns an error message "Too many arguments in command line.";
| however, "type filename.txt | more" works just fine. I would appreciate if
| anyone out here can help me out to fix this problem.
|
| Thanks.
|
| --
| Mazi
|
|
 
Back
Top