iTwins

Tain: Hmmm, I don't know how you can test the SiS drivers EVEN if you have the LSI Logic drivers for VMWare. Anyways, help yourself. Try adding it manually: DOSNET.INF: [FloppyDisk.2] d1,vmscsi.sys [Files] d1,vmscsi.sys TXTSETUP.SIF: [SourceDisksFiles] vmscsi.sys = 1,,,,,,3_,4,1 [HardwareIdsDatabase] PCI\VEN_104B&DEV_1040 = "vmscsi" [SCSI.Load] vmscsi = vmscsi.sys,4 [SCSI] vmscsi = "VMware SCSI Controller" Attached are the LSI Logic 1020/1030 Ultra320 SCSI drivers for VMware Workstation v5.5.x. The attached VMware drivers work on all platforms. VMSCSI.rar

Yep, something like this B) Nice. 10 years expat and you can retire! Now I know why you're helping out with this HFSLIP thingy...hehe...nothing else better to do in GZ! just teasing... Seriously, yes, its very challenging and I enjoy doing this kind of tinkering / tweaking Windows stuff too...only when I was not hooked on the da-mn Playstation. I would've enjoy it more if it wasn't the wife kicking my butt on the game!

You don't sound like a local. Quite a long way from home, sailor. What brought you to GZ? Expat?

You're welcome. Glad to lend a hand No, Hong Kong, right next door....no casinos over here, just plenty of smog, courtesy of mainland China.

Heh...you make it sound as if its a life or death situation. http://www.msfn.org/board/index.php?showto...&st=0

I hate Autorun's... Normally I just go into the Local Group Policy and disables it permanently FOR ALL DRIVES. Run GPEDIT.MSC. Browse to Computer Configuration > Administrative Templates > System. Set "Turn off Autoplay" to "Enabled > All Drives"

Check your motherboard's BIOS to see if it allows disabling AHCI. Some motherboards or some models such as Dell's Precision and Latitude series have a setting in the BIOS that you can disable AHCI or something about "Compatibility Mode". Once disabled, the SATA controller will act like a normal IDE. You can install your OS normally without the need for cumbersome drivers. Once you have completedly installed the OS, you can then install your SATA drivers and go back to the BIOS to enable AHCI again.

Well, I'm offering my first cent. Link to the RAID Slipstreamer v2.0's Mass Storage Drivers Inside "Mass Storage Drivers for Wintel.rar" are Windows drivers that are categorized by the following folders: 2K_2K3 2000 2003 XP COMMON XP_2K I think it's quite self-explanatory - platform specific drivers. For example. "2K_2K3" means this driver only works on Windows 2000 and Windows 2003. However, don't come crying to me if it works on XP as well for example. I simply took the vendor's words. They say it doesn't support XP and I take their words for it. If however I ignore this warning and the RAID array died, we cannot whine at the manufacturer! Anyways, inside each folder are the compressed SYS files. These are to be copied to the I386 share and specified in both TXTSETUP.SIF and DOSNET.INF Last but not least, inside each folder is a sub folder called FULL. These are the complete vendor supplied drivers that I tell the RAID Slipstreamer to copy to the "OEMPnPDriversPath" string specified in the Answer File. Note that I have modified some of the OEMSETUP.INF (I renamed most too to avoid any duplicate filenames) to point directly to the root directory rather than their original paths, usually categorized by platform type. For most people, you have no use for these drivers. For big corporations that have too much money to spend and can afford to buy US$4,000 controller cards AND YOU HAVE TO SUPPORT THEM, this is worth the trouble. OLEG: Feel free to add them to your set of drivers. Cheers,

Well, I rest my case then. Thanks for the offer; I'm honored...but I'll have to decline. Work is mostly hectic, only recently I get spare time to do some research. At home, **** Playstation is taking up all my spare time. I'll just barge in in your discussions, pretends to be pro, and offer my few cents. huh....that's a first I've ever seen on a forum...."You have posted a message with more emoticons that this board allows. Please reduce the number of emoticons you've added to the message". Geezus, and I thought the restrictions I integrate into the operating systems I developed for work were restrictive....

umm... 1) On the remote system, create an account with write permissions. Create the same account and password on the local system if you haven't already done so. 2) On the remote system, create a share (if you haven't done so) and give this account write permission 3) On the local system that you are to backup, create a batch file that maps to the share using the account you created in step 1, and add in the backup using command-lines 4) Scheduled the task to login using this account in Step 1 and set it to run the batch file you just created You can logoff and restart your system all you want. As long as you do not shutdown your local and remote system, the schedule task should login using the specified account, run the specified batch file, net use to the specified remote share, then finally run the specified backup That's all.

