Win2k installer crashing w/ SATA RAID

I created a slipstream CD of Windows 2000 Pro w/ Service Pack 4 and followed the instructions in the manual to copy the RAID drivers to a floppy. My disks are installed and configured for a stripped SATA RAID.
When I run the Win2k installer, all goes fine as I supply the RAID drivers from the disk. The installer chugs away for a little while until the bar at the bottom displays "Starting Windows". Then, after it thinks a little while longer, it crashes to a BSOD.
I tried this a couple times to be sure it wasn't a fluke, and also tried it with the supplied "XP only" driver disk, just to be sure. Every time it crashes. The error reads:
"PROCESS1_INITIALIZATION_FAILED" and also has the standard useless info about trying it again or asking your sysadmin.

I also copied the drivers from the Win2k directory on the MSI CD. However, I am trying to run my two SATA drives in the striped RAID, and the basic Win2K CD (SP1, in my case) would not recognised the RAID, even using the drivers. It would still just see two separate 80gb HDs. I read elsewhere on this board that only SP3 or higher will recognise the RAID.
BTW, I am using the beta 1.43 BIOS, because it was nesessary to resolve the erroneous temperature reading issue.

Similar Messages

Bootable SATA Raid after loading OS?

Hi,
So I have an OS on a single SATA HD.
Can I build a SATA Raid, move the OS to it and boot off it?
OK... I can see two ways to do this:
1. Add a 2nd HD. Pair it with the one I already have, that the OS is on (as a mirror).
I don't think this will work as the process of creating a Raid pair means the OS won't recognise the HD.
2. Create a Mirrored Raid from two new disks, set it up using the existing OS, and then clone the OS using Norton Ghost in the usual way.
This should work - but I'm assuming that if you don't load the raid drivers with the OS (can't - no floppy) they come in anyway off the mobo CD.
Does anybody KNOW?
Peter

Quote from: Plumbergeek on 28-February-06, 20:05:17
Read this: http://forums.pcper.com/showthread.php?t=340514
I already have read that guide.
"11. Finally press Enter to continue. Raid configuration is now complete and windows will continue loading."
This is the last step and I have got past this. It is the Windows installation that is crashing, not the RAID setup. As i have said, the RAID is detected fine, it's just when I try to install XP that it goes haywire.
I was wondering if FAT32 doesn't agree with SATA RAIDs...
-Graham

K8N Neo2 Platinum - New Bootable SATA RAID 0

I recently purchased 2 x Western Digital Caviar WD400JD Special Edition to use as a RAID 0.
I set them up according to several guides on these forums and it all worked fine until I started to install Windows XP Home (with SP2).
I got through to the partitions section of the Windows install but it was showing 2 drives instead of my single RAID array. I created a 15Gb partition on one of the disks for the install then I realised it was 2 disks and quit the setup.
When I came to it the second time round (I used both the drivers on the floppy supplied with the motherboard (on the 'Press S' part) and when I pressed Enter to continue it loaded some things then sat at "Starting to load Windows..." for ages. I left it for 20-30 mins and when I came back it had gone to the next part.) it listed 3 partitions on the one disk (array) available for installation: The 15Gb partition, the roughly 25Gb remainder of that disk, and the 40Gb of the other disk. I formatted (in FAT32) the 15Gb partition and began the installation again.
It got to the first restart, but when it did it got stuck on the Windows XP loading screen. By this time it was getting late so i gave up.
Does anyone have any ideas what went wrong or how to fix this?
-Graham

Quote from: Plumbergeek on 28-February-06, 20:05:17
Read this: http://forums.pcper.com/showthread.php?t=340514
I already have read that guide.
"11. Finally press Enter to continue. Raid configuration is now complete and windows will continue loading."
This is the last step and I have got past this. It is the Windows installation that is crashing, not the RAID setup. As i have said, the RAID is detected fine, it's just when I try to install XP that it goes haywire.
I was wondering if FAT32 doesn't agree with SATA RAIDs...
-Graham

SATA RAID problem on K8N Neo2 Platinum (nForce3 ultra) & winXP x64

I entered on MSI driver dowload page, put my model, and i found out that the RAID driver for win x64 wasn't released (nforce3 ultra), but in the same page was the driver for the nforce4, so I supposed it was compatible. I made the driver disk. press F6 and he askme for the drivers, ok, i introduce BOTH drivers, he detects perefctly the SATA RAID (stripping) format the disk, copy the files and ask me for some .CATof teh raid driver that wasn't on the zip file.... omit files, reboots, completes the instalation, but on the first boot of win x64 when it's just about to show the windows screen, a bue windows, and resets the pc so fast that's unreadable. fail safe start.. same crash.
I Installed win on an IDE and it run prefectly... In th other hand... without installing any driver the windows instalation recognices the SATA drives, but not the RAID. Maybe I just got to install the raid driver but not the SATA driver... the nforce3 driver form nvidia.com is pretty old... The real funny is that when i installed winXp x64 BETA i hadn' any problem... (winXP 64 doesn't admit the 32 bit driver=
Which driver i'm supposed to install? to INSTALL winxp64 on a SATA RAID and make it boot from there?
Thaks a lot

HI! i'm the one wih the raid problem on a k8n neo2....
That's what a i Did.. i unpacked the exe and copy the files in a floppy... question is: if i do that, windows instaler askme for some files that aren't in the .exe, anway it reconices the raid and everithing goes fine until the first BOOT on windos... it shows a blue screen, butremoves it so fast that i cant read it or pause the system. But i know it's a raid problem because if i install it on a ide disk it works.
The nforce3 drivers are almost a year old, and i'm not sure if nforce4 is compatible...
I think the're compatible because if you enter in msi driver download page and select my model, they put the Nforce3 and nforce4 for win64 and my model is only nforce3. The thing is they havent released the nforce3 for WIN 64.... So.. It's normal that win asks me for some files that ain't in the .zip file (i extracted the files o course) and Which driver should i put the Nvidia one year old nforce3 or the new nforce4. (the nforce3 for 32 bits is rejected by windows) or... i have to wait the new nforce3?
thanks for helps

K8n Neo Platinum non-booting SATA RAID setup question

I've spent several hours searching an reading trying to find out how to setup a non-bootable SATA RAID. All I can seem to find are posts about bootable installs using F6 and the drivers on a floppy.
I have setup the disks in the bios an defined the array an everything checks out. But when I boot back to WindowsXP it only sees 2 drives that it cannot find drivers for even if I point it to the correct Nvidia directory. I attempted to just reinstall the drivers but that caused a Bluescreen from a corrupt driver file that I then had to go into the repair console to copy from a floppy.
The manual an a couple of posts here say that I should go into Admin Tools-> Disk Management an it will then popup a wizard. But I'm not getting that far.
I currently have the disks on SATA 1 and 2 but will move them tonite because I've read its better for them to be on 3 and 4.
This is on a K8N Neo Platinum 7030 on Windows XP SP2. If anyone could help or just point me to where I can find help it would be greatly appreciated.

When the raid controller is enabled in bios and you start windows you can install the nvidia raid driver
from within windows .
Use the add hardware wizard from control panel .
Start the add-hw wizard .
Yes i have connected the hw - next .
Add a new hw device (bottom of the list ) -next .
Install the hw that i select manually from a list - next .
Select scsi/raid controller - next .
Choose have disk .
Then browse for the location of the nvraid.inf file

WinXP PRO install issue with SATA RAID floppy on P45D3

Hello,
My objective is to set up 2 RAID volumes (one in RAID0 + one in RAID1) using Intel RAID Matrix Manager.
After having enabled RAID mode on BIOS, created the 2 RAID volumes and pressed F6 at the beginning of WinXP PRO installation without any problem, I am stuck when one file from Intel SATA RAID driver floppy needs to be written on the disk.
The problem appears after having confirmed the partition I want to install WinXP on. I got the following message:
"Cannot write iaStor.sys" . And I have to cancel the installation.
I do not know where this file has to be written ... Additionally, this file was perfectly read (and written somewhere) just after having pressed "S" and provided the floppy during the first phase of WinXP installation.
Any suggestion to help me ?
Thanks
My config (partial):
- P45 D3 Platinum with E8500 Dual Core
- 2G DDR3
- 2x 500G SATA2 HDD

Quote from: didierpilon
How did you solved this ?
I Googled and found this page which was very useful (the blue text is a link; you can click on it).
In fact I already knew how to do it using nLite (which I normally use), but now I tried their F6 floppy advice for educational purposes and that worked as well!
Key is that the files have to be present twice, on different locations on the floppy...

VIA SATA RAID Drivers

I lost the floppy disk containing the VIA SATA raid drivers for Windows Installation. My M/B is the KT600 FISR. So I kinda need the drivers as I am setting up a SATA drive.
Can someone please say where I can get the drivers, or email me the attached drivers.
My email is:
[email protected]
Thanks,
Sam

I am worried my floppy drive controller or something on the motherboard is not working. I tried the floppy disk containing drivers and Windows Installer said still said "Please insert the manufactuer's disk", I took out the disc and got the same message.
Then I booted up Windows Installer with the same floppy disk in a different MSI motherboard (a P4 mobo I have) and it detected the drivers fine.
Tried all the updated drivers you specified, and the floppy drive reads fine from Windows and is brand new (same problem with old one which I replaced only to find the same problem :
The mobo is still under warranty, should I give MSI / dabs.com a call?
Sam

SATA RAID conflics with POMISE T3 RAID Bios

I've read quite a few of the RAID setup issues concerning the "Extra" RAID settings under "integrated peripherals" for the K9A2 Platinum. My problem seems to be a bit unique. I can't get both the SATA RAID and the Promise "Fast Track" to work together. If I enable the Extra RAID Controllers the Fastrack Bios does not recognize my SATA RAID.
This simply means that for some reason the motherboard SATA RAID conflicts or disables the PROMISE RAID Bios and vice versa. So I have not been able to activate my eSATA ports or use anything connected to the SATA5-6 ports without going into the CMOS and setting SATA DEVICES to IDE and then turning on the EXTRA Raid Controller under "Integrated Peripherals" in the CMOS. Unless I'm wrong. I am almost sure that this scenario is right.
The second issue is that I cannot get my ram to go in DUAL CHANNEL mode. But I will post that issue another time.
thx
Please Advise.
Ami Bios v1.4
K9A2 Platinum MB, 790FX,
AMD 9850 Black Edition,
8GB GSkill RAM (800Mhz),
Samsung 500GB SATA11 (x4),
Radeon HD 3870 512 MB Video,
Rosewill 950Watt PSU,
Pioneer DVD RW,
NEC DVD RW,
9-in-1 USB Card Reader
2 ext (USB/eSATA) hard Drives (eSATA will not work because these ports are controlled by the PROMISE T3 Bios)

With Vista Ultimate SP1 on my machine the USB Flasher Tool kept on crashing when the BIOS was at v 1.2 on the KA92 mainboard.
The DOS window came up fine but it appeared that every susequent module that was brought up for detecting the motherboard caught some kind of conlfict and terminated causing Vista to summon the program terminated message box. Eventually the dos prompt would state that it could not detect the motherboard and close. All in red text. This happened only when I flashed the BIOS with v1.2. I wanted to go back to 1.3 just to verify that the BIOS version was the cause and the only reason I got back to 1.3 or 1.4 easily was becaus it was backed up by the tool so all I had to do was rename the backup.bin file(s). Again everything went as expected with the USB Flasher Tool until I loaded the v1.2 BIOS. It could not even detect the mainboard.
The only reason I didn't need the tool anymore was that it backed up the versions of the bios for each time that I had flashed the bios previously.
Ami Bios v1.2
K9A2 Platinum MB, 790FX,
AMD 9850 Black Edition,
8GB GSkill RAM (800Mhz),
Samsung 500GB SATA2 (x4),
Radeon HD 3870 512 MB Video,
Rosewill 950Watt PSU,
Pioneer DVD RW,
NEC DVD RW,
9-in-1 USB Card Reader

Oracle Installer Crash running ODTwithODAC10202.exe

Can someone please help asap with the following problem? It sounds like it might be related to the psapi.dll problems others are having.
I installed the Oracle Dev Tools about a month ago on my Win2K workstation and have been using ODP.NET with no problems since.
I now need to reinstall ODT from scratch, so have run ODTwithODAC10202.exe, which successfully unzips files into /install and /stage. I'm then launching /install/setup.exe. This is when the problem occurs.
A command prompt appears stating all installer requirements are met, then the Oracle Universal Installer window appears for about 2 seconds, before disappearing without a trace. Digging into C:\temp I found a file called hs_err_pid2052.log which was created at the time the installer crashed (see content below).
What is happening here? C Shay - I would like to follow your advice re reinstalling the JVM, but there doesn't seem to be any obvious way to do so. Bear in mind I have admin privileges on my box, but Add/Remove Programs is not available to me.
**** C:\temp\hs_err_pid2052.log ****
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x77FCCA14
Function=RtlFreeHeap+0x3D0
Library=C:\WINNT\system32\ntdll.dll
Current Java thread:
     at oracle.sysman.oii.oiip.osd.win32.OiipwWin32NativeCalls.GetAllOracleHomes(Native Method)
     at oracle.sysman.oii.oiip.oiipg.OiipgOracleHomes.getOsdOracleHomeInfo(OiipgOracleHomes.java:291)
     at oracle.sysman.oii.oiif.oiifp.OiifpContentsTabPanel.add33Comps(OiifpContentsTabPanel.java:1020)
     at oracle.sysman.oii.oiif.oiifp.OiifpContentsTabPanel.fillInventoryTree(OiifpContentsTabPanel.java:702)
     at oracle.sysman.oii.oiif.oiifp.OiifpContentsTabPanel.refreshTree(OiifpContentsTabPanel.java:1508)
     at oracle.sysman.oii.oiif.oiifp.OiifpContentsTabPanel.prepareInvTree(OiifpContentsTabPanel.java:2253)
     at oracle.sysman.oii.oiif.oiifd.OiifdInventoryDialog.doModal(OiifdInventoryDialog.java:457)
     at oracle.sysman.oii.oiif.oiifw.OiifwWizDialog.onViewPrivate(OiifwWizDialog.java:863)
     at oracle.sysman.oii.oiif.oiifw.OiifwWizDialog.access$000(OiifwWizDialog.java:330)
     at oracle.sysman.oii.oiif.oiifw.OiifwWizDialog$PrepareInventoryTree.run(OiifwWizDialog.java:1778)
     at java.lang.Thread.run(Unknown Source)
Dynamic libraries:
0x00400000 - 0x0040B000      C:\TEMP\OraInstall2006-12-21_03-23-28PM\jre\1.4.2\bin\javaw.exe
0x77F80000 - 0x77FFD000      C:\WINNT\system32\ntdll.dll
0x7C2D0000 - 0x7C332000      C:\WINNT\system32\ADVAPI32.dll
0x7C570000 - 0x7C624000      C:\WINNT\system32\KERNEL32.DLL
0x77D30000 - 0x77D9F000      C:\WINNT\system32\RPCRT4.DLL
0x77E10000 - 0x77E6F000      C:\WINNT\system32\USER32.dll
0x77F40000 - 0x77F7C000      C:\WINNT\system32\GDI32.dll
0x78000000 - 0x78045000      C:\WINNT\system32\MSVCRT.dll
0x75E60000 - 0x75E7A000      C:\WINNT\system32\IMM32.DLL
0x6CA60000 - 0x6CA68000      C:\WINNT\system32\LPK.DLL
0x66650000 - 0x666A4000      C:\WINNT\system32\USP10.dll
0x08000000 - 0x08138000      C:\TEMP\OraInstall2006-12-21_03-23-28PM\jre\1.4.2\bin\client\jvm.dll
0x77570000 - 0x775A0000      C:\WINNT\system32\WINMM.dll
0x10000000 - 0x10007000      C:\TEMP\OraInstall2006-12-21_03-23-28PM\jre\1.4.2\bin\hpi.dll
0x007F0000 - 0x007FE000      C:\TEMP\OraInstall2006-12-21_03-23-28PM\jre\1.4.2\bin\verify.dll
0x00800000 - 0x00819000      C:\TEMP\OraInstall2006-12-21_03-23-28PM\jre\1.4.2\bin\java.dll
0x00820000 - 0x0082E000      C:\TEMP\OraInstall2006-12-21_03-23-28PM\jre\1.4.2\bin\zip.dll
0x1A890000 - 0x1A9A2000      C:\temp\OraInstall2006-12-21_03-23-28PM\jre\1.4.2\bin\awt.dll
0x77800000 - 0x7781E000      C:\WINNT\system32\WINSPOOL.DRV
0x76620000 - 0x76630000      C:\WINNT\system32\MPR.DLL
0x7CE20000 - 0x7CF0F000      C:\WINNT\system32\ole32.dll
0x1A9B0000 - 0x1AA01000      C:\temp\OraInstall2006-12-21_03-23-28PM\jre\1.4.2\bin\fontmanager.dll
0x51000000 - 0x5104D000      C:\WINNT\system32\ddraw.dll
0x728A0000 - 0x728A6000      C:\WINNT\system32\DCIMAN32.dll
0x5C000000 - 0x5C0C8000      C:\WINNT\system32\D3DIM700.DLL
0x6E420000 - 0x6E426000      C:\WINNT\system32\INDICDLL.dll
0x00840000 - 0x00869000      C:\temp\OraInstall2006-12-21_03-23-28PM\jre\1.4.2\bin\JavaAccessBridge.dll
0x02B80000 - 0x02B85000      C:\temp\OraInstall2006-12-21_03-23-28PM\jre\1.4.2\bin\jawt.dll
0x02B90000 - 0x02B98000      C:\temp\OraInstall2006-12-21_03-23-28PM\jre\1.4.2\bin\JAWTAccessBridge.dll
0x02E50000 - 0x02E69000      C:\temp\OraInstall2006-12-21_03-23-28PM\oui\lib\win32\oraInstaller.dll
0x77820000 - 0x77827000      C:\WINNT\system32\VERSION.dll
0x759B0000 - 0x759B6000      C:\WINNT\system32\LZ32.DLL
0x7C340000 - 0x7C396000      C:\temp\OraInstall2006-12-21_03-23-28PM\oui\lib\win32\msvcr71.dll
0x02F90000 - 0x02FAE000      C:\temp\OraInstall2006-12-21_03-23-28PM\jre\1.4.2\bin\jpeg.dll
0x77920000 - 0x77943000      C:\WINNT\system32\imagehlp.dll
0x72A00000 - 0x72A2D000      C:\WINNT\system32\DBGHELP.dll
0x690A0000 - 0x690AB000      C:\WINNT\system32\PSAPI.DLL
Heap at VM Abort:
Heap
def new generation total 832K, used 493K [0x10010000, 0x100f0000, 0x10770000)
eden space 768K, 57% used [0x10010000, 0x1007d9a0, 0x100d0000)
from space 64K, 86% used [0x100e0000, 0x100ede28, 0x100f0000)
to space 64K, 0% used [0x100d0000, 0x100d0000, 0x100e0000)
tenured generation total 10276K, used 7437K [0x10770000, 0x11179000, 0x16010000)
the space 10276K, 72% used [0x10770000, 0x10eb37e0, 0x10eb3800, 0x11179000)
compacting perm gen total 12800K, used 12733K [0x16010000, 0x16c90000, 0x1a010000)
the space 12800K, 99% used [0x16010000, 0x16c7f5d0, 0x16c7f600, 0x16c90000)
Local Time = Thu Dec 21 15:23:43 2006
Elapsed Time = 4
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.4.2_08-b03 mixed mode)
#

There are multiple folders (one for each botched installation) called:
C:\temp\OraInstall<timestamp>
These folders contain /diagnostics /jre and /oui folders, but the files you mentioned aren't there. Anywhere else I should look?
OS details:
Windows 2000 Professional 5.00.2195
Service Pack 4
Dump of HKLM/Software/Oracle:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE]
"NLS_DATE_FORMAT"="DD-MON-RR"
"TNS_ADMIN"="C:\\Program Files\\ORANT\\NETWORK\\ADMIN"
"API"="C:\\Program Files\\Oracle\\ora81\\dbs"
"COMPANY_NAME"=hex(2):42,00,61,00,72,00,63,00,6c,00,61,00,79,00,73,00,20,00,43,\
00,61,00,70,00,69,00,74,00,61,00,6c,00,00,00
"NLS_LANG"="ENGLISH_UNITED KINGDOM.WE8ISO8859P1"
"NLSRTL32"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,\
20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,4f,00,52,00,41,00,4e,00,54,00,5c,\
00,4e,00,4c,00,53,00,52,00,54,00,4c,00,33,00,32,00,00,00
"ODBC_SYS"="system32"
"OI_NLS32"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,\
20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,4f,00,52,00,41,00,4e,00,54,00,5c,\
00,6f,00,72,00,61,00,69,00,6e,00,73,00,74,00,5c,00,4e,00,4c,00,42,00,00,00
"ORA_NLS32"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,\
20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,4f,00,52,00,41,00,4e,00,54,00,5c,\
00,4e,00,4c,00,53,00,52,00,54,00,4c,00,33,00,32,00,5c,00,44,00,41,00,54,00,\
41,00,00,00
"ORACLE_GROUP_NAME"="Oracle - OraHome81"
"ORACLE_HOME"="C:\\Program Files\\Oracle\\ora81"
"OTRACE73"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,\
20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,4f,00,52,00,41,00,4e,00,54,00,5c,\
00,4f,00,54,00,52,00,41,00,43,00,45,00,37,00,33,00,00,00
"PLSQL23"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,\
20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,4f,00,52,00,41,00,4e,00,54,00,5c,\
00,50,00,4c,00,53,00,51,00,4c,00,32,00,33,00,00,00
"PRO18"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,20,\
00,46,00,69,00,6c,00,65,00,73,00,5c,00,4f,00,52,00,41,00,4e,00,54,00,5c,00,\
50,00,52,00,4f,00,31,00,38,00,00,00
"RDBMS73"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,\
20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,4f,00,52,00,41,00,4e,00,54,00,5c,\
00,52,00,44,00,42,00,4d,00,53,00,37,00,33,00,00,00
"SHARED_ORACLE_HOME"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,\
00,6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,4f,00,52,00,41,00,4e,00,\
54,00,00,00
"inst_loc"="C:\\Program Files\\Oracle\\Inventory"
"ORACLE_HOME_NAME"="OraHome81"
"OLEDB"="C:\\PROGRA~1\\Oracle\\ora81\\oledb\\mesg"
"OO4O"="C:\\PROGRA~1\\Oracle\\Ora81\\oo4o\\mesg"
"EXECUTE_SQL"=hex(2):50,00,4c,00,55,00,53,00,33,00,33,00,00,00
"PLUS_DFLT"=hex(2):50,00,4c,00,55,00,53,00,33,00,33,00,00,00
"PLUS33"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,20,\
00,46,00,69,00,6c,00,65,00,73,00,5c,00,4f,00,52,00,41,00,4e,00,54,00,5c,00,\
50,00,4c,00,55,00,53,00,33,00,33,00,00,00
"SQLPATH"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,\
20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,4f,00,52,00,41,00,4e,00,54,00,5c,\
00,44,00,42,00,53,00,00,00
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ALL_HOMES]
"DEFAULT_HOME"="ORAHOME81"
"HOME_COUNTER"="2"
"LAST_HOME"="1"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ALL_HOMES\ID0]
"NAME"="DEFAULT_HOME"
"NLS_LANG"="NA"
"PATH"="C:\\Program Files\\ORANT"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ALL_HOMES\ID1]
"NAME"="ORAHOME81"
"NLS_LANG"="NA"
"PATH"="C:\\PROGRA~1\\Oracle\\Ora81"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup]
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\ntinstall]
"MOH Icons"="exec"
"Shareable"="TRUE"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\ntinstall\OCSM Groups]
"Full Download"="ntcompat,exec,deinstl"
"Run From Server"="res:US,prodmsg:US,script:US,dll:US"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32netclt23]
"Shareable"="TRUE"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32netclt23\Map Vars]
"oracle_group_name"="Oracle for Windows NT"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32netclt23\OCSM Groups]
"EXEs DLLs Download"="deinstl:US,tns,cfg23,sample,msb:US"
"Full Download"="deinstl:US,tns,cfg23,sample,msb:US"
"Run From Server"="deinstl:US,tns,cfg23,sample,msb:US"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32nmp23]
"Shareable"="TRUE"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32nmp23\OCSM Groups]
"EXEs DLLs Download"="deinstl:US,dll"
"Full Download"="deinstl:US,dll"
"Run From Server"="deinstl:US,dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32plus33]
"Shareable"="TRUE"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32plus33\Map Vars]
"oracle_group_name"="Oracle for Windows NT"
"PLUS33"="C:\\Program Files\\ORANT\\PLUS33"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32plus33\OCSM Groups]
"EXEs DLLs Download"="deinstl:US,msg:US,sql,prefs,exe"
"Full Download"="deinstl:US,msg:US,sql,prefs,exe"
"Run From Server"="deinstl:US,msg:US,sql,prefs,exe"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32plus33\Registry Backup]
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32plus33\Registry Backup\Outside locations]
"1"="HKEY_LOCAL_MACHINE,SOFTWARE\\ORACLE,SQLPATH,1,1"
"2"="HKEY_LOCAL_MACHINE,SOFTWARE\\ORACLE,PLUS33,1,1"
"3"="HKEY_LOCAL_MACHINE,SOFTWARE\\ORACLE,EXECUTE_SQL,1,1"
"4"="HKEY_LOCAL_MACHINE,SOFTWARE\\ORACLE,PLUS_DFLT,1,1"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32rsf73]
"Shareable"="TRUE"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32rsf73\Map Vars]
"NLSRTL32"="C:\\Program Files\\ORANT\\NLSRTL32"
"OTRACE73"="C:\\Program Files\\ORANT\\OTRACE73"
"PLSQL23"="C:\\Program Files\\ORANT\\PLSQL23"
"PRO18"="C:\\Program Files\\ORANT\\PRO18"
"RDBMS73"="C:\\Program Files\\ORANT\\RDBMS73"
"SYSDIR"="System32"
"WINSYS"="C:\\WINNT\\System32"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32rsf73\OCSM Groups]
"EXEs DLLs Download"="deinstl:US,commdll,dll,msg:US,sql,nlsdata,user"
"Full Download"="deinstl:US,commdll,dll,msg:US,sql,nlsdata,user"
"Run From Server"="deinstl:US,commdll,dll,msg:US,sql,nlsdata,user"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32rsf73\Registry Backup]
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32rsf73\Registry Backup\Outside locations]
"1"="HKEY_LOCAL_MACHINE,SOFTWARE\\ORACLE,RDBMS73,1,1"
"2"="HKEY_LOCAL_MACHINE,SOFTWARE\\ORACLE,OTRACE73,1,1"
"3"="HKEY_LOCAL_MACHINE,SOFTWARE\\ORACLE,PLSQL23,1,1"
"4"="HKEY_LOCAL_MACHINE,SOFTWARE\\ORACLE,PRO18,1,1"
"5"="HKEY_LOCAL_MACHINE,SOFTWARE\\ORACLE,NLSRTL32,1,1"
"6"="HKEY_LOCAL_MACHINE,SOFTWARE\\ORACLE,ORA_NLS32,1,1"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32sodbc250]
"Shareable"="TRUE"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32sodbc250\Map Vars]
"ODBC_SYS"="system32"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32sodbc250\OCSM Groups]
"Run From Server"="deinst,ora,mfc,ctl3d:nt,iconnt"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32sodbc250\Registry Backup]
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32sodbc250\Registry Backup\Outside locations]
"1"="HKEY_LOCAL_MACHINE,SOFTWARE\\ODBC\\ODBCINST.INI\\Oracle73 Ver 2.5,,0,1"
"2"="HKEY_LOCAL_MACHINE,SOFTWARE\\ODBC\\ODBCINST.INI\\ODBC Drivers,Oracle73 Ver 2.5,1,1"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32tcp23]
"Shareable"="TRUE"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Backup\w32tcp23\OCSM Groups]
"EXEs DLLs Download"="deinstl:US,dll"
"Full Download"="deinstl:US,dll"
"Run From Server"="deinstl:US,dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME0]
"ID"="0"
"NLS_LANG"="NA"
"ORACLE_GROUP_NAME"="Oracle - DEFAULT_HOME"
"ORACLE_HOME"="C:\\Program Files\\ORANT"
"ORACLE_HOME_NAME"="DEFAULT_HOME"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME1]
"ID"="1"
"NLS_LANG"="ENGLISH_UNITED KINGDOM.WE8ISO8859P1"
"ORACLE_GROUP_NAME"="Oracle - ORAHOME81"
"ORACLE_HOME"="C:\\PROGRA~1\\Oracle\\Ora81"
"ORACLE_HOME_KEY"="Software\\ORACLE\\HOME1"
"ORACLE_HOME_NAME"="ORAHOME81"
"SQLPATH"="C:\\PROGRA~1\\Oracle\\ora81\\dbs"
"MSHELP_TOOLS"="C:\\PROGRA~1\\Oracle\\ora81\\MSHELP"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_ODACHome1]
"ORACLE_HOME"="C:\\Program Files\\Oracle\\Ora102"
"ORACLE_HOME_NAME"="ODACHome1"
"ORACLE_GROUP_NAME"="Oracle - ODACHome1"
"ORACLE_BUNDLE_NAME"="Enterprise"
"NLS_LANG"="ENGLISH_UNITED KINGDOM.WE8MSWIN1252"
"ORACLE_HOME_KEY"="SOFTWARE\\ORACLE\\KEY_ODACHome1"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ODP.NET]
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ODP.NET\1.102.2.20]
"DllPath"="C:\\Program Files\\Oracle\\Ora102\\bin"
"TraceFileName"="C:\\odp.net1.trc"
"TraceLevel"="0"
"TraceOption"="0"
"StatementCacheSize"="10"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ODP.NET\2.102.2.20]
"DllPath"="C:\\Program Files\\Oracle\\Ora102\\bin"
"TraceFileName"="C:\\odp.net2.trc"
"TraceLevel"="0"
"TraceOption"="0"
"StatementCacheSize"="10"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OLEDB]
"CacheType"="Memory"
"ChunkSize"="100"
"DisableRetClause"="1"
"DistribTX"="1"
"FetchSize"="100"
"OSAuthent"="0"
"PLSQLRSet"="0"
"PwdChgDlg"="1"
"SchRstLng"="10000"
"TraceCategory"="0"
"TraceFileName"="C:\\PROGRA~1\\Oracle\\Ora81\\network\\trace\\OraOLEDB.trc"
"TraceLevel"="0"
"TraceOption"="0"
"UserDefFn"="0"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OO4O]
"CacheBlocks"="20"
"FetchLimit"="100"
"FetchSize"="4096"
"HelpFile"="C:\\PROGRA~1\\Oracle\\Ora81\\MSHELP\\oracleo.hlp"
"OO4O_HOME"="C:\\PROGRA~1\\Oracle\\Ora81\\oo4o"
"PerBlock"="16"
"SliceSize"="256"
"TempFileDirectory"="c:\\temp"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ORACLE_HOMES]
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ORACLE_HOMES\ORACLE1]
"API"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,20,00,\
46,00,69,00,6c,00,65,00,73,00,5c,00,4f,00,52,00,41,00,4e,00,54,00,5c,00,44,\
00,42,00,53,00,00,00
"COMPANY_NAME"=hex(2):42,00,61,00,72,00,63,00,6c,00,61,00,79,00,73,00,20,00,43,\
00,61,00,70,00,69,00,74,00,61,00,6c,00,00,00
"NLS_LANG"="AMERICAN_AMERICA.WE8ISO8859P1"
"ORACLE_GROUP_NAME"=hex(2):4f,00,72,00,61,00,63,00,6c,00,65,00,20,00,66,00,6f,\
00,72,00,20,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,4e,00,54,00,\
00,00
"ORACLE_HOME"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\
00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,4f,00,52,00,41,00,4e,00,54,00,\
00,00
"SHARED_ORACLE_HOME"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,\
00,6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,4f,00,52,00,41,00,4e,00,\
54,00,00,00

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.

