TeraByte Unlimited

Hi

i use image for windows winpe and image for linux to restore image on my ssd

but does restoring often image degrade the ssd performance?
because restoring often images (several times at week), image for windows/linux writes data always on the same cells (i think like every image programs)

does terabyte test it and can confirm it?

thanks

guilia,

If you use "Write Changed Sectors Only" then just a percent or two of the sectors will be re-written. Depending on the changes.

Brian K wrote:
> guilia,
>
> If you use "Write Changed Sectors Only" then just a percent or
> two of the sectors will be re-written. Depending on the changes.
where is this option?
is enabled by default?
and are you sure about only a percent or 2 of the secotrs will be re-written? i know depending of the changes

giulia wrote:

> where is this option?

It's on the Options menu.

http://www.terabyteunlimited.com/ucf/vi ... f=4&t=1214

Brian K wrote:
> giulia wrote:
>
> > where is this option?
>
> It's on the Options menu.
>
> http://www.terabyteunlimited.com/ucf/vi ... f=4&t=1214
Hi Brian
i 'm using image for windows with winpe
can you please link a screenshot?
i can't find it in the program settings and the restore settings
thanks

giulia wrote:

> can you please link a screenshot?
> i can't find it in the program settings and the restore settings
> thanks

See pages 94 and 107 in the IFW manual.

Brian K wrote:
> giulia wrote:
>
> > where is this option?
>
> It's on the Options menu.
>
> http://www.terabyteunlimited.com/ucf/vi ... f=4&t=1214

hi Brian
thanks for the answer
may i ask a question only for the knowledge ?
how did you pass the /wco switch to image for windows winpe or linux based?

thanks

giulia wrote:

> how did you pass the /wco switch to image for windows winpe or linux based?
>

giulia,

It's easy when you can just select the "Write Changed Sectors Only" option. If you are restoring from a command line, add /wco for IFW and IFD. For IFL use --wco. You can use "Show Command" to create the command line.

Maybe I misunderstood your question. I used SSDLife to see how much data was written to the SSD.

Brian K wrote:
> giulia wrote:
>
> > how did you pass the /wco switch to image for windows winpe or linux based?
> >
>
> giulia,
>
> It's easy when you can just select the "Write Changed Sectors Only" option.
> If you are restoring from a command line, add /wco for IFW and IFD. For IFL use
> --wco. You can use "Show Command" to create the command line.
hi Brian , i know about "you can just select the "Write Changed Sectors Only" option."

but i did ask how can you pass the /wco to image for windows Winpe(w8.1) based
i mean i know i can use "show command" but working with image for windows winpe ,how can add it?
how can use a command line working with image for windows winpe?
i did burn the iso of image for windows winpe on a cd
after i create a command line how can i run it under winpe?
thanks

giulia wrote:

> how can use a command line working with image for windows winpe?

I use TBWinRE instead of TBWinPE. There are several ways to run a command line (See the tutorial) ....

"IFWModeParameters - Use this option to specify the command line options for IFW when using IFW mode. This is useful if you want to configure the TBWinRE build to auto-run IFW and perform a specific task (e.g. create a backup or restore an image).

Example: IFWModeParameters=/b /v /d:w0 /f:"e:\backups\win7.tbi" /desc:"Windows 7 Drive"

FindBootDrive - Searches for the TBWinRE boot media drive after booting (0 = disabled, 1 = enabled). If enabled, TBLauncher will search for the boot media. If found, the following applies:

The %TBDrive% environment variable will be set to the drive letter of the boot media and can be used in custom scripts or menu items.

If the \TBData\TBLauncher.ini file exists on the drive it will be used instead of the built-in INI file. Note that the initialization options in the replacement file won't be used since initialization has already occurred. However, the Mode option and menu items will be used.

If the \TBData\autorun.cmd file exists on the drive it will be run, overriding the Mode setting. This allows easy configuration and use of an auto-run script without needing to recreate the build. Important: Care should be taken when using an auto-run script. Depending on the script, having it run on the wrong system or when not applicable may have undesirable consequences."

I prefer a UFD as you can edit autorun.cmd in Windows.