• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About darthgrader

Profile Information

  • OS
    Windows 7 x64
  1. normal HDD likes your WD are not slow-downed by SATA2. No normal HDD is so fast. Only SSDs reach the limits. You can try to update the BIOS and load the default setting and try to install never AHCI drivers. If nothing helps, try a PCIe card which provides additional SATA ports. I deleted the active partition of WD 3 TB drive and created two partitions of 2 and 1 TB. The system now boots in less than 23 s. I guessing this has something to do with how Win 7 64 bit handles drives greater than the 2 TB limit for non 64 bit OS. Not real happy with this solution but I haven't found another one yet.
  2. With SSD only you have a delay in SMSS mostyl caused by the driver SiRemFil.sys: This is the Silicon Image SATALink controller driver. So I asked this after your first post. The detection of the drives was slow, so connect the WD and the SSD to different SATA ports on your mainbaord. Tghe same delay is also present in all other traces. "Connect the WD and SSD to different SATA ports." Here is the thing. The board has two Marvel SATA 3 ports, which it says not to use for the boot drive, two other SATA 3 ports. The two drives in question are SATA3 drives. If I connect them to SATA 2 ports (there are 4) it will slow down their performance in transferring data. (by the way, I have two internal SATA optical drives connected to two of those 4 SATA2 ports) I have already tried the WD 3 TB drive on the Marvel SATA 3 port that is not shared with the eSATA port and it had no effect on the boot time. Not even a minimal effect, none. I had the WD 3 TB drive on a SATA 2 port, which one I do not recall, and again it made no significant difference in the boot time. So the question then is, exactly what is it that you want me to try? I am happy to give it a go but I don't know what it is you think I should do here that I have not already done.
  3. http://dl.dropbox.com/u/84817323/boot_BASE%2BCSWITCH%2BDRIVERS%2BPOWER_1_SSD_1TB_3TB.zip http://dl.dropbox.com/u/84817323/boot_BASE%2BCSWITCH%2BDRIVERS%2BPOWER_1_SSD_1TB.zip http://dl.dropbox.com/u/84817323/boot_BASE%2BCSWITCH%2BDRIVERS%2BPOWER_1_SSD.zip If attaching files actually works on this site, it is not obvious how! It says it will, the files are under 500 k, as required, the files show up in the required window, then nada!
  4. Trace for SSD only attached.
  5. Since it boots in 19 s with the two WD hard drives disconnected, I am wondering how the firmware of the OCZ drive could be an issue? Also, since it boots in 22 s with the addition of the 1 TB black WD drive, it seems the issue must be directly related to the addition of the 3 TB WD green drive!! With the OCZ and 3 TB drive the boot time jumps to the 95 s mark. No drives are currently connected to the Marvell controller. Connecting the 3 TB drive to the Marvell controller made no significant difference to the boot time. Neither did changing the respective ports of the other drives on the non Marvell ports. All drives are running in AHCI mode. The OCZ drive and th 3 TB drive are both Sata 6G drives and are both connected to those ports on the MB, although I did try other ports for the 3 TB drive to no avail.
  6. Dropbox took an overly long time to upload, about an hour for 110 K file! Surely there is something faster than that! If I had compressed the file would I have been able to attach it to my message instead of using Dropbox?
  7. I am looking for assistance in shortening my boot time to some thing reasonable. Slow boot up with windows 7 64 bit. Asrock Z68 Extreme4 motherboard, 16 GB ram, AMD Saphire 5770 video, 240 GB OCZ Agility Sata3 SSD, 1 TB WD black internal drive, 3 TB WD30EZRX internal drive. Boots in 19 s after bios with internal drives disconnected, 22 s with 1 TB drive connected, but 97 s when 3 TB drive is added. Last bios update for MB installed. Latest Windows updates installed. No firmware update for the WD30EZRX drive that I am aware of. FWIW, I orignially used ghost to transfer the contents of a 1 TB drive to the 3 TB drive, which turned the drive into a 2 TB drive requiring a removal of partion etc to restore to a functioning 3 TB drive. I ran trace but I will admit it means little to me. It might mean more if I disconnected the 3 TB drive and ran it then so I could compare the 22 s boot to the 97 s boot with the 3 TB drive added, but this is not really my strong suit. I believe I have attached the trace file, but if not I'm sure you will let me know. Thanks! Link added: http://dl.dropbox.com/u/84817323/TraceLog120606.zip