Schiiwa

For sure, there are other ways, too. But FSC choose the integration with SLP1.vbs ... And lotz of other CMDs and REGs ... It´s really a transparent install-routine.... unfortunately with some bugs. I already mentioned the thing, when you cancel the recovery hta-script, there is a massage: System reset to default succesfully I´m not that fimilar to VBS, though i will leave the bug in there (and as it is not my Notebook ) I could attach it, if you would like to have a look at it (also the DVD-Burning is still not working ) But it is really a huuuuuuge vbs, so be warned I tryed to modify the BCD of the WinRE partition, but still it is US-Standard: bcdedit -store bcd -set {bootmgr} locale de-DE bcdedit -store bcd -set {default} locale de-DE Yeah... I know... i would have to compile a oem????.exe... do not remember the whole name, but i got a compiled one somewhere in this forum ^^ ... But if i build my own one, it will be a Win7-one.... You can win a washing-machine if you answer these questions: 1. Is it the reason, that the WINRE-Part. is the first one, so that it can still accessed if I would quickformat C: because it is located in front of it? 2. How many spare-sectors do HDD-manufactures include regulary? Have a nice day... Schiiwa

Same Problem :/ When I run it from C:\Windows\System32 it works fine.... But after copying it to X:\Windows\System32 and try to run it from there or any other Directory I get the same error: "Failed to create empty document" No solution yet! But maybe you´ve solved it since 2004 ^^ If so, let me know

I find it disheartening that Fujitsu would leave these files in their image... whatever happens, these files are non-redistributable, so you cannot share them or even post their code. Just an FYI. They leave it on the Image, because the script will be executed after recovery, so it has to be there. Did I post a code? I don´t think so. I use this file just for this notebook.... no worries please : An standard end-user won´t look into a image-file on an hidden partition... Thats the point... It was really funny to get through the whole costumized installation-prozess with lots of CMDs, VBSs, EXEs, UNATTEND.XML, OOBE.XML and so on. But finally with success But now the Recovery-Partition is nearly up-to-date. One thing, which I don´t like is the standard-keyboard-layout in the drop down. When I boot into it, it shows always US, but i want DE. There is no Lang.ini. I think, the BOOT.WIM´s metadata is responsable for that: imagex /info boot.wim --> <defaultlanguage>en-US ... i couldn´t figure out if there is a way to edit this one... i already tryed Intlcfg.exe /image:Bla:\BLA.wim /defaultlang:de-de --> no Lang.ini I think i have to use another boot.wim for last cosmetically modification. Or any better ideas?

The script SLP1.VBS and the Digital License-File (XrML) worked well! Cheers!

Thank ya ... I will rearm and try some other things first. I found a vbs-script (SLP1.vbs) and another interesting XML (SLP20Input.xml) in the orginal Factory.wim ... Will have a look at it first. Maybe the VBS can simply be executed ... Also I will try the REG-Key mentioned in my last post. Edit: Didn´t Work as expected!

The problem i have is, that i do not think it will grab the unatted.xml from now. I would have to reinstall it with all the entries in this XML-File. For registration this is the setting: <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" > <ProductKey>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</ProductKey> The Installation is already done (not unattended). I do not want to reinstall it. It is installed and configured through AUDIT-mode (pressed CTRL+SHIFT+F3) ... (This deleted the Information about the Key entered at the beginning of the installation, although i did not mark the GENERALIZE option) Will an unattend.xml on UFD will be picked up NOW, if i put these lines shown above in it.... I don´t think so.... Thats why i thought about OOBE.XML.... maybe there is a way!? Or any other... Maybe "sysprep /unattend:key.xml", with these 3 lines in it???? http://technet.microsoft.com/en-us/library/cc765993%28WS.10%29.aspx Here in the Grafik specialize is before Audit, so it will be deleted as well. But just realized a nice reg-path ... Maybe this could solve my problem ^^: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SL

