RogueSpear

I was just having the exact same problem in an application that I'm developing. I can't believe I stumbled across this thread. Anyway, what I found works for me is to use the -untranslated-filenames switch. From the mkisofs help: Allow Untranslated filenames (for HPUX & AIX - violates ISO9660). Forces -l, -d, -N, -allow-leading-dots, -relaxed-filenames, -allow-lowercase, -allow-multidot A little side benefit is that it cleans up the command line slightly.

I'm going to guess no. This is stricktly speculative, but when you look at the purpose behind RIS it would make me think not. The whole idea with RIS is to quickly get computers up and running in a medium to large enterprise. With that is the expectation of a domain. The fact that you can RIS a computer and not have it join a domain is probably more of a bug than feature. I've run into it when the NIC driver won't properly detect and install during PnP enumeration, but like I said this is unintended. With all of the hoops it looks as though you'd have to jump through, I'd say that you'd probably be better off making a good unattended installation on a DVD. I always have my clients purchase computers/laptops with a minimum of a DVD-ROM drive in them just for this reason.

When this was discussed previously I did a test on compressing the contents of driver.cab with 7-Zip and it was a noticeable difference. Sure, nothing is ever the best all of the time, but the flexibility of having 7z as an option would be nice. Unfortunately I do see a ton of complications with this project - like the possibility of Windows rejecting the new cabinet.dll file because of a different MD5 or a number of other reasons.

Indeed that would be an awesome creation. It has been discussed here before, but nobody has yet taken up the task. It's way way above and beyond my expertise, but I wish you the best in your efforts.

I'm not sure what your level of expertise is, but interfacing to cabinet.dll is a bit more complicated than one would first imagine. First, you're going to want to download the CAB SDK from Microsoft and give it a read. Just make sure you have lots of coffee (or some uppers) as this is not an exiting read. If you're interested in something .NET, there's a fellow who managed to write a class in C# that is essentially a wrapper for cabinet.dll: http://www.devsource.com/article2/0,1895,1731188,00.asp

Far as I'm concerned, if someone paid for the computer and it legitimately came with a royalty license then they're entitled to have the royalty version of the OS that they paid for on that computer. How it gets on there is irrelevant.

In the traditional sense, no I don't believe you can RIS without access to a domain. I know that there are some people out there who have rigged together systems where they're doing RIS from Linux, but to RIS the normal way you need to authenticate to a domain account in order to get the ball rolling. This doesn't mean the computer must join the domain, but I can't really see a way of avoiding the initial text mode sign on.

I haven't run into this before, but in reality I can't remember the last time I fired up two RIS installs nearly simultaneous with one another. I know you'd like to find the cause, and a solution, to the problem, but a possible workaround would be to wait to start another RIS install until the text mode portion of setup has completed on the first computer. After text mode, the computer shouldn't need to contact the RIS server again during setup.

Good selection and the best pricing I've found: http://www.bookpool.com

I use pretty much everything listed in the poll. Similar to About:Buster and CWShredder, I always keep Peperfix on my thumbdrive for the rare times I run into that. I personally browse with Maxthon in order to maintain IE compatibility. It has a pretty powerful blacklist feature with support for wildcards and has never let me down. For one of my clients I actually resorted to using whitelisting in IE. Basically I configure the restricted sites zone as you would normally configure the Internet sites zone and conigured the Internet sites zone as you would restricted. This way only the sites that the president of the company has approved of will receive normal access. Everything else is pretty well crippled. And even the approved sites are still subject to the blacklisting in Maxthon. Haven't had one problem there since this was implemented and some of the secretaries there could screw something up in a couple of seconds if anybody could.

Just a little friendly advice.. drop the RIPrep and just use RIS flat images. You'll save a lot of time and hassle.

I'm getting pretty close to releasing the first beta of AutoImage, the successor to AutoRIS. The program handles CD/DVD images in addition to RIS now. Here's some screen shots to give you an idea of what this will be like. As you can see I'm still working on the ScriptPack end of it which is proving a bit more challenging than I thought it would be. The main reason I haven't put out a beta yet is that the DriverPacks functionality isn't working at all. Everything is working on my end, it's just that the API mode of the new BASE needs a bit of tweaking and bug hunting yet. I'm sure when BTS is finished with his exams he'll have things working without too much delay.

