Tom's Hardware > Forum > Windows 2000/NT > Windows 2000/NT General Discussion > Wierd behaviourof "MORE" after the registry cleaning

Wierd behaviourof "MORE" after the registry cleaning

Forum Windows 2000/NT : Windows 2000/NT General Discussion - Wierd behaviourof "MORE" after the registry cleaning

Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions. Sign up now! Its free!
Ask the community Add a reply
Word :    Username :           
 
Anonymous   11-23-2004 at 05:25:57 PM

Archived from groups: microsoft.public.win2000.setup (More info?)

 

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

Add a reply
Sponsored Links
Register or log in to remove.
Anonymous   11-24-2004 at 04:48:19 AM
- 0 +

Archived from groups: microsoft.public.win2000.setup (More info?)

 

"Mazi" <!spamMe@NoSpammer.Null> wrote in message
news:97Fod.556700$mD.89378@attbi_s02...
> 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

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!

Reply to Anonymous
Anonymous   11-23-2004 at 05:25:58 PM
- 0 +

Archived from groups: microsoft.public.win2000.setup (More info?)

 

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/suppo [...] 2/1/75.ASP

What an In-Place Windows 2000 Upgrade Changes and What It Does Not Change
http://support.microsoft.com/defau [...] us;Q306952

--
Regards,

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

"Mazi" wrote:
| 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
|
|

Reply to Anonymous
Ask the community Add a reply
Tom's Hardware > Forum > Windows 2000/NT > Windows 2000/NT General Discussion > Wierd behaviourof "MORE" after the registry cleaning
Go to:

There are 946 identified and unidentified users. To see the list of identified users, Click here.

Forum map
Bestofmedia Forum ©
2000-2009 Bestofmedia Group
Page generated in 0.276 seconds
Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Sponsored links
  • Ask the community now
  • Publish
Ad
Related Topics
See all relatives topics
They won a badge
Join us in greeting them