johnhc

Bumbastik, sorry, I do not know what a "uefi structure" is, so I cannot help you. Enjoy, John.

Bumbastik, I do not know about WinPE 4.0 but I have created a 3.0 USB stick (nothing special done) that I can boot in both old BIOS mode and UEFI mode. I use it to start a flat install (from HDD). UEFI mode allows the creation of a GPT formatted disk. Enjoy, John.

Vengada, that does not look like a valid answer file. It does not start out properly. I have attached mine with modifications. I have replaced information I do not want public with ????. The product key is the default one, so it is in the public anyway. My file probably has lots of stuff you do not need or want. Also remember that the answer file must be named as mine is - AutoUnattend.xml. Good luck and enjoy, John. AutoUnattend.xml

Vengada, I am not an expert but am reporting what works for me. This is the code in my answer file: <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SystemLocale>en-US</SystemLocale> <UILanguage>en-US</UILanguage> <UserLocale>0409:00000409</UserLocale> </component>As you can see, the JA-JP should be fine but as I said, 0411 is accepted by Windows System Image Manager and I assume it will be OK for Setup (but I have not tried it). I was hoping one of the real xml experts would respond and help you. What I said makes sense, but I cannot determine what else might be missing. I do recommend that you run Windows System Image Manager against your answer file and see if it finds any problems. Did the initial phases of your install show English or Japanese? My debug steps for the answer file is to do test installs on a Virtual Machine (I use VMware Player - FREE). I suggest you give a VM a try before you hit the HW. It would be quick to try 0411 vs JA-JP, for example. Also look at the unattend.chm (C:\Program Files\Windows AIK\Docs\CHMs) help file for the details on the xml code for the answer file. BTW, if you have additional problems/questions, please attach your complete answer file, of course with your private data obscured (PWs, Key, etc). The one above is missing some parts. Enjoy, John.

EDIT: Deleted. System hung then put my reply in a second time when I clicked Add again.

Tripredacus, I think the numbers are OK. At lease Windows System Image Manager accepts them. Vengada, I suspect that the same information is needed in the oobeSystem pass as well as the windowsPE pass. My answer file (W7) has both. Perhaps the setup is in Japanese and the installed system is defaulting to English. Enjoy, John.

RickRollNW, I am really not qualified to reply to your problem, but have seen the CD/DVD driver missing message in another thread. This says simply that it is not a missing CD/DVD driver but a driver needed to locate an HDD to install Windows. It is just another example of bad MS Windows messaging. I was also curious what format of disk you are attempting to use - GPT or MBR? Will this affect your results? Enjoy, John.

RickRollNW, I found this tutorial on MS TechNet. I'm thinking of trying it on a VM. Enjoy, John.

RickRollNW, I think you use the Apply switch to imagex. I decided that it was not useful for the way I install W7 in my system so I looked no further. There are a number of people here with much more knowledge than I who can help. I assume you capture an image with everything in it, then run imagex and 'apply' the image to your system. Open a 'Deployment Tools Command Prompt' and issue imagex /apply /?',no quotes, for details. Enjoy, John.

Thanks, Tripredacus. I will do some research and see if I can use this method. Enjoy, John.

Tripredacus, I am curious how you do this. Is it the 32/64 nature of setup.exe that is causing the 'Load driver' function to fail to find a mass storage driver? Is this a work around for that problem? Thanks and enjoy, John.

JFX, thanks for your rely. Enjoy, John.

Tripredacus, thanks. I have about the same feeling but as I stated, many seem to think it is too much of a hassle. Thanks and enjoy, John.

JFX, this is a really good tool, but I am wondering if the actual WinPE image files could be DLed. The whole PETools folder is almost 1 GB, so maybe options for the various sub folders. Is this possible, doable and legal? When I encourage people to use WinPE, the requirement to DL and install WAIK seems to a significant roadblock. Thanks and enjoy, John.

