iTwins

heh...are you sure it's my RAID Slipstreamer that has the trojan and not yours (or your computer)? 1) The one on Rapidshare is named "Raid_Slipstreamer_v2.2.exe" and not "Rapid_Slipstreamerv2.2.exe" 2) I downloaded the one at Rapidshare, scanned using the 12/27/2006 virus definition of Symantec AntiVirus Corporate Edition v10.1.5.5000 and nothing unusual found 3) I extracted the contents, scanned using the same virus definition, and nothing found Anyhow, use at your own risk regardless who is at fault

Sorry, I was unable to replicate your problem despite using original operating systems from Microsoft Select CDs and re-running RAID Slipstreamer onto all of them. However, I haven't had the chance to test what the effects of running RAID Slipstreamer BEFORE or AFTER nLite or HFSLIP. But then, I use HFSLIP regularly on Windows XP SP2 only and nothing irregular encountered yet. RAID Slipstreamer's logic is very simple: 1) Check for the presence of NTDLL.DLL situated in the path in which you specified (it scans for each subfolder looking for a valid NTDLL.DLL file) 2) When found, checks for "Product Version" 3) If v5.2.xxx, slipstream Windows 2003 drivers into the I386 source 4) Else if v5.1.xxx, slipstream Windows XP drivers into the I386 source 5) Else if v5.0.xxx, slipstream Windows 2000 drivers into the I386 source 6) Write log 7) Loop and check the next subfolder until no more subdirectories found 8) Exit Anyways, you can find out yourself. 1) Search for the NTDLL.DLL situated in your I386 source (or in I386\SYSTEM32) 2) Right-click NTDLL.DLL > Properties > Version > Product Version 3) Find out the version number 4) Compare with the above logic on step 3 - 5 Is your NTDLL.DLL out of whack (wrong version used)? If you're still having problems, then maybe RAID Slipstreamer is not a good tool for you. Try HFSLIP... Cheers

http://www.msfn.org/board/index.php?showto...iew=getlastpost

...replied your email with the v2.3 BETA download link. Let me know how it goes please. Cheers

