Reply to thread

Message

<blockquote data-quote="Randy B. Singer" data-source="post: 1611090" data-attributes="member: 190607">I just re-read that, and I hope that it didn't come off as being too brusque. I sometimes type things too fast and don't realize what they will sound like when read.My aim was to tell you how to diagnose your problem, which is what you asked for.&nbsp; Doing this yourself might seem daunting to most ordinary Mac users.&nbsp; I'm not trying to tell you that you *must* do things that you may be uncomfortable doing.Apple can diagnose your Mac for you in seconds.&nbsp; But the problem might be with a peripheral or a cable, and most folks don't take all of their peripherals or cables with them to the Apple store.&nbsp; So rule out problems with peripheral hardware first, as I outlined, by running without them, before taking your Mac to Apple to have it looked at.&nbsp; Beyond that, you can let Apple handle diagnosing things, you shouldn't do anything that I suggested that is beyond your pay grade.&nbsp; ;D</blockquote>

[QUOTE="Randy B. Singer, post: 1611090, member: 190607"] I just re-read that, and I hope that it didn't come off as being too brusque. I sometimes type things too fast and don't realize what they will sound like when read. My aim was to tell you how to diagnose your problem, which is what you asked for. Doing this yourself might seem daunting to most ordinary Mac users. I'm not trying to tell you that you *must* do things that you may be uncomfortable doing. Apple can diagnose your Mac for you in seconds. But the problem might be with a peripheral or a cable, and most folks don't take all of their peripherals or cables with them to the Apple store. So rule out problems with peripheral hardware first, as I outlined, by running without them, before taking your Mac to Apple to have it looked at. Beyond that, you can let Apple handle diagnosing things, you shouldn't do anything that I suggested that is beyond your pay grade. ;D [/QUOTE]

Verification

Name this item. 🍎