Atheros

If objFso.FileExists(Sysfolder & "\1.txt") Then i think you'll find that it will always return a negative result until you remove the "\" corrected code: If objFso.FileExists(Sysfolder & "1.txt") Then also as i said before: sysfolder = syswow64 in 64-bit so your text file must reside there has this solved it? or am i being an id***?

the command to start an unattended file in winpe (if you didnt already know) is: wpeinit /unattend:<path to xml file> (e.g. wpeinit /unattend:x:\Autounattend.xml) this should help save the use of 3rd party programs to set screen resolution, and get the keyboard layoit for your country rather than en-US!

have you thought about customising you wim image to already contian your software install?? i try not to use first logon commands unless i really need to, to avoid the end user having to wait for 'said' installs to complete before they can use thier system. this way you have a complete install of your o/s and software and can be audited if need be. first logon commands will not run until oobe has completed.

OK, so MS still havent responded and i think i have debugged the issue on my own. so... ive decided that using the windows version of the tool (reagentc) would probably sort this out. oh how i was wrong (avoid online tools like no tomorrow). so heres the useful information: winrecfg.exe pipes data to windows\system32\recovery\ReAgent.xml on the OS drive (the drive can be hidden but the winre.wim can not be) so found that its actually windows during the generalize phase that creates all booting information for WinRE. it creates the following files on the WinRE partition. recovery\windowsre\boot.sdi recovery\system32 (an sub folders) all of which are given the readonly hidden and system file attributes after oobe completes. (found the problem) so before i run the winrecfg tool during the recovery process i now do the following. attrib c:\*.* -s -h -r /s /d del recovery\windowsre\boot.sdi rd recovery\system32 /s /q problem now resolved.

it is the default last option on the windows re screen, unless you have a custom factory recovery tool. also you could always start it in your custom tool. the winre srt package is launched from the winpeshl.ini. so you could also launch it there too.

try installing the language pack thats in the winpe_fps\en-us folder for the scripting package to see if that lets it work... i use winpe amd64 as a recovery source and letting you know it works fine. so defo something being missed.... also the exe application has to be 100% 64-bit as they WOW function doesnt work in winpe. just remember to copy mshta.exe from the system32 folder to the syswow folder as they still haven't corrected this bug. (but you seem to already have your hta running so you prolly dont have to do this) hope this helps

wpeutil -initializenetwork

use the split wim feature from imagex, then it should call the filename when it needs it.

does any1 know what file winrecfg creates. im getting an error after recovering where it says it cannot create a file that already exists. i know its a bit of a specialist question, but any help is appreciated [EDIT] OK, so no one seems to know, i have passed it to microsoft and i will be working to see if i can resolve it. ill post the solution once i have it, for future reference. [/EDIT]

if it is not auto-restarting you can press shift f10 to bring up a command prompt. from there you can use notepad to view the logs, the main one you should be looking at is setupact.log there are more scattered around. in the inf folder theres one for 3rd party driver loading etc. if it is auto-restarting i would advise breaking down your autounnattended file into chunks and work through it bit by bit, until you find the suspect setting. hope this helps ^^

you could always try the bootmgr.efi on the windows 7 install cd? i dont know if you have to rename it. but i know that a lotta new tech now is heading to efi. so if you do get it working can you post your solution for the community? thanks

use the files from the source cd. much easier tbh, %cdrom%\boot (and all its subdirectories) %cdrom%\EFI (and all its subdirectories) %cdrom%\bootmgr make a folder called sources in that folder rename your wimfile to be boot.wim the wimfile must be a bootable wim file (like all pe images) the drive must be FAT32 though. otherwise it will not work. as for BCD part. there is a new tool with win7 called BCDBOOT. i run the following command BCDBOOT.EXE %other path for windows% /S C: dont klnow if that will help ya though but is a thought

i had the same issue when building my recovery sector. i basically made a HTA and an autoit script to launch it, then found a third party hex exe file tage editor to change the descriptions and version information.

remebered to integrate the relevant packages? scripting etc... also have you used sysWOW32 instead of system32?

i dont know if this will help or not, but i do know if your running a batch script and a mouse click is detected on the cmd window it will pause with no notification until a key is pressed.

as far as i know windows 2003 drivers will not automatically load onto vista (winpe 2.0). do you not have a vista version of the driver to slipstram into your image? ahh. also, you may runinto major system instabilities by loading a 2003 driver on vista. but on the odd occasion they do work.