Try this (assuming you're using XP) and nothing fancy: 1) Using MAKECAB.EXE, compress the two files JRAID.SYS and JGOGO.SYS to JRAID.SY_ anD JGOGO.SY_ (You probably only need JRAID.SYS but just in case. do both...) 2) Copy the two SY_ files to your \I386 source directory 3) Edit the TXTSETUP.SIF file and search for the header [sourceDisksFiles]. Add this entry beneath it: jraid.sys = 1,,,,,,4_,4,1,,,1,4 4) Edit the TXTSETUP.SIF file and search for the header [HardwareIdsDatabase]. Add these entries beneath it: PCI\VEN_197B&DEV_2360&CC_0104 = "jraid" PCI\VEN_197B&DEV_2361&CC_0104 = "jraid" PCI\VEN_197B&DEV_2363&CC_0104 = "jraid" PCI\VEN_197B&DEV_2366&CC_0104 = "jraid" PCI\VEN_197B&DEV_2360&CC_0106 = "jraid" PCI\VEN_197B&DEV_2361&CC_0106 = "jraid" PCI\VEN_197B&DEV_2363&CC_0106 = "jraid" PCI\VEN_197B&DEV_2366&CC_0106 = "jraid" 5) Edit the TXTSETUP.SIF file and search for the header [sCSI.Load]. Add this entry beneath it: "jraid" = jraid.sys,4 6) Edit the TXTSETUP.SIF file and search for the header [sCSI]. Add this entry beneath it: jraid = "Whatever name you want to call this driver. It's purely cosmetic!" Optional, depending on circumstances (I normally include it anyways...just in case): 7) Edit DOSNET.INF and search for the header [FloppyFiles.2]. Add this entry beneath it: d1,jraid.sys 8) Edit DOSNET.INF and search for the header [FloppyFiles.2]. Add this entry beneath it: d1,jraid.sys 9) That's it. Try it out and don't press F6; the system should automatically detect and load the driver.

Actually Anderz already mentioned it here: 3. Copy only the .SYS file (iastor.sys) to the C:\XPCD\I386 folder. Keep the other files - you'll need some information from them a little later. Note that it's important that the .SYS file is uncompressed. Keep in mind this method only works for simple drivers that only comes with a SYS file. For more complex drivers in which it comes with its own GUI for configuring the controller in Windows, you will need to slipstream/integrate the DLL and other files that come with the driver as well. It gets complicated in these cases.

I think I screwed up again. Fixed in v2.2

Updated to v2.1. Now RAID Slipstreamer scans for all valid operating systems in the folder you specified, determines the platform type and then slipstreams the correct drivers into each platform automatically. Simply supply the path then click OK. That's all.

I am sure there are alot of similar programs out there. I personally use Driver Genius Professional for the last few years. It is no doubt the best on the market. It can backup, backup to zip, backup to self-extracting EXE, backup to auto-install EXE, search, download and update new drivers, etc, etc, etc, It's only US30 for the Pro - I think it's well worth it. But I am constantly looking for one that is good, stable, AND FREE FOR COMMERCIAL use (for work really). So far I have yet to find such a thing. Sorry, Double Driver is light years away...

@IcemanND Great idea with great potential. I really like the idea of such a tool. I tried this tool a while back. I tested it on a Dell Latitude D410 notebook and selected to backup ALL non-Microsoft drivers. I thought it hung, so I aborted it and never tried it again Just now I just gave it another try, using the same system but this time I backed up only one driver. The first driver I ask it to backup took over 5 minutes just to backup 3 tiny files: What's taking so long?

Updated. Try it out and let me know how it goes

The SI3112r drivers were integrated into v1.1 but I had to remove it because the da-mn drivers were dependent on which BIOS firmware version the system is using. And on top of that, my company no longer use SI3112r controllers. Anyways, I will include the SATA RAID driver into the next version. For non-RAID drivers (with the same filename but not inter-usable) model, that will have to wait until I have time to modify them. As for NForce RAID, show me the link to the driver and I'll see what I can do

The brain works better after a much deserved vacation. Sorry, Bilou. I know what you mean now. Download the v2.0.1a fix here

Simply create a c:\winnt\temp

Pure batch programming cannot but 3rd party DOS programs can. It's not like HFSLIP is purely batch file only so using 3rd party programs doesn't break that rule. I think I have such a program tucked away somewhere here...CHGINI16.EXE and INIFILE.EXE (attached) I don't remember what are the differences between the two but... Sample commandline: CHGINI16 C:\UNATTEND.TXT "GuiUnattended" "TimeZone" %TIMEZONE% > nul INIFILE SET C:\UNATTEND.TXT -s"params.MS_TCPIP.Adapter1" -kDHCP -vYES > nul If push comes to shove, you can always get HFSLIP to call up a VBScript or Kixtart script. Either one of them can be easily done. Both compilers can be run in XP/2000/2003/Vista. Cheers. chgini16.exe inifile.exe

I ran v1.0.1 with storage.ini in VMware Workstaiton v5.5.2 and I encountered this error: ..and teh following were added into the TXTSETUP.SIF [SourceDisksFiles] HFSLIPWU.INF = 1,,,,,,,20,0,0 A320RAID.CAT = 1,,,,,,,2,0,0,,1,2 A320RAID.INF = 1,,,,,,,20,0,0,,1,20 A320RAID.SYS = 1,,,,,,3_,4,1,,,1,4 AACCIN.DLL = 1,,,,,,,2,0,0,,1,2 AACMGT.INF = 1,,,,,,,20,0,0,,1,20 AACSAS.CAT = 1,,,,,,,2,0,0,,1,2 AACSAS.INF = 1,,,,,,,20,0,0,,1,20 AACSAS.SYS = 1,,,,,,3_,4,1,,,1,4 COCPYINF.DLL = 1,,,,,,,2,0,0,,1,2 DELPSEUD.INF = 1,,,,,,,20,0,0,,1,20 IAAHCI.CAT = 1,,,,,,,2,0,0,,1,2 IAAHCI.INF = 1,,,,,,,20,0,0,,1,20 IASTOR.CAT = 1,,,,,,,2,0,0,,1,2 IASTOR.INF = 1,,,,,,,20,0,0,,1,20 IASTOR.SYS = 1,,,,,,3_,4,1,,,1,4 MPIXP32.CAT = 1,,,,,,,2,0,0,,1,2 QL2300.CAT = 1,,,,,,,2,0,0,,1,2 QL2300.SYS = 1,,,,,,3_,4,1,,,1,4 QL2X00.INF = 1,,,,,,,20,0,0,,1,20 QL2XHAI2.DLL = 1,,,,,,,2,0,0,,1,2 QLPSEUDO.INF = 1,,,,,,,20,0,0,,1,20 QLSDM.DLL = 1,,,,,,,2,0,0,,1,2 SYMMPI.CAT = 1,,,,,,,2,0,0,,1,2 SYMMPI.DBG = 1,,,,,,,2,0,0,,1,2 SYMMPI.INF = 1,,,,,,,20,0,0,,1,20 SYMMPI.PDB = 1,,,,,,,2,0,0,,1,2 SYMMPI.SYS = 1,,,,,,3_,4,1,,,1,4 SYMMPI.TAG = 1,,,,,,,2,0,0,,1,2 SYMMPO.INF = 1,,,,,,,20,0,0,,1,20 ULTRA.CAT = 1,,,,,,,2,0,0,,1,2 ULTRA.INF = 1,,,,,,,20,0,0,,1,20 ULTRA.SYS = 1,,,,,,3_,4,1,,,1,4 VMSCSI.CAT = 1,,,,,,,2,0,0,,1,2 VMSCSI.INF = 1,,,,,,,20,0,0,,1,20 VMSCSI.SYS = 1,,,,,,3_,4,1,,,1,4 [SCSI.Load] A320RAID = A320RAID.SYS,4 AACSAS = AACSAS.SYS,4 IASTOR = IASTOR.SYS,4 QL2300 = QL2300.SYS,4 SYMMPI = SYMMPI.SYS,4 ULTRA = ULTRA.SYS,4 VMSCSI = VMSCSI.SYS,4 ;-------------------------------------------------- ;VMWARE [HardwareIdsDatabase] PCI\VEN_104B&DEV_1040 = "vmscsi", "VMware SCSI Controller" [SCSI] vmscsi = "VMware SCSI Controller" ;-------------------------------------------------- The reason? If you look in DOS, you will notice that the files A320RAID.SY_ and all other .SY_ files that are declared in [sCSI.LOAD] are missing in the $WIN_NT$.~BT directory. To correct that, you need to match those files into DOSNET.INF's [FILES] and [FLOPPYFILES.2] sections as well. Sadly, in this case, even if you fixed the DOSNET.INF issue, you still get a BSoD. I am still investigating... A proprosal Rather than using STORAGE.INI, is it possible to get HFSLIP to do everything intelligently and automated. To do that, follow these steps: *** I use QLOGIC's driver because its one of the more complicated ones 1) scan for each INF file within HKEXPERT\STORAGE for the string under the [Manufacturer] header. There can only be one string in [Manufacturer]. Example: [Manufacturer] %QLOGIC%=QLOGIC,NT.5.2 Watch out though, not all drivers include a comma. Most drivers look like this: [Manufacturer] %ADP%= ADAPTEC 2) Skip the value name but keep the value. In the above example, rename the comma in ",NT 5.2" and replace it with a period. ex ".NT.5.2" 3) Search for the [QLOGIC.NT.5.2] header and scan all the PCI\VEN entries. Example: [QLOGIC.NT.5.2] %ql2300.DeviceDesc% = ql2300_Inst, PCI\VEN_1077&DEV_2432&SUBSYS_01371077 extract the vendor and device codes PCI\VEN_1077&DEV_2432&SUBSYS_01371077 4) Take the code and intelligently place it into TXTSETUP.SIF as: [HardwareIdsDatabase] PCI\VEN_1077&DEV_2432&SUBSYS_01371077 = "qlogic", "????" 5) Finally, search for the value name "Floppy_Desc" under the [sTRINGS] header and you can find the device name. Stick the device name into these two areas in TXTSETUP.SIF: [HardwareIdsDatabase] PCI\VEN_1077&DEV_2432&SUBSYS_01371077 = "qlogic", "QLogic Software Diskette" [SCSI] qlogic = "QLogic Software Diskette" Oh. Be sure to declare in DOSNET.INF as well. If you can succeed here, then you are home free. QL2X00.INF

