siteepic.blogg.se

1. Techtool pro 9.6 fails to install drivers#
2. Techtool pro 9.6 fails to install update#
3. Techtool pro 9.6 fails to install download#

Authorized users only (password protected).

Techtool pro 9.6 fails to install download#

Click here to download Software.Ĭloning Tool– for Tech Tool Cloning Installations.

Techtool pro 9.6 fails to install update#

VOCOM I Device Driver / Firmware Update (Version 2.5.0.0)

Techtool pro 9.6 fails to install drivers#

The following Software Drivers and Documentation are available to Download for PTT:

Note: Do not use long expansion cables with USB hubs.Ĭompatible Adapter Matrix for TT 2. VOCOM, NEXIQ, J-PRO, DEARBORN, Cables: 6 pin, 9 pin and 16 pin).Īdapters and Firmware Updates: Need to find out which adapter is compatible with Premium Tech Tool? See the Adapter Matrix below for more information and ensure that the latest released firmware is downloaded to the communication unit. In my mind, this raises the possibility that the TTP 10 volume rebuild tool may have a bug that allows it to sometimes screw up the metadata of a fusion drive's logical volume group structure by leaving out the SSD capacity.Guide: Click here to access information on connection tips, identifying your truck’s electrical system, and for a description of the various connectors, cables, and adapters (ie. I booted back to the the e-drive and used Disk Utility and Disk warrior on my system drive when unmounted. The operation concluded with "success" and the system drive is now working normally. The last two lines of the Disk Utility fsck log were something like "restoring size of logical volume to 311,xxx,xxx,xxx" and "expanding partition". The error that it reported in its log, which I unfortunately didn't keep to append here, basically said that the size of the logical volume group for the fusion drive only included the HDD, not the SSD. I tried to do a live First Aid on my system drive using Apple Disk Utility. Apple disk utility showed the fusion drive as NOT was still all one volume. What I got instead was apparently a clean boot into my normal system drive not the recovery partition, not the e-drive (and yes I was holding down the right keys). I force-quit Disk Utility, powered the machine down by force with the power button, and tried to reboot into the system disk recovery portion using command-R (or whatever it is). Disk Utility hung permanently during an fsck. I ran Apple Disk Utility on my system drive (still booted from e-drive). Disk Warrior 5.1 is read-only until the very last step 10, which it never reached, so it didn't screw anything up. Disk Warrior 5.1 hung for 40 minutes in step 8. When I tried Disk Warrior 5.1, I got an apple "the disk you have attached is not formatted" error dialog when I tried to rebuild my system drive. Then it suddenly quit, with a "Recheck Failed" message with no further explanation. It looked like it was working, going through the steps up until Recheck. Thinking that it worked, I decided to use TTP volume rebuild on my Fusion Drive (which, recall, i was not booted from), which is also my system drive. I fsck'd the rebuilt drive and all was well. It worked fine.went through all of its steps in the log and then said "No Errors Found".

I experimented with the Techtool Pro Volume Rebuild on an unimportant USB HDD. I was booted off my e-drive, which is an external SSD. This time I decided to try Techtool Pro 10 volume rebuild. I usually use DiskWarrior 5.1 to compress the directory/B-Tree etc. The Volume Rebuild tool on TTP 10.0.1 wrecked my fusion drive by messing up some metadata in the logical volume group header having to do with the size.