Could it be this? Possible values are: "ConvertNTFS" or "LeaveAlone" Cheers

May I also add that if support files are referenced in the OEMSETUP.INF, then it is strongly advised to add them into the TXTSETUP.SIF. Although unrelated to RAID drivers, but integrating graphic card drivers are done similarly. If you noticed, the layout of the OEMSETUP.INF for RAID and VIDEO drivers are almost exactly the same. But then, some vendors have their own way to doing things that is differently from the rest of the boys. Some of the nVidia drivers are a real pain in the butt - especially those Quadro drivers. Eventhough the files are not referenced in the OEMSETUP.INF, these unlisted files are probably called by the DLL files themselves. If you missed one CHM or HLP file for example, it will abort the installation. Maybe this was the reason why your HFSLIP 60810 did not work. Don't feel bad though, nLite v1.2 RC didn't work either. Sorry to make it sound confusing. Anyways, the moral of the story is, it is better to reference ALL files in TXTSETUP.SIF...just in case.

Correction. According to this advice it may be useful to include all files INCLUDING SYS into TXTSETUP.SIF. If the SYS files are not included in the TXTSETUP.SIF, the system will BSoD at the initial Text Mode installation phase. The loading of RAID drivers are done in two separate phases. The first phase is the initial blue TEXTMODE screen. It's main purpose there is to load the RAID driver so that it can recognize and format hard disks or do FAT/FAT32 to NTFS conversion. The second phase is during the middle of GUI installation where the system is configuring the Windows GUIs. If the system found that the RAID driver is associated with support files, it will link and load them. Here, if the support files are not found, it will popup a dialog asking for the location of the files. If ignoring them, it will most likely BSoD. hehe...I hear you. However, I don't have too many servers for testing either. If your procedures are done accordingly and conforms to standards, you really only need one RAID controller for testing. The other drivers should work exactly the same way. The drivers that are included in my RAID Slipstreamer v2.0 tool, well, I have only physically tested less than 10% of the RAID controllers listed there. Normally, I get requests from country IT support staffs who have the "unsupported" controller on their servers. They simply send me the RAID drivers and I update the RAID Slipstreamer tool. They will then send me feedback whether it works or not. In most cases, they work flawlessly. In cases where it didn't work, it was usually because the vendor had introduced a new variation of an existing controller and have updated the driver to include new Plug 'n' Play codes. Ex. "PCI\VEN_9005&DEV_0286&SUBSYS_95801014". Nevertheless, I'll be happy to lend a hand whenever possible. I think in HFSLIP's case, it would be very hard to slipstream drivers because each vendor store their drivers differently. Some vendors also like to put their drivers into subfolders categorized by platform types (IBM loves doing that!). For example: \OEMSETUP.INF \2003\DRIVER.SYS \2003\DRIVER.DLL \2003\DRIVER.CAT \2000\DRIVER.SYS \2000\DRIVER.DLL \2000\DRIVER.CAT \XP\DRIVER.SYS \XP\DRIVER.DLL \XP\DRIVER.CAT CAREFUL, although they appear to have the same filename, they are not always the same!! Using of the wrong platform drivers could lead to BSoD. Anyways, in this case, either you modify the OEMSETUP.INF to tell it to find the drivers in the root instead OR you add the drivers in "\I386\$OEM$\$1\Drivers\RAID" exactly the way the vendor has specified: ..\I386 ..\$OEM$ ..\$1 ..\Drivers ..\RAID ..\OEMSETUP.INF ..\2003\DRIVER.SYS ..\2003\DRIVER.DLL ..\2003\DRIVER.CAT ..\2000\DRIVER.SYS ..\2000\DRIVER.DLL ..\2000\DRIVER.CAT ..\XP\DRIVER.SYS ..\XP\DRIVER.DLL ..\XP\DRIVER.CAT You may need to find some way to read the directory info from the OEMSETUP.INF and then migrate it to the TXTSETUP.SIF and/or DOSNET.INF. Just make sure you remember this advice: CAREFUL, although they [the drivers] appear to have the same filename, they are not always the same!! Using of the wrong platform drivers could lead to BSoD. I think you guys should have no problems. Since trying out HFSLIP, I no longer underestimate the power of batch programming. Keep up the good work, guys! For more info, see my post here: http://www.msfn.org/board/index.php?showto...173&st=164#