Actually, that is not a valid excuse. Simply load up VMware / Virtual PC and try the installation (even if you don't have the RAID controller), if it didn't show any errors and you can complete the whole Windows installation from beginning to the end, then the driver is most likely working. If I am sure, I will be developing Windows for Microsoft instead My goal is to make sure the methods I used is a standard and can be repeated on all other drivers. Whether I was overdoing it or not is not as important. As long as it meets my needs and it works, that's all it matters. haha...the guy's a tough one. He reminds me of the top honchos at work who always asks "Are you sure this? Are you sure that?" whenever you try to explain things to them, as if they don't trust you. Normally I would snap back, "If I know everything I wouldn't be working for you!" or "I don't have answers to every question. Trust me or fire me!" Of course, in this case, I would say "Take it or leave it!" No offense, Yzöwl, just teasing. I am always right! Actually, simply try it out and see. Like I mentioned earlier, load it up in VMware or Virtual PC. Don't include in [sCSI.LOAD] and/or [sCSI] and see how it goes. If it doesn't errs during installation, then you don't need it. Otherwise, live with it! My apologies, I haven't had the chance to lend a hand with the testing yet. I'm on vacation mood and I'll be off to Bangkok for a couple of weeks - food, spa, massage, food, spa, massage, food, spa....

Email me if you have any queries = itwins@gmail.com Download RAID Slipstreamer v5.4 Build 090424 (4.4Mb) *** NEW *** v5.4 Build 090424 * MD5 - 5439D152E7CA8F2DE96435FE8C09E2DD * SH1 - 9B9AACE2E2ACE312A0EDDB932311187E8C45EA74 NOTE - local Administrative privilege is a MUST! NOTE - Windows Vista x86/x64 users are required to install this Kixforms.Net MSI (screen capture from v5.3 Build 080626) Supported Drivers (2003, 2000, XP, AMD64) PS. During slipstream, it will create and copy all the RAID drivers to the "\I386\$OEM$\$1\Drivers\RAID" folder (x86 OSes) and "root\$OEM$\$1\Drivers\RAID" folder (x64 OSes) . You may need to add this string in your UNATTEND.TXT, WINNT.SIF or SYSPREP.INF answer file: [Unattended] OEMPnPDriversPath=Drivers\RAID; ---------------------------------------------------------------------------------------------------------------------------------- Supported command-line parameters, primarily for the purpose of automation or use in batch files: * /Install to install drivers * /Uninstall to remove drivers * /Source <root_path_of_OS_folder> or <path_to_SYSPREP.INF> or <path_to_i386> * /Mode "Sysprep" or "WinPE" * /OS "XP" or "2003" or "2000" or "AMD64" * /PNPINI <PNP_File> * /DRVPATH <DRV_Path> * /Export * /NoGUI * /Quick Example: "RAID Slipstreamer v5.3 Build 080626.exe" /Uninstall /Source C:\W2K3R2 /Quick - This uninstalls PnP codes and drivers from the C:\W2K3R2 source folder "RAID Slipstreamer v5.3 Build 080626.exe" /Install /Source P:\WINXP /Quick - Automatically slipstream into P:\WINXP\i386 unattendedly "RAID Slipstreamer v5.3 Build 080626.exe" /Install /Source P:\WIN2K3 /Mode SYSPREP /OS 2003 /Quick - For use with Sysprep if you wish to create one image that works for different hardware configurations. - Automatically updates driver info into P:\WIN2K3\SYSPREP.INF and copies all the Windows 2003 drivers into P:\WIN2K3\DRIVERS\RAID. You will need to manually copy the DRIVERS\RAID folder to C:\DRIVERS\RAID of your sysprep image. "RAID Slipstreamer v5.3 Build 080626.exe /Install /Source S:\XPe /Mode WINPE /OS XP /NoGUI - For use with WinPE 2005. Does not work with Vista PE. Actually Microsoft PEIMG does a better job than this. - This updates driver info to S:\XPe\TEXTMODE.SIF and copies Windows XP drivers to its corresponding directories. - /NoGUI tells the program to suppress the interface - When /NoGUI is used, /Quick is also enabled "RAID Slipstreamer v5.3 Build 080626.exe" /Export - This exports the RAID.INI file that is integrated into the program. You can then find out what PnP drivers the tool supports. - This exports the RAID.INI to the path where the RAID Slipstreamer executable resides in "RAID Slipstreamer v5.3 Build 080626.exe" /Install /Source P:\WXPSP2 /NoGUI /PNPINI X:\text\msd.ini /DRVPATH x:\Drivers\XP - This tells the program that you supply your own PnP INI file and drivers. - The PnP INI must be in this format. For example: ---------------------------------------------------------- [2003] 1=HPDRV 2=END [XP] 1=HPDRV 2=End [2000] [AMD64] [HPDRV] LABEL="HP ABC RAID 0,1,5,6,10,50 Controller" DRIVERNAME="HPMSDDRV.SYS" 1="PCI\VEN_9005&DEV_0285&SUBSYS_02989005" 2="PCI\VEN_9005&DEV_0285&SUBSYS_02999005" 3="PCI\VEN_9005&DEV_0285&SUBSYS_029A9005" 4="PCI\VEN_9005&DEV_0285&SUBSYS_02A49005" 5=End ---------------------------------------------------------- - This tells the program that the HPDRV driver supports both Windows 2003 and XP and the PNP codes to integrate are listed in the [HPDRV] header. You can find these PNP codes in the OEMSETUP.INF or TXTSETUP.OEM files that normally comes with the driver. - The LABEL variable is for visual use only. Windows doesn't care what you name it - The DRIVERNAME variable is the main DRIVER.SYS file used by the driver - Always include an "END" at the end of each section and the numbering must be accumulative. If you skip one number, the program might go into an endless loop. - /DRVPATH is used in conjunction with /PNPINI. You need to specify the path of where your physical storage drivers are located - When both /PNPINI and /DRVPATH are used, the program's integrated PNP codes and drivers are bypassed. You provide your own... Cheers, ---------------------------------------------------------------------------------------------------------------------------------- eLearning You don't wish to use RAID Slipstreamer but you wish to learn how to do it yourself. No problem: To learn how to slipstream drivers so you don't have to press F6: 1) Create a C:\TEMP 2) Create a blank file and name it DOSNET.INF 3) Create a blank file and name it TXTSETUP.SIF 4) Run "RAID Slipstreamer x86 v5.0 Build 071116.exe" /install /source c:\temp /os 2003 /quick 5) Examine and learn how RAID Slipstreamer does it. It shouldn't be too hard to learn... To learn how to slipstream drivers for use in SYSPREP: 1) Create a C:\TEMP 2) Create a blank file and name it SYSPREP.INF 3) Run "RAID Slipstreamer x86 v5.0 Build 071116.exe" /install /source c:\temp /mode SYSPREP /os 2000 /quick 4) Copy C:\TEMP\DRIVERS\RAID into your Sysprep image's C:\DRIVERS\RAID. 5) Manually add "OEMPnPDriversPath=Drivers\RAID" into SYSPREP.INF 6) Examine and learn. To learn how to slipstream drivers for use in WinPE 2005: 1) Create a C:\TEMP 2) Create a blank file and name it TXTSETUP.SIF 3) Create a C:\TEMP\INF 4)) Create a C:\TEMP\SYSTEM32 5) Run "RAID Slipstreamer x86 v5.0 Build 071116.exe" /install /source c:\temp /mode WINPE /os XP /quick 6) Examine and learn. Question about $OEM$ placements Some question the $OEM$ directory placement used by RAID Slipstreamer, where it defaults to "\I386\$OEM$". The $OEM$ placement depends on how you install your operating systems. For myself, I installed Windows OSes (32-bit only) using UNATTEND.TXT across the network and the $OEM$ folder must be placed inside \i386. However, if installing Windows using CD/DVD through the use of WINNT.SIF (or without) or installing 64-bit Windows, the $OEM$ must be placed in the same path as the \I386. ie: \i386 \$OEM$ Hope this clears things up. ---------------------------------------------------------------------------------------------------------------------------------- Updates What's new in v5.4 Build 090326: - This release is more of a bugfix than an update, but some drivers were updated nonetheless (although I don't remember which :-/ ) - Corrected the two corrupt drivers that were showstoppers in v5.3. - Tested to run on Vista x86 and x64. However, you are required to install the Kixforms.Net MSI. (Ignore the Microsoft .Net error that appears when run) What's new in v5.3 Build 080626: - Updated mainly because of the introduction of Intel's ICH10x AHCI driver. And as always, while I'm updating it, I updated all others as well. These include: Adaptec 20xx/21xx/22xx/24xx/26xx/28xx/ICP90X4R0 SCSI/RAID Controller (AAC.SYS /ARC.SYS -- 2000/2003/XP/AMD64) - Used (and renamed) by numerous vendors including Dell and IBM Adaptec SAS/SATA RAID / IBM ServeRAID 8i/8k/8k-l/8s SAS Controller (AACSAS.SYS / ARCSAS.SYS -- 2000/2003/XP/AMD64) - Used (and renamed) by numerous vendors including Dell and IBM Intel ICH6x/ICH7x/ICH8x/ICH9x/ICH10x SATA RAID Controller (IASTOR.SYS / IAAHCI.SYS -- 2000/2003/XP/AMD64) QLogic QL40xx iSCSI 1Gbps Controller (QL40XX.SYS -- 2000/2003/XP/AMD64) LSI Logic SAS 5e/5i/5iR/6iR/1020/1030/1035/1064/1064E/1068/1068E/1078/3000 (SYMMPI.SYS / LSI_SAS.SYS -- 2000/2003/XP/AMD64) - Used (and renamed) by numerous vendors including Dell and IBM LSI Logic MegaRAID 8408E / IBM ServeRAID MR10 SAS/SATA Controller (MEGASAS.SYS / MSAS2K3.SYS -- 2000/2003/XP/AMD64) - Used (and renamed) by numerous vendors including Dell and IBM AMD 790FX / ATI SB600 AHCI RAID Controller (AHCIX86.SYS -- 2000/2003/XP/AMD64) - Up to the ATi Xpress 3200 chipset LSI Logic MegaRAID SAS 8204/8208 XLP/ELP (MEGASR.SYS / MEGASR2K.SYS -- 2000/2003/XP) - Used (and renamed) by numerous vendors including Dell and IBM Marvell 6121 SATA Controller (MV61XX.SYS - 2000/2003/XP/AMD64) --> Used by some of those crappy Asus P45 motherboards that hang once in a while, just like its P35 brothers. Asus is CRAP! All other drivers are unchanged. What's new in v5.2 Build 080104: - Finally added AMD64 64-bit drivers. Limited testing was performed; only VMware Workstation v6.x's virtual LSI Logic Ultra320 SCSI controller and the Intel ICH9R AHCI and RAID0/1/5 configurations were tested. Next week I'll head out to the local Dell Solution Center to try out RAID Slipstreamer (and Sysprep Creator) on their latest and greatest workstations and servers. BTW, the x64 drivers are applicable to both Windows XP x64 and Windows Server 2003 x64 Editions. - Fixed the minor /NoGUI bug in previous version - Added a number of new controllers drivers and updated some existing ones as well. - Modifed some of the drivers that have a tendency to break Sysprep - Speed up the extraction process by sacrificing a little disk space. Even with 64-bit drivers added, the program is still only 4.1Mb...still very acceptable - Now when performing uninstallation, the $OEM$\$1\Drivers\RAID folder is deleted - Added new "AMD64" command-line parameters for the /OS switch. Changes to the logic: - DO NOT INCLUDE THE "I386" OR "AMD64" in the source paths. Otherwise, it will err. - AMD64 drivers are not installable on WinPE - AMD64 drivers are installable on Sysprep but was not tested yet - The $OEM$ placement will remain inside the I386 folder for x86 OSes but for x64 OSes, the $OEM$ is placed alongside the AMD64 folder. ie: x86 OSes ----------- \i386\$OEM$\$1\Drivers\RAID x64 OSes ----------- \$OEM$\$1\Drivers\RAID \AMD64 \I386 - This GUI section is now obsolete and is longer useful. It is really there just to take up space...for now. This tool is getting more and more complicated. One of these days I will need to write an usage guide. However, this might take some time as work, family, and XBox360/PS2/PS3/Wii/PSP come first (in no particular order )... Enjoy! What's new in v5.1 Build 071204: - My apologies for forgetting to mention v5.0's new directory structure for user-defined driver paths. Rather than explaining the complex path structure of v5.0, I've decided to release v5.1 that uses the simpler, older format instead. The old format is to put all the drivers into a single directory. ie. Download RAID drivers from manufacturer, extract to a directory (eg: C:\DRIVERS) and then specifying that with the /DRVPATH parameter (eg. /DRVPATH C:\DRIVERS). CAUTION 1: Subfolders within user-defined paths are not supported and there is no reason to. CAUTION 2: Uninstall does not remove user-defined /PNPINI or /DRVPATH. - With v5.1, when /DRVPATH is specified, the built-in drivers are not extracted. This allows for faster user [slipstreaming] experience. - Re-added VMWare's LSI Logic controller driver. VMware really gave me a wild goose chase having ONLY included the BusLogic drivers on their website but failed to also include the LSI Logic 1020/1030 SCSI Controller drivers. I always thought their custom made VMSCSI.SYS included support for both BusLogic and LSI Logic. I was wrong. - Added the LSI Logic 8408E controller drivers, which are the same used on the new IBM ServeRAID MR10 series of RAID controllers. The Windows 2003 driver uses MSAS2K3.SYS while Windows 2000/XP uses the MEGASAS.SYS driver. - Corrected the confusion with SYMMPI.SYS drivers (I think), especially those released by Dell. Dell has a habit of editing LSI Logic drivers and removing those PnP codes that they don't use. However, if you download the same driver from LSI Logic, it contains more PnP device codes as it supports other manufacturers as well, not just Dell's. Remind me to always download drivers from LSI Logic and not from Dell. What's new in v5.0 Build 071116: - There are three main features in v5.0. 1) Uninstall feature 2) Driver Info list 3) Slipstream only the drivers you selected First 2 of the features I most wanted and the last one was from popular demand. Other feature: 4) Removed / edited those drivers that break Sysprep (those JRAID crap was one of them) 5) Removed drivers that are obsolete or hard to set (nVidia 680 SLI. Somehow I found these drivers confusing) 6) Now supports a number of PCMCIA and PCI-Express eSATA controllers 7) I bought and tested on a number of ATi Crossfire motherboards and Core2Quad systems 1) Install / Uninstall -- With command-line installation, you now need to specify the "/install" switch. Ex: "RSLIP.EXE /Install /Source <i386 path> /Quick" -- To uninstall, provide the source path, select the Uninstall radio button and click Proceed. -- Built in is a database of drivers and device codes since RSlip v3.0. It removes only those drivers and codes listed. -- Uninstall can be command-line'd. Ex: "RSLIP.EXE /Uninstall /Source <i386 path> /Quick" - auto uninstall drivers and device codes -- Uninstall feature only removes main drivers and info listed in TXTSETUP.SIF and DOSNET.INF; supporting .SYS drivers are not removed. No issues here really. The objective is to eliminate those annoying missing drivers messages during installation when the driver file is removed but the device infos are left behind -- Uninstall feature does not delete any files listed in \$1\Drivers\RAID directory. It's no big deal really as it only takes up space. If space is an issue, manual delete then. -- User-provided pnp/driver list is not supported for command-line uninstall 2) Driver Info List -- Clicking on the "DrvInfo" button on the main menu displays the driver info of the selected OS -- Well, not much need to be explained here. This allows me to easily see which driver needs to be updated and which doesn't 3) Slipstream only the drivers you selected -- To install only the drivers you selected, Click on the "DrvInfo" button on the main menu, select at least one of the driver checkboxes, provide the source path and click Apply -- Single-driver installation is not supported in command-line -- Info in the driver list is collected in real-time. Therefore, there could be performance inpact for slower systems. I will improve this on future versions... Last but not least, in case you don't know, RAID Slipstreamer since v2.x allows automatically slipstreaming to multiple operating system folders. For example, my remote server share contains all my different operating system source folders: ...too many to list but you get the picture. To automatically slipstream drivers into each and every folders listed there, simply specify the root path and click Proceed. For my case, I just type in "V:" and click Proceed. Come back in a hour with v3.0.4 12 minutes with v4.0 Build 070915 - and all source folders are updated to the latest. Neat, huh? That was really the main reason why I created RAID Slipstreamer...to save me time!

As Tomcat76 pointed out, there is no "SiWinAcc"...among other problems too. I've list out the problematic entries (see above) The strings from all 3 sections MUST MATCH. Yours don't: 1) jgogo is defined in [sCSI.LOAD] but missing in [sCSI] and [HardwareIdsDatabase] 2) SiWinAcc is defined in [sCSI.LOAD] but missing in [sCSI] and [HardwareIdsDatabase] 3) iaAHCI is defined in [sCSI] but missing in [sCSI.LOAD] and [HardwareIdsDatabase] Take a look at the structure of the VMware driver (the simplest of all drivers) and see what you did wrong with yours: ------------------------------------------------------- [sCSI.Load] vmscsi = vmscsi.sys,4 [sCSI] vmscsi = "VMware SCSI Controller" [HardwareIdsDatabase] PCI\VEN_104B&DEV_1040 = "vmscsi" -------------------------------------------------------