It was not a wrong key.... CTRL + SHIFT + F3 resets the activation as u said, tripredacus. For me the problem isn´t the activation @ all. But I just do NOT want to get prompted for the key. Can i put it in a file where windows will have a look @ or before oobe. If i do not enter audit-mode, i do not get the popup: "Enter your License key". But then, for me, the system isn´t PREPaired. now just remaining the problem with the java- and visual basic-scripts, which must have a little mistake (i think there is a line missing or something like that).... the error-output is: 'document.getElementById(_)' is zero or no object! Line 139 Bye.... Shiva

Storage: You missunderstood. I don´t want to use it as a storage or up large files. For this, there are 1000s of filehoster available like sendspace and all the others. But i wondered, why I can´t attach any screenshot anymore (the one with the script-error when trying to recover from DVD) I also wanted to attach the scripts. i think i have to remove the legacy screenshots. The problem is, that i often related my text to those pics. I realized that MSFN is not meant to upload any screenshots afterwards, because there is just 1 MB. This is a little bit confusing, because there was a popup of max-file-size of 64 mb! 1MB ... makes me feel like in 90s. Grafic-cards with 1 MB were premium Activation: There are 2 Keys. One on the sicker at the bottom, and the other one i extracted from the preinstalled OEM-version (Because I know such MS-related problems). Maybe i took the OEM-Key which is not compatible to the untouched, standard DVD. I´m not sure, which key i took for the last installation. I will reinstall Vista now... And find out. But for sure, the last time! i will take a raw-image before booting to oobe Try if the key is asked about again (the one on the sticker) If no, i will enter audit mode then try again, if key is wanted. If No --> Everthing is fine (just took the wrong key) if Yes --> Sysprep will reset the activation like u said and I will have to find out in which file to put the activation-information (the key) if it even is possible without an unattended.xml and all the stuff (XMLs) around there! or i won´t be able to prepair the system for the owner (which SYSPREPair should be able to).... and sue MS for the complete waste of time I am such glad that i backed up the \windows\softwaredistribution\download - Folder before deleting it! Hope u will help me with the script-problem later ^^ P.S.: An installation of windows always end up in a reinstallation-party!

