Jump to content

SisRaid.sys


Recommended Posts

Posted

I'm using Windows XP SP2 as my starting point. I'm trying to slipstream the drivers at this location.

http://global.msi.com.tw/index.php?func=dr...no=6125&i=0

Its a SIS windows text mode SATA driver. It unzips to a directory structure as follows

SISRAID 1kb file

TXTSETUP.OEM

RAID

Srv2003

win2000

winxp

sisraid.sys

etc....

WS03XP64

If I pick the folder the driver file is in, winxp sisraid.sys, nLite will add the driver but it won't see it as a txt.mode driver. And if I add it, burn it, and try to install XP, it says it can't find the sisraid.sys file, and perhaps others. If I move the TXTSETUP.OEM to the WINXP folder, nLite will recognize the driver as a txtsetup driver, but still fails during installation(this is a brand new nLite session, with new i386 files, etc.), saying it cannot copy the sisraid.sys file during windows install.

I've worked with nLite before and the interface has changed a bit. I just can't figure out what I'm doing wrong. I've had similiar problems with other drivers as well. Do I need to edit the TXTSETUP.oem file so that it doesn't use a folder structure, or do I need to copy the sys file to the root of the folder, where TXTSETUP.OEM is, so that nLite cans see it as a TXT.mode driver, and the TXTSETUP.OEM folder references still work out, or is there something else I'm just screwing up?


Posted (edited)

OK take the XP folder out and place the txtseup.oem file IN it.

Then point nLite to just that folder.

Like so.

Also place a unmodified copy of that sisraid.sys file into the 1386 dir. (At least thats what I had to do when I kept getting those errors.)

Edited by Kelsenellenelvian
Posted

That's the same as moving the TXTSETUP.OEM to the WinXP folder. And that didn't work. Same error, cannot find SisRaid.sys during Windows install.

Posted

If I look at the created ISO, I386 folder Driver.cab file, there is no sisraid.sys file. Which I believe is where it ends up. Maybe I'm mistaken on the location, I can't remember exactly where its supposed to go.

Posted
Also place a unmodified copy of that sisraid.sys file into the 1386 dir. (At least thats what I had to do when I kept getting those errors.)

I edited my post

Don't mess with driver.cab please thats only asking for trouble.

Just add the file to the i386 dir.

Posted

So, I'm guessing nLite is broken because it isn't able to add any text mode drivers correctly as far as I can tell? Seems like nLite could add the drivers to the directory itself, or the driver.cab, or even the $OEM directory.

What happens if I do edit the driver.cab file? Is it hashed or is there something additional I need to do? Does nLite work at all? I've tried 4 different drivers, and nLite is unable to add any of them. It sees the driver, it begins installing the windows on the drive, but then says it can't find the associated files.

Posted

Gr8BigApe, what kind of HDDs do you have? If they are SATA, you probably need text mode drivers for them also. Enjoy, John.

Posted

I have a SATA150 drive and an IDE dvd drive. I've added the text mode driver. It's now able to see the drive, format it. However, when windows begins installing it says "Setup cannot copy the file: SiSRaid.sys"

Posted

Gr8BigApe, I assume you are sure you have your RAID set up properly? I DLed the folder you pointed to and here are the statistics on SiSRaid.sys: 47.0 KB (48,128 bytes) MD5 826B83CDAAFB6E164BBC1D77CB99E2CE. Check your's and see it agrees. Perhaps you have a corrupted DL. Is there any more information with the error message? I opened the the SISRAID (no extension) file with notepad and it had only one line of "SiSRaid". I don't know what this is for, but you might try just placing it into your driver folder - shouldn't hurt. Perhaps MSI can cast some light on what is going on. Enjoy, John.

Posted

No raid, just SATA. But these are the drivers that are listed for the SATA controller. The board has no floppy controller, and for some reason I can't get it to see a USB floppy.

Posted

Gr8BigApe, I assume your size and MD5 are the same as mine? I have seen some here trying to get a USB floppy to work. I don't know if they were successful, but I assume you would need a text mode driver for that. What MSI board do you have, so I can look around? Enjoy, John.

Posted (edited)

I was gonna give a shot at using SIS's own driver, instead of MSI's but I don't expect any different results. The drivers are there, under the i386, and also seem to be where nLite installed them too.

D:\WinXP\I386\NLDRV\

Think I'm gonna try a different computer, just to rule out a bad burner, and then see how it installs on a different computer as well(bad reader). But the problem seems to happen whenever I try to add text mode drivers to windows XP. I am adding them as textmode, and not pnp.

My last attempt, which similiarly failed, I added drivers as both textmode, and pnp. Figured I give that a shot as well. I think these are some relevent lines from my txtsetup.sif. If that helps any. Its been a while since I've messed with some of this stuff, so I may be barking up the wrong tree with some of this.

1984 = %cdname%,%cdtagfilei%,,"\i386\NLDRV\001"

1985 = %cdname%,%cdtagfilei%,,"\i386\NLDRV\001\RAID\srv2003"

1986 = %cdname%,%cdtagfilei%,,"\i386\NLDRV\001\RAID\win2000"

1987 = %cdname%,%cdtagfilei%,,"\i386\NLDRV\001\RAID\winxp"

1988 = %cdname%,%cdtagfilei%,,"\i386\NLDRV\001\RAID\WS03XP64"

1989 = %cdname%,%cdtagfilei%,,"\i386\NLDRV\002"

SiSRaid.sys = 1,,,,,,4_,4,1,,,1,4

sisraid.sys = 1984,,,,,,,1984,0,0

sisraid.sys = 1985,,,,,,,1985,0,0

sisraid.sys = 1986,,,,,,,1986,0,0

sisraid.sys = 1987,,,,,,,1987,0,0

sisraid.sys = 1988,,,,,,,1988,0,0

sisraid.sys = 1989,,,,,,,1989,0,0

Edited by Gr8BigApe

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...