TeraByte Unlimited

I uninstalled IFW v. 2.99 before I installed Suite 3.0. Can I
re-install 2.99 and use both 3.02 and 2.99? I'm having similar LBA
failure problems on my OS Drive. I'd like to use 2.99 just for that
drive. The failures are beyond my abilities to solve.
--
Walter B

I allowed IFW 2.99 to stay on my laptop as well as using 3.02.
Since I was not sure how I would like the new version I wanted 2 options.
Mary

On 9/4/2016 11:41 AM, Walter Blanchard wrote:
> I uninstalled IFW v. 2.99 before I installed Suite 3.0. Can I
> re-install 2.99 and use both 3.02 and 2.99? I'm having similar LBA
> failure problems on my OS Drive. I'd like to use 2.99 just for that
> drive. The failures are beyond my abilities to solve.
>

I know I should have done that, Mary, but I had such confidence in TBU
which I have been using since the first iteration of IFW many years ago
that I uninstalled 2.99 before installing 3.0.

What I want to know is whether I can still reinstall 2.99 without doing
any harm to 3.02 and use it for that one drive that has my OS on it.

I did get 3.02 to work correctly on that drive yesterday after I blindly
used the chkdsk c: /r on a box that has a new UEFI motherboard, GPT
drives, and Windows 10 upgraded from Win 7, all at the same time. In
the past when I was actively doing a lot of external beta testing for
several companies for both software and OS betas, I would have been in a
position to be current. I'm 83 now, and haven't done any testing since
Windows 7. Much has changed, and I am woefully out of touch.

I'll try 3.02 again later this week, saving the image to a different
external drive. Maybe it's fixed; maybe yesterday's success was a fluke.


On 9/4/2016 12:56 PM, MJNelson wrote:
> I allowed IFW 2.99 to stay on my laptop as well as using 3.02.
> Since I was not sure how I would like the new version I wanted 2 options.
> Mary
>
> On 9/4/2016 11:41 AM, Walter Blanchard wrote:
>> I uninstalled IFW v. 2.99 before I installed Suite 3.0. Can I
>> re-install 2.99 and use both 3.02 and 2.99? I'm having similar LBA
>> failure problems on my OS Drive. I'd like to use 2.99 just for that
>> drive. The failures are beyond my abilities to solve.
>>
>
>

--
Walter B

lba read/write errors would most likely be cable or drive going bad.

validation failures, memory (although byte-for-byte failure on non-DRAT
drives are becoming more common - that option may be turn off on those in
the future).


"Walter Blanchard" wrote in message news:12467@public.image...

I made a small change in the name. That allowed me to install both.
Maybe that would work in reverse.
Mary

On 9/5/2016 11:14 AM, Walter Blanchard wrote:
> I know I should have done that, Mary, but I had such confidence in TBU
> which I have been using since the first iteration of IFW many years ago
> that I uninstalled 2.99 before installing 3.0.
>
> What I want to know is whether I can still reinstall 2.99 without doing
> any harm to 3.02 and use it for that one drive that has my OS on it.
>
> I did get 3.02 to work correctly on that drive yesterday after I blindly
> used the chkdsk c: /r on a box that has a new UEFI motherboard, GPT
> drives, and Windows 10 upgraded from Win 7, all at the same time. In
> the past when I was actively doing a lot of external beta testing for
> several companies for both software and OS betas, I would have been in a
> position to be current. I'm 83 now, and haven't done any testing since
> Windows 7. Much has changed, and I am woefully out of touch.
>
> I'll try 3.02 again later this week, saving the image to a different
> external drive. Maybe it's fixed; maybe yesterday's success was a fluke.
>
>
> On 9/4/2016 12:56 PM, MJNelson wrote:
>> I allowed IFW 2.99 to stay on my laptop as well as using 3.02.
>> Since I was not sure how I would like the new version I wanted 2 options.
>> Mary
>>
>> On 9/4/2016 11:41 AM, Walter Blanchard wrote:
>>> I uninstalled IFW v. 2.99 before I installed Suite 3.0. Can I
>>> re-install 2.99 and use both 3.02 and 2.99? I'm having similar LBA
>>> failure problems on my OS Drive. I'd like to use 2.99 just for that
>>> drive. The failures are beyond my abilities to solve.
>>>
>>
>>
>

