installing a large HDD - conclusions...

Hello All! Well, in general it worked out... Almost. Installation. Win was not installed due to the fact that the percentage does not have time to process data flow. Well, or something like that. Treated by installing in BIOS prohibits DMA (and often also reduces PIO). And also _non-use_ of smartdrv at the entire development stage new screw and running setup with the /c key. This problem and its solutions are documented in Windows. Drivers. It was not possible to ban UDMA66. Branded program and BIOS configure UDMA 16/25/33/48/66/100 only for DOS, and Win their settings are indifferent - either UDMA66 or none. There is such software for ALi, but I haven’t found it for VIA yet. Moreover, Win ignores UDMA BIOS settings completely, but if you disable DMA in Win, then the PIO settings in the BIOS on Win have the desired impact. However, under Win UDMA66 I have it really works and everything is fine - I'm not having a problem there searched... But in some cases UDMA66 should be prohibited - if For some reason the computer can't handle it. Software In the Windows directory I found a file with a list of software that may not work if there is free space on the screw more than 2GB. I suspect that his list can be very strong enlarge...MS recommends not to screw all the extra space fill with swap... Access time and AAM. Turned on screw AAM (software noise reduction, screw I can’t hear it _at all!). And with maximum AAM on the lastsection installed Red Alert 2 after several attempts! Before that it was not installed due to mistakes (well, for some reason he thought so)... But it is not installed on the initial sections - there are errors in some There are no installation sites (where there are no AAMs), but they still occur in some specific places. In general, AAM of course good - because it’s quiet, but the speed of the propeller is as simple as DMA, although everything is UDMA66 Here is a comparison of IBM (Deskstar 305040) without AAM, with enabled to maximum AAM (there is no clear on/off at all - but a smooth coefficient setting) and Seagate 3.2Gb: This Drive (Normal): Drive Index 18653 This Drive (AAM): Drive Index 6776 This Drive (S): Drive Index 7616 EIDE UDMA66 27GB: Drive Index 13000 EIDE UDMA33 10GB: Drive Index 8000 EIDE UDMA 6.4GB: Drive Index 6500 EIDE 4GB: Drive Index 3500 Buffered Read (Normal): 47 MB/s Buffered Read (AAM): 6 MB/s Buffered Read (S): 18 MB/s Sequential Read (Normal): 27 MB/s Sequential Read (AAM): 5 MB/s Sequential Read (S): 10 MB/s Random Read (Normal): 6 MB/s Random Read (AAM): 4 MB/s Random Read (S): 3553 kB/s Buffered Write (Normal): 33 MB/s Buffered Write (AAM): 33 MB/s Buffered Write (S): 6 MB/s Sequential Write (Normal): 22 MB/sSequential Write (AAM): 21 MB/s Sequential Write (S): 10 MB/s Random Write (Normal): 6 MB/s Random Write (AAM): 5 MB/s Random Write (S): 3050 kB/s Average Access Time (Normal): 8 ms (estimated) Average Access Time (AAM): 2 ms (estimated) Average Access Time (S): 12 ms (estimated) By the way, I don’t understand why SiSoft Sandra writes that in AAM he has 2ms access... Apparently a test glitch, because in the AAM setup doc it says that there is access time It turns out to be about 18-20ms, but the test says 1 or 2. Although the system has become slower. Result. It is not yet clear why Red Alert 2 is not installed on this screw from a virtual image (VCD emulates 50x - large stream data?..), but it is installed from a CD, though only on the last one section and at the maximum AAM level. And it’s still not clear what access time with AAM is about 18ms, which is more than the old 12ms screw - but it can be installed on an old screw without any problems. F22-Raptor simply does not start from this screw, when starting writes that there is an error in some of its modules "file_RawLoadEx..." and this module cannot open any file. Because of a word "raw" I suspect that it climbs directly onto the screw and does not transfers the size to 40Gb... F22-Raptor is not particularly new toy Best regards, Evgeniy.