rseiler

Member
  • Content Count

    23
  • Joined

  • Last visited

Everything posted by rseiler

  1. rseiler

    Drive indexing

    Actually, it doesn't, a couple people there were just an argumentative sort and refused to face the facts. I'm not the only one seeing this and it's easily documented, as I did in the thread. Note that those with 1GB or less will tend not to see it, because SuperFetch doesn't do much fetching with so little RAM. Fortunately, I'm in position to have gotten MS's attention on this, and the suggestion for SuperFetch configurability is officially logged with them.
  2. rseiler

    Drive indexing

    I definitely think that you can't say SuperFetch definitely shouldn't be disabled, since it's behind one of the most common complaints about Vista: "Why is my disk light solid red so often?". Read some of the debate about it here: http://forums.anandtech.com/messageview.as...hreadid=2000877 So for me it was a case of diminished returns: Do I want some apps to load a little faster at the cost of the system often feeling like I'm doing a mass file copy in the background? No. I will enable it again if/when MS allows us to configure it. First thing I'd do? Exclude my data drive, which contains massive VM and multimedia files. SuperFetch LOVES those.
  3. rseiler

    VISTA AAM control

    And I didn't have any luck with HDD Scan either (even with "Run as Administrator"). Boot DOS and run the Hitachi Feature Tool, which works great. It's not like you have to set it more than once anyway.
  4. rseiler

    Drive indexing

    I'm assuming that's what he's talking about (i.e. modern search engines), as opposed to the indexing service in 2000/XP, which was a semi-functional joke. The one that's everywhere in Vista is a godsend and lightning fast. I particularly love what it's done for the Start menu. BTW, unless you have a HUGE amount of data, indexing pretty much finishes its work early on, and you really never see it working obviously again, since your data only grows slowly in most cases. MS was also very smart about limiting the scope of what's indexed. Now, SuperFetch, that's the troublemaker, since you CAN'T limit its scope. It precaches everything you've ever touched, no matter what size it is. 8GB VM file? Let's precache it. I disabled it early on.
  5. rseiler

    pata, sata or sata 2 ?

    Yes, an sata2 drive will work fine on an sata controller. In some cases, a jumper is provided to put the drive into sata mode, and if that's available, use it. There's no reason to get a pata drive, unless it's a lot cheaper. There will be no performance difference because of the interface choice. More about that here (where drives, regardless of interface, top out at about 85MB/s): http://www.tomshardware.com/2007/03/05/und...ance/index.html
  6. How new is the AAK exactly if it's newer than the AAE? I ask because I just bought a 7200.10 320GB PATA, and when checking its warranty the date came back March 10, 2010, which means it was made less than a month ago (date code of 07283, whatever that means). The firmware? AAE.
  7. rseiler

    Maxtor DiamondMax Plus 9

    That's really awful. The warranty situation for many drive vendors is confusing and in flux, but Maxtor made that 3-year declaration you mentioned for this model of drive "purchased on or after May 12, 2003." The question is, what was it before that? Maxtor actually increased their warranty?! Note that you can get into their Support section and enter the drive's serial there just to double-check what they're saying. A loophole might be that the warranty kicks in from the date of purchase, not the date on the drive....
  8. rseiler

    Maxtor DiamondMax Plus 9

    J-frog, that makes sense, since it's a small drive with a single platter. It's a different story when you get three platters in there, which the larger DM9's need.
  9. rseiler

    Maxtor DiamondMax Plus 9

    I was recently able to compare a Maxtor DM9+ 200GB 6Y200M0 dated 4/21/04 with an identical one circa late summer '03 (both Y6 serials). The old one is YAR51BW0, while the new one is YAR51EW0, so it's odd that the ones you reference, with a wider range of dates, remain the same. I wish I knew what the firmware change means in this case. Not sure what to say about write numbers, but maybe try 2.7? A note about these drives (at least mine): they run damn hot. Have good cooling, or on a warm day you'll pass 50C without trying. By comparison, my Maxtor DM9+ 160GB 6Y160P0 runs quite cool (typically 15C cooler!), and I think part of the reason for that is that the 160GB is a Y4, meaning two 80GB platters. The three platters in the larger drives apparently make a large difference, at least in this case.
  10. Before taking action with replacing the drive, I'm trying to figure out what's normal. My Maxtor DM9+ 200GB SATA (6Y200M0) runs 15C to 20C over case ambient. And with case ambient often around 30C, that puts me around 50C or a little more quite often. Now, you may be thinking case problems (I use as both case fans, all it allows), but then how to explain what happens if I put a Maxtor DM9+ 160GB PATA (6Y160P0) in there instead: it runs at or just a few degrees above case ambient! Clearly something is out of whack with the larger SATA drive. If platter density or the number of platters have anything to do with it, I list that data below, and I encourage anyone reporting back here to do the same: 6Y200M0 (Sep 2003), Firmware YAR51BW0, Serial Y6... Therefore 6 heads, 3 platters each 68GB 6Y160P0 (Sep 2003), Firmware YAR41BW0, Serial Y4... Therefore 4 heads, 2 platters each 80GB Thanks
  11. True, but as I'm thinking about that now, with the exception of the 100GB/platter drives that just came out, it seems to me it's impossible to get away with using only two platters/four heads once you hit 200GB. If this is the key factor, shouldn't more people with other drive brands of this size or larger be seeing these kinds of temps? I wonder if more things play into it, like how well the firmware is directing the drive in its actions.
  12. continuum, yes I've touch-tested both of them, and the 200GB is noticeably warmer. Your Maxline Plus II seems like a very similar drive, but I think it has 83GB platters, which may be what's keeping things in check for you. I'd be very happy with only a 10C rise. So far, the comments indicate that my flavor of Maxtor is not exactly the coolest in town, and summer's not even here yet. Short of directing a gale force at it, which is not possible with my case, I guess the question is what these seemingly "normal" hot temperatures mean, as Zstation mentioned. For such a similar drive as the 160 to be dead cool by comparison is puzzling, but if it's not the platter situation causing that, I'd like to know what is. I think the latest version of the 200's do come with 80GB platters.
  13. natrap, check out your IDE configuration section. The feature essentially makes programs think the drive is running on a standard IDE controller. I really don't know how prevalent this option is, but it can be handy for the odd program like this one.
  14. A couple notes: -Maxtor's AMSET (http://tinyurl.com/3fpsd) does work fine for SATA drives, at least for me, if you go into the BIOS and temporarily set your SATA into "legacy/compatibility" mode (terminology may vary by vendor). Then just set it back afterwards. -In response to the first message, even if you're using the Hitachi tool, for a Maxtor, there are only two AAM settings: quiet and fast. Quiet: Quietest seeks, the speed of the seek operation is reduced to its lowest level to provide the quietest operations, this level has the most impact on drive performance. Fast: Fastest seeks, the speed of the seek operation is reduced to provide quieter operation with the least amount of impact on the drive performance. The default is FAST. I've seen more than one person say they can't hear the difference between Quiet and Fast, though I'm sure that varies by drive. You can also use the utility to turn the feature OFF for maximum performance. -Someone mentioned not knowing what's causing disk activity. This is the tool for that: http://www.sysinternals.com/ntw2k/source/filemon.shtml -Maxtor put out an excellent article (http://tinyurl.com/yqrn7) that gives quite a few thresholds and guidelines to keep in mind about heat. They say the magic temperature to keep below is 55C. -An alternative to DTEMP is HDD Health: http://www.panterasoft.com
  15. rseiler

    Maxtor DiamondMax Plus 9

    Is this right or is it guesswork? 1) 6Y160P0 (Sep 2003), Firmware YAR41BW0, Serial Y4... Therefore 4 heads, 2 platters each 80GB 2) 6Y200M0 (Sep 2003), Firmware YAR51BW0, Serial Y6... Therefore 6 heads, 3 platters each 68GB The reason I'm interested in this is I'm trying to figure out why the latter drive runs warmer. More platters/heads, I guess, would explain it.
  16. I think the big question is how accurate a given drive's sensors are. I have one of those indoor/outdoor digital thermometers with a probe attachment at the end of a wire lead, and I think I'll use it to see if the top of the drive compares with the SMART data. Has anyone here tried this already and seen a notable difference? I came across this interesting Maxtor article (http://tinyurl.com/yqrn7) which gives quite a few thresholds and guidelines to keep in mind. They say the magic temperature to keep below is 55C. According to DTEMP, my Maxtor DM9+ 200GB SATA drives pretty much stays around 41C or 42C (when the room temp is around 18C), so I may have something to worry about come summer. The weird thing is that my Maxtor DM9+ 160GB PATA drive runs about 10-12C cooler, consistently, and it has nothing to do with where it's positioned in the case, either (I've swapped them). Either the temperature probes in these things are whacked, or the varying, what, platter density(?) in these basically identical models makes a huge difference.
  17. rseiler

    Maxtor DiamondMax Plus 9

    Out of curiosity, why aren't you using Maxtor's acoustic management program on your Maxtor drive? Who knows if those range of numbers you see with the IBM utility are even applicable to Maxtor, which as you see further up this thread has three modes only. What you did is probably put it in "quiet" mode from the default "fast." It's my understanding that these utilities reduce the activity seek noises not the overall spin or hum. I don't know if HDTach is accurate at all or an appropriate benchmark for this task. With my two Maxtor's, a 200GB SATA and a 160GB PATA (both DM9+), the former measured 19.5 and the latter 17.5 with the default "fast" mode (which is not "off" and not "quiet" but in between).
  18. Google has failed me, please help. Here's the short version: What exactly can I do post XP install, or maybe at the F6 point when installing, to get the SATA drive to run in the so-called "Native" mode? Background: Intel 865GBF board (ICH5) with an SATA Maxtor drive hooked to SATA Port 0. I also have a PATA drive hooked to PATA Primary Master 0. The BIOS is set for "Enhanced" drive capabilities, meaning SATA and PATA are giving me everything they can. The BIOS is set to boot the SATA drive, and it does fine. XP SP1 installs fine to the SATA drive, and without supplying an F6 driver, I guess due to backwards compatiblity (see below). But once in Windows, I looked at DM and found this passage from the manual to be true, proving I'm in legacy mode: "In legacy mode, standard IDE I/O and IRQ resources are assigned (IRQ 14 and 15)." At the end of this article, there's some more information (basically saying to enable it in your BIOS, which I've done with the "Enhanced" setting), but not much: http://support.microsoft.com/default.aspx?kbid=812415 And I definitely did install to the 12GB NTFS partition I carved out of my 200GB SATA drive. My 160GB PATA drive is not even partitioned at the moment. Funny thing is, I could even boot a 98SE floppy and see the SATA drive (earlier FAT partition). I think because of this: "For compatibility, the underlying Serial ATA functionality is transparent to the operating system. The Serial ATA controller can operate in both legacy and native modes. In legacy mode, standard IDE I/O and IRQ resources are assigned (IRQ 14 and 15). In Native mode, standard PCI resource steering is used. Native mode is the preferred mode for configurations using the Windows XP and Windows 2000 operating systems." If I was using a PCI SATA controller, or maybe even a non-Intel one on the MB, I suspect that wouldn't be the case. Intel provides no disk driver for me to use with F6 or afterwards either. I do have the Intel Chipset Configuration utility installed, but that's as close as it gets. My SATA drive reads UDMA5 in DM, but that's not "native" mode according to the IRQ situation. Looking at the BIOS revision history (I'm running the latest), I do see "native" mentioned twice, with older versions: -Added work-around for IRQ sharing with Serial ATA native mode operation. -Fixed issue where Microsoft Windows XP legacy-to-native IDE runtime mode switching was not functioning. So there's gotta be a way to do this.
  19. rseiler

    Maxtor DiamondMax Plus 9

    Yes, you have to set your BIOS temporarily to compatibility mode in order for that utility to see SATA drives. It still might be worthwhile running some tests to see the difference between /off and /fast.
  20. Eric, I understand what you're saying, but this is a case where the BIOS is set one way and XP seems to ignore it. I have the BIOS set to Enhanced (native), not Legacy; there is no backward emulation going on, and I can see all SATA and PATA ports there. I could also set the BIOS to Legacy mode, which I actually need to do temporarily when I want Ghost.exe to be able to run and not lock up the machine, or if I want, say, the Maxtor acoustic management utility to see the SATA drive. But why doesn't XP see how the BIOS is set and run with it? Instead, by running the drive in UDMA5 (with those noted IRQ differences which supposedly proves native mode), it seems to be treating the SATA drive exactly as if the BIOS was set to Legacy.
  21. rseiler

    Maxtor DiamondMax Plus 9

    These are the three modes: /off - Turns Acoustic Management off, the drive operates at normal acoustic levels /quiet - Quietest seeks, the speed of the seek operation is reduced to its lowest level to provide the quietest operations, this level has the most impact on drive performance. /fast - Fastest seeks, the speed of the seek operation is reduced to provide quieter operation with the least amount of impact on the drive performance The DM+9 drives come with the latter setting, ON but fast. Has anyone run any tests to see how much of a difference moving it to OFF makes?
  22. That quote above about native being preferred is right from the Intel technical manual, so it can't be hardwired the other way. I'm prepared to reinstall as soon as I can figure out how to do this, even if there isn't a performance advantage (though I've seen others say there is, like 50% by some measures). Confusing.
  23. rseiler

    Fix for IBM 75GXP, 60GXP and 120GXP

    If A46A (or later by now) has been in drives for at least most of this year if not all of it, why are they still providing A45A?