I think that's a pretty good solution to the issue myself. I would imagine that in any given place only a few machines at most would need special handling of partitions like that.

The reason I included them was because someone here posted a link to them as part of a thread discussing this issue. For the life of me, I cannot find the post again. So I can assume these drivers do indeed work with RIS?

Description: Generate MD5 Values of Files Language: Visual Basic 2005 [Function] Usage: String = GenerateFileHash(filename) My initial search for examples on this led me to an example of using MD5 with strings. Specifically, using MD5 to secure the transmisson of passwords. You can find that article here. I spent quite some time trying to rework the example code to work with files rather than strings. Further searching yielded only a single example, in C#, at the MSDN forums. While not very helpful for VB, it did open my eyes to the BitConverter function. Private Function GenerateFileHash(ByVal SourceFile As String) As String Dim strFile As New IO.FileStream(SourceFile, IO.FileMode.Open, IO.FileAccess.Read) Dim MD5 As New MD5CryptoServiceProvider() Return BitConverter.ToString(MD5.ComputeHash(strFile)).Replace("-", "") strFile.Close() End Function GenerateFileHash.vb.txt

I believe these are the same drivers that I included, experimentally, in the latest version of AutoRIS. I've received zero feedback. No good news, no bad news. Makes it hard to know if something is working or not.

Under the [Data] section, try making this entry: UnattendedInstall="Yes"

It sounds as though you're missing a necessary entry from your template (.sif) file. I don't know them all by heart anymore since I always use the same one, but its something like OEMUnattended = Yes or something similar.

The network is not active again until the part where it says "Configuring Network" is finished. I can verify that it is active from cmdlines because I download files at that stage.

No, the decompression of the .7z file is just that.. decompression. What I've though about is adding an option to completely 100% delete the All Users Start Menu. Then it would be up to the user to include everything that they need in the .7z file.

No, you can't have the computer search a network location for drivers during the GUI portion of setup where device PnP enumeration is done (T-39). First of all, your NIC isn't active since it's a device itself. Second, the network configuration happens after device installation, so even when the NIC gets installed you would still have to wait for it to be configured.

