Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since it was changed in iLife ‘08 to allow for 3rd party drive support (this was because of the release of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
+
Unless there’s still modern applications Apple develops that need an Apple blessed drive with the "correct" firmware, I have not seen or heard of that problem with 3rd party units in quite a few years after iLife '09 came out ('08 still often needed the blessed drive). The reason for this change was because of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
-
Since it hasn’t been a problem for at least 12 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
+
Since it hasn’t been a problem for at least 12 years, it sounds like you’re running one of the legacy application from that time period when this was a problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs, but these are rare.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
== Update (6/7/19) ==
-
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA, but is rMBP compatible (asyou just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule. If you’re concerned about the handful of bad drives, buy the one I’ve vetted (Revision shouldn’t matter) or from a place with a solid return policy. If the one you get is Lightscribe ready,it won't hurt compatibility -it will work as if it doesn’t have it, but you probably won’t see the Lightscribe function being useful. The discs are price gouged and the software requires [https://lightscribesoftware.org/how-to-install-system-software-on-el-capitan/|compromising system security] since SIP needs to be disabled. HP stopped supporting it in ~2013.
+
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple external DVD drive as that was originally designed for the MBA and the rMBP when they came out. However, any 3rd party drive is fair game in MacOS. There may be a handful that don’t work, but that’s the exception, not the rule. If you’re concerned about the handful of bad drives, try to buy one I've found works with a proper return policy just in case, or the drive is no longer sold.
-
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (Non Lightscribe) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, so baby the drive.'''
+
If the one you get is Lightscribe ready, it won't hurt compatibility - it will work as if it doesn’t have it, but you probably won’t see the Lightscribe function being useful. These days, the media needed to use it is price gouged and the software requires [link|https://lightscribesoftware.org/how-to-install-system-software-on-el-capitan/|compromising system security] since SIP needs to be disabled. HP stopped supporting it in ~2013.
+
+
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: ***~~MRX-650LE V7 (Non Lightscribe) - Memorex~~ (OLD DRIVE, NO LONGER SOLD NEW - MAY BE AVAILABLE USED). I am no longer testing for this since the bad drives are a known distant memory at this point.***
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since it was changed in iLife ‘08 to allow for 3rd party drive support (this was because of the release of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
Since it hasn’t been a problem for at least 12 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
== Update (6/7/19) ==
-
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA, but is rMBP compatible (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule. If you’re concerned about the handful of bad drives, buy the one I’ve vetted (Revision shouldn’t matter) or from a place with a solid return policy. If the one you get is Lightscribe ready, it won't hurt compatibility -it will work as if it doesn’t have it, but you probably won’t see the Lightscribe function being useful - the discs are price gouged and the software may not work in Sierra or even High Sierra. HP stopped supporting it in ~2013.
+
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA, but is rMBP compatible (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule. If you’re concerned about the handful of bad drives, buy the one I’ve vetted (Revision shouldn’t matter) or from a place with a solid return policy. If the one you get is Lightscribe ready, it won't hurt compatibility -it will work as if it doesn’t have it, but you probably won’t see the Lightscribe function being useful. The discs are price gouged and the software requires [https://lightscribesoftware.org/how-to-install-system-software-on-el-capitan/|compromising system security] since SIP needs to be disabled. HP stopped supporting it in ~2013.
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (Non Lightscribe) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, so baby the drive.'''
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since it was changed in iLife ‘08 to allow for 3rd party drive support (this was because of the release of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
Since it hasn’t been a problem for at least 12 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
== Update (6/7/19) ==
-
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA, but is rMBP compatible (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule. If you’re concerned about the handful of bad drives, buy the one I’ve vetted or from a place with a solid return policy. If the one you get is Lightscribe ready, it won't hurt compatibility - the function will probably not work but as a standard drive it will behave as if it wasn't present.
+
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA, but is rMBP compatible (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule. If you’re concerned about the handful of bad drives, buy the one I’ve vetted (Revision shouldn’t matter) or from a place with a solid return policy. If the one you get is Lightscribe ready, it won't hurt compatibility -it will work as if it doesn’t have it, but you probably won’t see the Lightscribe function being useful - the discs are price gouged and the software may not work in Sierra or even High Sierra. HP stopped supporting it in ~2013.
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (Non Lightscribe) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, so baby the drive.'''
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since it was changed in iLife ‘08 to allow for 3rd party drive support (this was because of the release of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
Since it hasn’t been a problem for at least 12 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
== Update (6/7/19) ==
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA, but is rMBP compatible (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule. If you’re concerned about the handful of bad drives, buy the one I’ve vetted or from a place with a solid return policy. If the one you get is Lightscribe ready, it won't hurt compatibility - the function will probably not work but as a standard drive it will behave as if it wasn't present.
-
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (Non Lightscribe) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, s baby the drive.'''
+
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (Non Lightscribe) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, so baby the drive.'''
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since it was changed in iLife ‘08 to allow for 3rd party drive support (this was because of the release of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
Since it hasn’t been a problem for at least 12 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
== Update (6/7/19) ==
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA, but is rMBP compatible (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule. If you’re concerned about the handful of bad drives, buy the one I’ve vetted or from a place with a solid return policy. If the one you get is Lightscribe ready, it won't hurt compatibility - the function will probably not work but as a standard drive it will behave as if it wasn't present.
-
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (Non Lightscribe) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, s baby the drive.'''
+
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (Non Lightscribe) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, s baby the drive.'''
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since it was changed in iLife ‘08 to allow for 3rd party drive support (this was because of the release of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
Since it hasn’t been a problem for at least 12 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
== Update (6/7/19) ==
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA, but is rMBP compatible (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule. If you’re concerned about the handful of bad drives, buy the one I’ve vetted or from a place with a solid return policy. If the one you get is Lightscribe ready, it won't hurt compatibility - the function will probably not work but as a standard drive it will behave as if it wasn't present.
-
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (Non Lightscribe) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, so you need to baby the drive.'''
+
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (Non Lightscribe) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, s baby the drive.'''
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since it was changed in iLife ‘08 to allow for 3rd party drive support (this was because of the release of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
Since it hasn’t been a problem for at least 12 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
== Update (6/7/19) ==
-
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA, but is rMBP compatible (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule. If you’re concerned about the handful of bad drives, buy the one I’ve vetted or from a place with a solid return policy.
+
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA, but is rMBP compatible (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule. If you’re concerned about the handful of bad drives, buy the one I’ve vetted or from a place with a solid return policy. If the one you get is Lightscribe ready, it won't hurt compatibility - the function will probably not work but as a standard drive it will behave as if it wasn't present.
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (Non Lightscribe) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, so you need to baby the drive.'''
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since it was changed in iLife ‘08 to allow for 3rd party drive support (this was because of the release of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
Since it hasn’t been a problem for at least 12 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
== Update (6/7/19) ==
-
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA, but is rMBP compatible (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule.
+
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA, but is rMBP compatible (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule. If you’re concerned about the handful of bad drives, buy the one I’ve vetted or from a place with a solid return policy.
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (Non Lightscribe) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, so you need to baby the drive.'''
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since it was changed in iLife ‘08 to allow for 3rd party drive support (this was because of the release of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
Since it hasn’t been a problem for at least 12 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
== Update (6/7/19) ==
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA, but is rMBP compatible (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule.
-
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (LS deleted) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, so you need to baby the drive.'''
+
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (Non Lightscribe) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, so you need to baby the drive.'''
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since it was changed in iLife ‘08 to allow for 3rd party drive support (this was because of the release of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
Since it hasn’t been a problem for at least 12 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
== Update (6/7/19) ==
-
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule.
+
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA, but is rMBP compatible (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule.
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (LS deleted) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, so you need to baby the drive.'''
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since it was changed in iLife ‘08 to allow for 3rd party drive support (this was because of the release of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
Since it hasn’t been a problem for at least 12 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
== Update (6/7/19) ==
-
-
Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule.
+
@artistcain Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule.
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (LS deleted) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, so you need to baby the drive.'''
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since it was changed in iLife ‘08 to allow for 3rd party drive support (this was because of the release of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
Since it hasn’t been a problem for at least 12 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
+
+
== Update (6/7/19) ==
+
+
Any other 3rd party drive will work if you need an external for whatever reason you need it. You can’t use the Apple drive as that was originally designed for the MBA (as you just learned), but any 3rd party drive is fair game in Mac OS. There may be a handful that don’t work, but that’s the exception; NOT the rule.
+
+
I use this with my 2011 13” Pro running High Sierra and it behaves perfectly fine: '''MRX-650LE V7 (LS deleted) and it’s made by Memorex. If the drive goes out you need to replace the unit as the USB port is integrated to the PCB, so you need to baby the drive.'''
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since it was changed in iLife ‘08 to allow for 3rd party drive support (this was because of the release of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
-
Since it hasn’t been a problem for at least 10-11 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
+
Since it hasn’t been a problem for at least 12 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since that requirement was put to bed for good with iLife '08. It sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking this is probably more likely to be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter.
+
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since it was changed in iLife ‘08 to allow for 3rd party drive support (this was because of the release of the MBA, since these didn’t have an internal drive Apple could bless for iDVD direct burn support).
+
+
Since it hasn’t been a problem for at least 10-11 years, it sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking it may be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter with 1st party programs.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since that requirement was put to bed for good with iLife '08. It sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking this is probably more likely to be a 3rd party app if it cares if the drive is blessed by Apple on a machine that’s way too new for it to matter.
+
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since that requirement was put to bed for good with iLife '08. It sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking this is probably more likely to be a 3rd party app if it cares about blessed by Apple firmware on a machine that’s way too new for it to matter.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since the end of an era when iLife ‘08 put that phase to bed for good. It sounds like you’re running a legacy application from that time period when this was a real problem. I’m thinking this is probably more likely to be a 3rd party app if it cares if the drive is blessed by Apple on a machine that’s way too new for it to matter.
+
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since that requirement was put to bed for good with iLife '08. It sounds like you’re running a legacy application from that time period when this was a real problem. I’m also thinking this is probably more likely to be a 3rd party app if it cares if the drive is blessed by Apple on a machine that’s way too new for it to matter.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since the end of an era when iLife ‘08 put that phase to bed for good. It sounds like you’re running a legacy application from that time period when this was a real problem. I’m thinking this is a 3rd party app if it cares if the drive is blessed by Apple on a machine that’s way too new for it to matter.
+
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since the end of an era when iLife ‘08 put that phase to bed for good. It sounds like you’re running a legacy application from that time period when this was a real problem. I’m thinking this is probably more likely to be a 3rd party app if it cares if the drive is blessed by Apple on a machine that’s way too new for it to matter.
-
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. https://www.ifixit.com/Guide/Adding+images+to+an+existing+question/21499
+
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. [guide|21499]
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since the end of an era when iLife ‘08 put that phase to bed for good. It sounds like you’re running a legacy application from that time period when this was a real problem. I’m thinking this is a 3rd party app if it cares if the drive is blessed by Apple on a machine that’s way too new for it to matter.
-
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years.
+
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years. https://www.ifixit.com/Guide/Adding+images+to+an+existing+question/21499
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since the end of an era when iLife ‘08 put that phase to bed for good. It sounds like you’re running a legacy application from that time period when this was a real problem.
+
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since the end of an era when iLife ‘08 put that phase to bed for good. It sounds like you’re running a legacy application from that time period when this was a real problem. I’m thinking this is a 3rd party app if it cares if the drive is blessed by Apple on a machine that’s way too new for it to matter.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years.
Unless there’s still modern applications Apple develops that need an Apple blessed drive, I have not seen or heard of that problem with 3rd party units in years since the end of an era when iLife ‘08 put that phase to bed for good. It sounds like you’re running a legacy application from that time period when this was a real problem.
Post a screenshot of the error and program that’s giving you this error. I haven’t heard of this issue with 3rd party drives in years.