I thinks it depends on the actual drive and if there is a "translation mode" in it's firmware set to "on" (via jumper or through OS driver ) , but I don't really have any detailed experience with these new 4 kb sector drives. jaclaz Never Mind.... I ´ll find out some day 1. Is there any way to get a larger upload-storage... or do i have to remove all the pictures? Here is another Problem, which is really annoying to me.. I´m pretty sure that this is a LOL-Problem for Tripredacus mentioned in his signature ^^: I installed Vista SP2 on this Notebook without unattended-answer-files or any other XML (no experiences since Vista, as i dont own a PC/Notebook at the moment, which is runnable for Vista (sometimes i ask myself why I always have to handle with this old crap or any other celeron-low-cached systems) at OOBE i went to AUDIT-MODE I pre-configured the system AND ACTIVATED IT! But when i boot to OOBE again, i have to activate again, which i am not able to accept 2. Is there a way to ACTIVATE vista before running OOBE, not nessecery to activate at OOBE again? If I have to use a unattended.xml, syspref.xml or anything like that, can I just put the information for the activation in it? I´ve read something about \Windows\Panther, but do not want to do all the steps through Windows System Image Manager! I´ve been looking around but didn´t find a solution, just for the inverted problem: Windows_welcome_may_not_prompt_for_product_key.doc i guess, that should be OOBE In this article of TechNet: http://technet.microsoft.com/en-us/library/cc766514%28WS.10%29.aspx it says: But how... for me that doesn´t work. Always have to enter the VLK (without imaging or applying between AUDIT and OOBE) And there are only about 3 times remained. I read somewhere that i can only activate online 10 times Tripredacus, the HTML/VBS/JS-Problem has to wait. Is there a way to get a larger up-box? Or do i have to delete all these funny, little screenshots?

Won´t work @ Vista Another (i think the last one) question related to the 4kb-sector-thing I ran "fsutil fsinfo ntfsinfo C:" and the output with the new HDD is the same as the old one: Bytes per sector: 512 Is this because of cloning from an "old" drive or just normal. Does Windows emulate 512kb-sectors Cheers,

RegFromApp is also a nice tool to detect REGISTRY-Modifications of a Prozess and its really easy-to-use ^^

I hope it wouldn´t have been that easily in Vista also... http://www.sevenforums.com/installation-setup/141810-cannot-access-winre-environment-f8.html Will try and post back ^^

Hey Jayclaz... Thank you for your elaborate answers, even if i can´t follow everything I read in a german forum: - that the modern OS doesn´t take care of cyl.-b. because of LBA-Access - that Vista/7 ignores the cylinder-bounderies, because of the support of SSDs. The Offset is aligned to 1MiB (1024kb). But in fact, the partition-table-data is virtual... Because there are no 255 heads So if i want to start/end a partition at a cylinder-boundaries, i have to calculate where a real cylinder starts/ends! My new HDD supports Advanced Format (4KB Sectors). The old one is Nov/2006 --> 512byte-sectors It is to be feared, that the image won´t work as the Laptop is from 2006. But the hdd´s firmware will do it, i hope New WD-drives even have a jumper to make the drive compatible to XP !? Just read the first time ^^ ... Here´s the source: http://www.ibm.com/developerworks/linux/library/l-4kb-sector-disks/#benchmarks The effect is shifting the sectors by 1 I´ll try Advanced Format Software, which helps to align the partitions Maybe this is not the suitable thread, but i think, its ok, if anybody can´t access the "repair" option through a HDD-crash (the IDE-HDD of my own, ancient notebook becomes not initalizised any more, with XP without recoverypartition But had a hidden partition with a Image of the C-Drive on it... Kind regards.... chris P.S.: One of those questions that can be answered with yes/no/maybe/who knows. I think to remember I´ve read about a year ago that the firmware of the hdd is also involved in handling the geometry, too

Wasn´t sure, if the geometry is saved in mbr or not. Your answer says, that its not saved ^^ So its just the partition-table, which is included I will delete the DATA D: Partition and increase it to the maximum. As you can see on the image "2. Screen TestDisk" on post #15 on the 1st page, that the structure looks ok (this is still the old HDD), but you said, that the creator of the partition-set has taken bingo-numbers... Why did you say that? Is the start or end of an partition not set correctly. I read somewhere, that the end of an partition has to be at the end of a cluster, sector or zylinder boundary. Or because there is unlocated space between partition 2-3 and between 3-4 ? ^^ Cheers, Chris And another question is, where is the geometry saved. With testdisk for example, you can change the geometry, but where is it saved. Or will it determed through the OS?

Was able to rebuild the Recovery-DVDs. In the Recovery-Package on the Recovery-Partition, there is a visual basic script, which creates a 0-Byte-File! Its called $#Repair\DVD.TAG. Rename this file and the burn-option is available again. But it failed will fail: "823: Variable nicht definiert: 'txtInsertDiskInfo2' " ... Just add this line... var txtInsertDiskInfo2 = "Kennzeichnen Sie einen beschreibbaren CD/DVD-Datenträger mit"; in the file \sources\recovery\tools\recoverypackage\scripts\ger\language.js with your own output and it will work again. "ger" can be replaced with your language! Maybe renaming the "DVD.TAG" file is enough, if you choos another language as the first time, because the burning-script will also delete this line. So after burning it is missing again ^^ I ve added it bettween var txtInsertDiskInfo1 = ..... var txtInsertDiskInfo3 = ..... This is still with the orginal-factory-state of 2006 ^^ Already bought a new hdd due the sectors are clearing away. Can i copy the raw-image of a 120 gb on a larger drive? Will the system determ the right "unlocated space" in diskmgmt.msc? Would be nice to know, as the USB-Disk is really slow and takes a lot of time! I am really not sure, if i can use a updated FACTORY.WIM, as the recovery-dvd holds a file called FACTORY0.FPT, which is different to FACTORY.WIM (nearly the same size, but compared with "FC"). But should work, because it has to use Factory.wim as source because of the nearly similar size and fast progress. Letz have a try.... I think its ok to use imagex for that, because this Laptop was expensive at that time (Nov 2006) and there is a right to an updated system § 346 II 1 Nr. 3 GCR (Global Computer Rights)

Thanx for effort, but have Vista-WAIK already installed ^^ Nice concept... but why not simply copy the needed files on the http-server, or simply extract the iso... anyway, there is no compression in ISO-Format ^^ Maybe for mounting the ISO B) But i don´t care, because i will never use this parameter And Jayclaz.... here´s a present for you

