DOS recovery

User discussion and information resource forum for Image products.

DOS recovery

Postby borate » Mon Dec 24, 2018 2:50 pm

Almost certain that this is the correct procedure, but want confirmation.

The target drive is OS-1TB-SSD. The backup is on a WD Elements external drive.

In the DOS recovery environment the "restore from" dialog is as follows...

Elements (next)
IFW folder (next)
Specific back-up file (next)
OS-1TB-SSD drive (active)

It's the drive name of this last entry that gives pause. Is that indeed the back-up file on the Elements drive, to be restored to OS-1TB-SSD?
Thereafter, the "restore to" target lists this same C: drive.

Simple mode is not used when creating images. At restore via DOS a prompt appears to the effect that it cannot detect backups made in simple mode and to disable that mode in settings.
When that is done the UI responds that "settings could not be saved." But CANCEL, and you're allowed to proceed.

Can this extra step be overcome? And is there a way to save the product key when using this utility, instead of having to retype it each time? Gracias
borate
 
Posts: 96
Joined: Thu Oct 27, 2011 2:51 pm

Re: DOS recovery

Postby Bob Coleman » Tue Dec 25, 2018 7:40 pm

borate wrote:
> Almost certain that this is the correct procedure, but want confirmation.

What are you doing? Booting an IFD (Image for DOS) CD/DVD/UFD? For now, I'll assume Yes.
>
> The target drive is OS-1TB-SSD. The backup is on a WD Elements external
> drive.
>
> In the DOS recovery environment the "restore from" dialog is as
> follows...
>
> Elements (next)
> IFW folder (next)
> Specific back-up file (next)
> OS-1TB-SSD drive (active)
>
> It's the drive name of this last entry that gives pause. Is that indeed
> the back-up file on the Elements drive, to be restored to OS-1TB-SSD?

Since this is "restore from", you should select whatever contains the image since that is where you will be restoring data from. Presumably this is Elements in this case, but anyway it is the location of the image file. Thereafter, you should be able to select the particular image file if you have more than one and possibly "Full disk" or a partition within the image file if it contains more than one.

> Thereafter, the "restore to" target lists this same C: drive.

For "restore to", you should select the disk you are going to restore to (pretty straightforward and presumably OS-1TB-SSD). Again, you might get to select a particular partition if the target drive has more than one.

>
> Simple mode is not used when creating images. At restore via DOS a prompt
> appears to the effect that it cannot detect backups made in simple mode and
> to disable that mode in settings.
> When that is done the UI responds that "settings could not be
> saved." But CANCEL, and you're allowed to proceed.

I've never used simple mode and can't shed too much light on this, but maybe you are running IFD from a bootable CD which can't be written to so there is no place to save settings.

>
> Can this extra step be overcome? And is there a way to save the product
> key when using this utility, instead of having to retype it each time?

I'm getting a little confused as to what you are using. IFD bootable media created with Makedisk? If so, you should have been able to enter the product key during that process and it should then be part of the bootable media and not be asked for when using that media. I would also suggest choosing Complex mode or whatever the opposite of Simple mode is when creating the bootable media. Then you shouldn't have to worry about that issue again.

> Gracias

As an aside, IFL will almost certainly be faster than IFD.
Bob Coleman
 
Posts: 549
Joined: Fri Aug 12, 2011 10:58 am

Re: DOS recovery

Postby TeraByte Support » Wed Dec 26, 2018 10:01 am

Also, use "restore normal" (rather than automatic) to be able to pick the
target.

Also, IFL or TBWinRE/PE boot disk may work better depending on the system
bios.


"borate" wrote in message news:16165@public.image...


TeraByte Support
 
Posts: 2703
Joined: Thu May 05, 2011 3:37 pm

Re: DOS recovery

Postby borate » Wed Dec 26, 2018 2:31 pm

Attempted to create a TVwinRE IFW bootable recovery CD. This message appeared...

"TBOSDT not installed or invalid path specified.
Boot file support disabled (missing TBOSDT file, not activated, or incorrect
version).
- This issue does not affect creating the normal boot media."

With the statement that this would not affect creating the boot media, creation proceeded, and concluded successfully.
MakeDisk also reported success.

However, the disk spun up but would not boot.
After removing it, a prompt appeared that the PC would have to be repaired. A reboot bypassed that.

