• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About PeterGau

  1. @Outatouch Yes, I'm not complaining. 2 or 3 hotfixes is great compared to the 30 or more that would be needed without HFSLIP. I was confirming Electrician's findings on KB898461 because this may become more important in the future, so tommyp or fdv might like to investigate if they have time. I am now hoping that I will not re-install XP for another year as my PC is running much smoother. Maybe SP3 will be out by then? PG
  2. @tommyp, I also found that hotfix KB898461 needed to be installed by WU even though it was in my hotfix folder. This is the new windows installer package so I guess it may require some other way of integration? I was using ~Sep6 version of HFSLIP on WinXP. The new version sounds good - you are doing all of us a big favour with all your work! PG
  3. On page 44 or so of this thread, fdv asked It is a good question and as a newbie who has recently successfully used XPCREATE and HFSLIP to make a fresh XP install, I like the principle behind HFSLIP so I hope you will not mind me making some comments and suggestions. 1. HFSLIP does not have it's own forum which means that all different types of issues are under this one long thread. This makes it difficult to pick up on useful tips and the questions being asked are often complex and confusing to the newbie. Yes, I did real the whole thread! Possible solutions: a. Ask the MSFN moderators for nice shiny new HFSLIP section so there can be multiple threads. b. Make two sticky threads, one for non-English users who tend to have different types of issues than English users. 2. I took an initial look at FDVs instruction page for HFSLIP and it seemed to be very complicated at first impression. 13 steps is a lot. When I actually tried it, it was reasonably straightforward to follow, apart from my own inability to read. Possible solution: Make a list with only the basic steps absolutely required for success then add the more optional steps later on the page. The SP2 slipstreaming procedure seems a little complicated. Why not just copy your original Windows disk into the SOURCES directory, then integrate SP2 straight into the same directory. It worked for me. 3. I only have a copy of Nero Express which I have recently discovered cannot be used to create a Windows install disk. I also do not like Nero much as it is so large and being constantly updated with a full re-install being required for every update. It would be a nice feature if HFSLIP added the option to make the ISO and burn to CD. I used cdimage and cdburn programs from Microsoft, but I am a little unsure about whether these tools are fully legit. You would probably need a DOS menu or an ini file so that the user can control what steps are performed and I appreciate this is a fair bit of work. Anyway, just some ideas. Best of all about HFSLIP is how helpful tommyp and fdv are to us newbies. Respect to both of them. PS. For those who want to avoid Nero, Roxio etc, the cdimage command line options I used to successfully make my ISO file were: -L -N -H -O -M -B I ran cdimage from a batch file in a CMD shell ( an idea from Incroyable Hulk I think). and I did not use the -soa option for burning the CD. PG
  4. @ tommyp: Many thanks to you and FDV for your work. This project has given me some idea of the complexities of Windows and the problems you must have battled with. Thanks for your idea regarding file rename back to MS originals. I did this, re-ran HFSLIP and used some new options on cdimage and everything appears to be very OK. Hurray! A samll number of updates were needed from MS but nothing much. You never know, I might try nlite next. I will post my cdimage switches later, this might be useful for people who want to use this instead of Nero, Roxio etc. There are some people who say that cdimage cannot be used to create a bootable XP install CD. @outtatouch: thanks for your words of encouragement, it can be stressful when the install can fail at any moment and your PC is out of commission. It's amazing how difficult MS have made this for all of us. PG
  5. Hi, I'm fairly sure that my problem lies with the ISO creation process. I really don't want to use Nero after I had to download it on dial-up after it failed with SP2. I do have my original install disk but would have to download the latest version again, now on broadand thankfully. Talk about bloatware ~90megs for full version and badly constructed/confusing website. So I will try to use command line version of cdimage, not GUI version. Can anyone suggest correct switches for this with HFSLIP files? I have found many ideas for this on the web so will try to sift through. dreaMMar's success gives me encouragement that this will be worth persisting with. PG
  6. @tommyp Thanks for your offer to help. Fair point, I had been working on this for about 10 hrs so was a little tired - needed a beer. I have attached my HF directory listing. Other info: I used my Windows XP home genuine source disk. I slipstreamed SP2 into this first. Language is English. Not using FDV IE removal fileset. I have used basically the same fileset to make a succesful install but without integrating the hotfixes (used the .inf method) which is the OS I am currently using. Hope this is sufficient info to give you some clues. I need to find a utility to verify file integrity I think. PG HFDIR.txt
  7. Hi, I've been trying to make an HFSLIP'ed CD today but have run into a problem. It's a simple install with very few extra files other than the type 1 hotfixes, WMP10, and Sun Java switchless package from Ryan. When WindowXP setup gets to T-39 I get a fatal error message SXS:DLL syntax error in manifest or policy file "D:\I386\asms\60\microsoft\windows\common\controls\" Error installation failed on line 5 Data error (cyclic redundancy check) Fatal error Starnge, I thought, so I re-installed windows from an old disk and did some checking on the Web. There was some agreement that this type of error message is due to a corrupt source file. Line 5 of the above file refers to an SHA1 check of the comctl32.dll file as follows: <file name="comctl32.dll" hash="11f2b96b396fe88375a76e566628ed81b608b782" hashalg="SHA1"> I selected the comctl32.dll on the HFSLIP install disk and tried to copy it to C: but an error message ocurred saying the file is corrupted. Oh dear, I thought, I must have got a bad CD, I'll try again. I re-ran the HFSLIP_50906.cmd, re-made the ISO file and burnt another CD. But I got the same message again. I am using cdimagegui to make the iso and cdburn to burn the CD. The comctl32.dll file in SOURCESS appears to be OK in that it can be copied manually. Any ideas would be much appreciated as I have no idea how to proceed. I cannot believe that two CDs had errors in the same file. I am using the -sao option with CDBURN - could this be causing the problem? P.S. where should I put the GDITOOL hotfix? PG
  8. Hi, I ran HFSLIP this evening and everything seemed to go OK to create the SOURCESS folder. I have another quick question. In Step 6 for Windows XP slipstreaming, FDV's instructions say: Copy the root files from the Windows CD to D:\HFSLIP\SOURCE Windows XP WIN51 WIN51IP Win51ip.sp2 My question is, should I not also copy over setup.exe? I would have thought that Windows would not install without this file. Sorry to seem dim but in a later screenshot in section 8 of the guide, there is no sign of setup.exe in the top level source directory so it's a little confusing. I could copy this file into the SOURCESS folder before making the ISO etc. Thanks for any advice on this, I don't want to make too many coasters. PG
  9. Hi, I had a problem with XPCTVARS and other variables when I tried the Aug 18th version but I made a updated XP disk with no problems last weekend after I downloaded the Aug 20th version. I haven't tried installing the OS yet as ideally I would like to fully integrate the hotfixes into the source files. I suggest you should check carefully which version you have. Alternatively, it may be a problem with the non-English version. PG
  10. @fdv - thanks for your quick reply, I'll continue with my adventure into HFSLIP. I can forget about WGA as I'm not too fussed about having everything absolutely up to date. I'll look into your google suggestion. Yeah, I'm not keen on Microsodt either, but I don't want to spend too much time on keeping my computer safe so it's easy to use MS autoupdate. I noticed that the latest Sun linux distro comes on 6 CDs ....ouch, maybe MS is not so bad. PG
  11. Hi, I 've decided I would like to use HFSLIP because it seems to be a good program to re-install my computer without too much hassle and make a compact installation. I'm following instructions on FDV's web site but have hit a couple of snags. a. In the previous pages on this thread, there were references to a help file called instructions.txt, I cannot find this file but assume it has been replaced by FDV's web pages. Can anyone confirm this is correct? b. I have come to the point: "3. Download LegitCheckControl.msi (Windows Genuine Advantage) . Windows Update is explained in more detail here, XML file here. 4. Extract the file with winzip/winrar and put the MSI installer into the HF folder. If you just put it into the HF folder, the correct files will not extract." but when I click on the link "LegitCheckControl.msi", an exe file with a very long name is downloaded and I don't see how I can extract a file from it as advised. The second link in section 3 above "(Windows Genuine Advantage)" is currently not available from MS. I am a newbie to this so any advice would be appreciated. PG
  12. I have spent some time trying to get my head around the complicated process of making an XP install disk with all the latest updates. We have to thank GreenMachine for making XPCREATE that installs the hotfixes according to MS advice and which does not cause problems with WFP. My understanding now is that XPCREATE uses the svcpack.inf method to integrate the type 1 hotfixes. This means that the hotfixes are not fully integrated into the Windows source until the CD is installed onto the target machine. Another option is to use the /integrate switch to replace the outdated files in the original XP source disk. This means that the old files are deleted and the install is make with less obsolete junk. I would like to make a request to GreenMachine to add a switch to the XPCREATE.INI file to allow the user to choose which method is used to integrate the type 1 hotfixes. It seems to me that this would produce a cleaner install without the hotfixes appearing in the Add/Remove programs in the control panel. Would this be possible and does it make sense? PG
  13. Hi DSchwenk, OK, I've done some more research on this and I was wrong . You should be a able to slipstream a service pack and hotfixes on an OEM windows source. But you cannot slipstream onto a source which already has had hotfixes added. See MS article There is quite a lot of info about this subject on the web and I think you can sort it out if you use a clean Windows XP source disk (OEM or not). There is also some talk that one or two files may have to be deleted from an OEM source - particularly the name Dell seems to crop up. PG
  14. Hi DSchwenk, I was just about to post when I noticed that GreenMachine had responded. Yes, I have heard that it is not possible to slipstream on to OEM disks - what a pain You can get the mp10setup.exe from MS at: You need to go through their validation tool. PG
  15. Hmm, I am a newbie at this but interested in trying XPCREATE for myself. I found something else a bit odd in your log file: -- 11:10:01 -- Copy SP1.CAB. -------------------------------------------------------------------------------- TEMP\CABS\SP1\1394bus.sys TEMP\CABS\SP1\61883.sys TEMP\CABS\SP1\ac97ali.sys etc so I thought maybe your source CD was Windows XP with SP1. Can you confirm? I'm not sure if the 'wmcsetup.exe' file could cause your problem. Seems unlikely. This is the Windows Media Connect extensions, quote from MS, "Windows® Media Connect enables you to deliver music, photos, and videos that reside on your Windows XP PC to devices that support the uPnP protocol". The "mp10setup.exe" file is for Windows Media Player 10. I thought that the hotfixes would not appear in add/remove programs as XPCREATE is supposed to fully integrate them into the Windows source. Can anyone confirm or deny this? PG