Running IFL on BIOS without a Boot Disk

I've edited my setupifl.bat to...

Code:

@echo off
CD /d %~dp0
::
:: TARGETDIR parameter must be set to a drive letter located on boot drive 

It can run from a double click or Run as Admin.

 

This is my current RESTORE.tbs:

Code:

sub main()
  exec("/tbu/imagel --r --uy --um --d:l0@0x1 --f:l0@0x246:^"/win7x64^" --v --t --rft --log:0 --rb:4 --nvn:^"^"", 1)
end sub

Can I use it on different machines and different HDD as long as I keep the same partitioning layout (MBR and Legacy)?:
1. Primary active (OS) partition
Extended
2. Data partition
3. Small hidden partition

 

I think setupifl.bat is the only one that requires a double click. Annoying exception.

 

You will have to edit f:l0@0x246:
The logical volume on another HD is very unlikely to have that same partition signature.
No big deal once you know the new partition signature. Also you will need to confirm the OS partition is 0x1

 

Is there a quick way to see those parameters? A tool or something?

 

You can see them in IFW or boot an IFL boot disk. Or run tbosdtw.exe and enter...

list HD 0

The ID column is the partition signature.

 

Have you tested run_ifl.bat ?

Click Cancel when the Validate commences.

 

Got it. Oh my... You have a deep knowledge of many imaging software don't you? Awesome.

 

But if I run it the machine is going to restart no? I only have one machine for the moment.

 

OK

 

Well can I conclude I can carry IFL folder with the rest of sub-folders on every machine, then edit RESTORE.tbs accordingly and then run setupifl.bat to create the other 3 files inside C:\IFLBOOT
Right?

 

Correct. Edit RESTORE.tbs. Then run setupifl.bat. This needs to be done on each computer.

 

I won't confuse you with details but you can use tbosdt to copy a new tbs restore script into an existing ifl.bin. We can do that much later when you are comfortable with bootfile.

 

Good to know. Now I need to figure out how to create a BACKUP.tbs and gather all and put it to work.

 

OK, this is much more advanced indeed. I appreciate a lot what you are doing for me Brian, thank you thank you very much.

 

Btw did you know, well I believe you actually don't (lol), I translated IFL, IFW and IFD to Spanish lang? some years ago. I had contact with David F. iirc. to do all the work which lasted several days or weeks.

 

I forgot. Sometimes ifl.bin won't run because it is fragmented after creation. I defragment it with Defraggler. No further trouble.

df.exe C:\IFLBOOT\ifl.bin

 

I didn't know. Nice.

 

Noted and thanks for the tip.

 

I'm planning to use Defraggler portable, for convenience.

 

Brian I don't want to abuse your precious time, besides it's late here. So I will come back soon again to keep bugging you on this. Have a good day and take care.

 

That's what I used.

 

Hello Brian.

Now I created BACKUP.tbs file, do I need to add any extra parameters to it?:

Code:

sub main()
  exec("/tbu/imagel --b --d:l0@0x1 --f:l0@0x246:^"/win7x64^" --v --log:0 --rb:4", 1)
end sub

Does my IFL.ini file needs to be edited?

Code:

[Options]
TimeZone=MEX+6

[License]
ProductKey=XXXX-YYYY-ZZZZ

[BACKUP_DEFAULTS]
Compression=14
PostValidate=1

[RESTORE_DEFAULTS]
WriteMBR=1
RFT=1
PreValidate=0x1

 

In the backup script, can you add
--uy --um and --comp:14
The IFL.ini will not add this to a script.

IFL.ini is fine.

 

Got it:

Code:

sub main()
  exec("/tbu/imagel --b --uy --um --d:l0@0x1 --f:l0@0x246:^"/win7x64^" --v --comp:14 --log:0 --rb:4", 1)
end sub

Then what's the role of IFL.ini?