nws

Bashrat: I have problems with massdrivers in txtsetup.txt (when using ris). Setup wont work. Setup says something that has errors on setup.c and if i remember right the line was 3540. [sourceDisksFiles] sisraid2.sys = 1,,,,,,4_,4,1,,,1,4 ulsata2.sys = 1,,,,,,4_,4,1,,,1,4 S150sx8.sys = 1,,,,,,4_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_1039&DEV_0182 = "sisraid2" PCI\VEN_105A&DEV_3D75 = "ulsata2" PCI\VEN_105A&DEV_3D18 = "ulsata2" PCI\VEN_105A&DEV_8000 = "S150sx8" PCI\VEN_105A&DEV_8002 = "S150sx8" PCI\VEN_105A&DEV_8004 = "S150sx8" PCI\VEN_105A&DEV_8006 = "S150sx8" SCSI\ProcessorPromise_ = "S150sx8" [sCSI.Load] ulsata2 = ulsata2.sys,4 sisraid2 = sisraid2.sys,4 S150sx8 = S150sx8.sys,4 [sCSI] sisraid2 = "SiS 182 RAID Controller" ulsata2 = "Promise SATAII150 TX2plus/TX4 IDE Controller" sisraid2 = "SiS 182 RAID Controller" I just removed those lines, and then it works fine. Can you recheck those drivers? Windows version is SP2.

I think that the driverpack will fix that problem to both of you. Those drivers must be in i386 directory too and $OEM$\$1\lan directory. And you have to edit your ristnrd.sif ( it can be found under i386\templates dir ) oempath like this: OemPnPDriversPath="Drivers\Lan; But driverpacks instructions are quite same.

I think you should download this driverpack and follow the instructions. Bâshrat the Sneaky has done great job for it and those drivers are updated too. Thread and driverpack is here: http://www.msfn.org/board/index.php?showtopic=22094 edit: fixed my language

Check this thread: http://www.msfn.org/board/index.php?showtopic=27548

Copy your NIC drivers (.inf, .sys and .cat) to i386 folder and after that Run RISSetup again with "just checking errors". Then your network boot should work

RIS works over network. Ris works with PXE standard NICs (the client needs PXE-support) and it will boot from lan, so you don't need any cd-rom or any floppydrive . You can add many images (versions like xp home ENG xp pro ENG, win 2003 server, w2k and so on) and you can choose whitch OS you want to be installed to the client system. Images are easy to update, because the install files are in RIS servers harddisk. I am running the RIS system and i can tell that atleast 90% here at MSFN-forum advices will work straight with RIS. There are few basic things what you have to learn about RIS. (like oem directory difference between cd-rom and RIS and so on ) But after you have totally understand how the ris works and how to configure it then all the driver and other slipstreaming should be easy. I am just fighting with those hotfixes to get them all work but i think i will give up and wait SP2 and start with "clean table". If someone has got those hotfixes to work with RIS, please contact me or reply to this topic ... Maybie i will need your cmdlines.txt and runonce.cmd The problem is simple - when i am trying to add and run those fixes they will be shown in windowsupdate as not to be installed . I have tried to use qchain.exe, but it will not work.. And yes, i have read all those main topics about hotfixes too... More about RIS: http://www.microsoft.com/resources/documen...cc_ris_rvvt.asp

Please add Buffalo and SIS lan drivers too. Buffalo gigabit card: http://www.buffalotech.com/wireless/downlo...GY-PCI32-GT.zip And Sis Network drivers should be here: http://download.sis.com/ You can add those SIS Wlan dirvers also to Wlanpack Offopic: I think that Servicepack 2 may have many of driver updates too...

Please add Buffalo, Telewell and Edimax Drivers too. Telewell drivers are here: http://www.telewell.com/en/index.shtml Buffalo drivers are here: http://www.buffalo-technology.com/webconte...nload/index.php Edimax (is usually based on Realtek drivers) drivers here: http://www.edimax.com.tw/html/english/frames/b-download.htm Offtopic: Could you build driverpack for modems and DSL/ISDN PCI cards too?