Looks like a hardware problem. Commonly the RAM.

they claimed that this behavior was by design, although this little detail is mentioned nowhere in their documentation. .

If you're talking about Microsoft, of course they're gonna say that, because Microsoft don't care, they only care about NTFS.

I have just now noticed in your previous logfile that you are running on Windows 2000 service pack 1. That is very dangerous, you should seriously consider upgrading to service pack 4, and install all available updates. 

I agree!

Seems to work fine and JKDefrag seemed to only have done a little touchup after.

The pagefile location is fine for fixed pagefiles.

Well I'm surprised at that, it removed, as expected, JKD's free space and an analyse showed it had significantly mixed up JKD's zones (and took about 40 mins doing so). Also I think the pagefile position is fine on a low ram system but on a high RAM system that has little pagefile usage it just makes the distance the disk head has to move further when it needs to read data behind the pagefile. IMO, if the pagefile is to be moved, it would be best placed immediately after the disk data or just in front of JKD's spacehogs zone.

It don't have the same sort options, thus required to run JKDefrag again after,
especially if you like the -a 10 or -a 11.

They're only sort by name, descending and ascending, for the sort options.

Also, the pagefile is at the fastest part of the HDD.

It looks like Windows' fault, but dunno which component.

It's an arbitrary Windows defragmentation API limitation so Microsoft can force everybody to use NTFS.

You can get it here:

http://www.computeractive.co.uk/hdmanager8/index

But, hurry before it isn't offered anymore!

I just gotten it today and it can move the MFT.

This worked like a charm, because I wanted the unmodified files right at the beginning!   

I posted that here a couple of months back. It's not a bad program, can defrag the mft but it's built in full defrag is rubbish - takes ages and puts the pagefile near the start of the disk. Also on one occasion I tried the defrag it said it was gonna take 4 hours so I exited it (as it said I could) and my OS was gone, so whatever you do if you try the defrag just let it finish.
The partition functions seem to work well though.

Seems to work fine and JKDefrag seemed to only have done a little touchup after.

The pagefile location is fine for fixed pagefiles.

Your file system problem probably is because Windows wasn't shut down properly.

Most likely to occur when there's a blackout or brownout.

That would be exactly why you want a reliable UPS.

You can get it here:

http://www.computeractive.co.uk/hdmanager8/index

But, hurry before it isn't offered anymore!

I just gotten it today and it can move the MFT.

This worked like a charm, because I wanted the unmodified files right at the beginning!   

The write errors more likely are from Windows.

In most people's eyes, probably a bad hard disk drive.

But, this may be caused by bad RAM or wrong RAM settings in the BIOS.

OO OK! Then there should be a feature to change the clusters per block via a zoom in and zoom out.

Or use at least 50 clusters per block.

IMO, should use a 1 cluster per block map.

It looks like an ordinary server busy situation. Nothing happens for maybe 6-7 seconds, Firefox says "waiting for wws.kessels.com", and then the page loads in a few seconds.

"Waiting for" means unresponsive script or slow page generation, may mean that the server isn't getting enough processor time. Also, Web Shield, of Avast, can cause Firefox to hang with that message.

I had that problem with evga.com until I excluded evga.com in the Web Shield settings on a PC.

It's not a client-sided bandwidth issue, such as a bad modem or line or the ISP being a jerk by capping you, AFAIK, because it's not a dreaded "Connecting to" or hanging at "Transferring data".

I never saw this problem. PageDefrag don't touch files unless they're fragmented, AFAIK.

It appears to be fixed, at least for the majority.