TeraByte Unlimited

Hello i have IFW dos gui trial version installed on my win7 64-bit machine. IFW won't let me create a boot disk. i followed it stept by step:

http://www.terabyteunlimited.com/howto/ ... torial.htm

but when type in 1 and Enter (have trial version), then just the cmd window closes and nothing else happens. tried this several times now..


P.S. By the way is it save to restore an image from trialversion, or are problems to be expected?

Is booting into WinRE functional on the system?

You shouldn't need to press ENTER after pressing 1. Pressing ENTER could be clearing the following error message and exiting the script.

There should be an error message displayed if it runs into a problem. You could try running it directly from a Command Prompt window instead of from Explorer so the Command Prompt window stays open and you can see the output. To do this, open an Administrator Command Prompt (right-click on the Command Prompt shortcut and select "Run as administrator"), then change to the folder with the TBWinRE files (e.g. cd /d e:\tbwinre -or- cd /d "C:\Program Files (x86)\TeraByte Unlimited\Image for Windows\V2\tbwinre"), then run the script (tbwinre).

Except for the trial version limitations restoring is the same as the full version.

Hi,

just came to check it out. I did as you said and started an elevated Cmd and started script. The error message is in the attached picture. Since i installed in default location path is right, but to make sure that the files in the path are the right ones i attached you a picture of the content of the path.

What i should add: I know windows has sometimes 2 Partitions a 100MB for start and the "real" Partition. I just have one Partition (maybe because i installed an OEM Version).

What now?

P.S. "Except for the trial version limitations restoring is the same as the full version." What are the trial version limitations? Will i be able to restore an image of C (system) without problems?

Is the Windows language setting German (or the German version of Windows)?

Can you save the output from "bcdedit /enum all" to a file and then attach it to a post? You can do this from the Administrator Command Prompt. For example, to save the output to c:\bcdoutput.txt you would run: bcdedit /enum all > c:\bcdoutput.txt

Its both german version (OEM) and language is german

Since i couldn't attach .txt:

