hi @Brian K but i don't want to enarlge w10 of 715395 MB of Free Space i would like to enlarge w10 of 100GB what should i do ? slide the winre partion to the end increase the w10 partition of 100GB and how can i move the winre partition after w10? thanks Brian!
I just tried updating to 3.34, and I cannot get my custom programs to work. IFW 3.34 works, but no custom programs when I boot it. I'll keep looking.
I just checked and mine work. Did you put BuildScript.cmd in the config folder? I suggest using the same TBWinPE.ini as you used for 3.33. I copy mine every time.
Hi Brian. It's working now. I know what I did wrong. I have been adding custom programs to my bootable media for some time now using Method 2 in this Knowledge Base article. The path it suggests for custom programs is Path=%TBDrive%, and that works fine for me for creating custom bootable media. But it doesn't work for Boot.wim. At least not when I do it. But Path=%ProgramFiles% works. You suggested that some time ago, but I didn't notice at the time that there was a difference. So, my menu items in TBLauncher.ini for creating bootable media are: Code: [Menu_Item_11] Name=Explorer++ Path=%TBDrive%\CustomProg\Explorer++\Explorer++.exe WorkingDir= Parameters= Icon=0 [Menu_Item_12] Name=Snapshot Path=%TBDrive%\CustomProg\Snapshot\snapshot64.exe WorkingDir= Parameters= Icon=0 And for Boot.wim: Code: [Menu_Item_11] Name=Explorer++ Path=%ProgramFiles%\Explorer++\Explorer++.exe WorkingDir= Parameters= Icon=0 [Menu_Item_12] Name=Drive Snapshot Path=%ProgramFiles%\Snapshot\snapshot64.exe WorkingDir= Parameters= Icon=0 Also, when I make bootable media, as per Method 2, I manually copy my custom programs into the ISO folder and leave them there. I have noticed that this Boot.wim method that you suggested to me leaves the custom programs in the TBWinRE_Files folder and copies them with the script, and after building they are gone. Could I add the custom programs into the ISO folder and leave them there when creating a custom Boot.wim, or won't that work?
You don't need to use your Path=%TBDrive%\CustomProg\Snapshot\snapshot64.exe method. The Path=%ProgramFiles%\Snapshot\snapshot64.exe method should work for boot.wim and a UFD.
If you like, you can add extra portable apps to your UFD (TBData folder or root) and access them from Explorer++.
Yes, that's a good idea. That makes it simple to just double click the executables. I think there are portable app menus available so you can have a little menu of your portable applications. It has been a long time since I used one though.
All this seems like a lot of work to me. I just use the Stelec USB winpe 10, and copy image64.exe and ifw.ini from the ifw install folder and away it goes. Like having windows IFW on usb
Thanks @Brian K I used this script again to update the boot wim recovery environment to v3.35. All good. It only takes a few minutes once you know what you're doing. Here a couple of shortcuts I made to streamline the process. Copy and replace TBWinPE.ini to new version folder. Copy and replace config folder to new version folder.
Hadron, I do the same. I then copy the ISO to my SSD so I can boot TBWinRE from the SSD. Code: sub main() ext("open fs 0: 0 0x0E") ext("RD 0:\ /s /y") ext("dir 0:\") printl(" ") ext("copy D:\TBWinRE_files\335re\ISO\* 0:\ /s /y") ext("set vol TBWinPE335 0:") printl(" ") ext("dir 0:\") printl(" ") ext("close fs 0:") end sub
Do you have a dedicated SSD for that? Otherwise, I am already doing a similar thing. PS: I didn't know about those batches you posted in the other thread. One has a purge function. I'll have to look into it.
No, it's on the same SSD along with about 20 other OS. I'm using BootIt to boot these OS and TBWinRE.
This is a strange instruction. It seems to contradict itself. It says: In all cases, omit the trailing backslash, even for root directories (e.g. C: or D: Then the example has the backslash.