Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

  • Country

    Hong Kong

Everything posted by iTwins

  1. I wonder if you guys are over-reacting on this Sysprep / HAL issue. I have a Sysprep image that did not include the UpdateUPHAL entry and I am able to restore it onto most computer configurations. The image was created from VMWare Worktation v6.0 (Microsoft recommends Virtual PC 2007 for creating the Sysprep image as they claim it to be more compatible than physical computers). My colleagues and I have so far tested it on the following brands and models: Dell Optiplex GX240, GX260, GX270, GX280, GX520 745, 755 (Desktops) Dell Latitude D410, D420, D430, D430 (with SSD), D610, D620, D630 (Laptops) Dell Precision 380, 390 (Workstations) Lenovo Thinkpad X41 Tablet PC, X60, X60 Tablet PC, X61 Tablet PC (Laptops) My home computers: 4 desktops and 4 notebooks of various processors and RAID/AHCI/SATA/SCSI/IDE configurations All work execept my cheapo Taiwanese-made BenQ S73G gaming notebook. However, I don't think it had anything to do with the HAL as it runs on a 1.7Ghz Intel Core Duo processor. It refuses even to bootup and I suspect it may have something to do with the non-standard BIOS. I think it is fair to say that if you don't have to support any legacy hardware (pre-HyperThreading processors) then you really don't need worry about this confusing HAL issue. According to Microsoft referring to the UpdateUPHAL Sysprep entry: "This entry is not required in Windows XP or the Windows Server 2003 family." http://technet2.microsoft.com/windowsserve...3.mspx?mfr=true Also, personally I think Microsoft's ImageX is a better cloning tool than Ghost or Acronis. Apart from its speed, I noticed that it is more hardware friendly than Ghost. I don't know why but it is. Because of this, I have since helped my company's move from Ghost to ImageX. Not only did it saved over US$1 million for 100,000+ licenses but it also chipped a lot time wasted on the time it take to clone an image.
  2. Updated to v5.1 Build 071204. See 1st post for changes.
  3. 1) Place the Sysprep binaries into C:\SYSPREP 2) Place all the XP drivers into C:\DRIVERS (See OEMPNPDriversPath below for driver subpaths. ie. C:\DRIVERS\AUDIO) 3) Create a SYSPREP.INF with at least the following contents and copy into C:\SYSPREP [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; [GuiUnattended] OemSkipWelcome=1 OemSkipRegional=1 EncryptedAdminPassword = No [UserData] ProductID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX FullName ="Jeff Leung" OrgName ="OBTS" ComputerName="Core2Quad-XP" [TapiLocation] [Identification] JoinWorkgroup=HOME [Networking] InstallDefaultComponents=Yes [Display] BitsPerPel=32 Xresolution=1280 YResolution=800 Vrefresh=75 [SysPrep] BuildMassStorageSection=yes [SysprepMassStorage] PCI\VEN_1000&DEV_0054&SUBSYS_1F041028=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0054&SUBSYS_1F061028=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0054&SUBSYS_1F071028=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0054&SUBSYS_1F081028=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0054&SUBSYS_1F091028=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0058&SUBSYS_1F0E1028=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0058&SUBSYS_1F0F1028=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0058&SUBSYS_1F101028=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0058&SUBSYS_021D1028=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0030=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0032=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0050=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0054=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0056=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0058=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0062=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0622=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0624=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0626=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0628=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0640=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_0646=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_005A=C:\Drivers\RAID\SYMMPI.INF PCI\VEN_1000&DEV_005E=C:\Drivers\RAID\SYMMPI.INF 4) Extract the LSI 3041e (SYMMPI) drivers into C:\DRIVERS\RAID. Extract ALL files for the sake of argument 5) Change directory to C:\SYSPREP and at the command-line type "SYSPREP -bmsd" minus the quotes 6) At the command-line, type "SYSPREP -mini -reseal -pnp -quiet" minus the quotes 7) When complete, it will automatically shutdown the system. Now clone the partition using ImageX or Ghost. For single partitions, I recommend WIM (Microsoft ImageX). For multiple partitions, Ghost/Ghost32 or any other imaging tool that clone sectors/tracks - A note of caution concerning Norton Ghost...when the image is huge, it can corrupt easily. I really hate Ghost - regardless of versions they all have issues.
  4. v5.0 Build 071116 release. See main post for feature detail.
  5. I recently bought 2 x Quad core system each with an 8800 GTS 320MB. A week later, I learnt the 8800 GT was out, cheaper, faster, and more memory. However, I wasn't disappointed at all. The fact of the matter is I am still able to play all my games at 1680 x 1050 at high detail. Even Crysis (demo) I was able to play (happily, smoothly and flawlessly) at 1680 x 1050 high detail (no AA) or 1440 x 900 high detail (16Q AA). I really have no complains. However, if I were to buy now, I will definitely go 8800 GT. Afterall, it's everything the GTS has and it's only 1 slot whereas the GTS occupies two slots!
  6. Coincidentally I am working on a project that calls for using VMware's Virtual Desktop Infrastructure. According to Vmware, the current VIC v1.1 cannot support dual monitors and USB devices but v2.0 can. However, v2.0 is in beta and will not be available until the 1Q of 2008. But then, you're using ESX1 and we are using ESX 3.5 + VIC 2.0 Beta, therefore that could be a different story.
  7. The nVidia Crush drivers in which the P5N32-E uses, are not supported in this current version. You may have to do it yourself.
  8. Well, that was the intention. It should work, assuming that you have done everything correctly. Eventhough I don't have a motherboard that use VIA drivers, I was able to run the command-line and it showed that the pnp codes and drivers were slipstreamed to the corresponding paths. I haven't checked but that was also the intention of /PNPINI and /EXPORT switches so that you can do it yourself without me having to check if your codes were included. For your case, run RS with the /export switch. It will generate the RAID.INI file. Open using notepad and search the pnp code yourself to see if the code has already been included in RS. If yes, then run RS without parameters. If no, then you may provide your own when using /PNPINI and /DRVPATH switches.
  9. If you have extracted the files to the C:\TEMP\DRIVERS I asked you to, then you shouldn't get that error. It may be possible that when you extract VIA_DRV.RAR into C:\TEMP\DRIVERS, you also created a C:\TEMP\DRIVERS\VIA_DRV directory. When that happens, be sure to change the /DRVPATH parameter to /DRVPATH C:\Temp\Drivers\VIA_DRV
  10. It is best you use Raid Slipstreamer AFTER using Nlite or HSlip...
  11. To whoever who left me mail regarding using the RS v4.0 x86 version to integrate x64 drivers, here's how you do it (using Build 070920): 1) Download RAID Slipstreamer x86 v4.0 Build 070920.exe 2) Create a C:\TEMP 3) From a clean Win2K3, copy the TXTSETUP.SIF to C:\TEMP 4) From a clean Win2K3, copy the DOSNET.INF to C:\TEMP 5) Create a RAID.INI with your Windows 2003 x64 driver pnp codes (you have to do it yourself) and copy it to C:\PNP 6) Copy all the Windows 2003 x64 drivers into C:\PNP\DRIVERS. Copy everything, not just the INF or the SYS files. 7) Open a command prompt and type the following (with quotes): "RAID Slipstreamer x86 v4.0 Build 070920.exe" /source c:\temp /os 2003 /PNPINI c:\pnp\raid.ini /DRVPATH c:\pnp\drivers /quick 8) After the slipstream has complete, manually copy from C:\TEMP\i386\$OEM$ to your <root_path>\$OEM$. if you don't do that, it might BSoD at the GUI phase. 9) Then copy both C:\TEMP\TXTSETUP.SIF and C:\TEMP\DOSNET.INF to <root_path>\AMD64 overwriting the ones in there 10) Almost forgot...copy all the files with extension ".SY_" to <root_path>\AMD64 as well. If you don't do that, it will BSoD at the textmode phase. Remember the $OEM$ path must be placed at the root of the CDROM for unattended x64 The following is what my Win2k3 R2 SP2 x64 DVD looks like: \ \$OEM$ \AMD64 \CMPNENTS \I386 Be sure to update your WINNT.SIF to include: [unattended] OEMPnPDriversPath=Drivers\RAID; Let me know how it goes please.
  12. Hey almighty, Try this. Download the following: VIA.INI http://rapidshare.com/files/57016964/VIA.INI VIA_DRV.RAR http://rapidshare.com/files/57017094/VIA_DRV.RAR 1) From a clean WinXP, copy the i386 directory and subdirectories to C:\WINXP 2) Download VIA.INI and copy it to C:\TEMP 3) Download VIA_DRV.RAR and extract it to C:\TEMP\DRIVERS 4) Download RAID Slipstreamer x86 v4.0 Build 070920.exe 5) Open a command prompt and type the following (with quotes): "Raid Slipstreamer x86 v4.0 Build 070920.exe" /source C:\WINXP /os XP /pnpini C:\TEMP\VIA.INI /drvpath C:\TEMP\DRIVERS /quick 6) Now update your WinXP CD or ISO with this udpated i386 folder Be sure to update your WINNT.SIF to include: [unattended] OEMPnPDriversPath=Drivers\RAID; Note1. I have only included XP plug'n'play codes into VIA.INI and XP drivers into VIA_RAR.RAR. For other OSes, you have to do it yourself... Try it out and let me know if it works please.
  13. What's new in v4.0 Build 070920: - Fixed copying drivers to wrong path when /PNPINI and /DRVPATH switches are used
  14. Benchmarked the different versions of RAID Slipstreamer slipstreaming drivers to my 37 operating system folders housed in a remote NAS box through 100Mbps or 1Gbps full duplex LAN (no difference between the two): v3.0.4 took 43 minutes v4.0 Build 070914 took 4 hours and 4 minutes v4.0 Build 070915 took 12 minutes 13 seconds
  15. What's new in v4.0 Build 070915: - Replaced download link to Build 070915 - Increased processing speed by several hundred percent. Build 070914 took 2 minutes 35 seconds to process one OS; Build 070915 took 12 seconds. You do the maths. - Network processing speed is also speed up by many folds. - Fixed the two wrong driver info (AHCI8086.SYS and SISRAID4.SYS) in RAID.INI - Fixed unable to use non-auto detect platform drivers - Fixed minor visual bugs - Fixed minor logfile bugs - Removed nVidia drivers. Confusing as hell therefore, I removed them ALL but I'll re-add them later once I find time
  16. Known Bugs: - problem with the integrated RAID.INI where the 2 driver SYS was named incorrectly. Temporary workaround: 1) Run "RAID Slipstreamer x86 v4.0 Build 070914.exe" /export 2) Edit RAID.INI 3) Change these two lines: from DRIVERNAME="ATIAHCI.SYS" to DRIVERNAME="AHCI8086.SYS" from DRIVERNAME="SISAHCI" to DRIVERNAME="SISRAID4.SYS" 4) Use a clean operating system and run using the following command-line: RAID Slipstreamer x86 v4.0 Build 070914.exe /SOURCE <source_path> /PNPINI path:\raid.ini /QUICK That should do it. Thanks Namde for informing me of this problem.
  17. - June 28th, 2007 This is purely a driver update. The main reason for this update was to add support for my new Dell Latitude D630 laptop that requires the latest Intel IASTOR.SYS drivers. Since I was spending time on that, might as well look for other new drivers to update as well. And there were a few, including support for my new nVidia nForce 630a-based motherboard....
  18. You can run RAID Slipstreamer as many times as you want without having to worry about impacting the outcome. However, there are some entries that are duplicated, which can lead to duplicated efforts. i.e. repeatedly copying the same driver multiple times during the textmode phase. If you look into your DOSNET.INF file, look under the header [Floppyfiles.2] and search for ARCSAS.SYS for example. If you repeatedly run RAID Slipstreamer several times, you might notice dupplicated entries of "d1, arcsas.sys". Having too many of the same entries could take longer time for the copying to complete... I haven't had the time to work on this project. I've been meaning to provide an Uninstall feature for removing previous entries as well as allowing the user to choose which driver to include rather than currently, which includes ALL regardless whether you use it or not. I'll do it once I find time...
  19. - May 28th, 2007 - Just when you annihilated these vermins, another one pops up. Anyways, fixed the WinPE problem. VistaPE (WinPE v2.0) is still not supported but I am investigating. Also, not much updates to the drivers except the IBM ServeRAID 8i/8k/8k-l/8s SAS Controller, which should now support the latest controller revisions. The rest of the drivers appear to be the latest. Last but not least, the tool will close itself after each task. This is intentional and normal...for now.
  20. Confirmed. The WinPE feature doesn't work anymore. Hopefully it will be corrected next version.
  21. Yes, you are right, Kixform.NET requires .NET v1.1. It does not support v2 or v3 yet. And my fault for failing to mention this...
  22. Lain: Very much appreciate for the feedback. I wish everyone would contribute as much. 300 downloads of v3.0 but less than a dozen provided feedback regarding potential bugs. Anyways, you're not the first one complaining about the wrongful detection. I need to look further into this potential bug. Thanks again! Question: Could you please check the version of the NTDLL.DLL in the "i386" directory? That's where I tell the program to check for instead of the "i386\System32" directory.
  23. - April 23rd, 2007 - Just coincidence that the past 2 updates also happened on the 23rd. Anyways, v3.0.2 fixed the DOSNET.INF bug. This should correct the issue regarding drivers not found during textmode phase installation. I screwed up the codes while adding support for WinPE...
  24. Hmmm....supposedly the program will automatically detect the OS and install the corresponding platform drivers for you. Automatic detect checks for the presence of NTDLL.DLL to determine the platform type and automatically install the correct platform driver But you can also perform a manual slip like this: Manual method also checks for the presence of NTDLL.DLL to determine the platform type. If your OS selection is different from the detected OS, it will pop up a message asking for your confirmation to continue or abort. NOTE. Just noticed a bug (with manual slip) - it doesn't always work. But the automatic detect still works. For now, use autodetect instead. Update. On second thought, it wasn't a bug (for this case). My tests were flawed and now I know what I did wrong that made me thought it was a bug. However, there is different but minor bug that involves the DOSNET.INF entries. In most cases you don't need DOSNET.INF entries. Nevertheless, it is a bug and I will have a fix available asap. Of course, unless my testing is flaw again and...

  • Create New...