I just made a GPT-UEFI System Partition IFL UFD. It had no drive letter in Windows but during the IFW copy it was seen as FAT-32. BIBM showed the IFL partition as EFI System. Weird. This is somewhat different from your IFL UFD as your UFD had a drive letter.
That worked fine. I didn't catch the fact that when you said "copy" you were talking about IFW partition copy. Everything's fine now; IFL boots fine and the script runs. The IFL partion is fat32
Great work. Do you want to do more tonight or tomorrow. It's only 1710 here, so either is fine by me.
One more time to work on the IFL UFD. In your restore.sh, underneath your restore line paste these two lines... Code: rm /tbu/boot/scripts/scriptslist.txt reboot Also, delete --rb:4 from the restore line. Now you should have... Code: #! /bin/sh /tbu/imagel --r --uy --d:l1 --f:l0@0x3:"/System-07-13-2019-1544" --opw:6E2767A67664F4045677B782A3427B --sp:0x1,0x2 rm /tbu/boot/scripts/scriptslist.txt reboot Copy (IFW) the UFD partition to your HD. Over-write the IFL partition. This is in preparation for the Windows scripts.
Tomorrow would be better. Well, I guess technically later today. It's 0030 here, and I have a early day.
In BIBM, Settings, put a tick in BootNow Support. In BIBM, Part Work, select the IFL partition and click Properties. In the blue title bar, what is the number after Properties? We are almost done. In BIBM what is the Identity of your Windows? The same name in the Boot Menu?
Create a folder in your data (Games) partition. Call it Bootnow. Download the BootNow files from... https://www.terabyteunlimited.com/downloads-bootit-bare-metal.htm#addon The main link is the Windows version. Unzip them to the Bootnow folder. Make sure no folders are inside the Bootnow folder. Is this folder in the D: drive?
Well, now the restore script is not running at all; manually or automatically! When I had to recreate the UFD I went with the nonet version. Could that be why? The script stayed the same.
The Nonet version is fine. Try creating a restore1.sh in the UFD. Is there an error message in the black window underneath the menu? Or do you mean the restore script with 4 lines?
I mean my original one that ran successfully before I created a new UDF. It sees the script, it just does'nt do anything once selected.
I have no clue why this isn't working anymore. I even completely remade the UDF, to your directions. When I rebooted I got the no script error as planed. Then I copied the scripts over, replacing the scriptslist.txt file. Reboot in IFL. Then nothing; not even a command line window. So, I remade the scripts, imaging first and taking ther line from there. Reboot in IFL. Nothing. I tried simplifying the script using "test.tbi" and creating an image with no password. That did notyhing either. Reboot in IFL, again, nothingk...not even the CL. My script is below.
Nate, Code: --d:l1@0x1,0x2,0x4 Is invalid. Did you manually edit this section? Try this. It doesn't have --uy so the restore won't start and you can abort. But if you see the Yes/No question then we are on the right track. Code: #! /bin/sh /tbu/imagel --r --d:l1 --f:l0@0x3:"/test" --sp:0x1,0x2,0x4 --wco --rb:4
I copied and pasted your script ^ and still, after rebooting in IFL, nothing happens. I don't even get a CL window. When I try to manually run the script, by having IFL show me the list of scripts, nothing happens when I select it. I see the script in the list, but nothing happens when I select it.
This is frustrating for both of us and before I suggest you contact TeraByte Support can you do one last thing for me? Create another restore script and name it help.tbs instead of help.sh Please post the contents of help.tbs
I'm at a loss for what to do next. I tested each version of the scripts below within IFL (not as scripts but within the imagin program) and they all worked fine. Then when I put them each as scripts, regardless of .tbs or .sh extension (even though they should be .sh) none of them worked as sripts. If I create the cl in the IFL imaging program and save it to a file, the resulting file is not persistent, meaning that when I reboot it's no longer there.
I know that. They should be .sh files. But I've even had script s with a txt extension work, of course when I rebooted they were gone.
Correct. At least I think so. From what I can tell there are two scripts folders; the one on my flash drive or partition and there's also one that's created when IFL is loaded into memory. Since there's really no way to verify or copy any files,because all I really have is "editor" there's really no way to determine which version I am using (since the file structures are the same). Side note, can those above scripts be converted into tbs files?
When you boot into IFL your IFL partition is mounted as Boot. As you point out, the Script folder you see in /tbu/scripts is ephemeral. You don't save to this folder. When you save a script you navigate to /boot/scripts which is the Scripts folder in the UFD. These scripts will not disappear. In MC you can navigate to /boot/scripts and see your scripts and scriptlist.txt. .sh scripts can be converted to .tbs. But not easily.
Copy this ifl.tbs to the scripts folder of your UFD. Type ifl.tbs in scriptslist.txt. Boot the UFD. It should boot to the IFL gui without the script missing message. Code: sub main() printl(" ") printl("IFL gui") printl(" ") exec("/tbu/imagel", 1) end sub
If above works the .tbs scripts work OK. Another experiment. Create a simple restore script but don't edit it in any way. On the Summary screen click Show Command. Click Save to File. Click OK. Select boot (folder) and press Enter. Select scripts (folder) and press Enter. In the Name field type in nate.sh Click OK. Click Exit on IFL. Reboot into Windows and confirm nate.sh is in scripts folder. Don't open it. In scriptslist.txt, type nate.sh Boot the IFL UFD. Does the script run?
Ok. I now have both a backup and restore script that have worked a few times each. The only difference I can see between this and others is that these don't have extensions. But they seem to work, so I won't question. and What switches do you suggest I use?
If there are no extensions it suggests you saved the file without an extension. I can confirm that behaviour. Just create any restore script without any non default options (switches). As it won't have --uy it won't restore. It will open to IFL and give a warning. Click NO and it will abort. We just want to see if it opens.
