Image For Windows

Maybe it has something to do with the password. I don't use passwords. Sorry, no other ideas if you need a password.

 

I just created an image with a password. TBS script was created and the script ran successfully. I'll keep thinking.

Can you post your complete script? All lines. It should have 3. You line is quite different from mine. Mine is...

Code:

sub main()
  exec("/tbu/imagel --v --f:{5E7D3ED2-5C5C-EFFA-3EF5-855B7573FFFF}@0x2:^"/passwordtest^" --opw:6260E0D0C04D73", 1)
end sub

Edit... in Windows, open the .tbs with Notepad.

 

Here's the contents. But it's not formatted at all like yours. I followed the directions exactly, though, so I'm not sure why that is. Which version of IFL are you using; CL or GUI?

 

Nate, I'm using IFL GUI 3.31. What are you using?

 

Same. UGH!!

 

Can you try making a script with an .sh file extension instead of .tbs.

validate.sh

Here is mine. There are 2 lines.

Code:

#! /bin/sh
/tbu/imagel --v --f:l0@0x1:"/metadata" --sp:0x4 --rb:4

 

I end up with:

Should I try to run it?

 

Looks good. Run it.

 

SUCCESS!!!

/me does the Carlton!

I ran the script, but the first time it saw the script but did nothing. I had to enter the password switch. Then when I rebooted it saw the script and ran it, rebooting automatically when done!

What's next?

 

In scriptslist.txt delete any text and type...

validate.sh

Boot IFL. Let me know if this has already been done.

 

It has. That was what I was describing in my previous post.

 

OK. Next, delete the text from scriptslist.txt. Make a restore.sh (include your password) and post the result.

 

It worked. But there are a few things worth mentioning.

1. The restore command doesn't like the --rb:4 switch
2. It wasn't really automatic, because I still got prompted for confirmations
3. If there a "only write changes" CL option?

Here is my script

 

I'd try...

Code:

#! /bin/sh
/tbu/imagel --r --uy --d:l1 --f:l0@0x3:"/System-07-13-2019-1544" --opw:6E2767A67664F4045677B782A3427B --sp:0x1,0x2 --wco --rb:4

Press Enter after typing --rb:4 to put the cursor on a blank line.

Edit... just added --wco

 

It worked perfectly, but that was before I saw the --wco switch. What doesd it do?

 

--wco is Write Changes Only. Good for SSDs. I wouldn't bother with it if restoring to a HD.

 

Great news. The next step is to copy the IFL UFD partition to your HD/SSD.

Do you have BIBM installed? Unlimited primaries?

Copy the IFL UFD partition to 150 MiB of Free Space on HD0 or select 150 MiB resize on the Options page of the Copy.

 

BiBM is installed, and it's working (although I definitely need to tweak some things). It does boot my primary, but not the new IFL partition, but that can be accessed through the uefi menu. BiBM is set up to be my primary partition manager.

By the way, the --wco switch does nothing for me; there's no difference in speed at all.

 

--wco doesn't speed things up. It allows only changed sectors to be restored. So instead of writing 20 GB to your SSD, you might only write 200 MB. The restore time is unchanged as all sectors have to be read to see if they have changed.

The Boot Item for IFL should boot IFL. Click Boot Edit, this brings up the Boot Menu. Click Add
Identity IFL (type it in)
HD0
Boot... select the IFL partition.
OK, OK.

Does it work now?

 

Negative. It does not.

 

What partitions do you have on HD0? Only one HD? IFL is on the same drive as BIBM and Win10? Any partitions on HD1?

In BIBM Settings remove the Tick in Limit Primaries.
Restart into BIBM
Boot Edit
select the IFL Boot Item
Edit
In MBR Details move IFL to Slot 0)
Select the other partitions (one at a time) and click Clear
MBR Details should now have only one slot filled. IFL

Does IFL boot from the Boot Menu?

 

Interestingly enough, I was able to get it to boot (kind of). When I try to boot into it I'm told that it's not a bootable disc and to press any key. But if do that then IFL boots like it's supposed to. If I use BiBM to emulate any keypress at all, them IFL boots fine.

 

I suspect we have different setups. Can you list the partitions (from Partition Work) on HD0 and HD1?

Edit.... partition sizes too.

 

https://i.postimg.cc/65vss1kx/20190713-230522.jpg

I have no bootable partitions on any other disk.

 

Many thanks. Your IFL partition is EFI when it should be FAT-16 or FAT-32 depending on the size of your UFD. FAT-32 if the UFD is larger than 4 GB.

In Windows Explorer, what is the File System of the UFD partition? I've never seen this before so I've no idea how it happened. It could be due to choosing GPT-UEFI System Partition when making the UFD. Who knows.

Save your UFD scripts to your HD and make another UFD. Make sure you have...

USB Layout... Partition - FAT/FAT32 partition
Geometry Calculation Method... Use Device

Copy your scripts to the new UFD and make sure they work. Delete the IFL partition on the HD and copy the UFD partition (partition not drive) to the 155 MiB of Free Space. We must be close now. The IFL partition on the HD must be FAT-16 or 32.