On Sun, 15 Apr 2007 21:12:37 GMT, "atlantis43 via WindowsKB.com"
CQuirke;

Hi!

Your links are very interesting, but the specific troublesome problem seems
to elude 'figuring out'.

OK...

Generally, the year-old PC with lots of ram & free memory & cache seems to
work extremely slowly, predominantly in MSAccess2003.

Ahh... is there an av that is scanning "document files" while they are
in use? It's appropriate to do so, given that MS broke the data/code
distinction by allowing macros and scripts to be embedded in these
"data" files, and having these run automatically... but you can
imagine the performance impact of having a large Access database being
scanned every time it is updated or even cough accessed.

The shop failed to write zeros to my WD hard drive before they re-installed,
even though WD recommends that this should be done before any OS re-install,
so I think that this is a good place to start (in spite of your link).

I don't think that's likely to be relevant, as long as the HD was
file-system-formatted at the time.

What will trully clobber NTFS performance is if the NTFS volume is
mis-aligned so that it is created with 512-byte clusters. That can
happen if originally partitioned for FATxx and then converted to NTFS.

I'm using BING (www.bootitng.com) for partitioning, and that has a
setting to "align for NTFS" that I use even for FATxx volumes. Old
versions used to ask "do you intend converting to NTFS?".



------------------------- ---- --- -- - - - -
I'm on a ten-year lunch break
------------------------- ---- --- -- - - - -