Jump to content

Flagg

Members
  • Content Count

    46
  • Joined

  • Last visited

About Flagg

  • Rank
    New Member
  1. I've been running XP SP2 for about four months now with no problems at all. And that security notification can be turned off, FYI.
  2. And whatever you do, make sure you only have your raid array connected to your motherboard when installing Windows XP. That was my mistake, having my ide drive still connected, everything works great until you try to disconnect it, and you won't be able to access your raid array because the boot record is on the ide.
  3. That unfortunately didn't work, I now get the 'NTLDR is missing please reinstall' problem when I try to boot from the Raid drives. I'll just go ahead and redo my Windows installation but this time I'll disconnect my 120gig first!!! Thanks for the input.
  4. Good idea thanks. I was also considering seeing if I could do a repair installation but I seem to recall that option only being available if you run setup from Windows. I'll try the console when I get home
  5. This sounds similar to my current problem, except mine all works fine as long as I have a hard drive plugged into the ide port. I can dual-boot Win XP on each but can't access the raid array with the ide drive disconnected :-( I followed the above procedure to the letter, formatted in the raid setup screen, installed drivers at F6, etc. It all worked fine and I thought I was home free until I disconnected that 120gig.
  6. I was thinking the same thing regarding the mbr. I do have everything set correctly in the bios, except I've been trying to use my first boot device as scsi, not ide0 or ide1. I'm wondering if having the ide cable still plugged into the motherboard with nothing attached to it is causing this problem?
  7. I've been running my 2 - 80gig SATA's in Raid 0 alongside my original 120gig and dual-booting Windows XP on each. My problem now is that when I remove the 120 to put it in another computer I can't recognise the 80's, just get DISK BOOT FAILURE. As soon as I connect the 120 back it all works fine again. Is there any way to get my system to recognise the SATA's without reinstalling Windows?
  8. I tested both my Maxtor 120gig ATA and my dual Maxtor 80gig SATA Raid for comparisons, screenshot attached. You can obviously see that the 120 is a little faster in access time, uses less CPU, has a little bit faster burst speed, but has less than half the average read speed. Surprising that the SATA setup is so much slower than typical expected SATA 150 speeds as per the chart :confused:
  9. That all being said, do you notice an increase in speed and/or response times during general use? Like that heavy-duty program that used to take twice as long to load up? Sometime the raw numbers don't mean as much in the real-world.
  10. Hence the confusion LOL. Thank god I went to SATA Raid and don't really have to worry about that anymore Now that I said that, I wonder what's in store for me when I get home and boot that thing up...
  11. I thought most people had a problem with this? My system does not boot with my drives set to 'LBA', but work fine on 'AUTO' :confused:
  12. I've noticed a difference just in overall system speed, let alone in hard drive access times, by going to dual Maxtor SATA in Raid 0. That's coming from a Maxtor 120 Gig w/ ATA133.
  13. And invest in a Bios Saviour. You won't regret it, especially if you decide to start over-clocking and/or messing around with your bios versions
  14. Thanks a lot, bit more info in your post than the sticky; appreciate the feedback :nod:
×
×
  • Create New...