mcmahonp

great stuff! i rebuilt and the only error i got was with the signatures of 2 msxml2 files. other than that god knows what was going on. i removed the flash cab file but will probably add it or otherwise another security fix is required. i can live with error logs just as long as i know why they are there :-) thanks for your time and advice. phill

The file in question this time is msxml2r.dll Error: Setup detected that the system file named [c:\windows\system32\msxml2r.dll] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. I am doing another CD at the moment. To see what results I get this time. I am removing the flash cab for now as well. The patch in I386/SVCPACK is KB911164. It seems there is not a lot of information about this patch anywhere other than a mysterious post about support agreements and speaking with you TAM. If I remove this directory and the svcpack.inf from I386 is this is all that is required to get a clean source? Thanks for your time and help, much appreciated. Fingers crossed for a clean build :-) Phill

Hi. I am running it from Windows XP SP2 which was installed with a WINNT.SIF file which changed the default user and program locations. Nothing funkier than that. Now here it gets weird, I ran it all again, from the same OS with the same patch list and reinstalled in Parallels. This time I only got 2 errors, one was a failed installation of the Flash cab file and the other was a signature error. God knows if this has to do with running it on a beta VMware installation. I am gonna wipe the lot and start again and keep you posted if anything crops up again... If my CD is from MSDN, the corporate volume licensed XP with SP2 slipstreamed into it why it is being flagged as a dirty source. Other than mount it I have not done anything else to it. Cheers, Phill

Cheers Kiki, I much appreciate the help and advice. I think I have another ISO image on a HD somewhere, I'll dig it out and see if that makes a difference. I tested it in VMware on the Mac and I currently doing a test in Parallels before putting on my laptop via Bootcamp. Obviously the install works but I would rather understand the cause of the errors and remove them if possible. When running a sfc /scannow and checking the event log it looked like version number etc had been corrupted somehow. They were coming up as 0.0.0.0 in a lot of the cases. As I said before I am using stock ISO's from Microsoft and the standard set of patches. Nothing fancy and no dll patching etc. Very weird. I'll keep you up to date with my progress and maybe (hopefully) someone else might shed some light onto my problem :-) Enjoy the rest of your weekend. Phill

Kiki, My image is via my MSDN subscription with SP2 already slipstreamed as part of the image. It has not been touched in any other way than mounted via Microsoft's VirtualCD tool. Cheers, Phill

Cheers Kiki Burgh for the quick reply. My concern is that I am using a slipstreamed Windows XP SP2 disc with only the official hotfixes published by Microsoft. One thing though is that it says my sources are not clean, is this because SP2 has been integrated? Why would I need patched files and / or the flush the CAT files? My assumption after using nLite and the RyanVM pack would be that HFSlip would integrate the standard hotfixes with no errors. I hope you can help me :-) Phill

Hi, I am new to this tool and wanted to thank the author and contributors. It really is fantatic and a real time saver :-) After an initial install I find a large number of errors in the setuperr.log file. These all related to incorrect file signatures. I have attached both the HFSLIP and setuperr log files. Please can someone let me know what I need to do to prevent these errors occuring in the first place. Regards, Phill HFSLIP.TXT setuperr.txt