what you will notice between my answer file and your own is that mine has no user data or vista key inputted. this means it will stop you on that screen and ask what version you wish to install or automatically select by the product key that you enter. other than that you have no option but to have an answer file & disk per install.

use my autounattend.xml to compare to your own. mine is very basic as i only need to to install the wim onto a system. this will only work for x86 versions of windows vista. <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DiskConfiguration> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Size>15000</Size> <Type>Primary</Type> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Extend>true</Extend> <Format>NTFS</Format> <Label>SYSTEM</Label> <Letter>C</Letter> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> </ModifyPartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> <WillShowUI>OnError</WillShowUI> </DiskConfiguration> <ImageInstall> <OSImage> <InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> </InstallTo> <WillShowUI>OnError</WillShowUI> <InstallToAvailablePartition>false</InstallToAvailablePartition> </OSImage> </ImageInstall> <UseConfigurationSet>true</UseConfigurationSet> <EnableFirewall>false</EnableFirewall> <EnableNetwork>true</EnableNetwork> <Display> <ColorDepth>32</ColorDepth> <HorizontalResolution>1024</HorizontalResolution> <RefreshRate>60</RefreshRate> <VerticalResolution>768</VerticalResolution> </Display> <UserData> <AcceptEula>true</AcceptEula> <FullName /> <Organization /> </UserData> </component> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>en-GB</UILanguage> </SetupUILanguage> <InputLocale>en-GB</InputLocale> <UILanguage>en-GB</UILanguage> <UILanguageFallback>en-US</UILanguageFallback> <UserLocale>en-GB</UserLocale> <SystemLocale>en-GB</SystemLocale> </component> </settings> <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OEMInformation> <Manufacturer>Novatech LTD</Manufacturer> <Model>Novatech PC</Model> <SupportHours>Monday To Friday 09:00 To 17:00</SupportHours> <HelpCustomized>false</HelpCustomized> <SupportPhone>0870 112 0812</SupportPhone> <SupportURL>http://www.novatech.co.uk/novatech/helpdesk.html</SupportURL> </OEMInformation> <BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled> <DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet> <DoNotCleanTaskBar>false</DoNotCleanTaskBar> <ShowWindowsLive>false</ShowWindowsLive> </component> </settings> <settings pass="auditSystem"> <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Reseal> <Mode>Audit</Mode> </Reseal> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OOBE> <HideEULAPage>true</HideEULAPage> <ProtectYourPC>3</ProtectYourPC> <SkipMachineOOBE>true</SkipMachineOOBE> <SkipUserOOBE>true</SkipUserOOBE> </OOBE> <AutoLogon> <Enabled>true</Enabled> <LogonCount>5</LogonCount> <Username>Administrator</Username> </AutoLogon> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/vistax86/sources/install.wim#Windows Vista ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>

just a breif piece of information regarding this. WinPE 2.0 AMD64 "as microsoft call it" will only run 64 bit applications. it has no cross compatibility. the HTA package for this also has an issue. it places HTA package in the system32 folder and will not work from here. you will have to manually move/copy the contents of the package into the syswow64 folder. hope some more people will exprerement with PE 64 soon ^^

i have seen this before but without auto-login. basically the user force shutdown thier pc whilst an update was applying to the OS. you could no longer get past the login screen, it would just be a black window. what i decided to do from here was to tell the computer to shutdown from the login screen and it decided to install the updates. let it finish and booted up the machine worked fine. hope this information helps

retract, read incorrectly

from what i know about flash drives it appears you have it running in HDD or FDD emulation mode. So if the first boot device in the BIOS is your UFD then it will be booted everytime no matter what. the only way to get round this is to change the boot order in your bios or to install a boot manager on the UFD that selects IDE/SATA0 as boot after timeout as mentioned by OS2FAN2.

only way i can see of doing it is to reverse your partition order. so disk 0 = C: & D: and disk 1 = E: windows will address disk 0 before any other partition unless one is called C: so by moving the E: partition to disk 1 it should stop re adressing it. but i see there will still likely be a problem with the disk addressing on the other OS. so what i would do is [Disk 0] [Partition 1] [C:] Windows install 1 [Partition 2] [D:] Windows install 2 [Disk 1] [Partition 1] [E:] documents & settings this should keep E as E and not reassign it. however when you switch to the other install i belive C: will become D: and D: will become C:

looks to me that he didn't generalize the image, thats the usual cause of what he's getting.

it should work, from your hardware configuration you shouldn't be having these problems unless: 1> faulty piece of hardware 2> integrated drivers in the install i would run some tools on your system to see if your memory is acting up. p.s. wrong forum subsection :-p