by tas3086 » Sat Aug 04, 2018 9:58 pm
TeraByte Support wrote:
> You can do all the important stuff like multi-booting, partition
> work operations, disk imaging, including run scripting. What you can't do
> is run scripts from a boot item or from the desktop (I don't believe). To
> run scripts, you would choose scripting, then use the mount command to
> mount a partition and run it from there, but the more advanced scripts may need a
> particular drive 0: 1: 2:, etc.. so there is a potential conflict, we'll
> make a list available.
Thank you, I understand all of that. But with systems with many multiple hard drives, and many partitions on each, it is very difficult to keep track of drive numbers and partition id's in order to do a OPEN FS drive: phydrivenum [partitionid] (MOUNT)command. Especially when drives are constantly being added and removed. For this reason I created a script to determine/show all disk and partition numbers, and pass those as parameters to a number of other scripts that handle various mounting configurations and work efforts.
Again, with only the UEFIRenDirSafe=1 option everything worked with stated limitations, in version 1.01 . 1.03 introduced the bootit.dat problem and the required the UEFINoRemount=1 option to at least get into maintenance mode, where scripts are not easily available without yet another mount.
Like I said, I'm disappointed in BIU and UEFI not being kept current and standard by the motherboard manufacturers.
Luckily my motherboard allows easy selection of booting BIBM or BIU, so I may be able to use BIBM to setup BIU configurations and then boot over to BIU to test things out. Time will tell. Keep us informed of the evolving conflicts. Maybe AsRock will update their Bios someday too, as UEFI applications like yours continue to be developed.
Thank you for your information. Your products and support are still the best in the industry.