Windows-Start-Manager
---------------------
Bezeichner {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale de-DE
inherit {globalsettings}
default {current}
resumeobject {8febc16e-7266-11e1-ade8-8953572217f7}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows-Startladeprogramm
-------------------------
Bezeichner {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale de-DE
inherit {bootloadersettings}
recoverysequence {8febc170-7266-11e1-ade8-8953572217f7}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {8febc16e-7266-11e1-ade8-8953572217f7}
nx OptIn

Windows-Startladeprogramm
-------------------------
Bezeichner {8febc170-7266-11e1-ade8-8953572217f7}

Windows-Startladeprogramm
-------------------------
Bezeichner {8febc172-7266-11e1-ade8-8953572217f7}

Windows-Startladeprogramm
-------------------------
Bezeichner {8febc174-7266-11e1-ade8-8953572217f7}
device ramdisk=[C:]\Recovery\8febc170-7266-11e1-ade8-8953572217f7\Winre.wim,{8febc175-7266-11e1-ade8-8953572217f7}
path \windows\system32\winload.exe
description Windows Recovery Environment (wiederhergestellt)
locale
osdevice ramdisk=[C:]\Recovery\8febc170-7266-11e1-ade8-8953572217f7\Winre.wim,{8febc175-7266-11e1-ade8-8953572217f7}
systemroot \windows
winpe Yes

Wiederaufnahme aus dem Ruhezustand
----------------------------------
Bezeichner {8febc16e-7266-11e1-ade8-8953572217f7}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale de-DE
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Windows-Speichertestprogramm
----------------------------
Bezeichner {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows-Speicherdiagnose
locale de-DE
inherit {globalsettings}
badmemoryaccess Yes

EMS-Einstellungen
-----------------
Bezeichner {emssettings}
bootems Yes

Debuggereinstellungen
---------------------
Bezeichner {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM-Defekte
-----------
Bezeichner {badmemory}

Globale Einstellungen
---------------------
Bezeichner {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Startladeprogramm-Einstellungen
-------------------------------
Bezeichner {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisoreinstellungen
-------------------
Bezeichner {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Einstellungen zur Ladeprogrammfortsetzung
-----------------------------------------
Bezeichner {resumeloadersettings}
inherit {globalsettings}

Ger„teoptionen
--------------
Bezeichner {8febc171-7266-11e1-ade8-8953572217f7}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\8febc170-7266-11e1-ade8-8953572217f7\boot.sdi

Ger„teoptionen
--------------
Bezeichner {8febc173-7266-11e1-ade8-8953572217f7}
ramdisksdidevice unknown
ramdisksdipath \Recovery\8febc170-7266-11e1-ade8-8953572217f7\boot.sdi

Ger„teoptionen
--------------
Bezeichner {8febc175-7266-11e1-ade8-8953572217f7}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\8febc170-7266-11e1-ade8-8953572217f7\boot.sdi

"recoverysequence" is pointing to an empty entry. The entry that appears to be configured is {8febc174-7266-11e1-ade8-8953572217f7}.

You could setting "recoverysequence" to point to the correct entry or you could try disabling/enabling WinRE.

--
To set the "recoverysequence" value, run:
bcdedit /set {current} recoverysequence {8febc174-7266-11e1-ade8-8953572217f7}

Then try running the script again.
--
To disable/enable WinRE, run the following two commands:
reagentc /disable
reagentc /enable

Then try running the script again.
--

Thanks Paul! Genious Advice! Problem solved - didn't know that this forum is also such a good windows support forum

Just one more question you wrote:

"Except for the trial version limitations restoring is the same as the full version."

What exactyl are the trialversions limitations? If i want to restore an Image of C on my computer is that save/possible or will something stop me?

There are additional programs/scripts that are included with the full version you won't have access to. You'll have a time-out period when you run IFW and the trial is limited to 30 days.

Restoring an image using the trial version within the trial period will be the same as the full version -- same procedure, options, etc.

Oh @# i think i did something really bad... Sorry that i have to ask again. But i fear i did something bad to my system:

I restored an 3 days old image of C with IFW. Then the old error that i couldn't start the recovery environment at boot - what you helped me with - occured again. Then i typed in the cmd the line you gave - thought it would fix things again:

"bcdedit /set {current} recoverysequence {8febc174-7266-11e1-ade8-8953572217f7}"

when i try to make Recovery disk now i have the same errormessage as before
But now when i start windows press F8 choose fix computer then not the recovery tools start but the regular windows is starting. This was NOT the way it was before. So i fear i f'd up my system with that command.

Could you help me one more time, since i don't know how to fix this now?
bcdedit now:

Windows-Start-Manager
---------------------
Bezeichner {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale de-DE
inherit {globalsettings}
default {current}
resumeobject {8febc16e-7266-11e1-ade8-8953572217f7}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows-Startladeprogramm
-------------------------
Bezeichner {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale de-DE
inherit {bootloadersettings}
recoverysequence {8febc174-7266-11e1-ade8-8953572217f7}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {8febc16e-7266-11e1-ade8-8953572217f7}
nx OptIn

Windows-Startladeprogramm
-------------------------
Bezeichner {8febc170-7266-11e1-ade8-8953572217f7}

Windows-Startladeprogramm
-------------------------
Bezeichner {8febc172-7266-11e1-ade8-8953572217f7}

Wiederaufnahme aus dem Ruhezustand
----------------------------------
Bezeichner {8febc16e-7266-11e1-ade8-8953572217f7}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale de-DE
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Windows-Speichertestprogramm
----------------------------
Bezeichner {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows-Speicherdiagnose
locale de-DE
inherit {globalsettings}
badmemoryaccess Yes

EMS-Einstellungen
-----------------
Bezeichner {emssettings}
bootems Yes

Debuggereinstellungen
---------------------
Bezeichner {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM-Defekte
-----------
Bezeichner {badmemory}

Globale Einstellungen
---------------------
Bezeichner {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Startladeprogramm-Einstellungen
-------------------------------
Bezeichner {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisoreinstellungen
-------------------
Bezeichner {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Einstellungen zur Ladeprogrammfortsetzung
-----------------------------------------
Bezeichner {resumeloadersettings}
inherit {globalsettings}

Ger„teoptionen
--------------
Bezeichner {8febc171-7266-11e1-ade8-8953572217f7}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\8febc170-7266-11e1-ade8-8953572217f7\boot.sdi

Ger„teoptionen
--------------
Bezeichner {8febc173-7266-11e1-ade8-8953572217f7}
ramdisksdidevice unknown
ramdisksdipath \Recovery\8febc170-7266-11e1-ade8-8953572217f7\boot.sdi