Seagate 160 SATA Drive & Neo-FIS2R mobo

Everyone, I need your help for a newbie.
I have installed a Seagate 160mb SATA drive as my primary bootable drive on a Neo-FIS2R mobo. I have successfully moved my partitions etc from the previous drive (80GB Seagate IDE drive).
The system boots fine, Windows XP sees the drive but everytime Windows XP starts, it pops up messages saying New Hardware found and tries to install the SATA drive under the IDE ATA/ATAPI Controllers section in Device Manager.
Under this section in Device Manager, I see 2 IDE Channels defined with yellow circles and exclamation marks inside the yellow circles.
I have 1 IDE drive attached as well and maybe later another IDE drive will be added.
What settings do I need in my BIOS? Are there drivers required to be installed in Windows XP?
Thanks for your help. This is driving my crazy!

In bios under Integrated Peripherals, On Chip ATA Operating Mode set
Native Mode
ATA Configuration - PATA only
SATA Keep enabled - yes
PATA Keep enabled - yes
PATA channel selection - both
This should let you boot from the SATA and see the PATA.

Similar Messages

  • Not detecting sata drive on ms7021 mobo

    I wonder if someone can help. just bought sata 80gb diamond max hdd.
    set it up with maxblast.when i start os disk it says no hdd detected.
    could some one take me thru setup or point me in the right direction
    I have never setup sata before.I am doing just one drive.
     any help will be welcome, Thanks

    TireSmoke sez:
    >>>Sata drives do not show in the Bios like IDE does. As Sata is not a native drive type like IDE you have to install it's drivers when you install Windows.<<<
    I've been mystified by the comments regarding BIOS detection, or lack thereof, of SATA drives.... maybe I'm missing something here, perhaps it's just due to the board I have not exhibiting these problems. The first time I booted up my RS482M4 the Maxtor DiamondMax 300g SATA drive showed in the POST, entering the BIOS it was identified correctly.
    >>> That means when you pop in that Windows CD you also need to pop in the driver Floppy disk that came with your MB. Then start the Install by booting from the CD. At the first blue install screen you need to tap the F6 key to load extra drivers. Windows will then prompt you in a few minutes when it is ready for the extra drivers with a window for chosing that driver from the disk. You will be OK after that as your Sata will show up in the list of Drives to Install Windows on. <<<
    Wouldn't these be *Windows* drivers... which would do *what* for the BIOS detecting the drive? The floppy that came with my mobo was labeled "RAID" drivers. Since I wasn't planning on running RAID I didn't install 'em. Everything appears to be working fine as far as I can tell. I *did* get an education on the XP 137gb limitation though <g> SP2 took care of that problem and an additional partition and logical drive allowed access to the entire drive. It always showed up in the BIOS correctly though.
    One of the things I was wondering about in the BIOS was the ability to select either enabling RAID, "enable as an IDE device" or enable as "Storage". Enable as IDE was the default.... was the diff if one was to select "storage"?
    TL
    MSI 7191 / RS482M4-ILD v1.1 - AMI BIOS v1.1
    Athlon 64 3200+ Venice
    2x512 Patriot dual channel
    300g DiamondMax SATA

  • What ram should i get for a neo-fis2r mobo

    im building a new system and i was wondering what is the best ram for gaming in this mobo.
    Thanks,
    Infern09

    don't go with cl2 becouse this mobo hates it and instability will never end
    and don't go with HYPERX pc 3500 its like  & it really sucks
    go with CL2.5 it is the best CL with this board
    if you overclock they will tell you go with higher pc like pc3500 , pc3700
    thats a big wrong, any thing higher than pc 3200 sucks
    pc 3200 o'c like hell    
    and forget about HIGH & TIGHT timming it really doesn't matter just go with larger
    capacity
    thats what i learned with this board after spending alot of $$$$ on RAMS
    GOOD LUCK any way  

  • MOVED: K8T Neo-FIS2R SATA and Linux Question

    This topic has been moved to Operating Systems.
    K8T Neo-FIS2R SATA and Linux Question

    Quote
    Originally posted by chasmon
    Hi all,
    I have just setup up a brand new system but am having probelms getting it working. I want to install XP on a single Maxtor 160Gb drive.
    I have my HD on Promise Ser1 and all SATA stuff in BIOS enabled. When I get to the screen I press F6 and then when promted I insert the floppy with the promise drivers on. I then get this message:
    "File txtsetup.oem caused an unexpected error (4096) at line 1742 in d:\xpclient\base\boot\setup\oemdisk.c"
    I can't get past this screen I have tried:
    1.Drivers from the CD supplied.
    2.Drivers from the MSI website.
    Please help me this lot cost lots of hard earned I'm pretty gutted at the moment. I have also tried the Via chipset with no joy.
    System:
    Antec 380W PSU and Sonata Case
    LG DVDROM 8163B
    NEC DVDR/RW 2500B
    Panasonic Floppy
    Neo FIS2R mobo
    Maxtor Diamondmax Plus 9 160Gb SATA150
    Benq RF K/B & Mouse
    Don't spam man! I posted something to this same question in another thread.. from you no less! Make a new thread! lol
    Hijacking = bad!
    Ian

  • MSI K8T Neo-FIS2R SATA CD/DVD Support

    Does anyone know if the K8T Neo-FIS2R mobo will or can be made to support a SATA CD/DVD drive. I am having no luck so far either getting it to recognize the drive or finding any info as to such. 
    Any help will be greatly appreciated.
    Cheers

    I was able to answer my own question. I was doing a bit of searching around on the MSI website and happened across a newer bios that doesn't come up in a regular search. The regular search turns up this page http://www.msicomputer.com/support/bios_result.asp (obviously inputing the correct platform and model) showing BIOS v2.2 as the most current. But by poking around on the site a bit, I came across another BIOS page for the same mobo, http://global.msi.com.tw/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=565 showing BIOS v7.1. I figured I'd give it a try and low and behold the bios is recognizing my SATA DVD Burner.
    The hd array has to be connected to the Promise controller as it will not see the optical drive even if it is set to SATA mode. I hooked the SATA DVD burner to the VIA controller and changed the setting in the bios for this controller to SATA mode as opposed to RAID mode (this was not an option on this controller in the BIOS before the flash to v7.1). I also had to have the PATA controller set to enabled or it would not recognize the drive. It is now a recognized device and shows up as an option in the boot menu. I added an additional SATA DVD drive to the other VIA SATA connector and it recognized it right away and made it available as a boot device. I tested with Knoppix and it booted fine.
    Hopefully when I try to load XP this evening, I will have a winner.
    Thanks again for your replies!!! 

  • K8T NEO (MS-6702 VT8237) can't find SATA drive

    I just got a Seagate 160gb SATA drive (retail).  In the bios settings sata is enabled (default), Serial Port 1 is on Auto (default) but I don't know where to look in the BIOS to see that the drive is recognized.  I felt the drive and it's warm so I know it's getting power.  Brand new SATA cable from the Seagate box.  I'm using the drive as the primary drive to install OS.  I downloaded "VIA VT8237(R) SATA RAID Driver (For floppy driver)". Put on floppy, restarted with my bootable XP disc, hit F6 when XP was starting setup.  It recognized the driver install (gave me driver choice of XP, 2000 and NT).  Picked XP and then it continues loading.  Finally says "no hard drive found" (or something like that).  I even tried keeping my IDE as primary so I could add it as a secondary drive in windows. Installed all the latest 4 in1 drivers, raid setup and everything and won't recognize.  This is my first SATA install so I guess I'm missing something.  I guess I shoulda got the EIDE to make it ez :(  Please help!

    Hi!
    Have a look at the connector you used. If you have the full K8T Neo, you have two SATA controllers. One VIA and one Promise. You then have 4 SATA ports on the board. you need to use the ones closest to your RAM, so, the upper ones.
    Did you buy a SATA or SATA-II disk? In case it's SATA-II, check the SATA/SATA-II jumper on the drive and set it to SATA-I. Your board does NOT support SATA-II.
    when you checked this, please verify in BIOS that you actually did enable the VIA V8237 SATA controller. When you did, boot further untill the POST screen disappears. Now, you see a VIA SATA BIOS screen. It should list your Seagate now.

  • Poor SATA performance, Seagate 160 GB on Neo2-S ?

    Hi there,
    I changed my drive. The old one is WD 80GB JB series, and I got the 29000-30000 results in SiSoft Sandra 2004Cnet ed.
    Now I have Seagate 160 SATA, I got the 22500 result in Sandra.
    My board is MSI Neo2-S (6728-010)
    865PE..op.sys. XP PRO,
    Kingston 256/400 x 2 Dual Channel
    What's wrong with it? Should I back my old drive ?
    Is there any software/patch/driver to work fast more ?
    Or SATA is better on in Raid0, if you using single drive SATA is a good choice or not ?
    Is that the problem because of Intel ICH5 chipset, If I will use Neo2-FISR2 the performance or better or not?
    Thank you.

    Thank you, that's good article. I got your point. But how can you explain The Seagate SATA 80GB disk got 30000 score on Epox8RDA3 ?
    Actually if you look at the Sandra referance scores, you can see the SATA120 has approximately 29-30k scores ?
    I just want to know ? Is the responsable for that ICH5 ?
    Best Regards.

  • [875P Neo Series] 875P NEO FIS2R - Bootup delay with disk attached to Promise RAID

    Hi,
    I have a problem with my 875P NEO FIS2R mobo. I just added a 400GB SATA RAID-0 array to the Promise controller and now I get a 50 second bootup delay after the BIOS has run through everything and beeped and before the first WinXP splash screen.
    I boot up from a 160GB SATA RAID-0 array on the intel ICH5R controller. Both arrays work fine from within Windows. I have two DVD drives on the ICH5R PATA connection but nothing else on the Promise.
    If I disable the Promise controller in BIOS the delay goes away.
    I have tried disabling SMART, turning off the quick-boot option with no effect.
    When I first installed my system I tested performance with booting from a single SATA drive on ICH5R vs Promise and I noticed the same issue, but didn't care then because I only needed one disk so I just kept Promise disabled in BIOS.
    Any ideas how I can get around this?
    Regards,
    Jonathan

    Sorry I have been a away for a few days.
    Details requested...
    Quote from: redeyedog on 21-June-05, 05:50:27
    If the Promise controller was out of the picture (Disabled), and you have the SCSI adaptor and its devices setup:
    1. What is the adaptor's SCSI ID?
    7
    Quote
    2. List devices, position in the chain and their corresponding SCSI ID's.
    #7 Adaptec 2930CU card
    #4 Nikon Coolscan LS30 scanner
    #3 Umax Astra 1220S scanner
    #5 Iomega ZIP 100 drive
    Quote
    3. What type of terminination are you using?
    Adaptec card has auto-termination.
    ZIP drive has a termination connector attached.
    Quote
    4. Are the devices in the chain functioning properly?
    Yes.
    Quote
    I agree that your problem is your SCSI controller. There may not be anything actually wrong with it. The 2930 was an agressive controller card and its BIOS simply may not coexist with your motherboard's BIOS optimally. Even with the BIOS disabled, it may be competing with the motherboard's request for handlers.
    You may want to check to see if there is a BIOS update on Adaptec's website. Adaptec usually released 1 or 2 updates for each SCSI generation they produced. It may or may not help but we need to make sure you have the latest BIOS released.
    Unfortunately, this card cannot be reflashed.
    Quote
    At any rate, I think you have found the component which is responsible for the delay. I'm willing to assist in diagnosing the issue but I need you to provide the specific information I'm requesting.
    Also, try to do a CTRL-Pause to catch exactly what the BIOS version is and any other information which is showing up with the BIOS disabled. The SCSI adaptor BIOS, in fact, should not be enabled in your SCSI configuration as you have described thus far.
    Adaptec AHA 2930CU SCSI BIOS v1.34.1.
    There seems to be a difference between BIOS and host adapter BIOS. You always get the BIOS screen, but you can disable the host adapter BIOS if it is not required.
    I am pretty sure it is not the SCSI chain that is wonr because the pause happens with nothing connected to the card.
    Jonathan

  • Help! XP install problems with K8T Neo-FIS2R

    The other day I put together a new system for a friend.  I got the system to POST properly, the diagnostic lights on the D bracket are fine, and I can edit the BIOS, and the BIOS sees all the drives properly.  
    However, installing XP Pro has been impossible.  I set the system to boot first to the CD, then to the hard drive (from the BIOS).  After booting to the CD, I never see the message I am used to seeing ("Press any key to boot from CD...) when booting from the XP Pro install disk.  The system thinks about things for a long time with a blank screen, then later it finally begins to do the install.  Things appear normal at this point as in any other time I have installed XP Pro.  I reformat the hard drive to start clean and then the XP install files are copied over.  I get the standard message that the system will reboot and this is where things get flaky.  The system reboots, but I never get the message once again on whether or not to boot from the CD.  So after a while the system tries to install XP once again (it would repeat this process forever....trust me).  I've popped the CD out right after the system reboots so it will try to go to the hard drive.  I just get some kind of boot failure message and to insert the bootable media or whatever.  I've even gone into the BIOS right after the reboot to switch the BIOS loading to try and load the hard drive first.  This still doesn't give me the desired results.
    This is by far the weirdest thing I've ever experienced when doing an install.  I've installed XP Pro on at least 15-20 desktops/laptops of different configs and never ran into this before.
    The BIOS settings are stock.  I didn't see anything in there that was really needed tweaking or that hadn't "set itself".  I haven't messed with the SATA or RAID stuff since it's not really necessary in this situation.
    Here are the system specs:
    --Antec 430 True Power PSU
    --K8T Neo-FIS2R mobo
    --AMD 3000+ 64 bit CPU
    --40GB Maxtor HD (master on IDE1)
    --Lite-On DVD-ROM drive (slave on IDE1)
    --80GB Western Digital (8MB buffer) (master on IDE2)
    --Sony DRU510A DVD-RW (slave on IDE2)
    --(2) Kingmax 184 Pin 512MB DDR PC-3200 Model# MPXC22D-38  
    --ATI 9800 Pro
    --3.5 Floppy
    All the components except the mobo, CPU, and memory are from another AMD system that was running fine.  No problems with any of the HD's or the optical drives.  All new components were purchased from newegg.
    I thought that maybe I had a problem with the jumpering of the drives so I messed with those in about every possible combination.  I took IDE2 completely out of the system and just tried to get it running with the 40GB Maxtor and the Lite-On drive.  I tried about every master/slave/cable select combination but nothing was working.  In certain combinations the BIOS recognized everything as I intended.  I've pulled everything off that doesn't need to be connected.  Keyboard, monitor, and internal components are the only things connected.
    I don't consider myself to be a guru at this business, but I can get through most things with enough trial and error.  This really has me stumped.
    Any help is certainly appreciated.
    Thanks,
    Heath

    Quote
    Originally posted by chasmon
    Hi all,
    I have just setup up a brand new system but am having probelms getting it working. I want to install XP on a single Maxtor 160Gb drive.
    I have my HD on Promise Ser1 and all SATA stuff in BIOS enabled. When I get to the screen I press F6 and then when promted I insert the floppy with the promise drivers on. I then get this message:
    "File txtsetup.oem caused an unexpected error (4096) at line 1742 in d:\xpclient\base\boot\setup\oemdisk.c"
    I can't get past this screen I have tried:
    1.Drivers from the CD supplied.
    2.Drivers from the MSI website.
    Please help me this lot cost lots of hard earned I'm pretty gutted at the moment.
    System:
    Antec 380W PSU and Sonata Case
    LG DVDROM 8163B
    NEC DVDR/RW 2500B
    Panasonic Floppy
    Neo FIS2R mobo
    Maxtor Diamondmax Plus 9 160Gb SATA150
    Benq RF K/B & Mouse
    Download the drivers from MSI again, and when you copy the contents of the XP folder to floppy ADD the file txtsetup.oem from the directory above that folder. Worked for me..!
    Ian

  • KT4 Ultra FISR Single SATA drive only

    I have the KT4 Ultra FISR and just purchased a Seagate 160GB SATA drive.
    Can I use this as my only drive?
    Do I simply need to set the SATA as my first boot device?

    Sadly you will need the sata drivers. You should have your drivers floppy close when you start your windows setup, and when it tells you Press F2 to install third party controllers.. you must press it.
      Some steps before:
    First connect your SATA drive. Go into bios at Integrated Peripherals/OnBoard PCI Controller and enable Serial ATA Controller. After reboot you should see the FastTrack Bios - press Control-F and get into FastBuild Configuration Utility. Then chose Define Array, chose 16k stripe, save settings. Now use some software like Partition Magic to partitionate the SATA HDD. the rest will be done by the windows setup.  
        About your other question, is safe to keep the old HDD, some say better to use it on the IDE2 connector on the mobo and to disable from bios IDE1. I tryed and I didn't notice any diference.

  • K8N nForce 4 (CK804) and SATA drive problems

    Hi,
    I have a K8N Neo MB with a 4 port sata and RAID. It seems that it is not stable with sata drives at all.
    I had at first 2 120G SEAGATE drives. I kept getting random hangups from windows AND linux. I thought it was a problem with one of the drives to I booted with one of them at a time and worked a bit... it seemed the problem went away.
    but later, after a week or so, it seems everything comes back again. same problems with freezes and hangups.
    when windows for example freezes, and i press reset. at the boot screen, the POST would hang up at the step which detects the SATA drives. it would stay like this foreever.
    I would have to totally shut down power for a few seconds and boot again.
    I tried working with pata drives and its totally great and stable. no problems. if i install a sata drive with the pata, i get the same hangup problems.
    i bought another seagate 80gb sata drive just to make sure that the older 120gb were not a problem. it worked for me fine a t first, but started to do exactly the same afterwards
    i tried to access the drive from linux in order to trace the access pattern of the drive and get a sense of what was going wrong. Here is the syslog from the kernel messages.
    any help with that issue is highly appreciated. thanks
    Mar  8 22:01:15 ubuntu kernel: [  715.201288] ata1: command 0x25 timeout, stat 0xd0 host_stat 0x1
    Mar  8 22:01:15 ubuntu kernel: [  715.201297] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
    Mar  8 22:01:15 ubuntu kernel: [  715.201300] ata1: status=0xd0 { Busy }
    Mar  8 22:01:15 ubuntu kernel: [  715.201308] sd 0:0:0:0: SCSI error: return code = 0x8000002
    Mar  8 22:01:15 ubuntu kernel: [  715.201310] sda: Current: sense key: Aborted Command
    Mar  8 22:01:15 ubuntu kernel: [  715.201313]     Additional sense: Scsi parity error
    Mar  8 22:01:15 ubuntu kernel: [  715.201318] end_request: I/O error, dev sda, sector 39086208
    Mar  8 22:01:15 ubuntu kernel: [  715.201322] Buffer I/O error on device sda5, logical block 0
    Mar  8 22:01:45 ubuntu kernel: [  731.858112] ata1: command 0x25 timeout, stat 0xd0 host_stat 0x1
    Mar  8 22:01:45 ubuntu kernel: [  731.858121] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
    Mar  8 22:01:45 ubuntu kernel: [  731.858124] ata1: status=0xd0 { Busy }
    Mar  8 22:01:45 ubuntu kernel: [  731.858132] sd 0:0:0:0: SCSI error: return code = 0x8000002
    Mar  8 22:01:45 ubuntu kernel: [  731.858135] sda: Current: sense key: Aborted Command
    Mar  8 22:01:45 ubuntu kernel: [  731.858137]     Additional sense: Scsi parity error
    Mar  8 22:01:45 ubuntu kernel: [  731.858143] end_request: I/O error, dev sda, sector 39086208
    Mar  8 22:01:45 ubuntu kernel: [  731.858147] Buffer I/O error on device sda5, logical block 0
    Mar  8 22:02:15 ubuntu kernel: [  748.515491] ata1: command 0x25 timeout, stat 0xd0 host_stat 0x1
    Mar  8 22:02:15 ubuntu kernel: [  748.515501] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
    Mar  8 22:02:15 ubuntu kernel: [  748.515504] ata1: status=0xd0 { Busy }
    Mar  8 22:02:15 ubuntu kernel: [  748.515511] sd 0:0:0:0: SCSI error: return code = 0x8000002
    Mar  8 22:02:15 ubuntu kernel: [  748.515514] sda: Current: sense key: Aborted Command
    Mar  8 22:02:15 ubuntu kernel: [  748.515516]     Additional sense: Scsi parity error
    Mar  8 22:02:15 ubuntu kernel: [  748.515523] end_request: I/O error, dev sda, sector 39086208
    Mar  8 22:02:15 ubuntu kernel: [  748.515526] Buffer I/O error on device sda5, logical block 0
    Mar  8 22:02:15 ubuntu kernel: [  750.227687] Losing some ticks... checking if CPU frequency changed.
    Mar  8 22:02:45 ubuntu kernel: [  765.554638] ata1: command 0x25 timeout, stat 0xd0 host_stat 0x1
    Mar  8 22:02:45 ubuntu kernel: [  765.554651] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
    Mar  8 22:02:45 ubuntu kernel: [  765.554654] ata1: status=0xd0 { Busy }
    Mar  8 22:02:45 ubuntu kernel: [  765.554666] sd 0:0:0:0: SCSI error: return code = 0x8000002
    Mar  8 22:02:45 ubuntu kernel: [  765.554669] sda: Current: sense key: Aborted Command
    Mar  8 22:02:45 ubuntu kernel: [  765.554672]     Additional sense: Scsi parity error
    Mar  8 22:02:45 ubuntu kernel: [  765.554681] end_request: I/O error, dev sda, sector 39086208
    Mar  8 22:02:45 ubuntu kernel: [  765.554686] Buffer I/O error on device sda5, logical block 0

    the answer for this problem is very simple.. I was having EXACTLY THE SAME PROBLEM as you... I changed 3 hds sata 200gb because I wasnt finding out the cause... so I found this link:
    http://www.msi.com.tw/program/service/faq/faq/esc_faq_answer.php?L_kind=1&Q_LIST=1141&NA=637
    The problem is the NCQ technology... just disabled it and everything will be fine... i did this here and now is everything PERFECT! lol
    regards!

  • SATA drive no longer recognized???

    Hello all,
    I got the MSI Neo4 Platinum & A64 3000+ RevE and it was running fine. Then, last week, my board stopped recognizing my Samsung 160GB SATA HD. The drive is OK, I hooked it up to a friend's comp and it booted up normally. But now, It does not recognize the SATA drive in BIOS. I also have an old IDE drive (40GB Quantum Fireball...seriously) hooked up and the MB recognizes that drive. So, is this an RMA case or am I missing something? I've tried new SATA cables and all 4 SATA ports and different power leads. I don't have an extra SATA HD lying around that I could test the board with, so is there another way to make sure the SATA ports are operational? I was thinking about trying to find a SATA to USB connector and try the ports with my keychain flash drive. Think that would work just to test the ports?
    Thanks in advance

    OK more frustration,
    So, my friend lent me a 160GB Seagate Barracuda SATA drive to test. Neither his drive nor my drive show up in SATA ports 1-4. When I attach either drive in ports 5-8 (the Silicon Image RAID ports), I get a message as the BIOS is closing - when you get the screen saying to press F4 to enter RAID setup - that says "No valide device"  Must be Italian? But the name of whichever drive I had in those ports is listed...so at least the motherboard can see the drive in those ports, just can't use it. So maybe the SATA ports 1-4 are fried? But why are the drives Invalide in the SATA ports when they're definitely functional?
    Here's what I don't understand though... In the "Standard CMOS Settings" menu in the BIOS, under the date/time, I see 4 listings all for IDE (>IDE Primary Master, >IDE Primary Slave, etc.) but no listings for SATA. My HD used to show up in that menu, but I don't remember if it was under "IDE master" or "SATA master" Does anyone know what that should look like?
    The drive doesn't show up in the "Boot Order" either.
    Any ideas?

  • Should I flash the bios? K8T NEO FIS2R

    Ok... I have a K8T NEO FIS2R mobo.  A couple of friends of mine have been telling me to flash the bios to the most current version...  Then some other people have been telling me that it is too risky and I should hold off untill something goes wrong that I know a bios flash can fix...
    I'm just wondering what is the concencious here... should I flash it, or should I stay with the current version I have now(the one that came with the mobo)  I Like to have my computer as up to date as possible, but all the reports of bad flashes have me a little worried.  This is a procedure that I have never done before, and I dont want to mess it up.
    If I should flash, Any insight, tips, tricks, special instructions, etc... would be greatly appriciated.
    Thanks!
    Magnum

    Thanks guys for the quick responces...  I'm used to not getting a responce from forums for 12-24hrs and here it is less than 24hrs later and I have 10 responces.
    I'm not at my computer in question right now, but I am almost positive that my bios is ver1.0.  Same one that came with my mobo.
    At this point I am leaning towards flashing...  If basically the only way to mess it up is to have my power fail, then I dont think I will have a problem.  I'll just borrow an UPS from work here to be on the safe side.
    hypothetically if i follow the instructions to a tee(windows flash/live update) are there any other ways it can mess it up?  I just want to get a hold on all the places where I could mess it up.
    Will live update take me all the way through the procedure, or do I need a separate set of instructions to read off of during the flash?
    Also what gear will I need...  floppy disk? anything else?
    Sorry about all the questions, just want to make sure I do this right the first time!
    Thanks!
    Magnum

  • Problem adding SATA drive

    Hi all
    First time poster, long time lurker.
    Hoping someone here can shed a bit of light on an unusual problem I am having.
    Before I outline the problem I will say that my system is running beautifully, I've not got any problems with it in its current configuration, in fact it is the most stable set up I've owned so far.  I am a happy MSI owner.
    If I can get this issue sorted I'll be an extremely happy MSI owner. Now to the actual problem...
    I have a pair of 36GB SCSI160 drives that I use for my system and apps drives and a 120GB ATA drive that I use for storage.
    I've purchased a 120GB Seagate Barracuda SATA drive to add to my system as I've just about run out of space on the 120GB ATA drive, my storage drive.
    I installed the new drive, set it up as a single Raid 0 volume using the SATA boot utility and checked it all under DOS, tested all OK.
    The problem happens once I've booted into windows and enter my username and password.
    I get a BSOD, IRQL_NOT_LESS_OR_EQUAL STOP 0x000000D1 Error which then does a memory dump, do a reboot and same thing.
    Remove the SATA drive and system boots and works flawlessly, I'm typing this on it right now!
    I can have the SATA drive connected to the system and NOT have a volume on it and the system works fine, naturally WINXP doesn't see the drive but it doesn't interfer with the operations at all. As soon as I put a volume on the drive... bam, BSOD next time I try to login after I boot up WinXP.
    This indicates to me that the issue is a driver problem... I've tried the latest and still the same situation.
    Any suggestions folks?

    Quote
    Originally posted by Wonkanoby
    https://forum-en.msi.com/index.php?threadid=49947&sid=&hilight=scsi
    things like this are all over the board though yours does not sound totally the same
    Thanks for the link.
    Very informative. Appears that there isn't an option for me at this time other than NOT using one or the other... I can have SCSI card and no onboard SATA OR I can have onboard SATA and no SCSI card.
    Seems to me a BIOS revision is needed as it appears that this is not an uncommon scenario.
    Thank you for your time Wonkanoby.

  • Mac Pro (early 2008): older SATA drive compatibility

    I have 2 Seagate Barracuda SATA drives pulled from my PowerMac G5 and I'm wondering if they are compatible with my new Mac Pro (early 2008) 2x-2.8 Quad.
    500 GB Seagate Barracuda 7200.9
    250 GB Seagate Barracuda 7200.8
    Will the drive bays on the new Mac Pro accept these drives?
    Thanks.

    I just put in a WD Caviar 750GB. To say it is faster than any other 7.2K drive I've used is an understatement. Never dreamed I'd ever see 90+ MB/sec, not without 15K drive. Tops out even my 10K Raptor which turns in 89MB/sec.
    When did the 7200.8/9 come out? 3-4 yrs is a lifetime for a disk drive.
    But if you just want something that works, they should be fine for your needs. There was a time when 75GB ATA drives were the new best thing, or 180GB that cost nearly $300 when it came out and first introduced a 'huge' 8MB cache vs 2MB that was being used.
    I would reformat and reload the data, serves to insure the data is backed up, then reloaded, especially if it was formatted until an OS older than 10.4.4.

Maybe you are looking for