Thanks for posting with your issue, I’ll be happy to help!
The 1.5 driver is the latest greatest version, newer than the older 1.4 version. Is there some reason you’re trying to use the older version?
Also, just for public record, our install walkthrough for USB Serial on OS X is at the link below if you’d like to work ahead: http://plugable.com/2011/07/12/instal…
Let’s first verify which kernel extension/driver you’ve got loaded so we can make sure the driver install actually worked by doing:
Note that version 2.0.0 is reported even though I’ve installed 1.5. Please let me know what you find for the command above and the additional detail will help recommend our next steps.
If we find the above driver is loaded, we’ll move on to checking USB serial device enumeration using:
FYI 1.5 was just released 4.8.13, and is recommended as it solved an issue where OS X could crash if all connections using the cable weren’t properly terminated before it was unplugged. I’m not sure of what (if any) issues the sourceforge version you’ve used might have.
i am trying to install the 1.5 version but at the end of the process the installer says: FAILED without any reasons.
My MAC is:
System: OS X 10.8.3 (12D78)
Identificatore modello: MacBookPro8,1
Nome processore: Intel Core i5
Velocità processore: 2,4 GHz
Numero di processori: 1
Numero totale di Core: 2
Cache L2 (per Core): 256 KB
Cache L3: 3 MB
Memoria: 8 GB
Versione Boot ROM: MBP81.0047.B27
Versione SMC (sistema): 1.68f99
I don’t think we’ve seen this particular issue before, and in googling around it seems that the kextcache error 71 is most often due to an existing corrupted kernel extension. Permissions issues also seem like a very real possibility.
As a first step, could you please run the “Verify Disk Permissions” utility in the OS X “Disk Utility,” then try the installation again? If the installation doesn’t work, can you please reply with the output of any folders/files it repairs permissions issues with (I know this may be a lot).
Whether or not the disk permissions tool finds a lot of stuff to work on should help indicate what extension might be having issue if the repair doesn’t solve the problem.