First time install probs with sata raid drive using k7n2g ilsr

hi all!!!
this is the first time i have tried 2 use a sata raid hdd. i dont use a raid drive for my c:, the raid drive is just extra space.
first i formated my pc. i installed the raid drivers, then xp. my pc worked fine. but then after a week it was time 2 try plug the drive in.
when i got my k7n2g ilsr motherboard i di not get a manual. so with the raid drivers installed, i just pluged in the raid drive. the drive seemed fine.... i formatted it and put a couple of games on. but after an hours usage the games would crash (high pitched tone instead of the audio, then full freeze).
i have tried putting these games back on my original drive and they work fine......
anyway....
i wanted 2 know if anyone had any ides what i was doing worng??? are there any settings in the bios that need changing when installing a raid drive????
thanks for any help!!!!!!!

ok still formatting drive..... looking over the files on the msi site for my motherboard it has 2 files available for raid drives:
the 'Promise Serial-ATA RAID Drivers' ( which i have installed)
and the 'Promise Serial-ATA RAID Utility' (which i dont hav installed)
do i need the Promise Serial-ATA RAID utility?? and if so how do i install it?? there are no setup files just dll files like the driver.... is istallation the same as the driver?
again, i thank u for your help!!!!!

K8N Neo2 SATA Raid problem finally solved

