12 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHMy portable durametric setup
Leading reported evidence
Use durametric
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
I use Durametric on a Windows XP VM on my Macbook Air - I have a snapshot of the VM booted and sitting at the desktop, so getting the app launched is pretty much immediate.
Leading evidence: 'Use durametric' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Run win 8.1 and had no issues at all' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I just loaded Ver 6 software on my Surface Pro 3 running Win 8.1 and had no issues at all
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
After my research and testing I have been able to get it working on all of the Win 8 devices.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
I use Durametric on a Windows XP VM on my Macbook Air - I have a snapshot of the VM booted and sitting at the desktop, so getting the app launched is pretty much immediate.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
12 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
What was odd about this was that it worked at one time and then stopped.
I bought a Rotor Windows Tablet 7" but anything that runs windows 8.1 will work.
Just make sure you follow these simple instructions to make the hook up work - courtesy of user mHarris660 on Planet9
"
Durametric software and Windows 8 tablet fix
Not real sure where to put this but after months of working with the Durametric cable and a Windows Surface Pro tablet I was finally able to get it to work. What was odd about this was that it worked at one time and then stopped. The symptom was the logo coming up and them a windows error. I have 4 Windows 8 devices and the Durametric software only worked on one of those devices. After my research and testing I have been able to get it working on all of the Win 8 devices. This will not work on the Windows RT devices. Now for the fix.
The first step may not be necessary for everyone, it's sort of weird that way. You can try it, it's easy to turn on and off and doesn't hurt anything. Go to the control panel and then add remove programs. On the left you will see "manage windows features". Go there and turn off Net 4.5 support. Later when you get the software running you can turn this back on.
The second step is to uninstall the software and drivers through add/remove program in the control panel. Have your cable ready for the next steps. Download the software and the drivers but do not install them yet. Install the software first then plug in the cable. When the cable is plugged in install the drivers. That's it. You can go back and turn on the NET 4.5 framework back on. This procedure has worked on my tablet and 3 Windows 8 laptops. I think the key is needing the cable plugged in during the driver install.
It really is much easier than it sounds and only takes a couple of minutes so if you were like me, loosing Durametric/Win 8 compatibility, try this. Hope this saves some frustration for the few that seem to have this glitch."
I use Durametric on a Windows XP VM on my Macbook Air - I have a snapshot of the VM booted and sitting at the desktop, so getting the app launched is pretty much immediate. I can't leave Durametric running as it seems prone to crash whenever the cable gets disconnected...
Durametric.com
Please buy the original cable from them.
They're a tiny business and without supporting them they will no longer be able to produce / develop s/w for the constantly shifting OS requirements....
I just loaded Ver 6 software on my Surface Pro 3 running Win 8.1 and had no issues at all
And yes, DO NOT buy a clone cable
Support Durametric and I have heard stories of the clone cables doing damage to the car
IIRC, the clone cables also won't work with the newer software
Any chance you have a PIWIS account to see how well it's IE works with the diagrams? That would be so much better than lugging around my 07 MBP and firing up VirtualBox when I need to plug in. Be even better if the PIWIS site plays nice.
This is a source reference. Confirm exact model applicability in the original material.