Maybe other files needed in TXTSETUP.SIF and DOTNET.SIF too. It's better to mentions them too only under [sourceDisksFiles] section. Only TXTSETUP.OEM is definetelly not needed. I noticed most of the newer drivers (ie. IBM ServeRAID 7k) do not use the other supporting files such as DLL, EXE, etc. Or at least they do not need it after it has completed OS installation. But I remember vividly that the IBM ServeRAID 4L/4M Controller needs the NFRDCI04.DLL during GUI installation. If the file is not present during installation, it will pop up a dialog asking to provide the location of the files. If you ignore them, it will BSoD. That is one of the reason why I copy all the vendor-supplied files into the directory specified in the UNATTEND.TXT's "OEMPnPDriversPath" string....just in case. In HFSlip's case (since you don't use answer files), it may be necessary to specify all supporting files into TXTSETUP.SIF and possibly DOSNET.INF as well. I find the work too tedious AND at work we use answer files, so I never really investigate this further. Update: I found a controller that uses its supplied DLL file. Check out the QLogic QL4010 iSCSI Controller that has a customized GUI similar to the standard Microsoft device dialog. Right-clicking on the Qlogic iSCSI Adapter device and you will see this dialog: The QLogic QL4010 uses the QL4X00PP.DLL file: Yup. You need all its supporting files as well. NOTE. Copying all the files into I386 without specifying them in TXTSETUP.SIF may not enough. The supporting files are needed during the GUI installation phases and during that phase, the $WIN_NT$.BT~ and $WIN_NT$.BT temp directories are already deleted. Because of this, you may need to tell the OS to copy these non-SYS files into the SYSTEM32 folder. BTW, HFSLIP is the most amazing batch file I've ever seen. Well done!

btw, I noticed XP works better with "1,,,,,,4_,4,1,,,1,4" while 2000 and 2003 work better with "1,,,,,,3_,4,1". I really don't have a clue why but over the years I have adopted this method and it seems alright.

