iTwins

Member
  • Content count

    119
  • Joined

  • Last visited

Community Reputation

0 Neutral

About iTwins

Contact Methods

  • Website URL
    http://
  1. Auto-slipstreaming into sysprep.inf is not hard, just that Sysprep is very picky. Some of the drivers I had to modify its INF file to prevent Sysprep from hanging during the preparation stage. No promises but I'll see what I can do....but DON'T keep your hopes too high
  2. I haven't tried Driverpacks before but doesn't it already do what RSlip does and probably better? Cheers,
  3. Rapidshare no more. Here's the Netload link: RAID Slipstreamer v5.4 Build 090424
  4. Could anyone help? I get this alot: The situation occurs on XP SP3 (both client and host) and I share a USB drive for other XP clients on the network. Whenever I try to NET USE to the host USB share from an XP client, the "Error 1130: Not enough server storage available to process this command" appears on the client side and NET USE is unsuccessful I have tried all suggestions found on the web: 1) Set IRPStackSize to hex:F or 2) Set PagedPoolSize to Dword:0 or 3) Set MinFreeConnections to Dword:5 All cannot solve my problem. The only way to resolve this was to re-run XP Service Pack 3, which you can imagine, is very time-consuming. Any other idea?
  5. Sounds great, any documents demonstrating this switch? heh, it was already mentioned in the first post. "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 how 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... The intention of this parameter is so you can DIY. You no longer need me to constantly release new updates. The design is nothing to write home about but it does the job right. Take it out for a test drive. Cheers,
  6. Ok, this is what I do: 1) Install Windows XP like a normal person does, regardless whether it's interactive or unattended. 2) After WinXP is installed, configure WinXP and then install all necessary MS or 3rd party applications, including service packs and hotfixes 3) Copy the required Sysprep directory to C:\Sysprep 4) Within C:\Sysprep is a Sysprep.inf. This is all you need in the INF file. Sysprep and RAID Slipstreamer will fill in the rest. [Unattended] InstallFilesPath=C:\Sysprep\i386 OemSkipEula=Yes DriverSigningPolicy=Ignore UpdateInstalledDrivers=Yes OEMPnPDriversPath=Drivers\Audio;Drivers\Misc;Drivers\NIC;Drivers\RAID;Drivers\System;Drivers\Video;Drivers\Modem;Drivers\PCMCIA; [RegionalSettings] LanguageGroup=1,7,8,10,11,9,13,14 [GuiUnattended] OemSkipWelcome=1 EncryptedAdminPassword = No [Identification] [GuiUnattended] TimeZone=210 [RegionalSettings] Language=409 [UserData] ProductID="ABCDE-12345-FGHIJ-67890-KLMNO" FullName = "Your Name" OrgName = "Your Company Name" Password = "Passw0rd" ComputerName= "Computer Name" [Networking] InstallDefaultComponents=Yes [Display] BitsPerPel=32 Xresolution=1027 YResolution=768 Vrefresh=75 [SysPrep] BuildMassStorageSection=yes [SysprepMassStorage] 5) In WinXP, open a command prompt and run "Sysprep -bsmd" 6) Then run "RSLIP54.EXE /install /source %SystemDrive%\Sysprep /mode Sysprep /OS XP /NoGUI" 7) Run Sysprep -reseal -mini -pnp -quiet -noreboot 8) Verify the WinXP configurations and applications are in place before [manually] shutting down 9) After shutdown, boot to Vista PE and proceed to create the WIM image When you have your WIM image, it is ready to deploy to other systems. Regarding the APIC HAL issue, if the image was created on a multi-processor CPU for example and the image is to deploy to another system with the same processor type, then no changes required. If however you are deploying to a single-processor CPU, then you may need to add the required parameter into the Sysprep.inf (sorry, I forget what to add. You may have to research yourself). Personally, I created a customized Vista PE that detects the CPU type and then automatically apply the correct HAL and Kernel files after the image has been restored. Actually, it's not really that simple if you are to support multi-core CPUs, single-core CPUs, and legacy and virtual CPUs (including Microsoft Virtual PC 2004/2007)
  7. Yes, you need Vista PE to recognize the HDD before you can deploy images to. It only requires 3 steps, providing that you have already installed MS Windows AIK: 1) "C:\Program Files\Windows AIK\Tools\x86\imagex" /mountrw "%Drive%\Dev\WinPE\HOME_PE20\boot.wim" 1 %Drive%\imagex Where: - "C:\Program Files\Windows AIK\Tools\x86\imagex" is the path and filename of the Imagex.exe - /mountrw "%Drive%\Dev\WinPE\HOME_PE20\boot.wim" is to mount the boot.wim boot image with read and write access - 1 is the first image within boot.wim - %Drive%\imagex is where the directory where you mount your boot.wim into 2) "C:\Program Files\Windows AIK\Tools\PETools\peimg.exe" /inf=%Drive%\Dev\00_OEM_DRV\XP\RAID\vmscsi.inf %Drive%\imagex\Windows Where: - "C:\Program Files\Windows AIK\Tools\PETools\peimg.exe" is the path and filename of the peimg.exe - /inf=%Drive%\Dev\00_OEM_DRV\XP\RAID\vmscsi.inf is the path and filename of the device OEMSETUP.INF. In this case, it's VMware's mass storage controller - %Drive%\imagex\Windows is the path to the Vista PE Windows root 3) "C:\Program Files\Windows AIK\Tools\x86\imagex" /unmount /commit %Drive%\imagex ....for dismounting the boot.wim image and the save the changes. Place the boot.wim back into Vista PE. That's all.
  8. Barely alive. The Nvidia drivers were confusing the hell of me and I didn't have the hardware to confirm if the codes were working or not. Because of this, I removed them from RSlip. You can however DIY by supplying your own PNP Codes and use RSlip's /PNPINI parameter.
  9. I have a similar WIM image that works on all of my home and work desktops and laptops, despite of different IDE/SATA/RAID controllers. I call it 1WIM4ALL. It's actually quite simple: 1) Run Sysprep with the following command-line parameter: Sysprep -bsmd 2) Download and run RAID Slipstreamer with the following command-line: RSLIP54.EXE /install /source %SystemDrive%\Sysprep /mode Sysprep /OS XP /NoGUI where: - %SystemDrive%\Sysprep is where the required Sysprep directory resides in. - /OS XP is to tell RAID Slipstreamer to install XP drivers only - /NoGUI is to run RAID Slipstreamer in silent non-interactive mode 3) Finally, run Sysprep with the following command-line parameters: Sysprep -reseal -mini -pnp -quiet -noreboot When complete (it could take some time, especially in VMware), shutdown and create your WIM image or clone using Norton Ghost. That's all. Cheers, Warning: I hope you are aware of the APIC HAL issues when deploying images to different processor types and ways to workaround it.
  10. There is nothing much to configure on a Txtsetup.sif. It either works or it doesn't; there's nothing in between. Your slowness maybe a result of file allocation errors or worst, hdd bad sectors. It may also be that you installed too many applications that makes the operating system sluggish. Best way is to backup your existing OS and do a clean install. If it's still sluggish, then its most likely a hardware issue.
  11. Updated to v5.4 Build 090326
  12. You are right; v5.3 screwed up somehow. I didn't have the time to figure it out why but it's good that you found a workaround. Well done. I'll see what I can in the future....or try the command-line method and see if it helps. Sorry!
  13. Sorry, I don't have my ICH10x board anymore and even when I had it I have not tried WinPE....so I'll take your word for it. I have no idea but the best way I can think of right now is to identify the Vendor and Device codes of your ICH10x (if it's really an ICH10x compatible controller) Download this program PCISCAN.EXE , run and extract to a floppy disk. Boot it up and run "PCISCAN -V" at the DOS prompt. Identify the "SCSI" subclass: Here's an example of a screen capture taken from VMware Workstation v6.0x configured with a Buslogic IDE controller The above capture shows at the SCSI subclass row, the Vendor code is "104B" and the Device code is "1040". If you look at the VMSCSI.INF that came with VMware Tools, this is the driver code: [VMware.Mfg] %DEVICE%=DDInstall,PCI\VEN_104B&DEV_1040 Anyways, the new v8.2.x Intel storage driver supports these codes: AHCI mode 1=PCI\VEN_8086&DEV_2681&CC_0106 2=PCI\VEN_8086&DEV_27C1&CC_0106 3=PCI\VEN_8086&DEV_27C5&CC_0106 4=PCI\VEN_8086&DEV_2821&CC_0106 5=PCI\VEN_8086&DEV_2829&CC_0106 6=PCI\VEN_8086&DEV_2922&CC_0106 7=PCI\VEN_8086&DEV_2929&CC_0106 8=PCI\VEN_8086&DEV_3A22&CC_0106 RAID mode 1=PCI\VEN_8086&DEV_2682&CC_0104 2=PCI\VEN_8086&DEV_27C3&CC_0104 3=PCI\VEN_8086&DEV_27C6&CC_0104 4=PCI\VEN_8086&DEV_2822&CC_0104 5=PCI\VEN_8086&DEV_282A&CC_0104 Find out if your controller is supported by the v8.2.x version that came with RSlip Build 080626. Cheers,
  14. 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.
  15. That tool includes RAID SATA/SCSI and IDE/AHCI SATA drivers too.