-0-

Burned a new DOS recovery disk, this time specifying TRADITIONAL. That bypassed the "simple" prompt mentioned earlier, and there was no need to retype the product key. Excellent. This will do the job.

Still, at the last step of the RESTORE FROM dialog, the chosen file on the Elements external drive D: \IFW folder, is "Win10_1803_z390.TBI"

That's what I would expect to see. But instead, it lists the drive name. I assume that this is simply a naming convention.

Best, hb
borate
 
Posts: 96
Joined: Thu Oct 27, 2011 2:51 pm

Re: DOS recovery

Postby TeraByte Support » Wed Dec 26, 2018 9:19 pm

go to the drive and partition that is D: in windows.

"borate" wrote in message news:16171@public.image...

Attempted to create a TVwinRE IFW bootable recovery CD. This message
appeared...

"TBOSDT not installed or invalid path specified.
Boot file support disabled (missing TBOSDT file, not activated, or incorrect
version).
- This issue does not affect creating the normal boot media."

With the statement that this would not affect creating the boot media,
creation proceeded, and concluded successfully.
MakeDisk also reported success.

However, the disk spun up but would not boot.
After removing it, a prompt appeared that the PC would have to be repaired.
A reboot bypassed that.

-0-

Burned a new DOS recovery disk, this time specifying TRADITIONAL. That
bypassed the "simple" prompt mentioned earlier, and there was no need to
retype the product key. Excellent. This will do the job.

Still, at the last step of the RESTORE FROM dialog, the chosen file on the
Elements external drive D: \IFW folder, is "Win10_1803_z390.TBI"

That's what I would expect to see. But instead, it lists the drive name. I
assume that this is simply a naming convention.

Best, hb

TeraByte Support
 
Posts: 2703
Joined: Thu May 05, 2011 3:37 pm

Re: DOS recovery

Postby borate » Thu Dec 27, 2018 1:26 am

> Go to the drive and partition that is D: in windows.

Thanks. I now see that the image file name appears on the confirmation screen.

Why the failure to create the TBWinRE/PE boot disk? Instructions were followed to the letter, with the absence of TBOSDT warning being the only deviation from what was shown.
borate
 
Posts: 96
Joined: Thu Oct 27, 2011 2:51 pm

Re: DOS recovery

Postby TeraByte Support(PP) » Thu Dec 27, 2018 2:34 pm

TBOSDT missing wouldn't affect booting. Are you using the most current version of TBWinPE/RE Builder? Did you try booting the CD on another computer? You could also try a flash drive (you can just run MakeDisk again and select that option if you don't need to rebuild).
Paul Purviance
TeraByte Support
TeraByte Support(PP)
 
Posts: 1294
Joined: Thu Aug 11, 2011 5:51 pm

Re: DOS recovery

Postby borate » Thu Dec 27, 2018 6:01 pm

File properties lists this for the builder: Created Monday, ‎January ‎23, ‎2017, ‏‎12:47:37 PM

Didn't test the CD in another PC. Will attempt to create bootable Flash media next time.
borate
 
Posts: 96
Joined: Thu Oct 27, 2011 2:51 pm

Re: DOS recovery

Postby TeraByte Support(PP) » Fri Dec 28, 2018 12:28 am

Help | About... will show which version it is or you can right-click on TBWinPE.EXE and click Properties and then the Details tab. If it's an old version, updating current (1.16) is recommended and then try it again. Otherwise, if the problem persists, the log output for the build might be helpful.
Paul Purviance
TeraByte Support
TeraByte Support(PP)
 
Posts: 1294
Joined: Thu Aug 11, 2011 5:51 pm

Re: DOS recovery

Postby borate » Fri Dec 28, 2018 7:05 am

It's 1.16. Thanks, and a Happy New Year to you folks! The log from that day...