This took me a long time to figure this out because several years ago every Internet search resulted in telling you that you only need to add the entries into the TXTSETUP.SIF. THAT IS NOT ENOUGH! And for those who know, they are not willing to share, as if it was some commercial secrets or whatever. I am glad MSFN.org is around. I learnt alot from this forum and the generous people here who are willing to share! Kudos to you all! Anyways, how are you guys reading Kixtart scripts? It shouldn't be too hard to understand even if you don't know VB/VBS or Kixtart. The RAID Slipstreamer was mainly written using Kixtart scripts; the GUI was written using VB6. I am really not a programmer. In fact I am terrible in programming. This is just a small portion of the whole program. In this case, it was the IBM ServeRAID 8i/8k Controller subroutine: :AACSAS ; --------------------------------------------------------------------------------------------------------- ; IBM ServeRAID 8i/8k ; ; For Windows XP/2000 ; --------------------------------------------------------------------------------------------------------- writeprofilestring("$PATH\DOSNET.INF","FloppyFiles.2","d1","aacsas.sys") writeprofilestring("$PATH\DOSNET.INF","Files","d1","aacsas.sys") IF $OSTYPE="XP" writeprofilestring("$PATH\TXTSETUP.SIF","SourceDisksFiles","aacsas.sys","1,,,,,,4_,4,1,,,1,4") ELSE writeprofilestring("$PATH\TXTSETUP.SIF","SourceDisksFiles","aacsas.sys","1,,,,,,3_,4,1") ENDIF writeprofilestring("$PATH\TXTSETUP.SIF","HardwareIdsDatabase","PCI\VEN_9005&DEV_0285&SUBSYS_02f21014",'"aacsas"') writeprofilestring("$PATH\TXTSETUP.SIF","HardwareIdsDatabase","PCI\VEN_9005&DEV_0285&SUBSYS_02989005",'"aacsas"') writeprofilestring("$PATH\TXTSETUP.SIF","HardwareIdsDatabase","PCI\VEN_9005&DEV_0285&SUBSYS_02999005",'"aacsas"') writeprofilestring("$PATH\TXTSETUP.SIF","HardwareIdsDatabase","PCI\VEN_9005&DEV_0285&SUBSYS_029A9005",'"aacsas"') writeprofilestring("$PATH\TXTSETUP.SIF","HardwareIdsDatabase","PCI\VEN_9005&DEV_0285&SUBSYS_02A49005",'"aacsas"') writeprofilestring("$PATH\TXTSETUP.SIF","HardwareIdsDatabase","PCI\VEN_9005&DEV_0285&SUBSYS_02A59005",'"aacsas"') writeprofilestring("$PATH\TXTSETUP.SIF","HardwareIdsDatabase","PCI\VEN_9005&DEV_0286&SUBSYS_95801014",'"aacsas"') writeprofilestring("$PATH\TXTSETUP.SIF","HardwareIdsDatabase","PCI\VEN_9005&DEV_0286&SUBSYS_95401014",'"aacsas"') writeprofilestring("$PATH\TXTSETUP.SIF","HardwareIdsDatabase","PCI\VEN_9005&DEV_0286&SUBSYS_02A29005",'"aacsas"') writeprofilestring("$PATH\TXTSETUP.SIF","HardwareIdsDatabase","PCI\VEN_9005&DEV_0285&SUBSYS_02A39005",'"aacsas"') writeprofilestring("$PATH\TXTSETUP.SIF","SCSI.Load","aacsas","aacsas.sys,4") writeprofilestring("$PATH\TXTSETUP.SIF","SCSI","aacsas",'"IBM ServeRAID 8i/8k SAS Controller"') SHELL 'CMD /C C:\WINNT\TEMP\ALTER.EXE $PATH\DOSNET.INF "d1=aacsas.sys" "d1,aacsas.sys"' SHELL "CMD /C DEL $PATH\DOSNET.DEL" RETURN PS. ALTER.EXE is a DOS program to search and replace text within a file. In this case, it searches for "d1=aacsas.sys" and replaces it with "d1,aacsas.sys" 1) Depending on the platform type, copy all the vendor-provided drivers to the user-provided "\$OEM$\$1\Drivers\RAID" path. Hence the reason why you need to specify the "OEMPnPDriversPath=Drivers\RAID" strings in the UNATTEND.TXT answer file 2) And then copy all the compressed .SYS files to the user-provided I386 path. You don't really have to compress the .SYS files but I'd like to follow the Microsoft standard and I have to conserve disc space as I have to stuff 18GB operating system files into a 4.7GB DVD disc. SELECT CASE $OSTYPE = "2003" SHELL "CMD /C COPY /y C:\WINNT\TEMP\2003\FULL\*.* $PATH\$OEM$\$1\Drivers\RAID" SHELL "CMD /C COPY /y C:\WINNT\TEMP\2003\*.SY_ $PATH" CASE $OSTYPE = "2000" SHELL "CMD /C COPY /y C:\WINNT\TEMP\2000\FULL\*.* $PATH\$OEM$\$1\Drivers\RAID" SHELL "CMD /C COPY /y C:\WINNT\TEMP\2000\*.SY_ $PATH" CASE $OSTYPE = "XP" SHELL "CMD /C COPY /y C:\WINNT\TEMP\XP\FULL\*.* $PATH\$OEM$\$1\Drivers\RAID" SHELL "CMD /C COPY /y C:\WINNT\TEMP\XP\*.SY_ $PATH" ENDSELECT That's all, really. For more information, refer to my other post elsewhere: http://www.msfn.org/board/index.php?showto...173&st=164#