Yzöwl: Try removing "@" from "Intel@" under the SCSI header

As do I, but Windows cannot install for me whether or not I use this thread's driver method.Not sure what the problem is. Maybe my VMWare installation has a problem? Everybody has a different way of building Windows. Maybe that has something to do with it I use DOS, run WINNT.EXE with lots of parameters and give it an answer file for installing unattendedly. If you also use this method then you might need to use UMBPCI.SYS to workaround this VMware / LSI Logic issue. Most people I see use WINNT32.EXE or simply booting up to CD and install step by steps, but I don't have much experience to this methods on VMware - I have not use step-by-step methods of many many years already. If you use Windows 98 SE DOS Bootdisk (MSDOS v7.10) to install any Windows using VMware's LSI Logic controller, you will get this error and VMware crashes:

I saw that message too but I ignored it by clicking OK. Well, blame it VMware. It is one extremely problematic program regardless of what version you use, hence the reason why I had to write Installation and Usage Guides for the guys at work to teach them how to workaround to building my Standard Builds. btw, Win98SE's EMM386.EXE crashes VMware's virtual LSI Logic SCSI driver and when booting up with WinME's DOS bootdisk, setting up Windows 2000 Pro could give tons of installation errors. Yup! VMware is so problematic! When using VMware's LSI Logic driver, I had to resort to using Uwe Sieber's UMBPCI.SYS memory manger to workaround this problem.

