[jaclaz]

Sure , the Setupfailover.cmd is the script normally used to add the WINRE partition option to the BCD, this is why I posted these:
http://www.svrops.co.../winvistare.htm
http://blogs.msdn.co...-hard-disk.aspx

if you read them you should be able to understand the usage of the script and/or (if needed) modify it to suit your needs.

jaclaz

[Schiiwa]

jaclaz, on 25 December 2010 - 11:48 AM, said:

Sure , the Setupfailover.cmd is the script normally used to add the WINRE partition option to the BCD, this is why I posted these:
http://www.svrops.co.../winvistare.htm
http://blogs.msdn.co...-hard-disk.aspx

if you read them you should be able to understand the usage of the script and/or (if needed) modify it to suit your needs.

jaclaz

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

Attached File(s)

•  DISKPART.jpg (40.1K)
  Number of downloads: 12
•  BCDEDIT.jpg (43.71K)
  Number of downloads: 10
•  Partition.jpg (49.45K)
  Number of downloads: 13

[Schiiwa]

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!

This post has been edited by Schiiwa: 20 January 2011 - 07:08 PM

[Schiiwa]

Here:
http://technet.micro.../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.micro.../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...

This post has been edited by Schiiwa: 20 January 2011 - 06:38 PM

[jaclaz]

The "normal" way a hard disk with a recovery partition is set is the following:

• hidden partition with recovery settings/files
  
• visible partition with OS and all programs running

(the order in which they are is not important)

In normal operation:
BIOS->MBR->PBR of active partition->Normal OS booting

In Recovery operation:
BIOS->MBR->HotKey pressed->Recovery partition is unhidden and set Active->PBR of active partition (which is now the recovery partition)->Recovery OS booting

What happens with the "new" approach should be something like:

In normal operation:
BIOS->MBR->PBR of active partition->BOOTMGR->BCD->Normal OS booting

In Recovery operation:
BIOS->MBR->BOOTMGR->BCD->HotKey pressed->Recovery OS booting (WINRE) ->get data from factory.wim->restore OS

Compare also with this (Dell specific - but actually "general"):
http://www.goodells....starecovery.htm

From what I can see there, the partition holding the Factory wim is not hidden on Dell's.

It is possible that your particular PC has a "mixed mode", where the Recovery partition where the Factory.wim is, is hidden and unhidden when booting the WinRE.

If you follow the setupfailover.cmd, you will find:

    REM
    REM Hide partition
    REM

    if not {%NOHIDE%}=={} (
        goto :EOF
    )

    set TEMP_FILENAME=%SCRIPTNAME%_Temp_DiskPart.txt

    echo sel disk %DISK% > %TEMP_FILENAME%
    echo sel partition %PARTITION% >> %TEMP_FILENAME%

    REM
    REM Remove the drive letter for the partition before hiding it. 
    REM The system will not allow us to remove the drive letter after hiding it.
 

In other words, when the original setupfailover.cmd is run, the hidden partition is unhidden and has a drive letter assigned to it (which should be the parameter you were asking about) then the batch itself removes the drive letter and hides the partition.

Hope that now it is more clear...

jaclaz

[Tripredacus]

Oooo be careful there. There are two things that the CMD uses to find the recovery partition and it may be compiled. I see from the post that there is a custom RE application so without knowing what is in there and what it does that may become broken. The recovery partition is detected by looking for the prescense of a certain file and also by the volume GUID. The reason it looks confusing is because the CMD is supposed to be run BEFORE the recovery partition is hidden (such as in deployment or when booted into WinRE). So in those cases, it has no problem finding the recovery or boot partition because it has a drive letter at that point.

There should be two CMD files, both similarly named. One is in the boot partition and one in the recovery partition.

Personally I like Win7 WinRE better. Vista's is just annoying.

[Schiiwa]

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.)

jaclaz, on 21 January 2011 - 04:26 AM, said:

• 
  In normal operation:
  BIOS->MBR->PBR of active partition->Normal OS booting
  
  In Recovery operation:
  BIOS->MBR->HotKey pressed->Recovery partition is unhidden and set Active->PBR of active partition (which is now the recovery partition)->Recovery OS booting
  
  
• 
  What happens with the "new" approach should be something like:
  
  In normal operation:
  BIOS->MBR->PBR of active partition->BOOTMGR->BCD->Normal OS booting
  
  In Recovery operation:
  BIOS->MBR->BOOTMGR->BCD->HotKey pressed->Recovery OS booting (WINRE) ->get data from factory.wim->restore OS

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

jaclaz, on 21 January 2011 - 04:26 AM, said:

It is possible that your particular PC has a "mixed mode", where the Recovery partition where the Factory.wim is, is hidden and unhidden when booting the WinRE.

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:

jaclaz, on 21 January 2011 - 04:26 AM, said:

In other words, when the original setupfailover.cmd is run, the hidden partition is unhidden and has a drive letter assigned to it (which should be the parameter you were asking about) then the batch itself removes the drive letter and hides the partition.

Hope that now it is more clear...

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

Attached File(s)

•  Recovery.jpg (53.77K)
  Number of downloads: 22
•  Restore.jpg (88.59K)
  Number of downloads: 16
•  Bcdedit.txt (3.07K)
  Number of downloads: 10

This post has been edited by Schiiwa: 27 January 2011 - 01:38 PM

[Schiiwa]

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!

This post has been edited by Schiiwa: 30 January 2011 - 05:47 PM

[Tripredacus]

BIOS->MBR->BOOTMGR->BCD->HotKey pressed->Recovery OS booting (WINRE) ->get data from factory.wim->restore OS

BIOS (motherboard) looks for drives with a MBR so it knows what it can boot.
MBR is the section on the drive that says "this is bootable" or "this is not bootable"
If it is bootable (In Vista's case), The answer is, find BOOTMGR on the active partition.
BOOTMGR looks at BCD to determine where Windows is located
Windows is loaded.

However, if you choose to run recovery, BOOTMGR changes the BCD, to de-activate the OS volume and active the recovery volume. Then BCD says boot to the active partition, which would then have WinRE. This is because the F8 menu is not part of the OS, it is a bootloader itself. I may have that backwards but the idea is the same.

The reason why you are seeing strange files is that Microsoft did not give OEMs a turnkey solution to make recovery partition in Vista. All OEMs HAD to make their own method (rather in Win7 OEM can use turnkey solution or do whatever they want) so there are subtle differences between Vista recovery partitions between different brands of computers. Also, it is possible that your notebook supports an EFI style boot environment.

Also, your answer to #5 is technically incorrect, but I cannot reveal as to where that last option really comes from.

[Schiiwa]

I´ll come back to you later.... Have to try some things!

Project Shiva! Long live Windows 98!!!!

This post has been edited by Schiiwa: 19 February 2011 - 09:12 PM

[jaclaz]

If I were you I would (provided that you have FULLY imaged that drive and have thus a "way back"):

• unhide the now hidden partition (so that it gets a drive letter)
  
• verify that it is first partition of first hard disk
  
• verify that i tit there are the \sources\boot.wim and boot.sdi files
  
• run the SetAutoFailover.cmd ]with command (provided that the unhidden partition is D:\ ):
  

  SetAutoFailover.cmd /target D: /wim /nohide
  

  
  as seen in the given link:
  http://blogs.msdn.co...-hard-disk.aspx

jaclaz

[Schiiwa]