Don´t think so, because if i would run it from my system, the parameter /mainos {current} is just needed, if you run it from the R.-E./P.E. as it is explained in the Setautofailover.cmd echo /mainos (guid of the main OS) [optional] echo Use the specified GUID for the main OS. By default the script echo assumes the current OS. Note -- always specify this option when echo running from WinPE. To configure the default OS in BCD specify echo {default}. But doesn´t matter to me. I know the BCDEDIT-Commands and thats enough to fix a similar problem! For me, that is no conspiracy, i call that reality. It is really hard to imagine, whats going on in background in this sick world... Especially everything around money... Believe me If you want to assure me of beeing wrong, you have to show me a link of any MS- or OEM-Site, where this parameter is specified [\Device\HarddiskVolume1] to fix the F8-Issue. The operative point is, that the transaction-volume in $ of the OEMs is a little bit higher that Ghost´s, Acronis´, etc. So Ghost, Acronis etc are not able to deal with MS But i don´t want to dis MS or the OEMs, it is normal to maximize profit The Happy-Bunny-Basket feels good

So far so good... I just wrote to Jayclaz, that i think, that there is a turnkey solution to make recovery partition in vista over "F8"! Meanwhile, i read much about the WinRE @ Vista. There is always told, that the WinRE-Partition has to be the first one. The reason is, that the "Letter" for the ID=27-Partition is [\Device\HarddiskVolume1]. I think, that u can also do it as 2nd partition, with [\Device\HarddiskVolume2]. But i nowhere found this information. I found out over the command: BCDEDIT /enum all There is a line: ramdisksdidecive Partition=\Device\HarddiskVolume1 So i tryed it, and it went fine I think that MS deny this information and gets money from the OEMs But thank you anyway. There where alot of useful information in your posts

[in the post from the 27. january i that, that i tryed it with X: ... that was not right, i tryed it with F:, but i edited it already] First of all, i made it! I tryed to do it with the Setautofailover! I booted with the Vista-DVD and tryed it in the Command Prompt of the Repair-options! the called Setautofailover.cmd returned a lot of ERRORS. (attached as screenshot SETWINRE.JPG) So i had to add 2 entries, which the script didn´t add! It was: BCDEDIT -set {default} recoveryenabled yes BCDEDIT -set {default} recoverysequence {572bcd56-ffa7-11d9-aae0-0007e994107d} Don´t ask me, why the script didn´t do that job I used a little canged syntax, because there was that file called setwinre.cmd and i thought, that FSC put it there to use it. But it didn´t seem, that it is there to use it again, as the Recovery-Partition has already the ID=27. By the way, the Partition isn´t hiddn! Just the fact, that it has the ID=27, Windows won´t assign a letter to it! I didn´t want to change anything @ the WinRE-Partition so far. But now, i want to cange the default language to "DE" (German) ... Maybe u can say, what to cange! The costum recovery-tool, i found in the BOOT.WIM in the directory \sources\recovery\tools\bin\ (i posted a screenshot of the directory in the past, dont know which post) But the solution is that easy! I used the letter F: because when i boot with the Vista-DVD, go to "REPAIR-OPTIONS" and go to Command-Prompt, F: was the WinRE partition! Instead of that, u have to use the variable [\Device\HarddiskVolume1], as this is the first Partition! (The ID27-Partition) Just use this commands, to restore the Partition [but u have to adapt the Guid for RAM-disk, the RED-one] BCDEDIT -set {default} recoveryenabled yes BCDEDIT -create {572bcd56-ffa7-11d9-aae0-0007e994107d} -d "Windows Recovery Environment" -application OSLOADER BCDEDIT -set {default} recoverysequence {572bcd56-ffa7-11d9-aae0-0007e994107d} BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} device ramdisk=[\Device\HarddiskVolume1]\sources\boot.wim,{ad6c7bc8-fa0f-11da-8ddf-0013200354d8} BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} path \windows\system32\boot\winload.exe BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} osdevice ramdisk=[\Device\HarddiskVolume1]\sources\boot.wim,{ad6c7bc8-fa0f-11da-8ddf-0013200354d8} BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} systemroot \windows BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} detecthal yes BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} nx optin BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} winpe yes BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} custom:46000010 yes Thats it :] to Tripredacus: The answer on Question#5 is correct!!! Winpeshl.ini is the File, which will be used to extract the Directory/File to use, if u choose the recovery option (the last one) In my case: AppPath=X:\sources\recovery\tools\recoverypackage\bin\FSCPEStart.exe <-- the FSC-recovery-tool But maybe, it is TECHNICALLY incorrect, as there is shown the pic (PRE.JPG) first, so its maybe a script, that is executed. The bitmap is in that location: \sources\recovery\tools\recoverypackage\scripts\bootlogo.bmp. In this Folder there are alot of VBS-Scripts. But it is be possible, that is also compiled in the FSCPEStart.exe And i like Windows 7 better as well, but my girl-friend has just a license for Vista! thats the problem ;] MY NEXT PROJECT: I WILL UPDATE FACTORY.WIM, as the supplyed one is not usable anymore, because SP1 cannot be installed :] Hope you 2 guys will follow it! I will start a new Thread, it will be called: Update the Recovery-Partition-WIM ... But first of all, i have to validate some things... Cy@ Later m8z EDIT: deleted the attachments

