Schiiwa

YES.... Meanwhile thinking and speaking in codes UPS... used " ´ " again instead of " ' "! I´ve used that key for apostrophe for years, because i do not have to use SHIFT then, Coffeefind @Kelsenellenelvian: Good to know... but i expected that except i would have been unsure for 2000

U didn't understand what i try to say. I related to the previous post #14 That was in my mind: Make a Winpeshl.ini: [LaunchApps] %SYSTEMDRIVE%\Windows\system32\startnet.cmd And a startnet.cmd REM wpeinit %SYSTEMDRIVE%\Programs\bginfo.exe %SYSTEMDRIVE%\Programs\bginfo.bgi /timer:0 /accepteula %SYSTEMDRIVE%\Programs\nu2menu\nu2menu.exe X:\sources\recovery\recenv.exe BUT: As expected the cmd-windows stays behind the shell until reboot, or if it will be closed, reboot is the consequence I will try to run my Commands from [LaunchApps] now to avoid the CMD in background rundll32 setupapi,InstallHinfSection DefaultInstall 132 %SystemDrive%\windows\system32\drivers\wimfltr.inf Net start wimfltr According to phgddr's post #13, it should look like this: %SYSTEMDRIVE%\Windows\System32\rundll32.exe, "setupapi,InstallHinfSection DefaultInstall 132 %SYSTEMDRIVE%\windows\system32\drivers\wimfltr.inf" %SYSTEMDRIVE%\Windows\System32\net.exe, "start wimfltr" %SYSTEMDRIVE%\sources\recovery\recenv.exe works great..... big thanks to phgddr

XP as I said and it worked FOR 7 also, but do not know if it works for 7Home-Edition and I did´n try @ Vista @ all but it is treated yourself to have a try

Hi Salim @Kali: I think he wants to do buissness in this sector: Tools for Data-Recovery: A very nice, freeware tool is TestDisk! A very nice, expensive tool is WinHEX.... WinHEX as dits name implies is just for Windows-OS.... works well under XP and later for me But just useable if you can access at least the HDD in the BIOS and available under diskpart/diskmgmt.msc To repair a harddisk physically, you need a dust-free space! For example, if the head´ve had a crash, you can put in the head-unit from another (but same mode) into the HDD. After that, it is possible that you can read data again, but hurry up with doing a image, as it probbably/most likely NOT on a continuing basis. But this is like a ambulatory surgery @ the heart or brain of a living being It is possible that if the head-unit will be destroyed again through the graves (which came up with the crash) or loose particles again very soon, so make a image immediately after such a "surgery" Much more easier/promising to exchange the logical board... should be same model & firmware (and if you have the choice, as near to the manufacturing date to the broken HDD) Cheers

For all the other members and visitors with user-related problems: "control userpasswords2" did always a great job in USER related problems. You can even change the the user-account in Windows XP Home although MS documents, that it´s not possible here: http://support.microsoft.com/kb/283111/en-us

Grützi!

Why not include the 2nd and 3rd in STARTNET.CMD to avoid the unlovely comma & quotes?

Thats right. You can see the GUID with /L parameter. powercfg /L But you can import a configuration to a specified GUID, if i remember. POWERCFG -EXPORT <Filename> <oldGUID> POWERCFG -IMPORT <Filename> <newGUID> I used that when I did my WinRE and did the import before capturing the Image @ OOBE by pressing Shift+F10 EDIT: I know, this is no reg, but may help anyway You could also add the following command to RUNONCE if you are able to put the POW-Files somewhere (here in C:\Windows\POWER for example): POWERCFG /IMPORT C.\Windows\Power\Balanced.pow SCHEME_BALANCED POWERCFG /IMPORT C:\Windows\Power\Minimal.pow SCHEME_MIN POWERCFG /IMPORT C:\Windows\Power\Maximal.pow SCHEME_MAX Because u can use these aliases instead of the GUID

Give me a larger storage and i will post it EDIT: Problem: Just can compile either Win32 or x64 ... do not know how to include both in one file! Itanium won´t work also: Compiling for unsupported platform. Only x86 and x64 platforms are supported by MFC. I thought Itanium is for Intel-CPUs, that is IA64 (for example i3/i5/i7) ... but maybe the x64 work for these cpus also It work without these 2 DLL as i now changed the setting in MFC from "Use MFC in common shared DLL" in "Use MFC in static libary". This will enlarge the EXE from 12kb to 2mb I could zip it to about 700 kb, but my web-space here is only about 500kb free HTA will follow when completed

