TeraByte Unlimited

NEW SSD
Installed BIU (with UEFIRenDirSafe=1)
Booted from Pen Drive and Installed Windows to a new partition
rebooting started Windows directly.
Used bios to boot into BIU
Went to maintenance mode first ... Efi directory shows BOOt, BootIt, and Windows subrirectories.
got out of maintenance mode. BIU menu shows Windows as only selectable item.
Pressing enter get popup the says something like EFI\Microsoft.001\boot\ ..... file not found (did not write down whole file name)
going back to maintenance mode. EFI directory now only shows Boot and BootIt as subdirectories.
Microsoft directory is gone.
---------------------------------------
I did it again,redid the windows install over the existing partition.
Rebooting started Windows
Used BIOS to boot into BIU
Went to maintenance mode first ... Efi directory shows BOOt, BootIt, and Windows subrirectories. Scripting also shows those subdirectories are available as well.
this time I used scripting to copy the EFI\Microsoft directory to \XEFI\Microsoft for safe keeping.
got out of maintenance mode. BIU menu shows 2 Windows as selectable item. Both entries loading same file from exactly same place.
Pressing enter get popup the says something like EFI\Microsoft.001\boot\ ..... file not found (did not write down whole file name)
going back to maintenance mode. EFI directory now only shows Boot and BootIt as subdirectories.
\EFI\Microsoft directory is gone. but \XEFI\Microsoft still exists.

Why is the Microsoft directory disappearing when using BIU ?
Note: I never saw a Microsoft.001 directory anywhere, only Microsoft. But boot items defaulted to Microsoft.001
Any ideas or additional things to test?

Simple, you can't use UEFIRenDirSafe=1 because your UEFI is not safe for
renaming dirs.

You'll want to chkdsk /f of fsck the efi system partition since the old dir
is just taking up space.


"tas3086" wrote in message news:[email protected]...

NEW SSD
Installed BIU (with UEFIRenDirSafe=1)
Booted from Pen Drive and Installed Windows to a new partition
rebooting started Windows directly.
Used bios to boot into BIU
Went to maintenance mode first ... Efi directory shows BOOt, BootIt, and
Windows subrirectories.
got out of maintenance mode. BIU menu shows Windows as only selectable
item.
Pressing enter get popup the says something like EFI\Microsoft.001\boot\
...... file not found (did not write down whole file name)
going back to maintenance mode. EFI directory now only shows Boot and BootIt
as subdirectories.
Microsoft directory is gone.
---------------------------------------
I did it again,redid the windows install over the existing partition.
Rebooting started Windows
Used BIOS to boot into BIU
Went to maintenance mode first ... Efi directory shows BOOt, BootIt, and
Windows subrirectories. Scripting also shows those subdirectories are
available as well.
this time I used scripting to copy the EFI\Microsoft directory to
\XEFI\Microsoft for safe keeping.
got out of maintenance mode. BIU menu shows 2 Windows as selectable item.
Both entries loading same file from exactly same place.
Pressing enter get popup the says something like EFI\Microsoft.001\boot\
...... file not found (did not write down whole file name)
going back to maintenance mode. EFI directory now only shows Boot and BootIt
as subdirectories.
\EFI\Microsoft directory is gone. but \XEFI\Microsoft still exists.

Why is the Microsoft directory disappearing when using BIU ?
Note: I never saw a Microsoft.001 directory anywhere, only Microsoft. But
boot items defaulted to Microsoft.001
Any ideas or additional things to test?

BIU will not start unless that option is set. The system hangs. Anything else I can do or try?

Why can I add, copy, and delete directories through the script biu process, and not biu itself with that option set?

You can uncheck the "rename' flag. Windows can boot even if the dir is Microsoft.001. At least, it works for me.

copy and create is not the same as "rename". "ren test test.001"


"tas3086" wrote in message news:[email protected]...

BIU will not start unless that option is set. The system hangs. Anything
else I can do or try?

Why can I add, copy, and delete directories through the script biu process,
and not biu itself with that option set?

BTW did you ever list your machine or mobo make/model and bios version?

"tas3086" wrote in message news:[email protected]...

BIU will not start unless that option is set. The system hangs. Anything
else I can do or try?

Why can I add, copy, and delete directories through the script biu process,
and not biu itself with that option set?

TeraByte Support wrote:
> BTW did you ever list your machine or mobo make/model and bios version?
Asrock z97 Extrreme6 Bios:2.80 16G memory - Windows 10 pro
Should I let Asrock know, Is this a known industry problem? Is it their problem? Or is it Terabytes implementation of a the rename command?
-------------
Eric: Thank you for your Rename suggestion. Turned off letting BIU handle EFS files. Remane option no longer available, as expected and desired.
BIU now working and Windows now working via BIU. Managing multiple os's will be a problem however.

Tried the rename directory test under scripting. Yep, the directory disappears. Is there an equivalent of "scandisk/checkdsk" under TBOS scripting somewhere? I don't think that windows chkdsk will work !

The problem is in the UEFI code (FAT32 support was provided by Intel). They
should all be using the same EDK code base without too many customizations,
so when bugs fixed and applied, should be easy to roll out for them and bugs
would be fixed for everyone. I'll go ahead and report it, I guess I could
fix it, but the maintainer could do it in a jiffy.

You can use linux fsck -f or in windows use diskpart to apply a drive letter
to run chkdsk /f on it.



"tas3086" wrote in message news:[email protected]...

TeraByte Support wrote:
> BTW did you ever list your machine or mobo make/model and bios version?
Asrock z97 Extrreme6 Bios:2.80 16G memory - Windows 10 pro
Should I let Asrock know, Is this a known industry problem? Is it their
problem? Or is it Terabytes implementation of a the rename command?
-------------
Eric: Thank you for your Rename suggestion. Turned off letting BIU handle
EFS files. Remane option no longer available, as expected and desired.
BIU now working and Windows now working via BIU. Managing multiple os's
will be a problem however.

Tried the rename directory test under scripting. Yep, the directory
disappears. Is there an equivalent of "scandisk/checkdsk" under TBOS
scripting somewhere? I don't think that windows chkdsk will work !

TeraByte Support wrote:
> The problem is in the UEFI code (FAT32 support was provided by Intel).
> They should all be using the same EDK code base without too many customizations, so when bugs fixed and applied, should be easy to roll out for them and bugs would be fixed for everyone. I'll go ahead and report it, I guess I could fix it, but the maintainer could do it in a jiffy.

I reported it as a problem to AsRock Support. Evidently they do not see it as a problem in their motherboard, as there I no problem with the operation aspects of the motherboard: "You did not mentioned anything about having problems with this motherboard. Please provide details about your problem or complete description of the implemented option you are looking for."

Any ideas how I can reply to them in terms that they would understand and would want to fix the problem. Thanks

PS: Although it is messy, it appears that managing EFS files and associated windows files myself is working, but would be nicer if BIU could do it.
BIU - NICE JOB !

tas3086 wrote:
> PS: Although it is messy, it appears that managing EFS files and associated windows
> files myself is working, but would be nicer if BIU could do it.

Depending on how you're having to manually manage the files, is it something you could create a .run file (or .tbs script) for that would run as part of the boot item? Maybe it could process some (or all) of it and simplify things a bit.