Hi guys,
finally got my SATA Raid 0 array to work.
Problem was that XP didn't find a correct array on installation although i used F6
to load drivers from disk. Sometimes it didn't detect any hard disk, sometimes
it showed two hd's and an array and so...
The whole spectrum of errors mentioned here over the last days and weeks...
I tried different bios like 1.1, 1.2, 1.2b5, 1.3b5 and i got the newest drivers
directly from nvidia as mentioned in some other thread. Nothing worked.
One should think that nvidia would have the latest drivers... but that was the
major fault.
As mentioned in a different thread i downloaded the unified nforce drivers from
nvidia's homepage and extracted the ide drivers to a floppy. I used these drivers
in all of my attempts and it never worked..
Yesterday i downloaded the MSI Nvidia nForce3 System Drivers package 5.03 from
http://www.msi.com.tw/program/support/download/dld/spt_dld_detail.php?UID=607&kind=1
and compared the version numbers to the files from the nvidia package.
The relevant files nvatabus.sys and nvraid.sys are version 5.10.2600.412 from
nvidia while the MSI versions are 5.10.2600.446 !!
I put these files on the disk, set up my bios (default 1.1) from scratch, started XP installation,
hit F6, loaded the new drivers and voila... one 230 gb array ready for installation
Took me FOUR days to figure this out. THANK YOU MSI support team,
wherever you are.... (definitely not working on an updated hp)
So to put it in one line:
What really worked for me were the drivers from the MSI nforce3 driver package 5.03
No messing around with beta bios, no voltage tweaking or SATA 3/4 preferred
or DIMM Slot preferred crap.
Of course you have to set up an raid array as described in rsheppicks raid setup guide
Only thing about bios versions is that only in bios 1.1 i got an array shown in the
hard disk boot priority list
So i hope this helps you guys out there that are having troubles setting up SATA Raid.