Not all tests finished yet one Problem left: I did this one: C:\Windows\System32\Reagentc.exe /setosimage /path Z:\ /target C:\Windows My costum-tool is displayed without specified the /costumtool-parameter. I´ve just specified my costum exe in WinREConfig.xml. That´s OK, but how can I remove the option at the bottom now (Reinstall Windows) ??? when I do: reagentc /info Setup activated = 1 how can i reset it to 0 I´ve just ran: C:\Windows\System32\Reagentc.exe /setosimage /customtool /target C:\Windows But still Setup activated = 1 .... I'll reboot now and see the effects SOLVED: The command directly above will hide the "Reinstall Windows" option, even though "Setup activated = 1" will leave Wonderful... all works fine (UNTIL NOW.... not ran the HTA till now... have to edit some things first). I´ll also add the BOOTKEY for /SETREIMAGE to F11, because the other PCs where my brother lives have the Acronis Boot loader installed, which can be activated with F11 Would be interesting, if F8 would be available anyway!? Maybe I will reinstall windows again, to create the ID=27 Recovery-Partition. But I think I will keep that back for my own PC/Notebook and simply deactivate the access through windows with: ATTRIBUTE VOLUME SET NODEFAULTDRIVELETTER=1 Maybe also HIDDEN=1 and READONLY=1, but don´t know if it is possible to boot to win-re then.... we´ll see Cy@ soon in a HTA-Threat

HERE AGAIN FOR THE GRAND MASTER JAYCLAZ: Because of the Problem Don´t be rude my friend. I didn´t write in here EXACTLY the 2 files, because you will be informed through the executeable..... But If you want details...here we go! First it said: mfc100u.dll not found and after placing it from C:\Windows\System32 into the RE-image:\Windows\System32 (as we all here know, which has normally the letter "X" assigned), the next message was: msvcr100.dll not found Then same procedure.... and ta-da.... The HTA was Popping up. And I didn´t write these details, because I am sure it hurts some copyrights because nearly everything is illegal. If MS haven´t changed the EULA of IMAGEX, i am not allowed to do a Image of my OS-Partition, right Jayclaz?? Maybe (but do not know) these files went to C:\Windows\System32 through the installation of Visual C++ (on my brothers Computer). But Maybe they are some standard WIN-Files BTW... here´s the source-code #include "stdafx.h" #include "windows.h" int _tmain(int argc, _TCHAR* argv[]) { ShellExecute(NULL,_T("open"),_T("x:\\Windows\\System32\\Mshta.exe"),_T("x:\\sources\\recovery\\tools\\RestoreImage.hta"),NULL,SW_SHOW); return 0; } And I saw the possibilities of Visual C++ the first time and was really flashed. So in my opinion, if someone buys and gets along with this programm, they already know the option to change the platform! It´s just because i have no idea of programming in C++ Additional Information: :w00t: :w00t: :w00t: You can change the platform in Visual C++ by opening the properties of your projekt and search for KONFIGURATION MANAGER!!!!!!!!!!!!!!!!!! Win32, X64 and Itanium will be available. As this box here holds an AMD, i chose x64

Work´s well now. you can see here: Thx for assisstance tripredacus. I guess you´re bussy at the moment B)

I already made it. After a little bit of googeling and taking over my brothers PC with remote-desktop i changed the platform to x64 and re-comiled. 2 Files were missing and after I implemented them into X:\Windows\System32 all works fine! Just have to edit the HTA-script for my needs I personally like a recovery-option because I have installed windows enough! I think more often than a normal user would in 10 lifes But this computer i am preparing is for my little brother (15 years) and I know what's gonna happen I will copy the nessessary partitions also to another disk, because i had some hdd-crashes also and this one isn´t new

The reason which i figured out is, that WOW64 isn´t available for WinPE x64

This was really a fast answer .... NOPE, HTA works well. I can call any hta with "MSHTA.EXE somehta.hta" The actual massage, when i try to run the executeable via CMD, this will return: The subsystem needed to support the image type is not present Das zum Unterstützen des Abbildtyps erforderliche Subsystem ist nicht vorhanden. Yeah... I can offer u 2 languages And what do u use EDIT The application works well under Windows but not under WinRE

I managed the MSHTA to work now and also have tryed to compile a exe With Visual C++ and Quick Batch File Compiler .... Description and Icon is fine, but it do not want to run. The problem: The subsystem needed to support the image type is not present I guess the reason is the architecture. WinRE is x64 and the created exe is a Win32 application ... but maybe i am wrong

