johnhc

MagicAndre1981, so why does MS present this update to us that have SP1 and why does the KB article say it applies to SP1? Enjoy, John.

Bad boy Warrior, I found this thread that looks interesting. I assume you are talking about SSH FTP (SFTP) and not FTP SSL (FTPS). I have used Glub, FileZilla and FileZilla Server (all free for non commercial use) to do some testing of FTPS on W7 Ultimate x64 using VMware Player VM (also free). Enjoy, John.

winfor, I am running W7 Ultimate x64 with SP1 and just got notified that KB2533552 is available. The KB article indicates it is for SP1 and well as no SP1. How did you create your image with SP1? I used sysprep but have not tried to inject this update or install it on my running machine. Enjoy, John. EDIT: I just noticed that KB2533552 is not checked in Windows Update. I am going to try installing on my VM.

neuropass, in case you do not read German, you might take a look at this thread: http://www.msfn.org/board/topic/149068-unattended-ati-catalyst/ The interesting thing is that the search function in MSFN did not find this thread, but Google showed it as the first answer. Chipset drivers inject normally. Enjoy, John.

Sorry, ricktendo64, the first part is certainly true but running nLite under W7 to create an XP ISO often leads to bad results. The main one I remember is if an SP is integrated, then it may not be possible to get the key accepted. In general, running nlite under W7 is discouraged here (as per Sp0iLedBrAt's response) due to the large number of failures we have seen. lolka, please find a way to run nLite under XP. You can use a VM under W7, including the one available in some versions of W7 if you are processing 32 bit XP. Enjoy, John.

Thanks, Kurt_Aust. I think your new C++ files have been superseded. I just did an install of my W7 on VM with these then ran Microsoft Baseline Security Analyzer 2.2. It found later versions for 2005 and 2008 of KB2467175 and KB2467174, respectively. Please let me know if you disagree. Thanks, John.

maxXPsoft, yes, x64 Ultimate. Did you change the FirstUXRes.WIM files in SP1 before slipstreaming? There are at least two copies in SP1. I did another install (VM) yesterday and all went fine. My Install.wim came from a sysprep/capture from a DVD installation plus SP1 and IE9 (installed after W7 installation). I did a similar search as yours the other day with about the same results. Enjoy, John

Markus1234, I suggest you look at the videos and tutorials in ricktendo64's signature (above) on the WinCert forum. He shows you step-by-step how to use DISM, SysPrep and Imagex. Also see this MSFN thread. Enjoy, John.

maxXPsoft, how was your DVD made? I made my image that works (including FirstUXRes) using sysprep/capture. Have you searched the DVD, including images, for FirstUXRes? The only thing else I can think of is that a new file is being DLed. Do you have an Internet connection during install? Good luck, John.

maxXPsoft, I assume you are injecting SP1. I suspect that many aspects of SP1 install is being executed during the actual install. You probable need to copy your FirstUXRes.wim into SP1 (replacing their two copies) before you inject it. Enjoy, John.

maxXPsoft, I should have said my hashes are SHA-1 not MD5. My MD5 hashes are the same as yours. My SP1 was installed before I did a sysprep/generalize. As you can see there are two apparently different FirstUXRes.wim files (different size and hash). When I extract these they contain the exact same size and number of files. I suspect they are really the same. There is no source that I can find for one of the files, so I suspect Setup creates this file from some other files. Perhaps the FirstUXBackground.bmp file is being copied into a folder and a new FirstUXRes.wim being created, thus replacing your file. We would need to discovery which file this is and replace it also. You did not answer my question about the size of the imageres.dll. It looks like you have modified the one in the boot image and replaced the one in the install image with it. The one in the install image is about twice as large as the boot one. Does this not present a problem? Thanks and enjoy, John. EDIT: The larger version of FirstUXRes.wim is in SP1. EDIT: I just installed an ISO in my VM consisting of the install.wim from the sysprep/capture (with SP1) and running your background batch files against both install and boot wim files. All went fine during the install including the FirstUXRes image. I guess it is the SP1 copies of FirstUXRes.wim that is the problem. With the captured image, these have ben applied and your batch files then overlay them. I am still concerned by the size difference in imageres.dll. What do you think? EDIT: I extracted the two (different size) FirstUXRes.wim files and used the FC command to compare them. All file pairs are identical. You should be able to replace the file in SP1 with yours and be good to go. EDIT: I compared the 32 and 64 bit versions of spwizimg.dll and imageres.dll. Each pair has several differences and I suspect the differences may well not be ignorable.

maxXPsoft, I have been looking at your background procedures and files. My initial interest was to determine if any of the DLLs changed with SP1 and I do't think they have. What I found was your imageres.dll was about the same size as the one in the boot image but about half the size of the one in the install.wim. I attach a file with a summary of my findings. Why is there so much difference in size? I did not worry about the bit map files - assuming it is OK to change a picture. Maybe there is a potential problem using the smaller imageres.dll in the install image. What do you think? Thanks and enjoy, John.

docfxit, try removing .NET and reinstalling after a reboot. Let us hear. I run just .NET 4.0. Enjoy, John.

Here are some results of my testing under VMware Player. I was not able to start Setup from a VM and use a VHD file to install. I get the same message mentioned above except it also says I am using a Surfaced Virtual Disk, whatever that is. See attached screenshot. The Next button is grayed out so I cannot continue. I may have found a more straight forward method of installing on a VHD. I boot the CD (ISO on VM) and click Install Now, not Repair. I proceed to the partition selection window, then press SHIFT-F10 to open an Administrator Command Prompt and use Diskpart for the VHD part. After closing the command prompt, clicking Refresh then finds the VHD and installation continues normally. I still get the warning about maybe not being able to boot from it but not the Surfaced Virtual Disk part and I can click Next. It was also possible to create the VHD in my W7 system (VM) and use Diskpart to Select and Attach it. I have tried none of this on HW, only in a VM under VMware Player. nice_guy75, as you can see in the screen shot, I am able to have the VHD on the F: disk and have also used the E: disk. What disk I install on is determined by the fact that on my HW, XP was already installed (on C:), so W7 went to the F: partition. I have kept it this way and mimic my HW on VM by using the Unattended.xml file to partition my VM drive, format, assign drive letters and specify install to the F: disk. Enjoy, John.

Thanks, ricktendo64, I will give the file a try on my VM. Enjoy, John.

ricktendo64, did you get the BIOS warning on your VHD install on HW? Currently I do my installs on my HW with a dual boot (XP x64) and using a flat install (from a hard drive.) Do you think this will work for a HW install on a VHD file? Thanks, John.

ricktendo64, as stated, all testing was done using VMware Player. I used a VHD (xyz.vhd file) on the VM (also used separate partition, which worked OK). I wanted to use a VHD so when (and if) I do this for real on my HW, I will have experience on my VM using a VHD. Thanks, John.

ricktendo64, I did a lot of experimenting and finally succeeded. It seemed that MS was trying to block me in every way. All my attempts have been using VMware Player VMs. First I installed a bare bones W7 Ultimate x64, then created a VHD using Disk Management. After booting the CD again, I tried to use Diskpart to attach the VHD I created but it said it could not find it. I then rebooted my installed VM and deleted the VHD and ran defragger. After booting the CD again, I used Diskpart to try to create a VHD, but it said it could not because there was not enough space. There was plenty of space, but the size was reduced until the Create worked (50 MB). For some reason Diskpart could not detect the true free space. I then started over and let Diskpart create the VHD from the start and it worked OK. The Generalize went OK. I then copied the VHD file to my real system (also W7 Ultimate x64) and tried to run Imagex to do a capture. Repeatedly I got Access is denied on the attached VHD. I was using the WAIK tools prompt which sets up the paths and says it is an Administrator mode prompt. Turns out it is not. When I ran Imagex.exe directly from the WAIK folder, the capture ran just fine. I do not know why I needed the true Administrator prompt - perhaps because of the way I created and copied the VHD file. It also appears that a mapped network file cannot be used because I kept getting invalid file. I watched your excellent video (capture) many times and it was very useful. I also read the tutorial concerning using a VHD. Thanks again, John. EDIT: When I selected the VHD for my install on VM, Setup told me that Windows could not be installed on the partition because the BIOS might not be able to boot from it. I clicked Next anyway and it went just fine. It seems I remember some questions in the past when I first worked with W7 that some older MBs (BIOSs) could not boot into Audit Mode. Is this a possible problem if I try this on my HW? Might I have trouble installing on a VHD on my HW?

D.Arbib, I had the same problem. Please see http://www.msfn.org/board/topic/147973-w7-prefetch-does-not-seem-to-be-working/ and http://www.mydefrag.com/forum/index.php?topic=3740.0. Type this into a command prompt (rundll32 advapi32.dll,ProcessIdleTasks) and it will get layout.ini back. Enjoy, John.

Thanks ricktendo64 and myselfidem. I have done some research, created a VHD and attached it (on a VM). I have also found guides on how to make it bootable (bcdedit). Is the guide I referred to in my first post a good one to use? Can you point me to one that does the whole process using a a VHD? When I am through with this procedure can I use the install.wim as I do today (running DISM to add updates, drivers etc)? If I do it under a VM will the installed image looked like it is running in a VM? One of my main problems is that I am a home user and am not familiar with terms such as sysprep, generalize, etc. ricktendo64, I do not understand what you are saying here: Thanks for your help. Enjoy, John.

ricktendo64, thanks much, you always seem to have good ideas. I am going to do some research on VHDs and some of your other ideas. I am sure I will return with some questions. Thanks and enjoy, John.

I currently use DISM to create an Unattended install image for my installs. It works fine but I would like to try a more official method possibly using reverse integration. I have found this procedure . There may be much better, or easier, procedures and I would like to have a link to such. What I would like to do is capture an install.wim that contains SP1 and IE9 (now that both are RTM) and use this as a basis to my current process which includes using DISM to add drivers and updates. I also add Registry tweaks and the Unattended install adds most of the applications I use. The reason I do not want to capture a complete image is for update purposes. I do frequent installs and do not want to have to go through the capture procedure each time there is an update. I prefer to do the whole image creation process on VMware Player. Is what I am wanting to do possible? I would appreciate any help and comments. I am using W7 Ultimate x64. Thanks and enjoy, John.

fragbert, I am not familiar with oscdimg.exe, but I have created many an ISO larger that 6 GB and run them on VMware Player with no problems. I use ImgBurn to create my ISOs. The largest file is Install.wim and no other file exceeds about 450 MB. If you are interesting in trying ImgBurn, let me know and I will share my parameters. Enjoy, John.

OldNewb, some suggestions and questions: Write DVD at the lowest speed. You may be burning a bad disc. Are you using nLite to burn DVD - I assume so? Try another program to write DVD - such as ImgBurn. How large is your source folder after running nLite? Have you tried running nLite against your CD and burning a DVD with no changes at all? I have used DVD since my XP x64 ISO was so large but when it got to a certain size (my source is 2.6 GB now), nLite did create a good image. You can also try the alternate builder on the Create Bootable ISO page (see pull down list.) I just went to ImgBurn and have had no problems since with XP or W7. Please let us know what you learn. Enjoy, John. EDIT: Also be sure to use Verify whatever burn SW you use.

MagicAndre1981, thanks again, but you still have not answered my questions. I understand that what I, and others, are doing is not MS legitimate and I accept that. What I would like to know is should I run the SUR (and replace the altered files) or not? And, what are the consequences of what I have learned? Thanks and enjoy, John.