OK now! Dag, I was going crazy. I had two brand new Raptors and was trying to hook them up in a RAID 0 config. I am no dummy. It would hang at detecting arrays. I could not figure it out for the life of me. I will not talk about all of the combos that I tried. My buddy told me to try datalifeguard from WD. I did. Well, one HD showed no serial number in the extended test. An error message popped up. Said the drive was not working. So, Newegg sends me a dead drive and wastes days and days out of my life. I hooked up the one good drive just now. What do I see? For the first time in my life, I am seeing the raid bios! This almost cost me a divorce. Seriously though, the wife would come in and rub my shoulders like a fighter after a few hours of getting my azz whipped by this new rig. I am now going to make the floppy with the newer drivers like was done here. Just incase. I am in Raid bios now in the other room. Time to go set up XP on one drive for now. I refuse to wait for the RMA'ed second Raptor.

Intel(R) ESB2 SATA RAID Controller not working out of the box

Dear all,
I'm using, for my tests, an old server with a supermicro X7DBN Server motherboard.
This motherboard comes with an embedded Intel(R) ESB2 SATA RAID Controller.
When I try a native installation from the technical preview DVD it sees the RAID1 volume that has been created (2 disk mirror) but when I select it to proceed with the installation there is an unknown error stating that it's impossible to write to this disk.
The same installation works perfectly with 2012R2 and the out of the box driver provided bin the install media.
An update from the previously installed 2012R2 to the Windows Server Technical Preview also works without problem.
It would make sens for MS to revert to the driver version embedded in 2012R2 for Intel(R) ESB2 SATA RAID Controller which is:
Name : Intel(R) ESB2 SATA RAID Controller
Date : 10.08.2010
Version : 8.6.2.1025
inf section : iaStor_Inst_RAID
Device ID : PCI\VEN_8086&DEV_2682&CC_0104

