TeraByte Unlimited

@TeraByte Support(PP) is there an email address or other platform I could DM you on? I don't wanna waste board bits with my latest weird IFW problem. Thanks in advance.

It's best to email support if you don't want to post it on the forum. You can attention me if you wish.

The problem with taking issues off-forum is that the community doesn't get the benefit of a documented solution.

Could be tomorrow, next week, or 6 months from now...someone may come along with a similar issue looking for help.

OK. Why, once in TBLauncher, does the change monitor resolution item only show 1 selection? I have a new monitor and the TBWinRE display is way to big, like 800 x 600. In the build options section of of TBWinPE?RE building it says the resolution settings aren't supported on Windows 8 or later. Si is there another way to change the resolution. I need something like 2048x1536 or higher. Thanks in advance.

I think 1024x768 is the current default/lowest resolution generally used. What is the single resolution reported by TBLauncher?

Resolutions shown as available in TBLauncher are those reported by WinPE/RE. Some of the newer Windows 11 WinPE versions won't switch from 1024x768 even though other resolutions are reported as supported. WinRE seems to be better in this regard. It can also vary between WIM versions since Microsoft often changes what's supported/blocked.

On some systems, the available/supported resolutions can be different depending on if the system is booted in UEFI or Legacy mode. For example, Legacy may have many resolutions available while UEFI only has one (usually the maximum). It may also vary between connection types (HDMI vs DP, for example).

In TBWinPE/RE Builder, the resolution settings that aren't supported on Windows 8 or later are the 16-bit color (16bpp) options (marked with *). Make sure you're selecting a 32-bit option (32bpp). The resolutions listed are some common ones and may differ from what WinPE/RE shows. If you check in WinPE/RE and there is a better resolution that works there, you can manually specify the ChgRes parameters in the box.

Another thing you could check is if a higher DPI is being used. When the DPI (Scale) "Use default" setting is selected, it will adjust per what WinPE/RE thinks is optimal. If the resolution is high (monitor max, for example) and everything is too large it may be selecting a high DPI value. In that case, you could try specifying a lower DPI value (like 96).

You can try setting the following BCD options on the flash drive and see if it helps with getting a higher resolution.

Run the commands from an administrator command prompt. Use the correct drive letter for your flash drive. F: is used in the examples below.

Legacy booting: UEFI booting: Note that if it works and you get the higher resolution (4K for example), you may also want to set the DPI scaling up some for the build.

@TeraByte Support(PP) I tried the UEFI command since I formatted the WinRE as a GPT disk. Neither command worked. The error message was "The boot configuration data store could not be opened".

As an aside, the TBWinRE files and folders are being placed on a virtual CD/DVD drive designated as L:\ (and, yes, I did change the path
in the command you sent to reflect that location). I believe in some of my earlier builds, those files were placed on a non-optical virtual drive that I could write to.

@OldNavyGuy. Per your advice:
There are several issues to unpack after exchanging emails with support's
very helpful tips on my other issues.

I am using a custom TBLauncher.ini file.

1. Thanks to the Support email, I learned that boot media search time
makes a difference, especially with AMD boards which are slower to boot.
I had to increase search time to 9 seconds to get my TBWinRE image to
work with AMD.

2. It seems you cannot use a USB-c hub or anything higher than USB 3.0
to boot the USB drive or TBWinRE won't boot correctly. Mine booted
TBWinRE initially, but would not launch the menu; it just kept the USB drive
activity light going for several minutes until it stopped searching. I
ended up connecting directly to the PCs USB 3.0 ports. Maybe
incorporating USB 3.2 drivers into boot.wim would help. By the way, I
checked "Add installed network and storage drivers" and it made no
difference. (Adding my laptop's touchpad and "HID PCI Minidriver for ISS"
drivers to the drivers folder also didn't give me touchpad functionality.
But that's not critical for me. I can navigate with the keyboard, only.)

Yottabytes wrote: Wed Dec 04, 2024 12:37 am @TeraByte Support(PP) I tried the UEFI command since I formatted the WinRE as a GPT disk. Neither command worked. The error message was "The boot configuration data store could not be opened".

As an aside, the TBWinRE files and folders are being placed on a virtual CD/DVD drive designated as L:\ (and, yes, I did change the path
in the command you sent to reflect that location). I believe in some of my earlier builds, those files were placed on a non-optical virtual drive that I could write to.

If the final boot media is read-only, you would need to run the commands on the files before the media (UFD, ISO, disc, etc.) is created. You would need to adjust the command paths for the ISO folder of the build (this is the "root" folder of the media). For example, assuming the build is in F:\TBWinRE: Then, after running the commands, create the media with MakeDisk. Otherwise, if you are booting through a different BCD, you would need to run the commands on that file.

You could just create the normal USB flash drive boot media, run the commands on it, and see if it actually helps before trying to integrate it into your custom media.

The commands don't work with IFW v3.64. However, the display options offered in IFW v4.03a while creating a TBwWinRE and Bootit Collection iso do work.

However, since I'm a big fan of deploying TBWinRE and BootIt UEFI from my Ventoy rescue disk (viewtopic.php?t=4286 ) I cannot use version 4.03a because the ISO image it creates is compressed and cannot be compiled into an ISO that is extractable by Ventoy. While I understand the developer of IFW wants to thwart piracy, this is unfortunate and I will be sticking with version 3.64 for the time being.

The bcdedit commands wouldn't care if it was a 3.64 or 4.03a build. Those commands just add the options to the BCD entry for the boot media. The path would need to be correct for your build's ISO folder. Also, since you're using custom boot media (Ventoy), if it uses a BCD file to boot the media then it may be that one that needs modified. Basically, it would just need to boot through a BCD entry with those options to see if it helps.

If Ventoy will boot WIM files, you could copy the TBWinRE UFD files to the flash drive and configure Ventoy to boot the \sources\boot.wim file. That wouldn't require an ISO. Not really familiar with Ventoy, though, so not sure how it handles different file types.