Yes, these are similar to the methods I used If anyone is interested, I have recently updated the "RAID Slipstreamer" (for work) that integrates all known SCSI/RAID/SATA drivers used in my company into Windows XP, Windows 2000 and Windows Server 2003 I386 source, allowing for automatic detection of mass storage drivers (for use with unattended installation). Country IT staffs have been using this for several years already and they all seem very happy. And the best is that, I only need to update the package once every 1.5 to 2 years (IT support staffs hate change ) It's really nothing more than what you may already know but for [lazy] people who don't feel like doing it themselves... email me if you are interested = itwins@gmail.com. It's only 3.6MB small and it slipstreams these drivers (the editor attachment doesn't work!) Download RAID Slipstreamer v2.0 from Rapidshare (Work email excerpt to global IT support staffs) Raid Slipstreamer v2.0 supports: - All models of IBM System X servers - All models of IBM eServer xSeries servers - All models of Dell PowerEdge servers - All models of Dell Precision Workstations - All models of Dell desktops with SATA/RAID Controllers and AHCI enabled Raid Slipstreamer v2.0 supports the following Mass Storage Devices: Windows 2003 - IBM ServeRAID 8i/8k SAS Controller - Intel 82801FR/GHM/GR/GH/GBM/FBM AHCI/SATA RAID Controller - Adaptec Ultra320 SCSI Controller / IBM ServeRAID 7e SCSI Controller - IBM ServeRAID 4M/4Mx/4L/4Lx/5i/6M/6i/7k Controller - LSI Logic PERC 4e/Di,4e/Si,4e/DC,4/Di,4/DC,4/SC,3/QC,3/DC,3/DCL,3/SC - LSI Logic SAS 5x RAID Controller - LSI Logic Perc 5e/i Raid Controller - Adaptec 39160 Family SCSI Controller - Adaptec PERC 2, 2/Si, 3/Si, 3/Di SCSI Controller - QLogic QL40xx iSCSI Controller - QLogic QL2300 Fiber Channel Controller - Adaptec AIC-94xx SAS/SATA Controller - Adaptec ASC-48300 SAS/SATA Host Adapter - Promise Technologies Ultra 33/66/100/133 TX2 IDE Raid Controller - VMware SCSI Controller Windows 2000 - IBM ServeRAID 8i/8k SAS Controller - Intel 82801FR/GHM/GR/GH/GBM/FBM AHCI/SATA RAID Controller - Adaptec Ultra320 SCSI Controller / IBM ServeRAID 7e SCSI Controller - IBM ServeRAID 4M/4Mx/4L/4Lx/5i/6M/6i/7k Controller - LSI Logic PERC 4e/Di,4e/Si,4e/DC,4/Di,4/DC,4/SC,3/QC,3/DC,3/DCL,3/SC - LSI Logic SAS 5x RAID Controller - LSI Logic Perc 5e/i Raid Controller - Adaptec 39160 Family SCSI Controller - Adaptec PERC 2, 2/Si, 3/Si, 3/Di SCSI Controller - QLogic QL40xx iSCSI Controller - QLogic QL2300 Fiber Channel Controller - Adaptec AIC-94xx SAS/SATA Controller - Adaptec ASC-48300 SAS/SATA Host Adapter - Promise Technologies Ultra 33/66/100/133 TX2 IDE Raid Controller - VMware SCSI Controller Windows XP - IBM ServeRAID 8i/8k SAS Controller - Intel 82801FR/GHM/GR/GH/GBM/FBM AHCI/SATA RAID Controller - Adaptec Ultra320 SCSI Controller / IBM ServeRAID 7e SCSI Controller - IBM ServeRAID 4M/4Mx/4L/4Lx/5i/6M/6i/7k Controller - QLogic QL2300 Fiber Channel Controller - Dell SAS 5x RAID Controller - LSI Logic Perc 5e/i Raid Controller - Adaptec AIC-94xx SAS/SATA Controller - Adaptec ASC-48300 SAS/SATA Host Adapter - Promise Technologies Ultra 33/66/100/133 TX2 IDE Raid Controller - VMware SCSI Controller Raid Slipstreamer v2.0 has been tested to work on the following servers: - IBM ServeRAID 8i SAS Controller (IBM System X x3650 server - Windows XP and Windows 2003) - Intel 82801FR SATA Raid Controller with AHCI enabled (Dell Precision Workstation 390) - Home-Built server (Promise Technologies Ultra 33/66/100/133 TX2 IDE Raid Controller) - VMware Workstation v5.5.x (virtual LSI Logic 1020/1030 Ultra320 SCSI Controller) PS. During slipstream, it will create and copy all the RAID drivers to the "\I386\$OEM$\$1\Drivers\RAID" folder. You may need to add this string in your UNATTEND.TXT answer file: [Unattended] OEMPnPDriversPath=Drivers\RAID; Cheers,

Microsoft had a program called the "MS Internet Explorer 6 SP1 Setup MSI Wrapper". you can use it for other purposes, not just IE6SP1. It's no longer available for download, therefore you might have to contact a MS representative instead. http://support.microsoft.com/default.aspx?...;810011&sd=tech A nice guy wrote another program called the Windows Installer Wrapper Wizard v0.0.0.1 (haha) Don't let the version fool you...it's not buggy at all. I've attached it for your reviewing pleasure....only 450k small. Enjoy!