Hi,
Thank you for the information. As you said from the behavior it seems that the build-in drivers of Windows Server Technical Preview will not work with the specific motherboard hence the RAID1 cannot work well.
I'll log the issue down.
If you have any feedback on our support, please send to [email protected]

SATA RAID and K92A Platinum

OK Guy’s
I need your assistance here. I just purchased a MSI K92A Platinum motherboard and having the darnest time setting up RAID 0 (or any RAID period). Before I go any further this is my setup.
SATA 1 Western Digital WD2500JS 250GB SATA
SATA 2 Western Digital WD2500JS 250GB SATA
SATA 3 LITE-ON 20X DVD SATA MODEL LH-20A1S
SATA 4 Western Digital WD2500JS 250GB SATA
SATA 5
SATA 6
Floppy drive installed
Memory: Kingston Hyper 2GB 1066 (x2)
Processor: AMD 6400+ (3.2)
Video: Ge Force 8800 GTX
In the basic (CMOS) screen I see all my drives. When I move to the advance screen and select RAID. All the drives including my DVD disappear from the basic (CMOS) screen. In the RAID utility, I see all three hard drives (minus the DVD drive). I created my RAID 0 with two of the drives and left the last drive free for future use. The problem arises when I reboot and try to use my DVD drive with Windows VISTA. After the initial boot from the Windows CD, I followed the on screen instruction by selecting the install tab. It would prompt me for my license number and move to the next screen. After that it would return with the error unable to find DVD/CDROM (no further installation possible). Just remember it had booted off the CD in the first place. Not sure what is the problem. Unfortunately I can’t install WINDOWS on a RAID drive until I figure out why when I select RAID that my DVD is not seen correctly after booting .
All things being equal, I have no problem installing WINDOWS without defining a RAID device on this motherboard. All the drives are seen including my DVD. A little history I just came from using an ASUS MSN-SLI Deluxe motherboard and I did not have any of these problems. At this point is seems ASUS had the easiest RAID utility. Final note, hardware is good and tested. Any response would be greatly appreciated.
Thanks in advance
Richard