I´ll come back to you later.... Have to try some things! Project Shiva! Long live Windows 98!!!!

The Guid for the Ramdisk was already set ({ad6c7bc8-fa0f-11da-8ddf-0013200354d8}) Thats why i skipped these 3: %BCDEDIT% -create %RAMDISK_OPTIONS% -d "Ramdisk Device Options" -device %BCDEDIT% -set %RAMDISK_OPTIONS% ramdisksdidevice partition=%DRIVE% %BCDEDIT% -set %RAMDISK_OPTIONS% ramdisksdipath \boot\boot.sdi I did these commands always with a "successful" output :] BCDEDIT -set {default} recoveryenabled yes BCDEDIT -create {572bcd56-ffa7-11d9-aae0-0007e994107d} -d "Windows Recovery Environment" -application OSLOADER BCDEDIT -set {default} recoverysequence {572bcd56-ffa7-11d9-aae0-0007e994107d} BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} device ramdisk=[F:]\sources\boot.wim,{ad6c7bc8-fa0f-11da-8ddf-0013200354d8} BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} path \windows\system32\boot\winload.exe BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} osdevice ramdisk=[F:]\sources\boot.wim,{ad6c7bc8-fa0f-11da-8ddf-0013200354d8} BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} systemroot \windows BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} detecthal yes BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} nx optin BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} winpe yes BCDEDIT -set {572bcd56-ffa7-11d9-aae0-0007e994107d} custom:46000010 yes --------------------------------------- After that, the F8-Option was available again, but it returned an error, if i chose it: Status: 0xc000000f info: the boot selection failed because a required device is inaccessible. ENTER=continue If i push ENTER, it simply boots the installed system. Then i deleted the GUID {572bcd56-ffa7-11d9-aae0-0007e994107d} and tried to let the OS assign a guid with these: BCDEDIT -delete {572bcd56-ffa7-11d9-aae0-0007e994107d} BCDEDIT -create -d "Windows Recovery Environment" -application OSLOADER --> that returned the GUID: {43f982df-29d7-11e0-b393-00030d588b4f} BCDEDIT -set {default} recoverysequence {43f982df-29d7-11e0-b393-00030d588b4f} BCDEDIT -set {43f982df-29d7-11e0-b393-00030d588b4f} device ramdisk=[f:]\sources\boot.wim,{ad6c7bc8-fa0f-11da-8ddf-0013200354d8} BCDEDIT -set {43f982df-29d7-11e0-b393-00030d588b4f} path \windows\system32\boot\winload.exe BCDEDIT -set {43f982df-29d7-11e0-b393-00030d588b4f} osdevice ramdisk=[f:]\sources\boot.wim,{ad6c7bc8-fa0f-11da-8ddf-0013200354d8} BCDEDIT -set {43f982df-29d7-11e0-b393-00030d588b4f} systemroot \windows BCDEDIT -set {43f982df-29d7-11e0-b393-00030d588b4f} detecthal yes BCDEDIT -set {43f982df-29d7-11e0-b393-00030d588b4f} nx optin BCDEDIT -set {43f982df-29d7-11e0-b393-00030d588b4f} winpe yes BCDEDIT -set {43f982df-29d7-11e0-b393-00030d588b4f} custom:46000010 yes As i expected, same error again I will attach 2 txt-files. BEFORE.TXT (Before applying any command with BCDEDIT.EXE) returned with BCDEDIT /enum all >before.txt AFTER.TXT (After applying all these commands with BCDEDIT.EXE) returned with BCDEDIT /enum all >after.txt Attachment doesn´t work at the moment... it will follow! Help would be appreciated!

