That O & O is very nice, I have never heard of it before, but giving it a try, it is well worth it.
I think I tried that one once... is that the one that can defrag while you're in screensaver?
2009 MULTI CORES CONTEST STATS
http://neogen.amdusers.com/contest2009/contestoverall.htm
CHRISTMAS QUEST CONTEST STATS
http://neogen.amdusers.com/contest2008/xmascontest.htm
http://neogen.amdusers.com/contest2008/stats.png (snapshot)
FEBRUARY '08 RACE STATS
http://neogen.amdusers.com/contest2008/racefeb08b.htm
http://neogen.amdusers.com/contest2008/racefeb08nb.htm
Hi NeoGen
I don´t know. When I run it I had stopped all programs as Boinc, Panda (Virusprogramme) and WhatPulse. I think it isnt good have antivirus running at the same time.
Lagu![]()
Once an AMDuser always an AMD user
[quote="Lagu"]=
There are some strange things. The disc as have a size of 80 GB seems to have more than it says. The disc should be 81 GB instead for 80 GB.
The other disc seems to be more correct say 40.02 GB./quote]
Maybe thats the same explanation as I gave earlier except there taking everything as 1000 chunks whereas Windows is correct at 1024 chuncks?
I mean what happens if the manufacturer's take a Mb as 1000Kb but MS 1024Kb?
Yea, they also have a screensaver version @ their website. I haven't used it, but i guess i will when trial runs out since it says it's free.Originally Posted by NeoGen
yeah its just the rounding. On a small drive it isnt too noticable but as the drives get bigger so does the size lost.
AMD-USR_JL![]()
Ya, way to post that here. ;)
![]()
Works better if you copy it and paste into Notepad where there's no formatting :p
Anyhow...whast the benefit of running that over the MS one?
Guys,
In reference to the disk space usage. It is important to understand block sizes (Microsoft call them cluster sizes), as it is the size of the block that greatly affects not only disk usage but disk performance.
If you use FAT32 then it has a scaling block size which is dependent on the size of the volume. If you're using more than a 32GB volume then it will have 32KB blocks. Now if a 33KB file is written then it will use two of these blocks and phyisically take up 64KB of disk space. Very inefficient use of disk space.
If you're using NTFS then it has a uniform block size of 4KB. So if you write that 33KB file to an NTFS disk it will use 9 NTFS blocks which total 36KB of disk space. By the way, even though NTFS uses smaller block sizes than FAT32 it is still a higher performing format as it's tables are in binary and so do not need to be read as many times as the old FAT32 format.
In UNIX/Linux and on servers you would change the block size based on the type of access and usage it requires. The larger block sizes are more suited to large files for example databases that require fast and large read/write access. Small block sizes are typically better for system partitions and small file access.
Hope this helps!