I know I just found out while u where answering Strange... thought i've read "This post has been edited by CoffeeFiend" ...Now it has been edited by Yzöwl OK, i'll try Now my brother has compiled the EXE and it works fine, but just in the normal OS... When I boot to WinRE, it says something about a missing subsystem. I guess it is because of the wrong architecture. My WinRE is x64, but the Application created with Visual C++ is an Win32-Application The Recovery-Environment does well with the Icon and Description, but when i click on the option, a window pops up that there´s something wrong! When I open the CMD and try to run, it returns the error with the missing subsystem! ... Now got stuck ... No idea how to continue I Also tryed to compile the EXE with Quick Batch File Compiler Like robbo101 here: But with the same result (missing subsystem) ....

My brother is in a computer science apprenticeship.... he is able to compile for me Let´s see, if it will success BTW.: Why did you edit my post CoffeeFiend. And why are you a coffeefiend

Just wanted to add: EDIT: JUST FOUND: Visual C++ Express editions don't have a resource editor. That is one of its limitations. But i need a executeable with a valid description and icon to display my EXE in the recovery-options-menu when i boot to winre... And the only code i found was c++

This is the Vista´s code: #include"stdafx.h" #include"windows.h" int _tmain(int argc, _TCHAR* argv[]) { ShellExecute(NULL,_T("open"),_T("x:\\Windows\\System32\\Mshta.exe"),_T("x:\\sources\\recovery\\tools\\CostumRestore.hta"),NULL,SW_SHOW); return 0; } As i read from the TechNet... http://technet.microsoft.com/en-us/library/dd744576%28WS.10%29.aspx Windows 7 Recovery Environment extracts the ICON for the options-menu from the Executeable. Vista takes it from OEMFactoryRestore.hta. As I read in Creating_a_Windows_Vista_Hard_Disk_Recovery_Solution.pdf, the Icon and Description can be included I will try to build an EXE compatible for Windows 7 x64.... But i have no experiences with C++ . I just did an dos-programm with Turbo C++, but i just could accomplish with help. I am installing MS Visual C++ Express right now. Do not know, if the *.h files are available there... Let´s see Will update when i have tryed it <Edit /> 1. Problem: Can´t add a "Resource File" as discribed in Creating_a_Windows_Vista_Hard_Disk_Recovery_Solution.pdf Is that a limitation of Visual C++ Express?

Hey tripredacus I already added HTA and SCRIPTING with DISM /image:C:\WINRE\MOUNT /addpackage /packagepath:PATH-TO-PACKAGE worked well.... but when I boot to this image and run MY-HTA.HTA via CMD it don´t know with which programm the OS should open it (as windows does when the file-type is unknown) ... I could open with EDITOR, but i want to execute it ... maybe i have to open with MSHTA... I´ll try immediately I do not have the MSXML-Package... Which Packages are nessassary for HTA? Or do I have to completely rebuild a WINRE.WIM and add the MSXML via PEIMG before i /PREP the image? or can I download the MSXML-Package.CAB somewhere Greetings and thx so far.... EDIT: Maybe i´ll build a new WINRE.WIM, so i simply can add the nessassary packages with PEIMG.EXE, but can´t remember what´s needed. For Vista i think there where 3 Packackes required, but can´t can´t remember and do not know if 7 is the same way... SORRY, forgot to answer: OS: Windows 7 SP1 %PROCESSOR_ARCHITECTURE%=x64 AMD64