As you can see in Post #15 in my attachments, Testdisk found 2 hidden Partitions: 1 NTFS [WinRE] and 1 FAT32 [FSC_OTS] !? The NTFS is a OEM Partition with ID=27. The FAT32-Partition is just a service-partition and holds just 85 MB! It should have been deleted i guess, as you can see in the following lines In the ROOT there are these files (and more): SET_ENV.BAT FINDRAMD.BAT AUTOEXEC.BAT ... ::GDISK-LOESCHE OTS_PART echo. echo Loesche SERVICEPARTITION... echo. gdisk 1 /del /p:%OTS_PART% /y gdisk 1 /act /p:2 /y echo. ... This Partition should nothing have to do with the Recovery-Partition. I copied all files to my external HDD via TESTDISK and looked in the BATCH-Scripts.... Just do configure the System´s Hardware (CMOS/BIOS/FIRMWARES/etc.) I think, the green one is the way, the WinRE was accessed, because the Menu looked like Vista´s Boot-Menü with the Option "Repair Computer". 1st Question: Or is the BCD and BOOTMGR on the WinRE-partition an indication for booting it over the MBR with its own Boot Configuration Data? 2nd Question: If i mount the FACTORY.WIM, can i edit the \Boot\BCD, to see it´s content or even Export the entries to a file? Or do i have to APPLY the Image to C:, that i can export the BCD via BCDEDIT /EXPORT ANSWER: Yes: With the command BCDEDIT /store \boot\bcd /enum all 3rd Question: Can a WIM-File hold the original MBR? ANSWER: NO I don´t think so. Because i already ran the recovery-partition several times in the past, i think it will be accessed over the BCD. The WinRE partition with id27 is designed for this, if the partition is the first one, like on my HDD! All recovery-stuff is hidden. The FAT32-Partition i can only see via TESTDISK/BOOTDISK. Windows disk management Lists only 3 Partitions. 1 is OEM, 2 and 3 are C: and D: Yeah, i knew, that the script will take the letter away and hide the partition. But mine is already hidden, exept i will boot with the Vista-DVD to the CMD, then WinRE is F:\. That is the reason, why i would prefer a solution with BCDEDIT.EXE. But i don´t know the Syntax/variables/parameters/guids yet! (completely new @ vista/7) The problem is, that i don´t want to make any changes to the partitions for now. So i can restore factory wim in case of emegency and will have the factory-state again (i hope). Then extract the BCD and restore my current SYSTEM.WIM (with proud 110GB), import bcd, let Vista repair the start-up and everything is fine. I CAN ACCESS MY WINRE-PARTITION if i boot from the VISTA SP2-INSTALL-DISK and go to the REPAIR-OPTION - CMD. WinRE Partition [id=27]=F:\ could i run the setautofailover script there? SetAutoFailover.cmd /target F: /wim /nohide /partition 1 /mainos GUID .... 4th Question Where can i find this GUID of my OS? I will attach the BCDEDIT.TXT, created with: BCDEDIT /ENUM ALL >BCDEDIT.TXT IS IT THIS ONE: {2ebf8c8c-0e38-11e0-9fc4-e7505350ad8a} ? ANSWER: YES but {current} should work also I imaged my current system on C: with this syntax: imagex.exe /capture /boot /compress none /verify C: F:\Recovery\System.wim "SYSTEM" And i connected the 2,5" Sata-Drive to a PC and made a RAW-Image with WindowsPE (XP), because the Laptop always hung at the destroyed sectors. I have found an interesting Folder in the FACTORY.WIM! Look at the Restore.jpg in ATTACHMENTS. Such an EXE-File (like RESTORERECOVERY.EXE) could possibly restore my MBR, so restoring FACTORI.WIM maybe would help me to fix my problem via its installations-routine. Or it does the same like the Setautofailover-Script compiled in a EXE-File. I just know the responsible files of XP (Files like WINNT.SIF or CMDLINES), which contain additional or costum files added by the manufacter. But where to look in VISTA? Where could a file like RESTORERECOVERY.EXE could be executed in the Installation-routine? I already looked @ the $OEM$-Folder. That is important, to look for parameters. @ Tripredacus 5th Question: Look @ recovery.jpg! The Picture is the standard one, but the last option "Fujitsu Siemens Computers" which would be there, if i would had booted it. Where does the Environment take this information? (it is not the orginal-screenshot ) ANSWER: from the WINPESHL.INI i think! in mine, this is the content: [LaunchApp] rem AppPath=%comspec% AppPath=X:\sources\recovery\tools\recoverypackage\bin\FSCPEStart.exe [FSCRECOVERY] AppPath=X:\sources\recovery\recenv.exe Bcdedit.txt