heh...now you had me worried. Although I use VMware everyday and I have written VMware installation guides (for work) and RAID Slipstreamer Installation Guide (for work), one can never be too sure about anything. Therefore, I had to test it out immediately to make sure I wasn't BS-ing myself, BS-ing my colleagues, and BS-ing everyone whom I made the tool available on MSFN, that my RAID Slipstreamer supported VMware's SCSI controller. My conclusion...phew... .... I am happy to say I was able to unattendedly build Windows 2000 Professional successfully using LSI Logic and set to use SCSI HDD. I used my RAID Slipstreamer v2.0 to slipstream all drivers into the Windows 2000 SP4 i386 source. I then setup VMware Workstation v5.5.1 Build 19175 using the following settings: ...and the final result and proof: BTW, you know why I say the VMware SCSI Controller is an LSI Logic 1020/1030 SCSI Controller? The reason was because when I attempted to add the LSI 1020/1030 into RAID Slipstreamer v1.1.0 (2 years ago), I realized both VMware v4.x SCSI Controller and LSI Logic's 1020/1030 have exactly the same vendor and device codes: PCI\VEN_104B&DEV_1040

oh...hehe...I snatched it from inside VMware. When you click on "Install VMware Tools...", it is then accessible from the virtual CDROM from inside VMware. The driver can be found at \Program Files\VMware\VMware Tools\Drivers\SCSI\Win2k

Sorry. Those are unrelated topics and my post should have been more clear. That error causes text-mode setup to fail. I fixed the entry and was able to continue, but wanted to let Oleg know so that the package could be updated.Where did you get this other driver? Ah...my mistake. Umm...what other driver?