Imagex would be faster for sure, but Setup can install a captured WIM as well. That is how I use it. The answer file is likely optional, but even if you have captured an image after using sysprep /unattend switch, Setup ignores that answer file. For example, even if your XML only specified the Locale settings (to hide the language select page of OOBE), after Setup applies the image, you'd still see that page. So if you didn't have any special settings, you don't even need to specify a custom tool or have the answer file. Just overwrite the install.wim with your custom WIM, but it still needs to be called install.wim. The only reason I needed to come up with this was because I needed the image in the recovery partition to deploy and then boot to the desktop. If the image is supposed to boot to OOBE, I don't use the custom tool option. My experience is another one... I installed Windows 7 without a special ID=27 partition, because i had no time and computer at the moment, to do this job (create a RE-Partition/Image). I should allign my files and folders first, in order to be effective. but as i saw the new command (reagentc.exe), i thought it might be very easy... So after the Installation was complete, i slashed SP1, all later updates and drivers on it. Then i realized, that the WINRE.WIM is already implemented on C:\RECOVERY\d89.......\WINRE.WIM ... so i moved it onto a new partition at the end and adapted the BCD. Also the WIM captured from my ready-installed Windows. And i was really happy when i saw the new Option when i booted to WINRE at the bottom "Windows neu Installieren/Reinstall Windows" ... but when i klicked on it, there came a window up where i should select the OS i want to install (I think the editions) Unfortunately it was empty except "No Images available" my WIM was already called INSTALL.WIM and in the ROOT... Maybe I´ll try again in \SOURCES folder EDIT: TRYED and DOND WORK! DOESN´T REALLY MAKE SENSE, BECAUSE THE /SETOSIMAGE-PARAMETER´S PATH WAS SET TO F:\ .... BUT AS U KNOW, WITH MS-SOFT U NEVER KNOW So i tryed putting the INSTALL.WIM from the DVD to F:\ ... that worked and moved my stuff on "C" into "WINDOWS.OLD" in the first seconds and started copying the setupfiles immediately! But i cut off the power and moved my stuff back after taking ownership, cause i do not want to reinstall....again.... because i think i installed Windows (esspecially 95a/b/c/98/98SE) about 1K-times So it didn´t work. Maybe when I capture it before OOBE after entering AUDIT (or without), it may work!? *not again..* Can U tell my, how i can start a HTA The HTA-Package isn´t available at the WinRE-Image yet..... i´ll add it now and come back later *hope i can still add it. Think to remember a DISM-Option to finish the WIM and then no package can be added anymore, when i created the Vista-PE EDIT: NOPE, it was the /prep command with peimg.exe Maybe thats the way, aha, aha, i like it d-_-b <Recovery> <RecoveryTools> <RelativeFilePath>MSHTA.EXE name-of-hta.hta</RelativeFilePath> </RecoveryTools> </Recovery> OR <Recovery> <RecoveryTools> <RelativeFilePath>MSHTA.EXE</RelativeFilePath> <CommandLineParam>(/)name-of-hta.hta</CommandLineParam> </RecoveryTools> </Recovery> EDIT: BOTH WON´T work ... Did´t expect that to work, because the ICON for the Recovery Options will be extracted for the executeable. After all, MSHTA.EXE has no ICON Cheers, Schiiwa

Hi Jayclaz, Tripredacus and Friends I´m now bussy with my Windows-7 RE-Partition, because i had a look at this page: http://technet.microsoft.com/en-us/library/dd744280%28WS.10%29.aspx I saw this line and thought, toooo easy: C:\Windows\System32\Reagentc.exe /setosimage /path R:\ /target C:\Windows It worked well, but just for a new Installation with an INSTALL.WIM from the Install-disc I already copied the C:\Recovery directory to the partition (HarddiskVolume4) And the BCD is modified well, too. So i have to use a costum tool with this line: C:\Windows\System32\Reagentc.exe /setosimage /customtool /target C:\Windows Here it says: http://technet.microsoft.com/en-us/library/dd744576%28WS.10%29.aspx <Recovery> <FactoryRecoveryTool> <RelativeFilePath>path_to_exe</RelativeFilePath> <CommandLineParam>parameter_1 parameter_2</CommandLineParam> <AdminOnly>access_level</AdminOnly> </FactoryRecoveryTool> </Recovery> P.S.: But as I read Gremo´s solution with the Auto-Unattended: <Recovery> <RecoveryTools> <RelativeFilePath>..\..\Setup.exe /unattend:X:\unattend.xml</RelativeFilePath> </RecoveryTools> </Recovery> I ASKED MYSELF, IF THIS MAYBE WOULD BE POSSIBLE: <Recovery> <RecoveryTools> <RelativeFilePath>IMAGEX.exe /apply F:\System.wim 1 C:\ </RelativeFilePath> </RecoveryTools> </Recovery> OR <Recovery> <RecoveryTools> <RelativeFilePath>IMAGEX.exe</RelativeFilePath> <CommandLineParam>/apply F:\System.wim 1 C:\</CommandLineParam> </RecoveryTools> </Recovery> I know, this solution is not the best , because if the Windows-Partition isn´t present any more, it would be applyed on another C-Drive Maybe I´ll try today, but would appreciate a more bonnie solution P.P.S: I had a look at this: But there are 3 problems: 1. What is inside Clean_part.txt Maybe: SELECT DISK 0 SELECT PARTITION 2 DELETE PARTITION CREATE PARTITION PRIMARY FORMAT FS=NTFS OVERRIDE 2. What is ISA.EXE; Can it replaced with IMAGEX.EXE ? 3. What costum-tool-exec is used? Can i call it with MSHTA.EXE? P.P.P.S.: Still not my own PC Cheers.... Schiiwa EDIT: Another example here: http://reboot.pro/8729/ But user says, doesn´t work. And whats not clear for me, what executeable "tblo" uses in WinREConfig.xml

Very useful for WinPE ... Thank u for this nice hint ^^