Here: http://technet.microsoft.com/en-us/library/cc766450(WS.10).aspx I found out, that the EFI-Based Computers also have a FAT32 PArtition, so i guess, i have one, too because of the "FSC_OS" Fat32-Partition found by TESTDISK Here it says: http://technet.microsoft.com/en-us/library/cc753840(WS.10).aspx For GUID partition table (GPT) disks, specifies the new GUID value for the type field for the partition. Recognized GUIDs include: EFI system partition: c12a7328-f81f-11d2-ba4b-00a0c93ec93b Diskmanagment says, i have a EISA-Konfiguration I think i have to give up, tho i think it could easy be reimplement. I could try to give it another ID (at the Moment 27) and assign X: to it and run setautofailover.cmd /target X: /wim /nohide ... maybe it works Another Question is, if i APPLY the FACTORY.WIM to C:, if then my problems are gone?! Thank u Jayclaz for your support. I will regard this thread in future, maybe someone can help...

I mounted the Boot.wim, which i extracted from the WinRE-Partition via WinHEX The file "WINPESHL.INI" is in \windows\system32 and hold this context: [LaunchApp] rem AppPath=%comspec% AppPath=X:\sources\recovery\tools\recoverypackage\bin\FSCPEStart.exe [FSCRECOVERY] AppPath=X:\sources\recovery\recenv.exe Everything looks fine on the WinRE-Partition. There is also a BCD and BOOTMGR in the ROOT.... WHY? I thought the Boot Configuration Data is on C: The MBR is in factorystate or overridden while i installed Vista from a Untouched SP2 integrated DVD!

I need a little bit more help: From the SETAUTOFAILOVER.CMD: echo /target (drive where WinRE is installed) [required] echo The drive where WinRE is installed w/o the trailing backslash, echo e.g., C: echo. WHICH DRIVE? Where it has been installed? The recovery-destination? The recovery-source, which has no Drive-Name in my case!? My WinRE-Partition has no letter and is hidden, still in Factory-State. BTW, what is the FAT32 Partition good for? I could read out of the Script, that it want to remove the drive letter and to set it inactive! But the OEM-Partition is hidden and inactive yet (look attachment) Thats why i´m afraid of running the script. I would appreciate the solution with all the BCDEDIT-Commands with syntax :ange