Q: Is there a way to completely disable AirPort?

mwille64 wrote:

 

Csound,

 

Communication is a two way process and it seems we both do not comprehend what we have to say to each other.  Maybe in my case the excuse is that English is not my native language.

To make it clear, I had no intention to offend you.

In matter of fact I felt almost offended by your first remark about my lack of testing and that I'm quite foolish about that...

"You should also know that by refusing to properly test you are the obstruction to the search for a solution, but that is your decision (foolish one at that)."

And I still can't see why you have commented regarding testing anyway.

Then I will endeveaour to explain why:

You have 3rd party modifications to OS X loading, Moom is one, it is capable of causing the issue you describe. That does not mean that it is the cause, but you refuse to perform a simple test because you think it is "irrelevant"

You also fail to understand why, as an IT person testing software for possible unwanted effects it is important not to use the machine that you actually use day to day for work. The simplest (and cheapest) method of achieving this is to connect an external drive, clone the internal to it, boot from the clone and do the tests of new software on it. That way you have 2 things, a control (the internal) and your day to day Mac is not compromised.

I would like to know how your Mac runs when it is back to the way Apple intended.

mwille64 wrote:

 

I'm just not claiming that with all my experience that I will never fall for it though.

It's easier than you may think to avoid malware. However, if you really want some kind of second safety net, you can't do better than ClamXav. It will not cause problems and can be used for manual scans of things that you aren't sure about. At this time, this really won't do you much good, since both ClamXav and Mac OS X recognize all currently known Mac malware, but perhaps the redundancy will give you peace of mind.

I don't recommend setting ClamXav to scan your hard drive periodically or anything like that. Just use it to manually scan things you're unsure of, or at most, set it to automatically scan anything that gets downloaded into your Downloads folder.

In any case, my point in this response to Csound was that a back up is not a solution to preventing an attack.

A backup is, of course, not a solution for preventing an attack. However, it's an important tool to have if you think you might have been infected by something. You can restore your system to a known good state prior to opening whatever questionable app or installer you think may have been malicious. Good backups that store multiple states over time, like a Time Machine backup, are key to recovering if you do happen to get infected by some future malware.

And keep in mind... nothing can protect you from future, undiscovered malware except for your own behavior.

I am no longer offering advice, please ignore any previous advice.

Still Sleep Wake Failures with 10.10.2. I removed ALL software except apps that don't run background tasks (need to work after all and I don't have spare  MacBooks in the locker). I also made sure all apps are closed before I send the machine to sleep. It all did not make any difference.

I have to assume that the issue is indeed AirPort/OSX.

No problem Mwille64!

Have fun with your Mac.

To Flexier- Hi!

Kindly start a new thread where you could state your own problem. You will have a better chance that your specific problem will be noticed and subsequently addressed than by jumping on somebody else's wagon. The serious fixers don't want to read through pages and pages of posts just to notice that somewhere a new problem is lurking. In that time, they could have helped possibly six others.

Enjoy using your Macs

Leo

Anybody can make a mistake, no problem. I just wanted to point the new poster in the right direction!

When you did the update, did you download and use the Update Combo? As stated before, I try to use a Combo update as it normally fixes a lot of possible problems, permissions, etc.

The last issue could be that there could be some 'remnants' remaining of crapware that you have removed. Shout when you need advice with that, or you can also search for a solution which Linc Davis had about 10 days ago to help somebody. But to start of, what you could do is to start up in Safe Mode. You don't have to log in as a user. Leave the Mac in that mode for 30 minutes or so. During that time, some scripting routines are run which do some maintenance on the System, permissions are checked and corrected etc. Thereafter do a normal restart. If an SSD is used, ensure in your power saving preference setting that it is not set to sleep whenever possible, then start it tonight by pressing Alt so that you can see your boot options. Leave the SSD powered on that way. You can close the lid. During that time, essential routines will be run on the SSD to check and verify it's integrity and perform cleaning. Restart your Mac normally the next morning.

Have fun

Leo

OK, reinstalled OSX. Back to normal.

Must have been some leftovers from TrimEnabler that caused this (as I already had deinstalled it).

Testing continues.

The strange 'intruder' is back! Should I, or shouldn't I speak to him about his own thread?

Have fun

Leo