VIA RAID Combo Diskette?

Ok, so I'm building a new SFF PC using a  K8MM-V motherboard and a Western Digital SATA HD. I'm also using an external floppy drive to load the SATA drivers when prompted with F6. The disk that came with my motherboard did not work when loading these drivers, so I had to go and download the drivers and put them on a floppy disk of my own. When I get to the screen to load the drivers everything works fine. Windows goes on, loads its stuff, I hit F8, partition, etc. Problem is that after I partition the drive I am prompted to put the "VIA RAID Combo Diskette" in my floppy drive and press enter to continue before Windows goes on to setting up its files. I have no idea what this disk is. I tried the one that came with my motherboard and the one that I created, both yielding no luck. All that happens when I use those two disks is that I hit enter but nothing happens, like, the drive doesn't even try to access the floppy.   
Anyone know what this disk is, or if I'm doing something wrong? Any help would be appreciated. Thanks. 

Im having a similar problem.
I have Windows X64 bit edition with an Athlon 64 3200+
When I boot from the CD I press F6, it loads the drivers fine (that I downloaded from the MSI website http://www.msi.com.tw/program/support/driver/dvr/spt_dvr_detail.php?UID=574&kind=1 )
I then go through the other various steps and at the end when it begins to copy files (before the reboot) it asks for the VIA RAID Combo Diskette.
I try using the disk I already have - from MSI website.
I have also tried many times fiddling around with files and puting them onto the disk, from the X64 download from MSI.
No luck. Any help would be muchly appreciated

Similar Messages

  • Uninstall VIA RAID tool

    I mistakenly installed the VIA RAID tool from Live Update - however I only have 1 SATA drive and do not intend to add further drives. The RAID tool now loads at windows start up and I cannot find any options to prevent this or even to unistall. Any ideas?

    Just to conclude..
    BIOS doesn't show RAID (at all.. KM4M-V) - I also disabled 2nd SATA drivebut as I suspected the VIA RAID Tool still loaded at start-up. I was unsure about removing SATA RAID driver from device drivers as apart from the offending tool loading at power up everything was working sweetly. So I installed Winpatrol and removed RAID Tool from start-up items.
    Now I'm happy

  • Updating VIA RAID Bios on K8T Master-FAR 2

    How do I update the VIA Raid bios that came with the v.220D SATA drivers?
    I see the two rom files (6420R231.rom and 6420N231.rom) in the bios directory, but no directions on how to update the bios.
    Tim

    You don't. You have to wait for MSI to integrate any RAID BIOS improvements into a new BIOS release for the board.

  • MSI K8T NEO 2 VIA RAID & 2x120GB S-ATA Connection Problem

    Hello,
    I have 2x120GB S-ATA HDDs. I tried connect them to VIA Raid Controller (Raid 0), but Second HDD connected on S-ATA 2 is not detected .. I don't know why. I've connected them to Promis PDC 20579 and everything works fine. But now I wanna install Windows XP 64bit edition, and there are no 64bit dirvers for PDC20579, So I wanna connect it on VIA RAID, where drivers are available. Can anybody help me please ? (Can I lost my data if i reconnect from Promise to VIA ?)

    I agree, but it seems that the VIA controller is more sensitive to it then the Promise one
    Still, I think the entire SATA cable+connectors are poor design in total....rushed out the door so to speak....I wish they asked me....

  • K8T NEO - MSI/Via Raid Tool useless

    I am one of those unfortunate people who bought a K8T Neo FSR Motherboard (Mine has been replaced 3 times after failing totally but whose counting?). I am now having serious problems with my fourth version of this motherboard or at least I think I am. I am not sure!
    Let me explain:
    My SATA HDD Disk drives keep failing - or more correctly - I am getting messages from Windows Error Reporting that tells me there are disk problems. The exact error messages are reproduced below:
    Event Type:   Error
    Event Source:   viamraid
    Event Category:   None
    Event ID:                9
    Date:      31/08/2006
    Time:      8:32:41 PM
    User:      N/A
    Computer:   MASTER
    Description: The device, \Device\Scsi\viamraid1, did not respond within the timeout period.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 0f 00 10 00 01 00 6a 00   ......j.
    0008: 00 00 00 00 09 00 04 c0   .......À
    0010: 00 01 00 00 00 00 00 00   ........
    0018: 5b 09 00 00 00 00 00 00   [.......
    0020: 00 00 00 00 00 00 00 00   ........
    0028: 00 00 00 00 02 00 00 00   ........
    0030: 00 00 00 00 07 00 00 00   ........
    This is immediately followed by the following message:
    Event Type:   Warning
    Event Source:   Disk
    Event Category:   None
    Event ID:                51
    Date:      31/08/2006
    Time:      8:32:41 PM
    User:      N/A
    Computer:   MASTER
    Description: An error was detected on device \Device\Harddisk2\D during a paging operation.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 04 00 68 00 01 00 b6 00   ..h...¶.
    0008: 00 00 00 00 33 00 04 80   ....3..€
    0010: 2d 01 00 00 00 00 00 00   -.......
    0018: 00 00 00 00 00 00 00 00   ........
    0020: 00 00 00 00 00 00 00 00   ........
    0028: 57 87 00 00 00 00 00 00   W‡......
    0030: ff ff ff ff 03 00 00 00   ÿÿÿÿ....
    0038: 40 00 00 44 00 00 02 00   @..D....
    0040: ff 20 0a 12 88 02 20 40   ÿ ..ˆ. @
    0048: 00 00 01 00 0a 00 00 00   ........
    0050: 00 00 00 00 00 06 6c 84   ......l„
    0058: 00 00 00 00 60 36 62 86   ....`6b†
    0060: 00 00 00 00 f7 04 81 05   ....÷..
    0068: 2a 00 05 81 04 f7 00 00   *...÷..
    0070: 80 00 00 00 00 00 00 00   €.......
    0078: 00 00 00 00 00 00 00 00   ........
    0080: 00 00 00 00 00 00 00 00   ........
    0088: 00 00 00 00 00 00 00 00   ........
    I started getting these messages from a brand new SATA HDD which I immediately replaced. All went well for a week or so and then I started getting the exact same error messages all over again!
    Were both HDD's really defective? I am beginning to wonder!
    The practical implication of the above errors is that my computer freezes totally - I can't do anything at all - no mouse - no keyboard - no saving work - nothing! When I reboot and run Scandisk /F /R I sometimes get some disk surface errors but mostly I don't.
    To my way of thinking there are two possibilities:
    (1) Both these disk drives have genuine technical problems (ie such as surface errors)
    (2) The MSI/Via SATA disk controllers on the motherboard are faulty and this is causing disk errors or possibly even disk crashes (is this even possible? I don't know!)
    After the bad run that I have already had with K8T NEO motherboards please forgive me for being suspicious that my HDD problems really could result from a faulty SATA/HDD/Controller rather than genuine disk errors.
    To help resolve the issue I downloaded and installed MSI's latest SATA HDD disk drivers which includes the VIA RAID TOOL. The raid tool includes an option to "check the status of controllers and disk drives" and a system "log" which is supposed to record all error conditions/events that occur on devices it controls.
    The main problem here is that *IT DOESN'T WORK* !!!
    Just a short wile ago my system started acting strangely and then it froze again (third time this hour). I opened the MSI/VIA Raid Tool from the System Tray and checked the logs - There was nothing in them at all - and yet in Windows Error Reporting there were 5 distinct error conditions reported. Obviously the MSI/VIA Raid Tool doesn't work too well.
    I am at a loss as to what to do next. Has anybody out there had similar problems?
    What steps should I take to resolve these issues?
    Any comments/suggestions?

    Not sure how a scope can let you know if you are supplying enough amps. Ripple and noise are basically non issues as the voltages are further regulated on the MB before they get to the componant level.
    Almost everything is now regulated from the 12v supply unlike past systems were. As Watts do not tell how much 12v is being supplied by the PSU it is a non starter when you desribe your PSU. You can have a PSU that is 500w and only provides 8a on the 12v rail. That will not even allow an A64 system to startup. As is said over and over again in the forum don't assume that a 500w PSU will ruin your Rig. 24 or more amps on the 12v rail is recommended for a small to mid size build now days. More may be needed as you add parts to your system.
    As this is not a common problem on that board, and I should know as I built a fairly large rig from one... We need to have complete specs. Did you know that a high end ATi Vid Card can use more juice than many CPU's you can use on that board? See why this is a concern that we get all the specs?
    Like Hans said though I won't bother asking again either. Without some idea what we are looking at all we are doing is looking into a crystal ball. We would like to see if we can help but working with a crystal ball isn't in the tech manual.

  • Promise RAID vs. Via RAID

    When I was setting up my system I wasn't really sure which RAID controller I should use in order to get the best performance...I opted to go with the Via controller as it is an integrated part of the KT800 chipset whereas the Promise RAID controller is an optional add-in chip (or such is my understanding), so I figured using the Via controller would give the best performance...but I'm curious as to how the Promise controller performs.  Has anyone tried setting an array up both ways and testing to see which controller performed better?
    I'm running two 36 GB WD Raptor SATA drives in RAID-0 off the Via controller, and I get a score of 61 MB/sec in Sandra 2004's File System benchmark...if anyone is running a similar array off the Promise controller and could post their benchmark results, I'd appreciate it.

    I've 'tested' both controllers.
    Before the K8T, I was using a KT4 ultra with a Promise 376 and two raptors RAID0 (around 60-70Mb/s with HDTach)
    Then I switched to the Promise 378 of the K8T (I keep promise to keep data). A little bit better than with the 376 of the KT4V but not very clear. I recently put the two raptors on the VIA. A little bit better but again, not very clear. It seems however that with the VIA the output is more 'unstable' .. I mean: with Promise, HD Tach gives me a straight line from the begining of the disk array to the end; with VIA, it's less straight.
    I think I will crash my RAID 0 to test with one raptor on the VIA and one on the Promise. OSsystem for a disk, software and apps for the other one. I'm not sure that it's a goo idea

  • [Athlon64] Preventing VIA RAID during boot with a K8T Neo?

    Is there a way to stop the VIA controller looking for RAID devices on a K8T Neo MS-6702 VER 1.0 board?
    The system has a single SATA connected to the VIA controller.
    Thanks.

    It's looking 4 disks, since u have a disk, and use it, i gues u want it to be found 
    It's the same thing with IDE devices, only thing is that the message is displayed shorter, giving the impression it works faster.

  • Via Raid

    Hey all,
    I have a Seagate 160 SATA HDD. I have just purchased another of the exact same make and model. I already have my OS built on my existing HDD. Can I add the new drive and build the array without reformatting and starting over? I hear of nothing but problems with the Promise RAID so I will go with VIA.
    TIA

    OOOF ! That is going to be some serious work .
    Well thanks for the info and speedy response .

  • VIA Raid 0: Red screen of Death - fatal error during boot sequence

    I have been using two Maxtor 120GB SATA drives in a RAID 0 array on my Athlon 64 MSI MB.  I have occasionally had messages saying "Hard disk error. Can't find drive 0".  I've assumed that this has been a driver issue because if I power down, wait a while I can reboot and continue without issue (other than chkdsk running during boot up).  However after the last such error, when I next tried to reboot I got an error message as the RAID was initialising.  The error message was in a red box on a black screen and stated that there was a fatal error and that the raid relationship and all HHD would be destroyed if I continued.  Naturally I switched off at this point, but on rebooting got exactly the same message.  Eventually, as I have backups, I continued past this point and sure enough the RAID had gone.  So I rebuilt the raid array and everything seems to be OK.
    However, I'd forgotten that my MSI DVD burner was incapacitated due to a failed firmware update so had temporaril;y replace it with a DVD rom drive to get access to my backups.  BUT the drive won't read all my backup discs, in particular it won't read the Drive C backups .
    Has anyone else had this RAID erro.  Is it a driver error or is it a dsik failing (even though they were new at Christmas).
    I am using a Superflower power supply which has 22A on the 12V rail
    1GB PC3200 ram by A-Data (CAS 2.5)
    Elderly HP 9100 CDRW
    MSI DR-8 DVD RW
    Ethernet card
    Radeon 9600 128MB
    AMD64 3000 processor
    Freeflow

    Raids do not really help benchmarks unless you considure hard drive benchmarks. Most games and benchmark proggies load everything they need prior to running. So unless you have a low memory condition that forces the game or benchmark to use the swap file the only place that you would typically see any gain in speed is during the loading of the game or benchmark. That is hard to quantify other than through experience.
    Where a raid shines is in file tranfer situations. When you create and save large files such as movies, Reading or copying large files, defragging, or any other massive file effort. Overall the gains can be very small compaired to the rest of what you do with your system. However that is not to belittle what a Raid does. It does give a finer sheen to the overall computers operations and will make sluggish file transfers seem much more bearable overall.

  • Moving from VIA RAID controller to another RAID controller?!?

    Hello
    I'm going to install a RAID-1 with 2 SATA harddisks from seagate using the onboard VT8237 RAID controller of my KT6 Delta.
    I guess there should be no problems and that the temperature on the motherboard will be fine.
    However, what will happen if I want to move later on to a new motherboard with another raid controller or install a dedicated RAID controller?!?
    Will I loose all my data?  Or will the new raid controller duplicate the data based on the source drive?
    Thanks
    JohnQM

    I have read somewhere that the following migration paths apply for raid:
    1. raid-1 can always be migrated to a new RAID controller, no matter which brand, because raid-1 is just a mirror and no important information is written in the partition table
    2. raid-0 or other raid-levels
    2.0 from one brand of RAID controller to the same version of the RAID controller of the same brand: no problem
    2.1 from one brand of RAID controller to a new version of the RAID controller of the same brand: usually no problem (upwards compatible)
    2.1 from one brand of RAID controller to a RAID controller of another brand: no go
    Can someone confirm this please?
    Thanks
    JohnQM

  • 3.4 via audio combo drivers

    http://www.viaarena.com/?PageID=69
    28 January 2003
    VT8231
    VT82C686A
    VT82C686B
    VT8233
    VT8233A
    VT8233C
    VT8235

    Hi Wonka,
    You forgot to mention this:
    VIA audio drivers should not be installed on those systems that utilize third-party audio cards. For third-party audio drivers support please contact your audio card supplier directly.  
    Also, most MSI boards don't use this as far as I know....

  • How to map LUN via Raid Admin?

    i want to map a LUN used by a ESXi 5 server to another 2 ESXi servers but I could not find option for it on Raid Admin 1.5.1

    It's been a while, but I seem to recall that LUN masking was removed in version 1.5.1 for unknown reasons.
    If you can roll back to (I think) RAID Admin 1.5.0 you have the option to use LUN masking, but 1.5.1 doesn't have it.

  • [VIA] RAID 0 Data Recovery with MSI K7T266 Pro2

    Well my Motherboard has seem to have gone TU on me, and it is well beyond it's warranty. 
    I have two 60gb HD running in Striped mode using the on-board raid.  If I were to get the same motherboard, would this allow me to see the striped array and recover my data, or am I at a loss?  I have some of the data backed up, but since most of it isnt, because I have nearly filled my 120GB of space and I don't have a good backup solution. 
    Thanks.
    Current Config:
    AMD XP 1900+
    MSI K7T266 Pro2
    GeForce 4400Ti
    Two WD 60gb @ RAID 0.

    Quote from: Richard on 29-November-05, 06:33:47
    SporkLover,
    My current RAID Array is on its 6th or 7th mobo (Multiple different mobo chipsets and different controllers) and I have not lost either the Array, Partition, or any Data.
    You just have to make sure that you make the primary HD the same on the new RAID and it is Crucial that you use the same Stripe Size, if you do not, then all data will be lost!
    Take Care,
    Richard
    Rich,
    Thats comforting to know!  This setup has been the best, and most reliable, so when I bought all of the components years ago, I set it up and forgot most of the parameters. 
    I completely used up all of the available space so I think that should make guessing that stripe size easy.
    osnavi, not entirely sure what happened.  It started to lock up on me randomly, and after much trouble shooting and frustration, I gave up.  Eventually I saw the problem, a few of the capacitors on the motherboard started to peak, and eventually busted.  Not sure what caused it, maybe it was my power supply.  Its an Enermax 400W, and when I bought it, it was within the required specs for the processor and Mobo.  There was plenty of case cooling, as well as CPU Cooling... so it is a great mystery to me.
    Thanks again!

  • Updated to 10.5.7 via Combo Update, FCSvr Desktop App doesn't open

    Last week I updated two Dual G5 2.5's to 10.5.7 via the Combo Update. Upon completion, the Final Cut Server.app desktop application wouldn't open. I tried re-downloading the app from our server, and my machine opened the Final Cut Server.jnlp file in TextEdit as if Java wasn't installed. So I downloaded the Java Update 4 for 10.5 from Apple. Now I can run the Final Cut Server application only if I open the Final Cut Server.jnlp file. I deleted the Final Cut Server.app, and cleared all cache files using Java Preferences in the Utilities folder (I no longer have a Java folder there, just the Java Preferences app) and reinstalled the Final Cut Server.app, so I'd have a fresh app. Still doesn't work. When I double-click it, the icon expands but nothing happens. In my console, I get this message:
    7/8/09 10:49:00 AM [0x0-0x55055].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[552] [LaunchRunner Error] The main class "com.sun.javaws.Main" could not be found.
    7/8/09 10:49:00 AM [0x0-0x55055].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[552] [JavaAppLauncher Error] CallStaticVoidMethod() threw an exception
    7/8/09 10:49:00 AM [0x0-0x55055].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[552] Exception in thread "main" java.lang.NullPointerException
    7/8/09 10:49:00 AM [0x0-0x55055].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[552] at apple.launcher.LaunchRunner.run(LaunchRunner.java:112)
    7/8/09 10:49:00 AM [0x0-0x55055].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[552] at apple.launcher.LaunchRunner.callMain(LaunchRunner.java:50)
    7/8/09 10:49:00 AM [0x0-0x55055].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[552] at apple.launcher.JavaApplicationLauncher.launch(JavaApplicationLauncher.java:52)
    7/8/09 10:49:00 AM [0x0-0x55055].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[552] at apple.launcher.JavaApplicationLauncher.launch(JavaApplicationLauncher.java:52)
    7/8/09 10:49:00 AM com.apple.launchd[80] ([0x0-0x55055].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[552]) Exited with exit code: 1
    I have tried deleting com.apple.java.JavaPreferences.plist and com.apple.java.util.prefs.plist to no avail.
    I get the same results on both machines. I have searched and found no answers. Again, if I open the Final Cut Server.jnlp java file itself, it works. It's not a huge deal, but I'd like to fix if possible.

    Done. Deleted all files mentioned. Then downloaded and reinstalled the update 4. No change whatsoever.
    I really thought this would work though. The Final Cut Server program redownloaded, prompted me to install the desktop app, which I did, and then gave me the initial licensing agreement. Final Cut Server opened, but then when I quit it and tried to open it via the new desktop app, I got this in the console:
    7/14/09 2:06:45 PM [0x0-0xb30b3].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[1733] [LaunchRunner Error] The main class "com.sun.javaws.Main" could not be found.
    7/14/09 2:06:45 PM [0x0-0xb30b3].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[1733] [JavaAppLauncher Error] CallStaticVoidMethod() threw an exception
    7/14/09 2:06:45 PM [0x0-0xb30b3].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[1733] Exception in thread "main" java.lang.NullPointerException
    7/14/09 2:06:45 PM [0x0-0xb30b3].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[1733] at apple.launcher.LaunchRunner.run(LaunchRunner.java:112)
    7/14/09 2:06:45 PM [0x0-0xb30b3].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[1733] at apple.launcher.LaunchRunner.callMain(LaunchRunner.java:50)
    7/14/09 2:06:45 PM [0x0-0xb30b3].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[1733] at apple.launcher.JavaApplicationLauncher.launch(JavaApplicationLauncher.java:52)
    7/14/09 2:06:45 PM [0x0-0xb30b3].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[1733] at apple.launcher.JavaApplicationLauncher.launch(JavaApplicationLauncher.java:52)
    7/14/09 2:06:45 PM com.apple.launchd[132] ([0x0-0xb30b3].com.apple.jnlp-http__fcs1.jplcreative.com__~fcsvr_webstartmacJnlp.php[1733]) Exited with exit code: 1
    The "Main class "com.sun.javaws.Main" not found" is presumably what's causing the problem...

  • Neo2 BIOS 3.3 Disables VIA SATA Raid AND Promise IDE3 RESOLVED

    I recently corrputed my VIA SATA Raid installation of Windows by overclocking my FSB.  I have since read that you can't do this, and I definitely learned my lesson.
    But in the process of attempting recovery, I upgraded my BIOS from 1.8 to 3.3.  (I know, didn't really keep up on that  =)
    Now I have a strange problem.  I can't have both the Promise controller ENABLED as well as the VIA SATA enabled.  During boot, if the Promise controller is Enabled and has an IDE HDD plugged into it (important!) which was created by this Promise controller a few months ago, the VIA SATA section of BIOS boot does not show up.  It will not even show the text where it is looking for attached drives.  Herein lies the problem.
    Here are a few scenarios.  If I unplug all drives from the Promise IDE connector, but leave it enabled, it will proceed to the VIA section of BIOS boot right after the Realtek initialization.  It will also show the VIA section of the BIOS boot if I disable the Promise in the Integrated Devices section of the BIOS.
    But, if I leave a single drive connected to the Promise IDE connector, and have them both enabled in BIOS (VIA "On Board" is ENABLED and Promise is set to RAID) then the only boot options I see are the Promise section, where it will correctly identify the IDE drive connected to it (remember, it was made a drive by that very same controller chip a few months back) and then proceed to the Realtek initialization.  After that, there is no VIA section at all.
    Interestingly, if you hit DEL to go into setup anytime during the scenario where there is no VIA init section, the VIA SATA drives do not show up on the Boot Sequence at all.  It is like it is not there at all, which I suspected since it wasn't showing up during BIOS boot.
    SO.  This leaves me with the unfortunate scenario of not being able to use one or the other.  The only thing I can think of is that I updated my BIOS revision.  Please, is someone able to duplicate this, or is there a known workaround?  I would hate to lose half of the functionality of the mboard as far as additional controllers goes.
    I will add my config below just in case that helps:
    K8T Neo 2
    AMD 3500+
    2 x Kingston 3500 HyperX 512
    Antec NeoPower 480w
    2 x 36GB Raptors SATA (Drives I am attempting to run on VIA for boot)
    2 x IDE drives (Maxtor 250GB and WD 160GB) on the Promise IDE 3 channel (sometimes anyway  =)
    2 x CD ROM on IDE 1
    2 x IDE drives (WD 60GB and WD 120GB) on IDE 2 (I leave these unplugged during windows install and T/S'ing this problem)
    ATI Radeon X800XTPE
    I hope that is all you would need to know about the box.
    Thanks for your ideas.

    Quote from: Tiresmoke on 09-April-05, 22:52:31
    http://www.msi.com.tw/program/support/bios/bos/spt_bos_detail.php?UID=608&kind=1
    I trslly would suggest first though to do a Bios reset and then re-examine the problems if any and let's see if we can track and sort them out.
    The first thing I found odd is that you claimed to have updated the Bios from 1.8 and there is no version 1.8 for the Neo2's. Their Bios range starts at 3.0 and that is the lowest number you should have been at.
    Second let's take a look at your Bios settings. Typically when you flash a Bios you have to go back and reset the bios again to what is needed for your rig. Otherwise the default settings may not allow you to run your system at all properly.
    I appreciate your looking at this with me Tiresmoke.  You must be right on the previous BIOS version.  It is my original Neo that I am thinking of for 1.8.  Now that you mention that, I don't know what the previous BIOS version is, but I am now going to assume it was the original.
    Tracking through it though has been strange.  Another change I noticed is that my RAM would no longer run at DDR400.  It was stuck at DDR333 no matter what I did.  I had to move the Kingston 3500 that I had from 1/2 to 1/3 to get it to work.  Something must have changed in the BIOS update to make that happen, as it was running fine before that, and differences in operation at that level have nothing to do with whether I corrupted my RAID based windows install.
    The boot order is as follows:
    1)  Promise Controller (Press CTRL + F)
    2)  Realtek LAN Boot  (Press SHIFT + F10)
    >
    3)  VIA RAID Controller.
    It is #3 that will not show up if there is a drive attached to the Promise controller.  This has got me completely stumped.  Is there a direction we can go with T/S'ing this?
    Thx.

Maybe you are looking for