Thanks, but doesn't answer the original question: can I now re-install
IFW v.2.99 without doing any harm to v.3.02?

On 9/5/2016 1:33 PM, TeraByte Support wrote:
> lba read/write errors would most likely be cable or drive going bad.
>
> validation failures, memory (although byte-for-byte failure on non-DRAT
> drives are becoming more common - that option may be turn off on those in
> the future).
>
>
> "Walter Blanchard" wrote in message news:12467@public.image...
>
>

--
Walter B

Walter B wrote:
> Thanks, but doesn't answer the original question: can I now re-install
> IFW v.2.99 without doing any harm to v.3.02?
>

Walter,

Yes, sort of. See...

http://www.terabyteunlimited.com/ucf/vi ... f=4&t=2267

Thanks, Brian. I see the "sort of." Note the confusion in the two
sentences below:
1."If you uninstall V2 after installing V3 it will remove PHYLock. There
is no need to reboot here, just reinstall version 3, again no need to
reboot since the PHYLock driver is the same (that is the only reason for
the reboot requirement)."

2."If you install V2 after V3 is installed, the PHYLock version will be
replaced. It's recommended to not install PHYLock with the V2
installation. If you end up uninstalling V3, PHYlock will be removed and
V2 must be reinstalled."

Notice that in sentence 1, it says the PHYLock driver is the same. In
sentence 12, it says the PHYLock version will be replaced. Sentence 2,
at least as I interpret it, means to me that the PHYLock versions are
NOT the same.

On 9/7/2016 8:41 PM, Brian K wrote:
> Walter B wrote:
>> Thanks, but doesn't answer the original question: can I now re-install
>> IFW v.2.99 without doing any harm to v.3.02?
>>
>
> Walter,
>
> Yes, sort of. See...
>
> [
> viewtopic.php?f=4&t=2267
> ](http://www.terabyteunlimited.com/ucf/viewtopic.php?f=4&t=2267)
>
>
>

--
Walter B

They are not the same. The reason #1 says the PHYLock driver is the same is because you first installed V2 (V2 PHYLock installed), then you installed V3 (V3 PHYLock installed), then you uninstalled V2 (which uninstalls V3 PHYLock), and then you reinstalled V3 (which reinstalls V3 PHYLock -- the same version that V2 uninstalled -- no reboot needed).

You can reinstall V2 and not install PHYLock (so the V3 PHYLock remains installed) or you can just reinstall V2 normally and then reinstall V3 normally (selecting to not uninstall V2 and then rebooting when finished). Note that there are other considerations as well. For example, desktop shortcuts, TBIView, TBIMount, TBOSDT, context menus, etc.

Thanks for the clarification.

On 9/8/2016 2:39 PM, TeraByte Support (PP) wrote:
> They are not the same. The reason #1 says the PHYLock driver is the same is because you first installed V2 (V2 PHYLock installed), then you installed V3 (V3 PHYLock installed), then you uninstalled V2 (which uninstalls V3 PHYLock), and then you reinstalled V3 (which reinstalls V3 PHYLock -- the same version that V2 uninstalled -- no reboot needed).
>
> You can reinstall V2 and not install PHYLock (so the V3 PHYLock remains installed) or you can just reinstall V2 normally and then reinstall V3 normally (selecting to not uninstall V2 and then rebooting when finished). Note that there are other considerations as well. For example, desktop shortcuts, TBIView, TBIMount, TBOSDT, context menus, etc.
>
>

--
Walter B