Hi Folks,

After seeing the 5 bullshit tips on the microsoft website I thought I'd
share with you some real improvement tips for those people that don't know
these tips yet Here goes:

1. Disable "error reporting" (registry tweak needed).
2. Disable "dll cache" (command line command needed).
3. Disable "auto backup/restore points"
4. Disable "last access time"

One last tip in case background processess do not get enough time:
5. Disable "foreground boost option" for more equal time slices.

I won't explain how to do it, you'll have to google for information

Here is a short explanation about the tips:

1. Very infuriating. Every time a program crashes (which could happen a
lot), a stupid error report is made which could take long, after it's done
it ask if you want to send it to microsoft, do you really think microsoft
uses all these reports ? get real... in other words if you click no, the
****ing report was build for nothing and windows just wasted your valuable
time !.

2. Very bad for performance. The dll cache is a folder on the harddisk...
How stupid ! At least my dutch dictionary says: "a cache is a fast storage
place etc". Harddisk are not fast at all lol.. especially not for many i/o
operations. Anyway it seems windows back's up commonly used dll's,
compressess them, encrypts them, decompressess them, decrypts them, and
compares them, and loading and storing ofcourse... All in all very much
wastefull overhead. My dll cache was once 500 MB !!! After disabling it
(setting it to 1 MB) the performance of my system skyrocketed... like no
longer long stupid harddisks spins/waits... the DLL cache probably got so
full because I compressed my drive and later decompressed it etc... windows
got all confused and didn't recognize the dll's and starting comparing them
to the dll cache or something... I dont know what the cause is or if it's
normal or not... the only thing I know is that the DLL cache is a
performance killer !

3. Auto backup/restore points are totaly ****ing useless and waste harddisk
space and processing power etc... A better solution is to use a special
backup utility like norton ghost etc... for full system backup and easy
restore... and/or a simply backup your data with winzip etc.

4. Last access time... everytime a file or folder is accessed it needs to be
updated requiring more harddisk i/o operations... this is a small
performance improvement but still For some apps it can help a lot =D For
example when a app needs to build a folder tree... etc.. it's much faster
now

5. Little tweak.. windows will default boost the application which has
focus... which could possibly starve background processess etc...

Thanks to these tweaks my windows xp has be running like a little sun we say
in dutch =D for the past few years

Ofcourse I am always willing to listen to people who know other major or
small performance tweaks Dont bother about posting the graphical wizard
to turn off special graphic effects... I know that one already lol.. that's
pretty easy thx to the wizard but don't hestitate if you know anything
else

Bye,
Skybuck.

Skybuck Flying wrote:
>
> uses all these reports ? get real... in other words if you click no, the
> ****ing report was build for nothing and windows just wasted your valuable
> time !.

Spend some of your "valuable time" learning how to speak like an adult.

On Mon, 4 Jul 2005 17:21:52 +0200, "Skybuck Flying"
<(E-Mail Removed)> wrote:
>1. Very infuriating. Every time a program crashes (which could happen a
>lot), a stupid error report is made which could take long, after it's done
>it ask if you want to send it to microsoft, do you really think microsoft
>uses all these reports ? get real... in other words if you click no, the
>****ing report was build for nothing and windows just wasted your valuable
>time !.

I agree. I think Windows XP was created by people on crack.

On Mon, 4 Jul 2005 17:21:52 +0200, Skybuck Flying <(E-Mail Removed)>
said...
> Hi Folks,
>
> After seeing the 5 bullshit tips on the microsoft website I thought I'd
> share with you some real improvement tips for those people that don't know
> these tips yet Here goes:
>
<snip>
>
> Ofcourse I am always willing to listen to people who know other major or
> small performance tweaks

I know one: upgrade to Windows 2000.


Joe

Skybuck Flying <(E-Mail Removed)> wrote:
> 2. Disable "dll cache" (command line command needed).
[chop]
> 2. Very bad for performance. The dll cache is a folder on the
> harddisk... How stupid ! At least my dutch dictionary says: "a cache
> is a fast storage place etc". Harddisk are not fast at all lol..
> especially not for many i/o operations. Anyway it seems windows
> back's up commonly used dll's, compressess them, encrypts them,
> decompressess them, decrypts them, and compares them, and loading and
> storing ofcourse... All in all very much wastefull overhead. My dll
> cache was once 500 MB !!! After disabling it (setting it to 1 MB) the
> performance of my system skyrocketed... like no longer long stupid
> harddisks spins/waits... the DLL cache probably got so full because I
> compressed my drive and later decompressed it etc... windows got all
> confused and didn't recognize the dll's and starting comparing them
> to the dll cache or something... I dont know what the cause is or if
> it's normal or not... the only thing I know is that the DLL cache is
> a performance killer !

That might indeed be the only thing you know. One of the things you
*don't* know is what the DLLCache is actually used for. Windows does
*not* use the DLLCache during 'normal' operations, but only when
installing something, uninstalling something, or when running SFC
(System File Checker).
Since you're Dutch, I can understand that you don't know the original
meaning of the word "cache", which has nothing to do with speeding
things up, but is a place of storage. And that's exactly what DLLCache
is.
If a program you install overwrites a system DLL with an older and
incompatible version, the correct file can be restored from this
storage.
The cache is compressed (if using NTFS) to reduce disk space. Also,
with modern PCs, the CPU is so much faster than the hard drives anyhow
that it's *faster* to uncompress highly compressible files than to read
them uncompressed.

It's *highly* recommended that if you have installed multiple products,
you then open a command prompt and enter "sfc /SCANNOW" (you need your
installation media handy).

> 3. Auto backup/restore points are totaly ****ing useless and waste
> harddisk space and processing power etc... A better solution is to
> use a special backup utility like norton ghost etc... for full system
> backup and easy restore... and/or a simply backup your data with
> winzip etc.

Ghost can't revert registry entries, for one thing. It makes
*snapshots*, and, most importantly, you have to take the system down to
do it. That's even less efficient. Instead of a minor slowdown every
now and then, you lose hours while manually performing a Ghost snapshot.
WinZip can't correctly handle files that are locked ("in use"),
including your registry. It wasn't designed to do that job, and doesn't
do it well. It also can't handle NTFS streams or advanced protections
(WinRAR can, though), so restore from a zip file, and the files might
have wrong ownership and permissions, which might screw you up Big Time.

Unless you have a good backup program, the backup/restore point can be
what saves you. Ghost and WinZip are *not* backup programs, though.

> 4. Last access time... everytime a file or folder is accessed it
> needs to be updated requiring more harddisk i/o operations... this is
> a small performance improvement but still For some apps it can
> help a lot =D For example when a app needs to build a folder tree...
> etc.. it's much faster now

On the other hand, system utilities that speed up the system by looking
at the access time of applications won't work, which causes a
*slowdown*. One example is disk defragmenters which place files
accessed recently near the start of the disk and files not accessed for
a long time near the end. Since the start of the disk usually is about
twice as fast as the end, and sometimes more, this makes sense.

> Ofcourse I am always willing to listen to people who know other major
> or small performance tweaks Dont bother about posting the
> graphical wizard to turn off special graphic effects... I know that
> one already lol.. that's pretty easy thx to the wizard but don't
> hestitate if you know anything else

Sure: Don't post this to a.c.p.videocards.nvidia unless it contains
information directly relevant to nVidia video cards. Same goes for
a.c.p.mainboard.asus. You'll slow down our PCs when we have to download
your irrelevant (and largely incorrect) posts.

HTH, HAND,
--
*Art