Tripredacus, thanks but you are way beyond me and my curiosity about the way Setup loads drivers. Enjoy, John.

Thanks, for your reply Tripredacus. I have had this SSD for about six months now and have always injected the driver into W7 Ultimate x64 with no problems. Most of the users on the OCZ forum use the 'Load Driver' button on the "Where do you want to install Windows" screen. I assume, perhaps erroneously, that Setup (WinPE version) is using drvload to install the driver. Thanks and enjoy, John.

Thanks, Tripredacus. I guess I will be using drvload for the SSD driver unless OCZ can explain. The injected NIC driver seems to work fine. Thanks and enjoy, John.

I am using WinPE 3.0 to update and secure erase my OCZ SSD. I injected the SSD and NIC drivers into WinPE.wim (x86, as boot.wim) and booted it from a USB stick. With diskpart I can see my SSD W7 installation. To do an update I use a tool called OCZToolBox. The latest version (3.02.06) cannot see my SSD but the older one does. However, if instead of injecting the driver I use drvload to install the same driver files, I can see the SSD with the latest. What is the difference in injecting the driver and using drvload? Here is a link to the thread on the OCZ forum. It contains lots of extraneous information but possibly some useful to those here. Thanks for any help/suggestions. Enjoy, John.

bphlpt, right click and Save target as... Enjoy, John.

In the first post of this thread there is code to silently install WAIK: IF EXIST %SystemRoot%\SysWOW64 REG ADD %KEY%\054 /V 1 /D "msiexec.exe /i "%SystemDrive%\Install\Waik.EN\wAiKAMD64.msi" TRANSFORMS="%SystemDrive%\Install\Waik.EN\wAiKAMD64.mst" /qr /norestart" /f It requires a Transform file. I cannot find the wAiKAMD64.mst. I have PMed Major but got no response. I have searched the Internet without success. Hope someone can point me in the correct direction. Thanks much for any help available. Enjoy, John. EDIT: I have figured out how to create a TRANSFORMS file using OCRA, so don't need one now.

Kurt_Aust, you are correct. The one DL with the bad hash codes says the certificates on the signatures are not valid. I DLed again from both the direct and MS DL Center - codes and signatures are OK. The one I have been using was fine all along. Thanks and enjoy, John.

Kurt_Aust, as always, thanks for all your efforts. I was checking to see if my DirectX was up to date and ran into some confusion. Only one of the two hash codes you post checks (MD5) against mine. If I use the direct DL symbol (underscore with down arrow), I get a file that no hash codes agree but if I use the link to MS Downloads, I get the MD5 to agree. The three codes I look at are: CRC32: 9ECD3C73 MD5: 7C1FC2021CF57FED3C25C9B03CD0C31A SHA-1: F8F1217F666BF2F6863631A7D5E5FB3A8D1542DF All files are the same size. Which file is the correct one? Thanks and enjoy, John.

I have noticed that drag-n-drop into a command prompt (to insert the path) does not work in W8. A search revealed this did not work in Vista. Has it reverted or is there a work around? Thanks and Enjoy, John.

pogocomrules1, it is impossible to run nLite and not have a .ini file, unless you have selected the option to not save it. It should be in your source folder after running nLite. It sounds like you have not actually run nLite again. Please post your Last Session.ini when you get one. Be sure to answer Kelsenellenelvian's question about your source. You MUST have a valid (legal) copy of XP source, with a valid (legal) key, that has not been modified by nLite or any other program before. When your VM reboots, try hitting F8 and see if you can get into Safe Mode. If you can, then un-check the option for Automatic Restart (My Computer/Properties) and then reboot - post the BSOD code. John.

pogocomrules1, the most obvious problem is that you are running a down level version of nLite. Go to the nLite site (ONLY!) and DL the latest (1.4.9.1) and start over. Do no specify any Preset. Enjoy, John. EDIT: Obviously, you must have a fresh copy of your CD's files/folders.