johnhc

synthro, the 07B Stop code is saying Setup cannot find your HDD. My guess is that you included your Text Mode driver into the nLite build. When you use the original CD, you will need to hit F6 when asked and tell Setup to load the Mass Storage driver from your floppy drive. If you have further questions, please attach your nLite Last Session. Enjoy, John.

brex, great, glad you are running. You are welcome. Enjoy, John.

maxXPsoft, have you tried issuing, at the cmd prompt, "fsutil objectid query <filename>", with out the quotes, of course? Don't know what it will tell you, but should not hurt. Enjoy, John.

muffinman123, I guess you could enter an invalid key and Setup would then be forced to ask for one. Please let us know if you try this. Enjoy, John.

brex, I do not see anything really obvious. I would leave in Display Adapters. I would not think it matters, but I remove the (old) ones with no problems. A bigger problem seems to be how down level your system is. Unless you have installed SP3 and the about 100 updates, your system may not have some needed update for the screen SW. As a test, I would suggest you run nLite again (fresh source), include SP3, perhaps an Update Pack with subsequent updates and remove nothing. See if this will run. I would also not remove Administrator VBS scripts. I see you are including no drivers. How are you installing drivers? What is your main display and driver? Have you run nLite more than once against the same source? You should run nLite only once against a fresh copy of your CD files/folders. Enjoy, John.

Thanks, Kurt_Aust. Enjoy, John.

darklunar, I think maxXPsoft will have to answer your question, but I have some suggestions. There is a 7UA sub-forum above you should probably use in the future and look at now for an answer. Please post the version of 7UA you are using and particulars of the W7 being processed. I have had lots of problems with my security SW (Comodo Internet Security) and I use ImgBurn to make the ISO. Good luck, John.

poweriso, since you did not use nLite, you will not have a Last Session file. I am not familiar with the method you are using. I suggest you try the changes to your .reg file posted by cdob above. Good luck, John.

Thanks again, Kurt_Aust. I am wondering about .NET. Do we really need all the versions and the SPs? Right now I am installing only 3.5 and the SPs on my XP x64 system. My plan on my W7 x64 and next XP install is to use only 4.0. What else, if anything, do I need with it? Thanks, John.

zerstreuter, there is also a German nLite forum. Enjoy, John.

mactrekr, welcome. AddOns are included in the hot fix section. Be sure to select the Task Hotfixes, Add-Ons and Update Packs. Enjoy, John.

Mina, have you run nLite more than once against the same source? You should run it only once against a fresh copy of your CD files/folders. Did your oeminfo and oemlogo copy work? If not, you may need to add a Cmd /c in front of the copy commands. Please post a screen shot of your Automatic Updates tab of the My Computer Properties. Enjoy, John.

03GrandAmGT, I have not tried VirtualBox. I began using VMware Server (on XP x64) before VB supported x64. It was just natural for me to continue to use it for W7. When I ran into the hangs, my research revealed that Player was also free (for my personal use), so I took advantage of my knowledge/experience with Server - also could use existing VMs. I guess mainly I am too lazy to learn a new virtual system at this time. I will probably give VB a try if I run into problems with Player. Thanks for your comments. Enjoy, John.

cluberti, thanks for your comments. As I am running 64 bit OSs, some of those (VirtualPC for sure) can ruled out. I don't know the others, but I will say again, Player seems to be a good replacement for me. When I do my first install, perhaps I'll change my mind. The link I provided in my first post leads to links that point out the Server EOL. Thanks, John.

CoffeeFiend, I think for you that are really using VMware Server in a server environment are in some hurt. So far, I really like the simple window based interface in Player, but suspect it will not do your tasks. Perhaps VMware has decided that they want more revenue. Thanks for your comments. Enjoy, John.

MrJinje, thanks. I installed VMware Player (after removing VMware Server). I pointed to and started both of the VMs (XP x64 and W7 Ult x64) I had created and installed under Server and they both came up and ran under Player. It is simpler, lighter and has fewer functions than Server but I think for the testing I am doing on my builds it will be fine. I have seen no hang problem. For one thing Player DL is much smaller than Server - 90 MB vs 500 MB. Enjoy, John.

But it not work, then I use the Sata/Raid Driver from my Motherboard CD Drivers, the problem is the same. it can't boot after i set ACHI in bios. Sorry, if my english is so bad. Thanks. poweriso, welcome and your English is just fine. Please attach your Last Session as requested in the bold RED letters above. It is not clear to me how you are including your drivers. I assume you are using nLite or you would not be here. Are you running 32 or 64 bit OS? Enjoy, John.

I have seen a hang problem running W7 (Ultimate x64) in VMware Server. Please see this thread on the VMware Forums. I have DLed VMware Player (free for private, noncommercial use) and will give that a try (must remove VMware Server). Enjoy, John.

Thanks for all your replies. I think the idea of seeing things I have injected has some value, so will allow WSIM to create the .clg file - thanks ricktendo64. Enjoy, John.

When I defined my install.wim file to Windows SIM, it said my catalog (.clg) file was out of date. The image has been modified. When I pointed to a folder with unmodified .wim, I go no such message. I did some research on the the catalog file and found that it is typically much smaller than the .wim file (<1 MB vs > 2 GB). Is it really important to update (re-create) the .clg file? The research seemed to indicate it contains information about the .wim file. What code uses this information? What are the problems if it is out of date? Is WSIM the only way to get a new one created? Is there a command line interface to do the creation if it is really necessary? Thanks, John.

But did it? I'd check the logs closely especially since you had that 07B Could pause it at that point and do it manually Not sure but there may be a file zMountDir & "\drivers.log" that I delete at end of Pack Also one located here zMountDir & "\Windows\inf\setupapi.offline.log" I copy to my Logs location Sorry, maxXPsoft, I was not clear here. I was talking about my nLited XP x64 install and my VM experiences. I am currently running only under VM and do not plan on going to HW for some time. I have much to learn yet. Enjoy, John.

maxXPsoft, I was able to get my AutoUnattend to work, so now I am going to see if I can figure out what is going on with the drivers. Some things I did worked and some did not. I created a user account and AutoLogged it but forgot to make it an Administrator account, so I cannot do anything. I am impressed with your "It's still running"! My experience with VMware Server has been very good. When I did my current machine (XP x64), the only difference was HW stuff, like the HAL was wrong so I only had one of my four cores running. The drivers all worked except for the 3Ware RAID text mode one and Fernando1 helped me fix that. Thanks, John.

maxXPsoft, I was able to see the BSOD code - 07B. This basically means that the HDD could not be found. I do not know why this would ever show up on a VM system. I removed all drivers and my modified AutoUnattend.xml and it installed fine. Enjoy, John.

urie, as I thought, it uses the Windows expand command. I tried it on a few of the files and they were bigger afterward, but the names looked the same (xxx.ex_, etc). I assumed that the expansion did not work but did not try running dism. The released version of 7-zip did not work either (cannot open archive). The latest 7-Zip Beta (9.13 Beta) works just fine and I wrote a little batch file to expand all the files. They now appear with their original names and dism runs fine. I have not done an install and will not for some time as I am still learning the ropes and trying things on a VM under VMware Server. Thanks for your leads. Enjoy, John.

urie, if I knew what the .exe did and how it did it, I might consider using it. I found that the compressed files in the Catalyst Display drivers could not be decompressed with 7-Zip or Expand command. Thanks. Using the latest Beta version of 7-Zip (9.13 Beta) I have been able to expand the problem files and inject them into an image using DISM. Enjoy, John.