No, you can use as many as you would like. It's just that RAID 0 with three drives is not possible on the Promise controller (red ports), as it has only two ports. Therefore you will need to use the SB600 controller, which is somewhat picky about SATA RAID drivers...
Anyway, the Promise controller is already disabled. Set your SB600 controller to RAID in your BIOS, then enter the FastBuild utility using CTRL + F when prompted. Build the array to your likings and save the settings, then boot from your Vista DVD. If you're lucky the drivers from the MSI CD (for Vista) will work. Otherwise you will have to start trying SB600 SATA RAID drivers from other manufacturers, those from DFI are known to work quite well.

Promise 20378 sata raid ide controller: this device doesn't start

My WinXp Promise Fast Track 376/378 (tm) Controller doesn't start, despite installing the right drivers for vista and xp. Ik have a 40 gig Maxtor disk attached to the IDE port of the controller aangesloten. Het Fast Track bios sees this disk correctly. The disk is o.k. since I can access its contents while running Linux Kubunty gutsy gibbon. What is wrong with the windows drivers?
My system:
M/B = MSI KT6 Delta FIS2R
CPU = AMD Athlon(tm) XP 1700+
RAM = 1GB Twinmos M2G9016A-TT pc 3200 Cl2.5
VGA = Ati Radeon 9600 series
HDD = 2x Maxtor 6Y120M0 via raid-0, Maxtor 91303D6 IDE1 master, Maxtor 6Y060L0 IDE2 master, Maxtor 54610H6 promise IDE master
PSU = Trust PW-5159 370W
Optical = Plextor DVDR PX-504A IDE1 slave, Plextor CD-R PX-W121 0A IDE2 slave
OSS = XP Pro SP2, Vista Ult., Kubuntu Gibbon 32bits, Suse 10.3 32 bits

Quote from: Fredrik Åsenius on 14-November-07, 05:57:51
Hello!
Is SATA/RAID enabled in BIOS?
Have you hit F6 during Windows installation, for allowing Windows Set-up to locate the drivers?
If SATA/RAID was disabled, it wouldn't even appear in Device Manager
If the RAID is secondary storage, then hitting F6 won't acheive anything as Windows is already installed
You will however need to go into the RAID BIOS and create an array before you can use the RAIDed disks

Win2k installer crashing w/ SATA RAID

Similar Messages

Maybe you are looking for