Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

  • Country

    Hong Kong

Everything posted by iTwins

  1. Hey JockeII, You got the big picture. Here's a more complete procedure (which I failed to provide in the first place): 1) Download RAID Slipstreamer 3.0 2) Install MS Dot Net Framework v1.1 (no need to install 7-zip or Kixform as they are now included) 3) copy XP CD to "C:\XP" (use 8.3 formats please. Apologies. I haven't fully learnt the art of programming that allows me to add support for long filenames) 4) Run RAID Slipstreamer and point to "C:\XP" 5) Burn to CD For most drivers, you can simply boot from the CD and install XP just as you normally would For some heavy duty drivers (mostly server-class controllers), you may need to perform an unattended installation, which allows you to make use of the following entry in the WINNT.SIF or UNATTEND.TXT There are a lot of references in MSFN that teach one how to perform an unattended installation. Most teach the use of WINNT.SIF and WINNT32.EXE. I however, provided a Universal Windows Boot Disk that uses an alternate (still Microsoft approved and supported) way of performing unattended installation by using UNATTEND.TXT and WINNT.EXE. You might want to check it out. Hope this helps.
  2. As mentioned in email: "Anyways, it is always recommended that you use a clean OS before using RAID Slipstreamer. RAID Slipstreamer was not tested thoroughly enough whether it can coexist with other tools such as nLite or HFSLIP. If you still get this error, I would suggest editing the TXTSETUP.SIF file and remove all occurrences of the IASTOR.SYS entries. Just do a text search. OR You can manually add the uncompressed IASTOR.SYS file and place it inside $WIN_NT$.~LS (or $WIN_NT$.~BT...forgot which one). "
  3. Sorry, I haven't tried on an HS21 before. However, our IBM x3250 are based on the 8k/i SAS Controller that uses the LSI Logic 1064 controller chipset - the same driver as the 1064e/1068/1068e/1078 (lsi_sas.sys). That was confirmed working. I noticed that IBM has released a 11/26/06 driver for the LSI_SAS.SYS and that RAID Slipstreamer v3.0 used an older 03/20/06 version. Try using this, which comes with the 11/26/06 driver: RAID Slipstreamer v3.0 Update 1 Let me know how it goes. Normally, if it BSoD on the textmode screen (copying phase), it is a result of wrong/corrupt/missing SYS driver or TXTSETUP.SIF is corrupted or incorrectly labeled. If it BSoD in the GUI installation (plug 'n' play device driver detection phase), then almost always it is missing other supporting drivers (ie. DLL, EXE, and possibly other SYS files as well). This is the reason why you need to add "OemPnPDriversPath=Drivers\RAID;" which I see you already did (but is it correctly placed in \i386\$OEM$\$1\DRIVERS\RAID?). For most home- desktop/notebook controllers, you may only need the SYS files. For heavy duty controllers that costs as much as your paycheque, you need that entry in your WINNT.SIF or UNATTEND.TXT.
  4. - March 23rd, 2007 - Final Release is out. No driver changes. No code changes either. Just corrected the 7-zip issue by using SFX instead. No more updates for a long while...
  5. This is ALL that is in my Sysprep.inf: [Unattended] OemSkipEula = YES [UserData] FullName = "xxxxxxxxxxxxxxxxxxx" OrgName = "xxxxxxxxxxxxxxxxxxx" [GuiUnattended] AdminPassword = xxxxxxxxxx EncryptedAdminPassword = No [Identification] JoinWorkgroup = xxxxxxxx [Networking] InstallDefaultComponents=Yes My company's Enterprise Agreement's Volume License Keys do not include Windows XP Tablet PC Edition, therefore I have a sysprep image that doesn't include the Product Key. It will instead ask for the product key when it starts for the first time. For my X60T, it is definitely Sysprep. Sysprep v1.1 has crashed many times before. That is why we have to test the Sysprep image to ensure it is working prior to rolling into Production.
  6. I think it could be a Sysprep v1.1 error. I encountered a similar error last week while Syspreping the Thinkpad X60 Tablet PC. I have cloned the X60T several times before but this time it err on me. If I remember right, it crashes after I entered the Product Key. The reason why I think it's a Sysprep error is because I have seen this error when Microsoft consultants came and demonstrated Syspreping OSes inside Virtual PC. The consultant was baffled. He was using v1.1 as well. I am not sure if v2.0 helps or not...
  7. I had problems with nLite (and HFSlip and other methods of unattended installation) before where I tell it to unattendedly install certain device drivers. During the middle of the Post-GUI installation near where it detects plug 'n' play devices, the system always hangs. It took me a long time to figure out and narrow down the culprits: HD Audio drivers. Actually, this is not entirely nLite's fault. Even if you instruct your unattended installation to include OEMPnPDriversPath with the HDAudio drivers, your installation could still hang. I have experienced this behavior on WinXP SP2 and Win2K3 SP1. To correct this, either 1) tell nLite to integrate the KB888111 hotfix (KB888111) or 2) Remove the HDAudio drivers from the drivers directory (eg: remove HDaudio drivers from $OEM$\$1\Drivers\Audio) or 3) Remove the drivers from your unattended installation completely
  8. Unfortunately, this was not designed for the thumbdrive. However, in most cases, I use network install instead, which is much faster than CD install. Especially when it comes to testing drivers or testing unattended application installation and integration, you can make changes to the network source files and then immediately test it without the need to waste time on burning CDs.
  9. In the older versions, I used an older compiler that didn't support long file names. Now I switched to a different compiler and I was planning to correct this, therefore the warning message was removed. Obviously I forgotten about this. I'll try to fix this in upcoming releases. But the next release won't be out in for at least a while. I would say this BETA 2 is quite stable and not much problems encountered so far...so no rush on the next release. Plus, too much to do at work and too many games to play at home... Anyways, thanks for letting me know...
  10. heh, are you sure you want to do that!? I believe even after you deleted it, the system re-creates this directory eventually - pointless!
  11. Heh, in that case, I rest my case. But then, it would be pointless to say that "installation into VMWare requires activation". If VLK is not used, Installation ANYWHERE, inside or outside of VMware, would require activation.
  12. haha, sgt, you have such bad luck! You have quite a number of things that don't work for you only but work for others. Try this: 1) run GPEDIT.MSC 2) Browse to User Configuration > Administrative Templates > Control Panel > Display 3) Set "Screen Saver" to "Disabled" 4) Exit GPEDIT.MSC Your screensaver should now be greyed out, therefore disabled. If LGPO (Local Group Policy Objects) don't work for you either, then IT REALLY IS YOUR PROBLEM! Switch to Mac....
  13. [Unattended] Unattendmode = FullUnattended OemPreinstall = YES TargetPath = WINXP Filesystem = ConvertNTFS "FileSystem = ConvertNTFS"
  14. Best of luck there - I gave up on that idea after seeing a number of non-standard and unusual but nonetheless valid drivers that almost put me into a mental institution. Yeah, which is why I'm trying to recall the basic format of reading the inf file and determining from it what files are needed... or would the txtsetup.oem file be more appropriate for parsing? Or both? I mean, I literally forget, since the last time I integrated drivers, what was needed .. in fact I was an id*** and to save space deleted the folder that had my integrated driver source, shortly before screaming my head off and going "No!!!" hehe The TXTSETUP.OEM is best and much much easier than OEMSETUP.INF but even so, I have seen weird ones that do not conform to standards. But it is worth the challenge...for you that is. I am too old for this sh_t!
  15. Seeing a lot of you having a hard time with unattended Windows installation I figure I might be able to offer you some help. Back in the old days (about 8 years ago), my predecessors create one boot disk for each operating system and one for each RAID controller used. In some cases, there are also boot disks for specific LAN cards as well (because the original Norton Antivirus Corporate Edition cannot be unattendedly installed without the presence of a working LAN adapter). My company with over a dozen official operating systems at that time and half dozen different RAID controllers that the original MS Windows NT 4.0 operating systems do not support, the number of boot disks to choose from can be hazardous to your health to say the least. This is where I step in, the Universal Standard Build Boot Disk (official name used in my company) was first introduced in early 2004. It has now progressed to this first Internet release, the Universal Windows Boot Disk (UWBD). UWBD and USBBD are almost identical, except the juicy security settings, the VLK (Volume License Keys) and the other company details are removed in UWBD. The global company I work for is quite sensitive in nature and wish to be anonymous at all times. Download Universal Windows Boot Disk v3.0 RC4 Internet Edition here I never really enjoyed writing Installation Guides but in order for a product to be used in a Production environment, it is unavoidable. This guide is quite out of date in which it was based on the USBBD v2.1 dated August 2005. I have not updated it since. Being a BETA or Release Candidate, it is an exception to use in Production but do not required to write a guide. Therefore, I intend to keep this product a Release Candidate forever or until I have the time to update the guide. Anyways, it could provide you some understanding how to use UWBD Download UWBD Administrator's Guide here And here's a guide that teaches you how to insert this boot disk into an CD disc (or DVD disc). Simple stuffs. Surprisingly, there are a lot of IT people who do not know how to do this. What a shame! For advanced users, you're on your own. Download DIY Standard Build CD Administrator's Guide It's a complicated boot disk with many many options to choose from. If there is anything you are unsure of, simply give me shout and I'll try to help you asap. If not, help yourself by modifying the batch files yourself. IMPORTANT NOTES: - My company's Standard Build UNATTEND.TXT files were permanently removed for confidentiality and security reasons. If you choose Standard Build operating systems, it will err and nothing will happen or worst, drop to DOS - Page 11 of the Administrator's Guide listed out all the mandatory directory names that UWBD recognizes. That list is out of date. The below screen capture is the latest: Vanillas: ---------- W2K3ENT - Windows Server 2003 Enterprise W2K3ESP1 - Windows Server 2003 Enterprise with SP1 W2K3R2E - Windows Server 2003 R2 Enterprise W2K3R2S - Windows Server 2003 R2 Standard W2K3SSP1 - Windows Server 2003 Enterprise with SP1 W2K3STD - Windows Server 2003 Standard W2KASR - Windows 2000 Advanced Server W2KPRO - Windows 2000 Professional W2KSVR - Windows 2000 Server WXPSP2C - Windows XP Professional with SP2 (Customized) WXPSP2G - Windows XP Professional with SP2 (generic - Microsoft default) CTWXPSP2 - Windows XP Professional with SP2 (Chinese Traditional) WXPSP2M - Windows XP Media Center Edition with SP2 WXPSP2T - Windows XP Tablet PC Edition with SP2 All else are Standard Build OSes which you cannot use anyways. Ignore them... Your network share, if you wish to perform network installation, the directory naming convention must also be the same. - I was planning to add NT 4.0 and Win95/98/ME into this to make a a true Universal Windows Boot Disk, but decided otherwise because I will never use it anyways; why waste the effort! - UWBD's UNATTEND.TXT's do not come with Mass Storage Driver support. TXTSETUP.OEM are a thing of the past. Nowadays we use integration or slipstreaming. You can found many good references to slipstreaming SCSI/SATA/RAID drivers here in MSFN. Or you can use my RAID Slipstreamer tool - I know being an IT person we all have egos - we never read manuals. We think we know everything but in reality we don't. Anyways, if you come across something that you cannot solve, please read the Administrator's Guide first before asking for help. - There are always bugs with this boot disk - even I found it complicated. But rest assure, there are no showstoppers (apart from choosing Standard Build instalations). Nevertheless, please report all problems. - The UWBD includes support for unattended Active Directory domain controller installations. At one time it also included unattended installation of Exchange Server 2003 on Windows Server 2003 SP1 however, I must have misplaced it and it's now lost forever. It was one very amazing unattended installation OS. The Citrix Metaframe XP on Windows Server 2003 and Citrix Presentation Server on Windows Server 2003 R2 versions were also lost along with the Exchange Server 2003. Oh well... Have fun and hope you find this useful. Cheers Appendix: Each operating system's structure is similar to this, which is the Microsoft unattended installation standard. The $1\Drivers\RAID... must be defined the same as teh UNATTEND.TXT under "OEMPnPDriversPath". I never bothered to integrate drivers into the DRIVERS.CAB. This method is hassle-free. A sample UNATTEND.TXT. This is the Windows XP Professional Tablet PC Edition: [Unattended] Unattendmode = FullUnattended OemPreinstall = YES TargetPath = WINXP Filesystem = ConvertNTFS OemSkipEula = YES DriverSigningPolicy = Ignore ExtendOemPartition = 1 AutoActivate = No UnattendSwitch = Yes CrashDumpSetting = 0 DisableDynamicUpdates = Yes WaitForReboot = No 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 [Data] UseBIOSToBoot = 1 [GUIRunOnce] [UserData] FullName = "Generic Windows XP Pro Tablet PC with SP2" OrgName = "Jeff's Recovery DVD" [GuiUnattended] AdminPassword = * EncryptedAdminPassword = No AutoLogon = NO AutoLogonCount = 0 OemSkipWelcome = 1 OemSkipRegional = 1 [PCHealth] [Shell] DefaultStartPanelOff = Yes DefaultThemesOff = No [Display] BitsPerPel = 32 XResolution = 1024 YResolution = 768 VRefresh = 75 [Components] spider = off zonegames = off hearts = off freecell= Off minesweeper = Off pinball = Off Solitaire = Off deskpaper = off media_clips = off media_utopia = off msnexplr = off TabletOC=On TPG=On System=On OOBE=On Notebook=On Stickynotes=On [Branding] BrandIEUsingUnattended=Yes [URL] [Proxy] [Identification] JoinWorkgroup = HOME [Networking] InstallDefaultComponents=No [NetAdapters] Adapter1=params.Adapter1 [params.Adapter1] INFID=* [NetClients] MS_MSClient=params.MS_MSClient [NetServices] MS_SERVER=params.MS_SERVER [NetProtocols] MS_TCPIP=params.MS_TCPIP [params.MS_TCPIP] DNS=Yes UseDomainNameDevolution=No EnableLMHosts=Yes AdapterSections=params.MS_TCPIP.Adapter1 [params.MS_TCPIP.Adapter1] SpecificTo=Adapter1 NetBIOSOptions=0
  16. btw, there is a line in the UNATTEND.TXT (or WINNT.SIF) that tells the system to automatically activate: [Unattended] Unattendmode = FullUnattended OemPreinstall = YES TargetPath = WINNT Filesystem = ConvertNTFS OemSkipEula = YES DriverSigningPolicy = Ignore ExtendOemPartition = 1 AutoActivate = No UnattendSwitch = Yes CrashDumpSetting = 0 DisableDynamicUpdates = Yes WaitForReboot = No I have not tried setting it to "AutoActivate = Yes" before. Like I mentioned in an earlier post, I never need to activate with VLK Btw, If you are using Winnt.exe to install Windows (install from DOS), make sure that "UnattendSwitch = Yes". It's worth a try...but I believe you may need to have a direct connection to the Internet. If however you are behind a proxy server, try adding this: [Proxy] Proxy_Enable=1 Use_Same_Proxy=1 HTTP_Proxy_Server = http://proxyserver:80 I don't mean make it sound complicated but if your company uses Automatic Configuration Scripts like we do, add this setting instead of [Proxy]: [URL] AutoConfigURL = http://configserver/autoconfig.ins
  17. Your above two comments may not be valid if you use VLK. With VLK, you do not need to activate AT ALL (applicable to XP, 2000, and 2003). All else....I have no doubts. I am similar to you: - use unattend.txt - use both CD/DVD and NETWORK installation through MSDOS (WIN98SE DOS) and WinPE - use VMware Workstation, ESX, VPC and VPC Enterprise Server for developing and testing customized OSes I have never activated any operating systems with VLK before, except the WinXP Tablet PC Edition, which our Enterprise Agreement did not include VLK for Tablet PCs for some reason.
  18. This was a while back. I know this is really suicide for me right now (I'm rusty on my cpp) but I'm gonna try to write up a simple file parser to do exactly that. Well, it can, at certain points, perform specific commands we need it to do, at least... I hope... Wish me luck all, as I want to contribute and do well at this. If done correctly it would be easy enough to have subfolders so we can just include the drivers, and not even CARE what they are named, probably just cab them up as Userdrv<x>.whatever where <x> is an increasingly incremental number, then use the right "names" in the txtsetup and... whatever... that other file is... wow I can't thihk right now, it's only 2 in the afternoon and I'm getting ready for another mind-numbing day at work. Best of luck there - I gave up on that idea after seeing a number of non-standard and unusual but nonetheless valid drivers that almost put me into a mental institution.
  19. BETA 2 released. You no longer need to put 7z.exe into the search path but you are still required to install 7-zip before using the BETAs. I like UHARC better but that doesn't work with this tool. Anyways, also with BETA 1, slipstreaming WinPE did not work at all; this BETA 2 version fixed that. I did some basic tests on slipstreaming WinXP drivers to the original Microsoft WinPE v1.5 (based on Windows XP SP2) and I am happy to say that it appeared to work quite well. I tested it on the new Lenovo Thinkpad X60 Tablet PC that comes with an Intel 82801 GBM ICH7-M AHCI SATA controller (AHCI mode enabled in BIOS) and it worked - booting up to WinPE CD and accessing the HDD. Prior to slipstreaming, that was not possible. That's good. But I think I should be targeting WinPE v2.0 (based on Vista) instead. That however will have to wait...
  20. Just noticed that you need to install 7-zip and put 7z.exe into the search path for v3.0 BETA 1 to work properly. I'll try to fix this in later versions.
  21. - Feb 20th, 2007 - A rewrite of the program and most of the bugs in previous versions have been corrected (I think). However, not much have been done to the WinPE codes and testing was very limited. Also added many drivers and updated many of the existing drivers to the latest version. It seems this tool is no longer for work only as I have been receiving a lot of requests from friends and other people to add support for this controller and that controller. Good thing I have ditched WinRAR and switched to using 7-zip to compress the whole program. Despite adding numerous new drivers, the size for v3.0 is over 30% smaller than previous versions. Last but not least, added many new features to v3.0. Try it out and see for yourself. Cheers! Note 1: The reason why its still a BETA is because not enough testing were done on WinPE to confirm that the codes work smoothly. Apart from WinPE, everything have been tested quite thoroughly. Note 2: v3.0 requires Microsoft .NET Framework v1.1. It does not support v2.0 or v3.0. If you have already installed v2.0 and/or v3.0, be sure to install v1.1 as well.
  22. That command-line doesn't work. Try this: 1) Download the F6Flpy32.zip file from Intel website 2) Extract F6FLPY32.ZIP to a temp directory 3) Extract the F6FLPY32.EXE using WinRAR or WinImage (with WinImage, you can skip Step 4) 4) Finally, extract the contents of TEMP.IMA using WinImage or UltraISO In case you don't have the tools to do that, I've saved you the trouble. You can download v6.2.1.1002 (1/4/2007) from here: F6FLPY32.ZIP
  23. Let's just say if you have a problem with the operating system and you need Micosoft's help, they won't support you. In terms of supporting, they will stop all investigative work at the moment they found discrepancies with the OS. If you are using this in a corporate environment, I strongly suggest not.
  24. Added support for WinPE. However, more testing is required. Your feedback especially on BartPE or any other customized WinPE (including Vista's WinPE v2.0) is much appreciated
  25. Well, I really don't have a clue and I still don't see anything wrong with the program logic. Anyways, try the new v2.3 workaround - manually specifying the platform type. If you experience problems with automatic detection, use the manual method instead.

  • Create New...