Hadron, -m3 is the default resolution of 1024 x 768. That's what I use. https://www.terabyteunlimited.com/howto/tbwinrecmd_tutorial/
Brian, it gives an example of set screenresolution=-m5, but it doesn't indicate what resolution it changes it to. Is there a chart with the different resolution settings? It also says to refer to Appendix 4, which talks about the ChgRes.exe program. Maybe the user manual needs to be updated with this information.
I found this... https://www.terabyteunlimited.com/howto/builder_settings/ In TBWinRE, Command prompt... chgres You will see "everything".
I'll try some other screen resolution settings. Although it says that it's not supported on Windows 8 or later. https://www.terabyteunlimited.com/wp-content/uploads/2021/06/builder_settings/builder_ss03.png By the way. These are the TBWinPE.ini settings that I was asking about. Whether they work or not, I'm not sure. I plan to test some.
It's much easier in TBWinRE. Open a command prompt and enter... Code: chgres You will see all the options. Enter your desired choice. eg... Code: chgres -m3 At least you will find what works without having to make multiple TBWinRE.
I ran chgres from Command Prompt and got pretty much the same as you. I don't really understand the use of it as I can easily change the screen resolution from the TBLauncher Tools menu. At 1024 x 768, I get a black background. I never always had this problem. It only recently started happening. But if I change it to 1920 x 1080 via the TBLauncher Tools menu, it displays correctly.
Here is another image with the background completely black. As you can see, TBLauncher displays correctly, as do all the applications within TBLauncher. It seems that my monitor doesn't like the 1024 x 768 screen resolution anymore.
In my TBWinRE, Tools, Screen Resolution... I only have 1024 x 768 It's the only resolution I can use.
@Brian K Hi Brian I have update image for windows and linux to the last version 3.55 few days ago , i create a winpe for image for windows usb stick and image for linux usb stick both bootable may I ask 3 questions? 1) only under image for windows(not under image for linux) , i have in the backup the Summary (traditional mode ) , is there another summary mode ? Seeing the "(tradition mode)" let me think there is another summary view/report 2) about consolidate one backup file (i'm reading page 71 english help pdf) , is there a reason to consolidate 1 file (make it smaller or to restore to a smaller partition) ? About consolidate 2 or 3 backup files is reallt cool feature! 3) to restore a partition to a smaller partition , is much better to use the compact feature in the backup window options (page 34 manual pdf ) or compact option in the restore options ? I know I have asked so many times but just in case I 'm used to create almost only drive backups (and not partitions ) and I know according your advises , the best option to restore an drive image to a smaller drive the best option are scale to fit , while if the destination drive is bigger scale to target, right? thanks Brian, by the way some language packs are not very well translated ps i have used almost image for linux question number 1 , screenshot take from the guide pdf file https://i.imgur.com/xeQnMLZ.png
mantra, Some general comments. More later. Regarding scaling, does this help? Partitions less than 15 GB are not resized. Say you have a 600 GB HD containing... 100 MiB SRP 100 GiB partition 200 GiB partition 200 GiB unallocated free space You restore an Entire Drive image of the above HD (with Scale to Fit) to a 600 GiB HD and you will get (approximate partition sizes)... 100 MiB SRP 200 GiB partition 400 GiB partition If you used Scale to Target you would get... 100 MiB SRP 120 GiB partition 240 GiB partition 240 GiB unallocated free space They are different. I find Scale to Fit more suitable. ########################## One topic to remember when restoring or copying from a larger to a smaller partition is sector spread. TeraByte presents this as MiB to Restore. You may have to “Compact” the sectors if MiB to Restore is larger than the target partition. With restores, TeraByte apps do sector based copies/restores so if your original partition was....( * is sectors in use, - is free space) [---**----**--] then the target partition to copy/restore into cannot be smaller than... [------------] You can't restore into a smaller partition like this... [------] But you can compact the sectors to [**-**--------] and then create an image Now you can restore to a smaller partition like this [**-**] Even easier is the "Compact Data" option in Restore Options or Copy Options. This does a "full" compact and your restore would look like this. [****-] Don't use this option if you don't need to use it as the restore/copy time is prolonged compared with a normal restore/copy.
Question 1. Only IFW has the Summary window. Q 2. I don't use Consolidate. Others like it. Q3. Your choice. If I knew I'd have to restore to a smaller partition, I'd compact during the backup.
@Brian K Hallo Brian but you have considered the same 600 GiB HD , it's the same size & would like if you can make an example with an 600 GB hd to a 250 GB hd by the way the examples of is really great and very useful I like a lot image for linux , it's so fast and powerfull and I guess it has have the same features of image for windows and there is the powerfull partition tool too, but I have seen that on some it does freeze with some wireless mouse but I guess Write Changed Sectors Only is not realiable at all Brian you are the best , really! Thanks , I always appreciate your help
mantra, There was a typo in my post. It should have been a 500 GB drive to a 600 GB drive. You have suggested a 600 GB HD to a 240 GB HD. (The maths for 240 is easier than 250) 600 GB HD 100 MiB SRP 100 GiB partition 200 GiB partition 300 GiB unallocated free space If the two partitions are full then it's impossible as 300 GB of data can't fit on a 240 GB HD. Let's say the two partitions are only half full, then Scale to Fit will produce... 100 MiB SRP 80 GB partition 160 GB partition
I don't use a wireless mouse. My wife does and it works fine with IFL. I've never had an issue with Write Changed Sectors Only. I use it for all restores to SSDs. The SSD must support DRAT.
@Brian K but in the past , it did not work with some ssd brands and firmware ,do you remember it? Even the support forum did not know about it about crucials ssd or samsung evo 840 or 860 or sandisk and other brands about is there a tool to know it? about the example is very easy to understand now thanks Brian as always!