PDA

View Full Version : NTFS install creating corrupt system files


sebastian
06-04-08, 12:32 PM
usr/lib/libssl1137.dylib

The file above is corrupt in my system - I know it is part of NTFS for mac because I did a google search and it came up on a chinese website. Something to do with registration or limiting use on the trial version I believe. It keeps coming up as corrupt in Virus barrier scans but I'm not sure what to do about it. I managed to dig through and delete the file when I uninstalled NFTS. I ran virus barrier and disk utility permission repair to see what would happen, system was fine and the file was not detected by virus barrier. I reinstalled NTFS but the corrupt file came right back. Any ideas? I don't really want to have corrupt unix executable files in my system and I'd rather not have to reinstall OSX. The only thing that works is leaving NTFS of my system but I'd like to be able to use software I've paid for. Don't get me wrong, I love this software as I switch 4 external hard drives between mac's and pc's and it's easier to have NTFS support on 2 macs than having to install macdrive on all the pc's I want to connect my hard drives to.

MrDiscuss
29-10-08, 10:59 AM
Hi Sebastian
I got the same error showing up after a Virus Barrier X5 scan. NTFS is also installed. I removed the file "libssl1137.dylib" from the system folder about 2 months ago and nothing happened. My guess is that is better to have a missing file than a corrupt one. I trust the VirusBarrier X5 scan engine because it picks up corrupted files correctly.
To be precise I still have an issue with "coraudiod not responding" but I take notice of this activity monitor observation for over 6 months now and it does not affect my computer - at least not in a noticeable way. I dont think it is related to the libssl1137 file.
I will let you know if I find a problem with the deleted libssl1137 file.
Are there other people with this issue?
Regards
MrDiscuss
MacPro 2.6/5GB/2TBraid0 w/AppleRaidCard/Leopard10.5.5(9F33)/Darwin9.5.0

mikebore
30-10-08, 02:40 AM
I have the same problem, but have been ignoring it. I will try deleting it and see what happens.