In the course of developing a utility I found that precise identification of a Windows OS install source is vital for various branch decisions. This is information that I've gathered from what must be over a dozen sources. Among them are MSFN (of course), tacktech.com, bink.nu, tech-hints.com, and Microsoft themselves. There's even some information I came up with myself like the MD5's and a few additions to the CD volume list. I thought it would make things easier for others if all of this stuff were in one place and hopefully others will give me some additions and corrections. CD Volume Label and PID assignments This is a list of CD volume labels, the date & time stamp of the media and the PID number from SETUPP.INI. With the PID the first five numbers dictate the version and the last three numbers dictate the CD key. At the top is a legend for assistance with decoding the volume labels. CCP = Compliance Checking Program (Upgrades) FPP = Fully Packaged Product OEM = Original Equipment Manufacturer SEL = Select (No Key Required) VOL = Volume License Key Required EVL = Evaluation Software MS-DOS 6.22/Windows 3.11 OEM Combo = 05/31/94 2:22 AM / 11/03/93 4:11 AM Windows 95 Retail = 07/11/95 9:50 AM Windows 95 Retail Upgrade = 07/11/95 9:50 AM Windows 95 OEM = WINDOWS95 07/11/95 5:50 AMor 07/11/95 9:50 AM Windows 95 OEM OSR1 "A" = WINDOWS95 12/31/95 5:50 AM or 02/02/96 9:51 AM Windows 95 OEM OSR2 "B" = W95_FULL_AR 08/24/96 8:11 AM or 08/24/96 11:11 AM Windows 95 OEM OSR2.1 "B" = W95_FULL_AR 05/01/97 8:14 AM or 06/25/97 9:07 AM Windows 95 OEM OSR2.5 "C" = WIN95_C 11/25/97 10:16 PM or 11/26/97 12:14 PM Windows 98 Retail = Windows 98 05/11/98 8:01 PM Windows 98 Retail Upgrade = Windows 98 05/11/98 8:01 PM Windows 98 OEM = Windows 98 05/11/98 8:01 PM or 11/24/98 4:02 AM Windows 98 SE Retail = Win98 SE 04/23/99 6:22 PM or 04/23/99 10:22 PM Windows 98 SE Retail Upgrade = Win98 SE 04/23/99 6:22 PM or 04/23/99 10:22 PM Windows 98 SE OEM = Win98 SE 04/23/99 6:22 PM or 04/23/99 10:22 PM Windows ME Retail = Windows Me 06/08/00 1:00 PM or 06/08/00 3:00 PM Windows ME Retail Upgrade = Windows Me 06/08/00 1:00 PM or 06/08/00 3:00 PM Windows ME Retail Step Up = Windows Me 06/08/00 1:00 PM or 06/08/00 3:00 PM Windows ME OEM = Windows Me 06/08/00 1:00 PM or 06/08/00 3:00 PM Windows ME MSDN = Windows Me 06/08/00 1:00 PM Windows NT 3.1 Workstation Retail = Windows NT 3.1 Advanced Server Retail = Windows NT 3.5 Workstation Retail = WORKSTATION xx/xx/xx Windows NT 3.5 Server Retail = SERVER xx/xx/xx Windows NT 3.51 Workstation Retail = NTWKS xx/xx/xx Windows NT 3.51 Server Retail = NTSRV xx/xx/xx Windows NT 4.0 Workstation = NTWKS40A 10/13/96 9:38 PM 50036 Windows NT 4.0 Server = NTSRV40A 10/13/96 9:38 PM 50370 Windows NT 4.0 Enterprise Server Disc 1 = NTSE_BASE_D 09/12/97 8:00 AM 70234 Windows NT 4.0 Enterprise Server Disc 2 = NTSE_COMP 09/15/97 8:00 AM Windows NT 4.0 Terminal Server = WINNT-TSE40 07/22/98 2:09 PM 88090270 Windows 2000 Combo Pro/Svr/Asvr = WIN2000_EN Windows 2000 Pro OEM = W2POEM_EN 12/07/99 8:00 AM 51873OEM Windows 2000 Pro OEM SP1 = SP1POEM_EN 07/26/00 8:00 AM 51873OEM Windows 2000 Pro OEM SP2 = SP2POEM_EN 05/08/01 3:00 PM 51873OEM Windows 2000 Pro OEM SP3 = YRMPOEM_EN 07/24/02 8:00 AM 51873OEM Windows 2000 Pro OEM SP4 = ZRMPOEM_EN 06/20/03 8:00 AM 51873OEM Windows 2000 Pro Retail = W2PFPP_EN 12/07/99 8:00 AM 51873000 Windows 2000 Pro Retail SP1 = SP1PFPP_EN 07/26/00 8:00 AM 51873000 Windows 2000 Pro Retail SP2 = SP2PFPP_EN 05/08/01 3:00 PM 51873000 Windows 2000 Pro Retail SP3 = YRMPFPP_EN 07/24/02 8:00 AM 51873000 Windows 2000 Pro Retail SP4 = ZRMPFPP_EN 06/20/03 8:00 AM 51873000 Windows 2000 Pro Select = W2PSEL_EN 12/07/99 8:00 AM 51873270 Windows 2000 Pro Select SP1 = SP1PSEL_EN 07/26/00 8:00 AM 51873270 Windows 2000 Pro Select SP2 = SP2PSEL_EN 05/08/01 3:00 PM 51873270 Windows 2000 Pro Select SP3 = YRMPSEL_EN 07/24/02 8:00 AM 51873270 Windows 2000 Pro Select SP4 = ZRMPSEL_EN 06/20/03 8:00 AM 51873270 Windows 2000 Pro MSDN = W2PFPP_EN 12/07/99 8:00 AM 51873000 Windows 2000 Pro MSDN SP1 = SP1PFPP_EN 07/26/00 8:00 AM 51873000 Windows 2000 Pro MSDN SP2 = SP2PFPP_EN 05/08/01 3:00 PM 51873000 Windows 2000 Pro MSDN SP3 = YRMPFPP_EN 07/24/02 8:00 AM 51873000 Windows 2000 Pro MSDN SP4 = ZRMPFPP_EN 06/20/03 8:00 AM 51873000 Windows 2000 Server OEM = W2SOEM_EN 12/07/99 8:00 AM 51876OEM Windows 2000 Server OEM SP1 = SP1SOEM_EN 07/26/00 8:00 AM 51876OEM Windows 2000 Server OEM SP2 = SP2SOEM_EN 05/08/01 3:00 PM 51876OEM Windows 2000 Server OEM SP3 = YRMSOEM_EN 07/24/02 8:00 AM 51876OEM Windows 2000 Server OEM SP4 = ZRMSOEM_EN 06/20/03 8:00 AM 51876OEM Windows 2000 Server Retail = W2SFPP_EN 12/07/99 8:00 AM 51876000 Windows 2000 Server Retail SP1 = SP1SFPP_EN 07/26/00 8:00 AM 51876000 Windows 2000 Server Retail SP2 = SP2SFPP_EN 05/08/01 3:00 PM 51876000 Windows 2000 Server Retail SP3 = YRMSFPP_EN 07/24/02 8:00 AM 51876000 Windows 2000 Server Retail SP4 = ZRMSFPP_EN 06/20/03 8:00 AM 51876000 Windows 2000 Server Select = W2SSEL_EN 12/07/99 8:00 AM 51876270 Windows 2000 Server Select SP1 = SP1SSEL_EN 07/26/00 8:00 AM 51876270 Windows 2000 Server Select SP2 = SP2SSEL_EN 05/08/01 3:00 PM 51876270 Windows 2000 Server Select SP3 = YRMSSEL_EN 07/24/02 8:00 AM 51876270 Windows 2000 Server Select SP4 = ZRMSSEL_EN 06/20/03 8:00 AM 51876270 Windows 2000 Server MSDN = W2SFPP_EN 12/07/99 8:00 AM 51876000 Windows 2000 Server MSDN SP1 = SP1SFPP_EN 07/26/00 8:00 AM 51876000 Windows 2000 Server MSDN SP2 = SP2SFPP_EN 05/08/01 3:00 PM 51876000 Windows 2000 Server MSDN SP3 = YRMSFPP_EN 07/24/02 8:00 AM 51876000 Windows 2000 Server MSDN SP4 = ZRMSFPP_EN 06/20/03 8:00 AM 51876000 Windows 2000 Advanced Server OEM = W2AOEM_EN 12/07/99 8:00 AM 51879OEM Windows 2000 Advanced Server OEM SP1 = SP1AOEM_EN 07/26/00 8:00 AM 51879OEM Windows 2000 Advanced Server OEM SP2 = SP2AOEM_EN 05/08/01 3:00 PM 51879OEM Windows 2000 Advanced Server OEM SP3 = YRMAOEM_EN 07/24/02 8:00 AM 51879OEM Windows 2000 Advanced Server OEM SP4 = ZRMAOEM_EN 06/20/03 8:00 AM 51879OEM Windows 2000 Advanced Server Retail = W2AFPP_EN 12/07/99 8:00 AM 51879000 Windows 2000 Advanced Server Retail SP1 = SP1AFPP_EN 07/26/00 8:00 AM 51879000 Windows 2000 Advanced Server Retail SP2 = SP2AFPP_EN 05/08/01 3:00 PM 51879000 Windows 2000 Advanced Server Retail SP3 = YRMAFPP_EN 07/24/02 8:00 AM 51879000 Windows 2000 Advanced Server Retail SP4 = ZRMAFPP_EN 06/20/03 8:00 AM 51879000 Windows 2000 Advanced Server Select = W2ASEL_EN 12/07/99 8:00 AM 51879270 Windows 2000 Advanced Server Select SP1 = SP1ASEL_EN 07/26/00 8:00 AM 51879270 Windows 2000 Advanced Server Select SP2 = SP2ASEL_EN 05/08/01 3:00 PM 51879270 Windows 2000 Advanced Server Select SP3 = YRMASEL_EN 07/24/02 8:00 AM 51879270 Windows 2000 Advanced Server Select SP4 = ZRMASEL_EN 06/20/03 8:00 AM 51879270 Windows 2000 Advanced Server MSDN = W2AFPP_EN 12/07/99 8:00 AM 51879000 Windows 2000 Advanced Server MSDN SP1 = SP1AFPP_EN 07/26/00 8:00 AM 51879000 Windows 2000 Advanced Server MSDN SP2 = SP2AFPP_EN 05/08/01 3:00 PM 51879000 Windows 2000 Advanced Server MSDN SP3 = YRMAFPP_EN 07/24/02 8:00 AM 51879000 Windows 2000 Advanced Server MSDN SP4 = ZRMAFPP_EN 06/20/03 8:00 AM 51879000 Windows 2000 Datacenter inc. SP1 = W2DFPP_EN Windows XP Combo Home/Pro = WXPHFPP_EN 08/23/01 1:00 AM Windows XP Home Retail = WXHFPP_EN 08/23/01 8:00 AM 55277000 Windows XP Home Retail w/ SP1 = XRMHFPP_EN 08/29/02 8:00 AM 55277000 Windows XP Home Retail w/ SP1a = X1AHFPP_EN 03/31/03 8:00 AM 55277000 Windows XP Home Retail w/ SP2 = VRMHFPP_EN 08/04/04 8:00 AM 55277000 Windows XP Home Upgrade = WXHCCP_EN 08/23/01 8:00 AM 55285000 Windows XP Home Upgrade W/SP1 = XRMHCCP_EN 08/29/02 8:00 AM 55285000 Windows XP Home Upgrade W/SP1a = X1AHCCP_EN 03/31/03 8:00 AM 55285000 Windows XP Home Upgrade W/SP2 = VRMHCCP_EN 08/04/04 8:00 AM 55285000 Windows XP Home OEM = WXHOEM_EN 08/23/01 8:00 AM 55277OEM Windows XP Home OEM w/ SP1 = XRMHOEM_EN 08/29/02 8:00 AM 55277OEM Windows XP Home OEM w/ SP1a = X1AHOEM_EN 03/31/03 8:00 AM 55277OEM Windows XP Home OEM w/ SP2 = VRMHOEM_EN 08/04/04 8:00 AM 55277OEM Windows XP Home Volume = WXHVOL_EN 08/23/01 8:00 AM 55274270 Windows XP Home Volume W/ SP1 = XRMHVOL_EN 08/29/02 8:00 AM 55274270 Windows XP Home Volume W/ SP1a = X1AHVOL_EN 03/31/03 8:00 AM 55274270 Windows XP Home Volume W/ SP2 = VRMHVOL_EN 08/04/04 8:00 AM 55274270 Windows XP Pro Retail = WXPFPP_EN 08/23/01 8:00 AM 55274000 Windows XP Pro Retail w/ SP1 = XRMPFPP_EN 08/29/02 8:00 AM 55274000 Windows XP Pro Retail w/ SP1a = X1APFPP_EN 03/31/03 8:00 AM 55274000 Windows XP Pro Retail w/ SP2 = VRMPFPP_EN 08/04/04 8:00 AM 55274000 Windows XP Pro Upgrade = WXPCCP_EN 08/23/01 8:00 AM 55276000 Windows XP Pro Upgrade w/ SP1 = XRMPCCP_EN 08/29/02 8:00 AM 55276000 Windows XP Pro Upgrade w/ SP1a = X1APCCP_EN 03/31/03 8:00 AM 55276000 Windows XP Pro Upgrade w/ SP2 = VRMPCCP_EN 08/04/04 8:00 AM 55276000 Windows XP Pro OEM = WXPOEM_EN 08/23/01 8:00 AM 55274OEM Windows XP Pro OEM w/ SP1 = XRMPOEM_EN 08/29/02 8:00 AM 55274OEM Windows XP Pro OEM w/ SP1a = X1APOEM_EN 03/31/03 8:00 AM 55274OEM Windows XP Pro OEM w/ SP2 = VRMPOEM_EN 08/04/04 8:00 AM 55274OEM Windows XP Pro Volume = WXPVOL_EN 08/23/01 8:00 AM 55274270 Windows XP Pro Volume w/ SP1 = XRMPVOL_EN 08/29/02 8:00 AM 55274270 Windows XP Pro Volume w/ SP1a = X1APVOL_EN 03/31/03 8:00 AM 55274270 Windows XP Pro Volume w/ SP2 = VRMPVOL_EN 08/04/04 8:00 AM 55274270 Windows XP Pro Tablet PC w/SP1 Disc1 = XRMPFPP_EN 08/29/02 8:00 AM 55274000 Windows XP Pro Tablet PC w/SP1a Disc1 = X1APFPP_EN 03/31/03 8:00 AM 55274000 Windows XP Pro Tablet PC w/SP2 Disc1 = VRMPFPP_EN 08/04/04 8:00 AM 55274000 Windows XP Pro MSDN = WXPFPP_EN 08/23/01 8:00 AM 55274000 Windows XP Pro MSDN w/ SP1 = XRMPFPP_EN 08/29/02 8:00 AM 55274000 Windows XP Pro MSDN w/ SP1a = X1APFPP_EN 03/31/03 8:00 AM 55274000 Windows XP Pro MSDN w/ SP2 = VRMPFPP_EN 08/04/04 8:00 AM 55274000 Windows XP Pro Evaluation = WXPEVL_EN Windows Media Center Edition 2005 = MRMPFPP_EN 08/10/04 12:00 PM76487000 Windows Media Center Edition 2005 CD2 = MRMSD2_EN 08/10/04 12:00 PM Windows Server 2003 Combo Std/Ent = EN_WS03 03/25/03 8:00 AM Windows Server 2003 Standard Retail = NRMSFPP_EN 03/25/03 8:00 AM 69712000 Windows Server 2003 Standard Retail SP1 = BRMSFPP_EN 69712000 Windows Server 2003 Standard OEM = NRMSOEM_EN 03/25/03 8:00 AM 69712OEM Windows Server 2003 Standard OEM SP1 = BRMSOEM_EN 69712OEM Windows Server 2003 Standard Volume = NRMSVOL_EN 03/25/03 8:00 AM 69712270 Windows Server 2003 Standard Volume SP1 = BRMSVOL_EN 69712270 Windows Server 2003 Web Retail = NRMWFPP_EN 03/25/03 8:00 AM 69753000 Windows Server 2003 Web Retail SP1 = BRMWFPP_EN 69753000 Windows Server 2003 Web OEM = NRMWOEM_EN 03/25/03 8:00 AM 69753OEM Windows Server 2003 Web OEM SP1 = BRMWOEM_EN 69753OEM Windows Server 2003 Web Volume = NRMWVOL_EN 03/25/03 8:00 AM 69753270 Windows Server 2003 Web Volume SP1 = BRMWVOL_EN 69753270 Windows Server 2003 Enterprise Retail = NRMEFPP_EN 03/25/03 8:00 AM 69713000 Windows Server 2003 Enterprise Retail SP1 = BRMEFPP_EN 69713000 Windows Server 2003 Enterprise OEM = NRMEOEM_EN 03/25/03 8:00 AM 69713OEM Windows Server 2003 Enterprise OEM SP1 = BRMEOEM_EN 69713OEM Windows Server 2003 Enterprise Volume = NRMEVOL_EN 03/25/03 8:00 AM 69713270 Windows Server 2003 Enterprise Volume SP1 = BRMEVOL_EN 69713270 Windows Server 2003 Datacenter = NRMDFPP_EN Windows Server 2003 Datacenter SP1 = BRMDFPP_EN Windows Server 2003 Enterprise Eval = NRMEEVL_EN 69763000 Windows Server 2003 Enterprise Eval SP1 = BRMEEVL_EN 69763000 IDENT Files These are files in the root of a Windows 2000/XP/2003 install CD. They are referred to by some as IDENT files and by others as cd tag files. Windows 2000 (common): CDROM_NT.5 Windows 2000 Pro: CDROM_IP.5 Windows 2000 Server: CDROM_IS.5 Windows 2000 Advanced Server: CDROM_IA.5 Windows 2000 Datacenter: CDROM_ID.5 Windows 2000 Powered: CDROM_IW.5 Windows 2000 Service Packs: cdrom_sp.txt, cdromsp2.tst, cdromsp3.tst, cdromsp4.tst, cdromsp5.tst (Hotstream) Windows XP and Server 2003 (common to all): win51 Windows XP Home: win51ic Windows XP Home Service Packs: win51ic.SP1, win51ic.SP2 Windows XP Pro: win51ip Windows XP Pro Service Packs: win51ip.SP1, win51ip.SP2 Windows Server 2003 Standard: win51is Windows Server 2003 Standard SP1: win51is.SP1 Windows Server 2003 Advanced: win51ia Windows Server 2003 Advanced SP1: win51ia.SP1 Windows Server 2003 Datacenter: win51id Windows Server 2003 Datacenter SP1: win51id.SP1 Windows Server 2003 Web: win51ib Windows Server 2003 Web SP1: win51ib.SP1 EULA.txt The very bottom line of %windir%\System32\eula.txt will tell the XP version. Substitute OEM for RTL for OEM versions. Any help on this would be greatly appreciated Windows XP Home Retail: EULAID:WX.4_HOM_RTL_EN Windows XP SP1 Home Retail: EULAID:XPSP1_RM.1_HOM_RTL_EN Windows XP SP2 Home Retail: EULAID:XPSP2_RM.1_HOM_RTL_EN Windows XP Pro Retail: EULAID:WX.4_PRO_RTL_EN Windows XP SP1 Pro Retail: EULAID:XPSP1_RM.1_PRO_RTL_EN Windows XP SP2 Pro Retail: EULAID:XPSP2_RM.0_PRO_RTL_EN Windows XP Media Center 2005 Retail: EULAID:MCE05_RM.0_PRO_RTL_EN Windows XP 64-Bit Retail: EULAID:XPSP1_RM.1_P64_RTL_EN Windows Server 2003 Gold Standard/Enterprise: EULAID:WNET_RM.5_SRV-ENT_RTL_EN Windows Server 2003 R2 Standard/Enterprise: EULAID:WS03R2_RM.0_STD-ENT_RTL_EN Service Pack CAB Files All I did here was calculate an MD5 on the cab files. Windows 2000 SP1.CAB: 3109AF4A22179FA75107F463E8346365 Windows 2000 SP2.CAB: 4F1BDEF97B5FEBE59D4EFB289B634E36 Windows 2000 SP3.CAB: 23B04BC6EAAC3D3FE93FB6D43E4BB245 Windows 2000 SP4.CAB: DD08ECAEA2F4D0CF4DD148C06039214C Windows XP SP1.CAB: B162DDEB9376C983B467A6DAB56CD466 Windows XP SP2.CAB: A1EB1534E078B3D9CEBB548CFB7A412F Windows 2003 SP1.CAB: FB057C4F127F514E863D134222F1FE49

I always archive all of the log files to a 7-Zip file and then delete them. I've found that you just never know when you might want to take a peek at them for one reason or another.

The drivers need to be on the hard disk during the client install. That's why I always suggest doing a Method 2 install with RIS. Just put the .7z files in $OEM$\$1.

Ok, well just let me know if you want to bounce around any ideas. I'm (hopefully) close to releasing the first beta of a utility I've working on for install source preparation and this thread topic is something I'd love to include in it. If you're interested in seeing what I've got so far just send a PM.