2018-12-26 12:46:39 - TBWinPE/RE Builder v1.16
2018-12-26 12:46:39 - Initializing
2018-12-26 12:46:39 - Windows version: Windows 10 Pro [10.0.17134-1803,x64]
2018-12-26 12:46:39 - Checking for required build files
2018-12-26 12:46:39 - Initialization complete
2018-12-26 12:48:42 - Verifying build requirements (TBWinRE)
2018-12-26 12:48:42 - Image for Windows 3.25 found: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite
2018-12-26 12:48:42 - TBIView 4.48 found: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TBIView
2018-12-26 12:48:42 - TBIMount 1.18a found: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TBIView
2018-12-26 12:48:42 - Warning: TBOSDT not found (Path: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro)
2018-12-26 12:48:42 - Warning: Boot file support disabled (missing TBOSDT file, not activated, or incorrect version)
2018-12-26 12:48:42 - Build source: Windows 10 Pro [10.0.17134] WinRE
2018-12-26 12:48:43 - Locating WinRE image
2018-12-26 12:48:43 - WinRE located (Winre.wim, active): \\?\Volume{4f80ed07-0000-0000-0000-f04eee000000}\Recovery\WindowsRE
2018-12-26 12:48:44 - Version of installed WinRE: 10.0.17134
2018-12-26 12:48:44 - Version of backup WinRE: 10.0.15063
2018-12-26 12:48:44 - Updating backup WinRE image
2018-12-26 12:48:52 - Backup created successfully
2018-12-26 12:48:53 - Verification complete
2018-12-26 12:50:34 - Creating TBWinRE build
2018-12-26 12:50:34 - Build ID: {32074C2F-8488-4557-8005-DA7BC4788DC0}
2018-12-26 12:50:34 - Initializing DISM (1,0)
2018-12-26 12:50:34 - DISM initialized (A)
2018-12-26 12:50:35 - Copying WinRE image
2018-12-26 12:50:41 - Mounting WinRE image
2018-12-26 12:51:23 - WinRE image file architecture: x64 [10.0.17134.1]
2018-12-26 12:51:25 - Configuring WinRE
2018-12-26 12:51:26 - Info: DEFAULT hive loaded manually (0x2)
2018-12-26 12:51:26 - Info: SYSTEM hive loaded manually (0x2)
2018-12-26 12:51:26 - Adding TBLauncher [1.17]
2018-12-26 12:51:27 - Adding Image for Windows [3.25]
2018-12-26 12:51:28 - Adding TBIView [4.48]
2018-12-26 12:51:28 - Adding TBIMount [1.18a]
2018-12-26 12:51:29 - Finalizing build
2018-12-26 12:51:30 - Copying booting files
2018-12-26 12:51:31 - Saving WinRE image
2018-12-26 12:51:43 - Unmounting WinRE image
2018-12-26 12:51:53 - Creating CD/UFD/ISO file layout
2018-12-26 12:52:01 - Build process completed successfully
2018-12-26 12:52:12 - Program exiting with code 0
2018-12-26 13:16:39 - ---------------------------------------------------------------------------
2018-12-26 13:16:39 - TBWinPE/RE Builder v1.16
2018-12-26 13:16:39 - Initializing
2018-12-26 13:16:39 - Windows version: Windows 10 Pro [10.0.17134-1803,x64]
2018-12-26 13:16:39 - Checking for required build files
2018-12-26 13:16:39 - Initialization complete
2018-12-26 13:17:12 - Verifying build requirements (TBWinRE)
2018-12-26 13:17:12 - Image for Windows 3.25 found: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite
2018-12-26 13:17:12 - TBIView 4.48 found: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TBIView
2018-12-26 13:17:12 - TBIMount 1.18a found: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TBIView
2018-12-26 13:17:12 - Warning: TBOSDT not found (Path: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro)
2018-12-26 13:17:12 - Warning: Boot file support disabled (missing TBOSDT file, not activated, or incorrect version)
2018-12-26 13:17:13 - Build source: Windows 10 Pro [10.0.17134] WinRE
2018-12-26 13:17:13 - Locating WinRE image
2018-12-26 13:17:14 - WinRE located (Winre.wim, active): \\?\Volume{4f80ed07-0000-0000-0000-f04eee000000}\Recovery\WindowsRE
2018-12-26 13:17:14 - Version of installed WinRE: 10.0.17134
2018-12-26 13:17:15 - Version of backup WinRE: 10.0.17134
2018-12-26 13:17:15 - Backup copy of winre.wim found
2018-12-26 13:17:16 - Verification complete
2018-12-26 13:17:23 - Program exiting with code 0
borate
 
Posts: 96
Joined: Thu Oct 27, 2011 2:51 pm


Return to Image for DOS/Linux/Windows