Is This a Bug in IFL and/or TBIView?
Posted: Mon May 01, 2017 5:46 pm
OS = Windows 7 Pro x64 SP1
IFL = v3.06
TBIView = v4.39.0
User Account Control (UAC) = enabled
Scenario:
I am using an SSD drive. I image off the boot partition of the SSD using IFL bootdisk. When IFL is creating the image file(s) I have it create them on a separate partition of the SSD (one that I reserve only for use with tbi files). Once the image is made I reboot into the system. I want to check the image just made can be opened in TBIView. I double-click on the tbi file just made (in theory the files should open in TBIView) and then I get the following series of error messages:
---------------------------
TBIView
---------------------------
Insert media 1 containing file G:\Win 7 SSD\2017-05-01 Win7 Current Working System SSD\2017-05-01 Win7 Current Working System SSD.tbi
---------------------------
OK Cancel
---------------------------
If, in response to that error message, I click on the OK button then the same error dialogue is still shown. If I click on the Cancel button then the following error message appears:
---------------------------
TBIView
---------------------------
Unable to open file
---------------------------
OK
---------------------------
I have only one option, click on the OK button. When I do that the following error message appears:
---------------------------
TBIView
---------------------------
Error 6 opening file G:\Win 7 SSD\2017-05-01 Win7 Current Working System SSD\2017-05-01 Win7 Current Working System SSD.tbi.
This usually means the file is not accessible or the file is invalid.
Ensure the file exists and the user has read permissions; Update to the latest version of TBIView; Consider checking or replacing system RAM.
---------------------------
OK
---------------------------
I have no option but to click the OK button. When I do that the dialogue completely disappears. I should explicitly say that the files do in fact exist, all in one folder, on the SSD.
After a lot of struggling with this I found the following:
If I disable UAC, reboot the system, then double-click on the tbi file it opens in TBIView without difficulty. However, there is no way that I want to run the system without UAC running. So I re-enabled UAC, rebooted and looked for a solution elsewhere. What I found was that I had to take ownership of the folder containing the tbi files and, crucially, while doing that, had to select to "Replace owner on subcontainers and objects (and click the Apply button)." This despite the fact that the user account I use on the system is an Administrator account. It's almost like I'm having to reaffirm that the ownership of the tbi files in the folder are to have their ownership belong to Administrators (of which my own account is one) - which should be the case by default.
Once I do the above, taking ownership of the folder and all the files in it, then I can double-click on the tbi file and it will open okay in TBIView.
So, by my reckoning, something is going far wrong when I use IFL to create a image of the boot partition. Somehow, by some means, the ownership of the tbi files isn't being correctly assigned to Administrators. So my question is, is this a bug in IFL? I never had this problem before when using earlier versions of IFL (but, that said, at those times I was using a HDD not an SSD).
(I should also add that as part of my experimenting and trying to find a solution to this I did try explicitly launching TBIView.exe as an Administrator and when I did that TBIView would then open the files - however, that isn't a very convenient way of managing things. The taking ownership of the tbi files is by far the better solution. But why should I be having to manually do that? Seems to me there is a bug somewhere.)
IFL = v3.06
TBIView = v4.39.0
User Account Control (UAC) = enabled
Scenario:
I am using an SSD drive. I image off the boot partition of the SSD using IFL bootdisk. When IFL is creating the image file(s) I have it create them on a separate partition of the SSD (one that I reserve only for use with tbi files). Once the image is made I reboot into the system. I want to check the image just made can be opened in TBIView. I double-click on the tbi file just made (in theory the files should open in TBIView) and then I get the following series of error messages:
---------------------------
TBIView
---------------------------
Insert media 1 containing file G:\Win 7 SSD\2017-05-01 Win7 Current Working System SSD\2017-05-01 Win7 Current Working System SSD.tbi
---------------------------
OK Cancel
---------------------------
If, in response to that error message, I click on the OK button then the same error dialogue is still shown. If I click on the Cancel button then the following error message appears:
---------------------------
TBIView
---------------------------
Unable to open file
---------------------------
OK
---------------------------
I have only one option, click on the OK button. When I do that the following error message appears:
---------------------------
TBIView
---------------------------
Error 6 opening file G:\Win 7 SSD\2017-05-01 Win7 Current Working System SSD\2017-05-01 Win7 Current Working System SSD.tbi.
This usually means the file is not accessible or the file is invalid.
Ensure the file exists and the user has read permissions; Update to the latest version of TBIView; Consider checking or replacing system RAM.
---------------------------
OK
---------------------------
I have no option but to click the OK button. When I do that the dialogue completely disappears. I should explicitly say that the files do in fact exist, all in one folder, on the SSD.
After a lot of struggling with this I found the following:
If I disable UAC, reboot the system, then double-click on the tbi file it opens in TBIView without difficulty. However, there is no way that I want to run the system without UAC running. So I re-enabled UAC, rebooted and looked for a solution elsewhere. What I found was that I had to take ownership of the folder containing the tbi files and, crucially, while doing that, had to select to "Replace owner on subcontainers and objects (and click the Apply button)." This despite the fact that the user account I use on the system is an Administrator account. It's almost like I'm having to reaffirm that the ownership of the tbi files in the folder are to have their ownership belong to Administrators (of which my own account is one) - which should be the case by default.
Once I do the above, taking ownership of the folder and all the files in it, then I can double-click on the tbi file and it will open okay in TBIView.
So, by my reckoning, something is going far wrong when I use IFL to create a image of the boot partition. Somehow, by some means, the ownership of the tbi files isn't being correctly assigned to Administrators. So my question is, is this a bug in IFL? I never had this problem before when using earlier versions of IFL (but, that said, at those times I was using a HDD not an SSD).
(I should also add that as part of my experimenting and trying to find a solution to this I did try explicitly launching TBIView.exe as an Administrator and when I did that TBIView would then open the files - however, that isn't a very convenient way of managing things. The taking ownership of the tbi files is by far the better solution. But why should I be having to manually do that? Seems to me there is a bug somewhere.)