[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

This post has been edited by Schiiwa: 22 February 2011 - 07:40 PM

[Schiiwa]

Tripredacus, on 27 January 2011 - 04:31 PM, said:

BIOS->MBR->BOOTMGR->BCD->HotKey pressed->Recovery OS booting (WINRE) ->get data from factory.wim->restore OS

BIOS (motherboard) looks for drives with a MBR so it knows what it can boot.
MBR is the section on the drive that says "this is bootable" or "this is not bootable"
If it is bootable (In Vista's case), The answer is, find BOOTMGR on the active partition.
BOOTMGR looks at BCD to determine where Windows is located
Windows is loaded.

However, if you choose to run recovery, BOOTMGR changes the BCD, to de-activate the OS volume and active the recovery volume. Then BCD says boot to the active partition, which would then have WinRE. This is because the F8 menu is not part of the OS, it is a bootloader itself. I may have that backwards but the idea is the same.

So far so good...

Tripredacus, on 27 January 2011 - 04:31 PM, said:

The reason why you are seeing strange files is that Microsoft did not give OEMs a turnkey solution to make recovery partition in Vista. All OEMs HAD to make their own method (rather in Win7 OEM can use turnkey solution or do whatever they want) so there are subtle differences between Vista recovery partitions between different brands of computers. Also, it is possible that your notebook supports an EFI style boot environment.

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

[jaclaz]

Schiiwa, on 30 January 2011 - 07:41 PM, said:

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

Naah.
No conspiracy,
They are NOT after you, rest assured.
Most probably MS simply "convinced" OEM's that they could give the same kind of money they used to give to the Symantec (Ghost) or PCAngel guys to them instead, having a "native" recovery solution.

Most probably the batch is written to be run from the booted system and not from the PE on the Vista DVD.

You in the happy bunny basket now?

That's good.

jaclaz

[Tripredacus]

Good you got it to work. I think I see what that winpeshl.ini was doing. Not really sure what that custom app is, but it still executes the WinRE program (recenv.exe) which displays those 6 options. It will default to 5 options (as you know) but there is another file (that's not winpeshl.ini) that tells recenc.exe what to display as the 6th option.

[Schiiwa]

Quote

Most probably the batch is written to be run from the booted system and not from the PE on the Vista DVD.

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

[jaclaz]

Schiiwa, on 31 January 2011 - 01:39 PM, said:

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.

I don't really want to prove you wrong , when dealing with the good MS guys there is always something that is simply inexplicable.

Have you ever read the actual ImageX/wim related dll's license (yes, the one everyone has broken, one time or the other)
http://www.911cd.net...ic=19355&st=132
and my carpenter's comparison?
http://www.911cd.net...ic=19355&st=134

Schiiwa, on 31 January 2011 - 01:39 PM, said:

The Happy-Bunny-Basket feels good

I'll need to upgrade to a bigger basket.

[Tripredacus]

jaclaz, on 01 February 2011 - 08:12 AM, said:

and my carpenter's comparison?
http://www.911cd.net...ic=19355&st=134

Were these rules updated since Vista? I am pretty sure that the Windows System Backup tool (that works in conjunction with WinRE) uses Imagex to create system backups in Windows 7.

[jaclaz]

Tripredacus, on 01 February 2011 - 08:41 AM, said:

Were these rules updated since Vista? I am pretty sure that the Windows System Backup tool (that works in conjunction with WinRE) uses Imagex to create system backups in Windows 7.

Easy Instructions:

• get the WAIK
  
• open the downloaded .iso with 7-zip
  
• find in root file WAIK_License.rtf
  
• open it in Wordpad
  
• read it

Easier , download the attached, coming from the KB3AIK_EN.iso I have.

Cannot say if it has changed in the currently downloadable version:
http://www.microsoft...&displaylang=en

If you want to check without downloading the whole .iso, see here:
http://reboot.pro/13049/

jaclaz

Attached File(s)

•  WAIK_License.zip (3.17K)
  Number of downloads: 6

This post has been edited by jaclaz: 01 February 2011 - 09:48 AM

[submix8c]

Thx, jaclaz... haven't visited Reboot lately.

(post to keep me "hooked into" the above link - nice tool!)