TeraByte Unlimited

I had to roll back my rescue disk to IFL v3.64 because of the display issues with Windows 11 & IFW 4.x

OLD
https://u.pcloud.link/publink/show?code ... k4rjihSU5y

NEW
https://u.pcloud.link/publink/show?code ... hKC0qKm7d7

I tried to create a new IFW TBWinRE disk. Both have the same file structure. But the new TBwinRE can only find these directories:

%ProgramFiles%\TeraByte Drive Image Backup and Restore Suite
%SystemRoot%\System32\cmd.exe

It cannot find %TBDrive%\TBData even though it is on the USB drive and the TBLauncher.ini is at the root of \TBData with the correct ItemCount
number. How do I fix this?

Also IFW seems to have issues imaging USB drives with EFI partitions. I can image a USB drive but get an error every time I try to restore the image to a new usb. Is there a fix for that?

If it was a new build, maybe the option to search for the boot media wasn't enabled? That needs to be enabled or it won't find it and set the TBDrive environment variable. Also, by default, the Build ID GUID needs to match or it will ignore the media (you could update the ID in TBWinRE.txt file to match the new build or disable the option if you don't want to rebuild for it). So, if you're mixing old and new build files that could be the issue.

Also IFW seems to have issues imaging USB drives with EFI partitions. I can image a USB drive but get an error every time I try to restore the image to a new usb. Is there a fix for that?

No known issues, typically use USB drives during testing. It may be unable to lock but that would be the issue, if the drive is out of sync with what Windows thinks it is, it will look like nothing to lock but then give a write error because it's not locked. Remove and insert the USB drive typically fixes that, also antivirus programs can potentially block writes. Of course what the error is matters to what it could be, also see if anything in the system event log regarding the disk.

OK. I got the TBlauncher.ini issue sorted out. Thanks for the help. It was indeed the contents of the TBWinRE.txt file.

On the USB, I swear this Windows Dirty Bit drive issue is driving me crazy. It seems with EFI partitions on USB drives, if a user selects to unmount either the primary or the EFI partition the whole USB drive is ejected and so next time it's inserted Windows flags a dirty bit.

Finally, do you know what "System error 1312 has occurred." when trying to execute my network logon command from TBLauncher:

"/k net use y: \\Server\home @Password /user:XXXX"

For that error, try using the server name with the username. For example: server\username

"/k net use y: \\Server\home @Password /user:server\XXXX"

Otherwise, does it work to map the share using TBLauncher? Can you provide more details on exactly what method you're using to run the command? The error you're getting doesn't look like it's directly from TBLauncher so I assume you're running it from a menu item or script.

I created a menu item with the following command to activate my connection with my network home drive:

[Menu_Item_4]
Name=MyNetPath
Path=%SystemRoot%\System32\cmd.exe
WorkingDir=
Parameters=/k net use y: \\Network\Path2NAS\home PASSWORD /user:xxxx
Icon=0

After executing this command, I used to be able to open the network path using my file manager.\ listed in TBLauncher.
The command used to work. But I don't think it's initializing at all now with my new TBWinRE disk. I don't even see "Initialize Network" in the TBLauncher title bar, although I do so "Initialize WiFi"

If you're getting that error, the network is probably working.

Did you try including the server name with the username as suggested in my previous post? I ran a test and got the same error you're getting when I just used the username. Using the "server\username" worked. For example: Otherwise, for more testing:

You can open a Command Prompt and run 'ipconfig' to check if it has a network connection and is assigned an IP address.

You can run the 'net use' command from the Command Prompt to see what works there.

To test with the TBLauncher menu item command, move the running TBLauncher to a different location, edit the TBLauncher.ini file in Notepad, and then run TBLauncher.exe again to show the modified menu. You can exit the new TBLauncher by using File | Exit and it won't restart the system.

Thanks. I will test later today.

So after a few hours of troubleshooting, this is the issue: MY PC has a static IP address. But my PC was being assigned an incorrect IP, subnet and no gateway at all when I booted into TBWinRE, which I believe is why I got the network error messages. So, if any of you have a similar problem, you can fix it by running this command at the prompt:
You can also use the WMIC command to do assign this network information if you like. After you set your correct interface information, you can run the logon command posted above by TeraByte Support(PP) If you find yourself having to do this, you might want to embed the netsh command in the TBLauncher.ini file as a comment so that you can easily retrieve it when needed.

Not sure why all this changed from my previous TBWinRE USBs which would connect out of the box to my NAS using the logon command I originally posted. But in any event, problem solved.

By the way, is it possible to combine the netsh command with the logon command in the TBlauncher Item menu? That would be a lot more user friendly.

You could create a new .cmd file with the commands you want to run and then run that with the menu item. However, if it's something that should always be run on startup, using InitScript.cmd is generally the way to go. AutoRun commands could also be used (from a plugin or added manually).

An example with InitScript is shown in this KB article (last section):
https://www.terabyteunlimited.com/kb/kb ... bwinpe-re/