macOS 13 Ventura on Unsupported Macs Thread

[Sven G]

BTW, here are the changelogs, where one can see the progresses made in 1.0.0 and 1.0.1:

Full Changelog​

1.0.0 Changelog (click to expand)

• Resolve BCM2046 and BCM2070 support on macOS 13.3 and newer
• Workaround 13.3+ Kernel Panic on AMD GCN GPUs playing DRM content
• Add new macOS Installer download menu (Jazzzny)
• Refresh download UI (Jazzzny)
• Add support for Universal 2 distribution (x86_64 and ARM64)
  
  • Drops Rosetta requirement on Apple Silicon Macs
  • Note building from source will require Python 3.11 or newer and up-to-date Python modules
• Update font handling code, fixing font issues on Yosemite and El Capitan
• Resolve incorrect RELEASE usage of OpenCore binaries when DEBUG enabled
• Add RenderBox.framework patch for 3802-based Intel GPUs on macOS 13.3 and newer
  
  • Works around Weather and Widget freezing
  • Applicable for Intel Ivy Bridge and Haswell iGPUs
• Add macOS Sonoma support to PatcherSupportPkg validation in CI
• Implement basic support for macOS Sonoma:
  
  • Supports same range of hardware as Ventura, in addition to:
    
    • iMac18,x
    • MacBook10,1
    • MacBookPro14,x
      
      • T1 chip currently unsupported in Sonoma
  • Resolved issues:
    
    • Graphics Acceleration support for 3802 and non-Metal GPUs
    • UI corruption on 31001 GPUs
    • Wireless Networking for BCM94360, 4360, 4350, 4331 and 43224
    • USB ethernet support for adapters based on ECM protocol (ex. Realtek)
    • dGPU support for MacBookPro14,3
    • S1X/S3X NVMe Drive Support
    • PCIe-based FaceTime Camera support
    • Bluetooth support by switching to dynamic VMM spoofing
• Increment Binaries:
  
  • OpenCorePkg 0.9.3 - release
  • Lilu 1.6.7 - release
  • WhateverGreen 1.6.6 - release
  • RestrictEvents 1.1.3 - (rolling - 4f233dd)
  • FeatureUnlock 1.1.5 - release
  • DebugEnhancer 1.0.8 - release
  • CPUFriend 1.2.7 - release
  • BlueToolFixup 2.6.8 - rolling (2305aaa)
  • CryptexFixup 1.0.2 - release
  • PatcherSupportPkg 1.3.2 - release
• Build Server Changes:
  
  • Upgrade Python backend to 3.11.5
  • Upgrade Python modules:
    
    • requests - 2.31.0
    • pyobjc - 9.2
    • wxpython - 4.2.1
    • pyinstaller - 5.13.2
    • packaging - 23.1

Full Changelog​

1.0.1 Changelog (click to expand)

• Resolve rendering issues on Intel Ivy Bridge iGPUs
• Update non-Metal Binaries for macOS Sonoma:
  
  • Resolve unresponsive Catalyst buttons
  • Resolve window unfocusing issues
  • Resolve menu bar fonts not changing color automatically with Beta Menu Bar enabled
  • Improve Lock Screen clock transparency
• Prevent random WiFiAgent crashes
• Add error handling for corrupted patcher settings
• Remove CoreImage patch for 3802 GPUs on Ventura
• Avoid listing PCIe FaceTime camera patch on pre-Sonoma OSes
  
  • Only cosmetic in Root Patching UI, however removed to avoid confusion

 

[nicoletta]

Hello, for 9 months, I have this 2 bugs everyday on my macbook pro 2014 on macos ventura :

nsattributedstringagent quit unexpectedly

MTLAssetUpgraderD quit unexpectedly

Do you know where this comming from ? I do all update evertime (macOS + OCLP)

View attachment 2257377

-------------------------------------
nsattributedstringagent Translated Report (Full Report Below)
-------------------------------------

Process: nsattributedstringagent [10783]
Path: /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/XPCServices/nsattributedstringagent.xpc/Contents/MacOS/nsattributedstringagent
Identifier: com.apple.textkit.nsattributedstringagent
Version: 1.0 (858)
Build Info: UIFoundation-858000000000000~8
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: SUOSUPreferencePaneExtension [10618]
User ID: 501

Date/Time: 2023-09-09 16:10:13.2747 +0200
OS Version: macOS 13.5.1 (22G90)
Report Version: 12
Anonymous UUID: 8DD94584-3F1D-6458-6D0C-5DFF5B8DB27E

Sleep/Wake UUID: 8EB2505F-3CE6-4390-BEE7-9D7FF0941D86

Time Awake Since Boot: 72000 seconds
Time Since Wake: 20404 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000027cccc6a0
Exception Codes: 0x0000000000000001, 0x000000027cccc6a0

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [10783]

VM Region Info: 0x27cccc6a0 is not in any region. Bytes after previous region: 38762145 Bytes before following region: 2201172320
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
__LINKEDIT 27a611000-27a7d5000 [ 1808K] r--/rwx SM=COW ...ed __LINKEDIT
---> GAP OF 0x8582b000 BYTES
VM_ALLOCATE (reserved) 300000000-308000000 [128.0M] rw-/rw- SM=NUL ...(unallocated)

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x7ff808a78497 objc_msgSend + 23
1 CoreFoundation 0x7ff808e8d6bf mdict_rehashd + 183
2 CoreFoundation 0x7ff808e8d121 -[__NSDictionaryM __setObject:forKey:] + 892

Hello. Have you solved your problem because I too have these two messages which appear regularly? I also have a 27" iMac with Mac Os Ventura 13.6 and OCLP 1.0.1. If anyone else has had a solution to this problem, I'm interested. Thanks in advance!

 

[deeveedee]

@Sven G @MacinMan Thank you for your replies. I have applied Post-install patches to my Ventura 13.6 test volume with OCLP 1.0.1 (previously 0.6.8). All working well without any noticeable differences (although none expected) on my MBP6,2. For me, the only EFI change was changing OCLP-Version from 0.6.9 -> 1.0.1 (config.plist), since I had already been keeping pace with the OCLP 0.6.9 dev changes to EFI (e.g., Apple Compressor changes with RestrictEvents.kext and revpatch=sbvmm) and I was already using Open Core 0.9.5.

All good in my Ventura 13.6 test volume with OCLP 1.0.1.

 

[m4v3r1ck]

[deleted]

 

[MacinMan]

@Sven G @MacinMan Thank you for your replies. I have applied Post-install patches to my Ventura 13.6 test volume with OCLP 1.0.1 (previously 0.6.8). All working well without any noticeable differences (although none expected) on my MBP6,2. For me, the only EFI change was changing OCLP-Version from 0.6.9 -> 1.0.1 (config.plist), since I had already been keeping pace with the OCLP 0.6.9 dev changes to EFI (e.g., Apple Compressor changes with RestrictEvents.kext and revpatch=sbvmm) and I was already using Open Core 0.9.5.

All good in my Ventura 13.6 test volume with OCLP 1.0.1.

You're welcome. After following the Ventura, and Sonoma threads for a few months while trying OCLP for myself, I just find I have more questions keeping with the Mac going forward, and not just trying to keep an unsupported mac going.

My main apps that would require me to be on the latest version of the OS are the iWork, and Apple Pro Apps. Everything else of importance still is supported on Monterey, which I don't need any patches to run.

My major field of training is broadcast, and in addition to that, computer repair, with some other areas mixed in.

While I haven't done any sort of production in close to 10 years on a serious level, when I learned the business, we used Final cut studio, 6, and 7, and some used AVID and other tools. I never really took the time to learn Final Cut Pro X as for a long time it was never considered a truly professional solution by those who I'd consider veterans in production based on the impression I've gotten from how they present themselves.

I've heard arguments on both sides where the verdict is Apple is no longer for the "real professional" and Windows, or even Linux are better, depending on the workflow. Then there is the other side, where people have adapted and say Apple can still be used for professional work.

Here is where I am in this conversation.
1. I find the Open Core Legacy Patcher to be a good concept, and it works well, but it's not without it's issues, and it doesn't have support from Apple, and possibly not from any software vendors that develop for the Mac, and having their software run on unsupported configurations.
2. Then there is buying a new (supported Mac), but then I loose some compatibility with non Apple specific things by no longer having an X86 based processor, and the overall direction Apple is taking their platform. So, I don't feel confident in that being a set it and forget it type of solution either, or at least a guaranteed supported / compatible solution.
3. Then there is the switch to a different platform option, and away from Apple (mainly for desktop computing) Mobile devices such as the phones / tablets are fine, and even other devices such as an Apple TV work well. The issues with changing platforms is mainly the time and money invested in Apple over the last several decades, and mainly just finding alternatives. Open Source / Cross Platform software has made that much easier in the last several years, and most things that matter, aren't Apple specific software anymore that I use on a daily basis.

The last, and probably the most important concern of mine when looking at the Open Core route is of ethnics, is it legal. Based on my conversation a few posts back regarding virtualization, running macOS on a bare metal Hyper-V type setup that's not on Apple hardware violates their EULA. Isn't using Open Core Legacy Patcher, the same thing? since Apple doesn't directly support the machines anymore? This last point wouldn't be such a concern to me, is macOS was open source, or if Apple made some allowances in the EULA for the OS to be changed / modified as most Unix operating systems are today.

I've listened to the hobbyist community and enthusiast community on this topic by following these threads for the time I have, and have gotten some valuable feedback / experience. Now I think it's time for some realistic feedback even if it means I may need to change platforms to get what I'm looking for today, and really get questions answered.

Thanks for your time, I know this was a long post, but I felt like after my observations through watch the threads, and my own experiences in life warranted these questions to be asked.

 

[deeveedee]

@MacinMan Well-written. At the risk of opening this can of worms again, I don't think you need to be concerned with ethics. I have never questioned the legality of running a newer version of macOS on a real Mac and I don't think Apple does either. Just my opinion. I think OCLP is perfectly legal without any ethical issues. Comparing an OCLP-patched Mac to running macOS in a Hyper-V VM on a Windows machine isn't really a fair comparison.

BTW - I know you didn't actually say that OCLP was illegal. I'm just clarifying that it isn't for others who might not take the time to thoroughly read your post.

 

[deeveedee]

I am becoming increasingly impressed with Ventura 13.6 running on my MBP6,2 patched with OCLP 1.0.1. Despite having both macOS firewall enabled (both incoming and outgoing connections) and Norton Antivirus 360 / Firewall with an active subscription for updates, this MBP6,2 is VERY responsive. I am running the following apps without issues (I understand that my use cases may not be the same as yours, so YMMV):

• MS Office 2019 (Word, Powerpoint, Excel are most common apps for me in Office) (fully licensed for updates)
• Tunnelblick Open VPN
• Handbrake (yes, it's slow, but it works)
• Safari, Firefox
• MS Remote Desktop
• VNC Viewer
• XCode
• Terminal

Just a personal preference, but I do not have e-mail, private/sensitive documents on my MBP6,2 and I do not access my bank records, investments on my legacy Mac. I use a fully-supported system for more secure/sensitive operations. Again, this is just my preference.

All working extremely well!

 

[ElSooz]

I too have these two crash at certain points, reproducably. Like when I open contacts or check for software updates. I have a MBP 11,3 (Late 2013) running Ventura 13.6 and OCP 1.0.1. It is hardly a major issue (for instance the TV.app now works!) but it is disturbing, indicative of some underlying problem. Anybody have thoughts on this?

Hello, for 9 months, I have this 2 bugs everyday on my macbook pro 2014 on macos ventura :

nsattributedstringagent quit unexpectedly

MTLAssetUpgraderD quit unexpectedly

Do you know where this comming from ? I do all update evertime (macOS + OCLP)

View attachment 2257377

-------------------------------------
nsattributedstringagent Translated Report (Full Report Below)
-------------------------------------

Process: nsattributedstringagent [10783]
Path: /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/XPCServices/nsattributedstringagent.xpc/Contents/MacOS/nsattributedstringagent
Identifier: com.apple.textkit.nsattributedstringagent
Version: 1.0 (858)
Build Info: UIFoundation-858000000000000~8
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: SUOSUPreferencePaneExtension [10618]
User ID: 501

Date/Time: 2023-09-09 16:10:13.2747 +0200
OS Version: macOS 13.5.1 (22G90)
Report Version: 12
Anonymous UUID: 8DD94584-3F1D-6458-6D0C-5DFF5B8DB27E

Sleep/Wake UUID: 8EB2505F-3CE6-4390-BEE7-9D7FF0941D86

Time Awake Since Boot: 72000 seconds
Time Since Wake: 20404 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000027cccc6a0
Exception Codes: 0x0000000000000001, 0x000000027cccc6a0

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [10783]

VM Region Info: 0x27cccc6a0 is not in any region. Bytes after previous region: 38762145 Bytes before following region: 2201172320
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
__LINKEDIT 27a611000-27a7d5000 [ 1808K] r--/rwx SM=COW ...ed __LINKEDIT
---> GAP OF 0x8582b000 BYTES
VM_ALLOCATE (reserved) 300000000-308000000 [128.0M] rw-/rw- SM=NUL ...(unallocated)

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x7ff808a78497 objc_msgSend + 23
1 CoreFoundation 0x7ff808e8d6bf mdict_rehashd + 183
2 CoreFoundation 0x7ff808e8d121 -[__NSDictionaryM __setObject:forKey:] + 892

 

[deeveedee]

As many have discovered, there are limitations with running Ventura on unsupported Macs that even the miracle workers developing OCLP can't overcome. Some apps that heavily depend on metal graphics won't work well on non-metal Macs patched with OCLP - they just can't in some cases.

I'm looking for a simple video editing replacement for iMovie (which is already simple). I can use QuickTime Player for some simple editing and am looking for another app.

Has anyone found an iMovie replacement that still works in Ventura on an unsupported non-metal Mac? I am aware of the Dortania recommendations here and am looking for new information about apps that are tested/proven by members in this thread. Thank you.

 

[stephengrenfell]

Page I of this thread mentions that Time Machine and Migration Assistant are broken with OCLP and Ventura. So does this mean that after installing Ventura using OCLP further down the road there will be no way to recover from a SSD failure using TM ?. Or have I misunderstood.

 

[Sven G]

Despite having disabled hibernation, Wake on LAN and PowerNap, it happened again: after leaving the MBP11,1 (in closed lid mode, with external display) idle for some hours, it had to be forcedly shut down, with a kernel panic text on subsequent startup - very strange, indeed...

 

[deeveedee]

Page I of this thread mentions that Time Machine and Migration Assistant are broken with OCLP and Ventura. So does this mean that after installing Ventura using OCLP further down the road there will be no way to recover from a SSD failure using TM ?. Or have I misunderstood.

I have had no problems using MA from TM or from another macOS volume as part of the creation of a new macOS Volume. I always perform the MA as the last step of a clean macOS install to a new APFS volume. Never any problems. I think where you have problems is if you try to use MA into a macOS volume to which you have already applied OCLP post-install patches.

 

[LlamaLarry]

I use Time Machine on every single one of my OCLP Macs without an issue.

Like deeeedee says, using Migration Assistant on a clean macOS install has worked every single time, but if I try to MA after I've gone through initial setup it has failed every single time. I have one MBP that has needed to be redone several times for one reason or another and it's only been the last couple that I realized/remembered the right order to do the MA portion.

 

[K two]

I have had no problems using MA from TM or from another macOS volume as part of the creation of a new macOS Volume. I always perform the MA as the last step of a clean macOS install to a new APFS volume. Never any problems. I think where you have problems is if you try to use MA into a macOS volume to which you have already applied OCLP post-install patches.

Suggestion - MA and TM s/b enabled in Privacy & Security > Accessibility and Full Disk Access in normal use.

 

[internetzel]

Despite having disabled hibernation, Wake on LAN and PowerNap, it happened again: after leaving the MBP11,1 (in closed lid mode, with external display) idle for some hours, it had to be forcedly shut down, with a kernel panic text on subsequent startup - very strange, indeed...

Here's the panic log:

WindowServer not responding ... maybe graphics driver problems, but sleep/wake problems for me are very hard to debug (almost like EFI and/or bootloader debugging).

 

[mardecissab]

Hi, first and foremost I would like to thank all the developers again for all the spectacular work you do with this.

I have downloaded the OCLP 1.0.1 from my MBP 13" 9,1 mid 2012 graphics intel 4000HD and was able to install macOS Ventura without any issue. Everything works fine. I have 16gb of ram and a 500gb SSD. It doesn't fly but it runs really very well if I remove the transparency and motion settings.

However, on my other MBP 13" 8,2 late 2011 graphics íntel 3000hd , 16gb ram and 500gb SSD, I had installed a few years ago, macOS Catalina with the dosdude1 patch.
In this pc I had also updated the wifi and bluetooth 2.0 Airport board that came with this pc for the MBP mid 2012 model that brings better wifi and bluetooth 4.0.
and I had also upgraded the vRAM of the intel 3000hd from 512gb to 1024gb. Following the next kext

https://forums.macrumors.com/threads/2011-intel-hd-3000-macbook-pro-1024mb-vram-kext-work.1977308/

And now I have tried to upgrade, from fresh install this latest MBP 8.2, to Ventura.
I was able to do it, but after installing the OCLP on the hard drive and rebooting, in the last step, the machine freezes at 2/5 of the bar and won't boot. 🙀
I can only boot it if I use the pendrive with which I installed the operating system.

Is it because the MBP 8.2 has the latest wireless board installed?

I am waiting for help with this. 🙌
Thank you very much!

 

[sharpshooter50]

Could anyone please help me with this issue? I made a detailed thread explaining my problem and DeltaMac was kind enough to give me some suggestions. My thread got merged here and I was just wondering what I need to do exactly. My post is on page 290 at the bottom if anyone needs to read it: https://forums.macrumors.com/thread...unsupported-macs-thread.2346881/post-32627431

DeltaMac said:

I think that you may get a good result if you reinstall your Ventura system.
You would need to install with the same, or newer, version of Ventura that you boot from now.
I would suggest that you remake your bootable USB installer with the latest Ventura version 13.6.1 -- but that would also mean that you would need another Mac that you can use to make that installer

I have another Mac that I can borrow from my dad (an old one). I haven't gone through the process of OCLP since I updated my old mac to Ventura, so I just want to absolutely sure that I'm doing it the right way. Do I basically just follow the same installation process as before? Will it delete my data or will using an OCLP USB give me the ability to boot back into the same OS installation? Any help would be greatly appreciated.

 

[deeveedee]

Suggestion - MA and TM s/b enabled in Privacy & Security > Accessibility and Full Disk Access in normal use.

I'm going to respectfully disagree. I never grant more permissions to any processes/apps if I don't have to. If anything, I will only enable further restrictions. Just my personal preference. If it works without the relaxed security (which it should), leave it alone.

Also, I do modify TM preferences to exclude volumes that I don't want cluttering my TM storage. I boot multiple volumes with different macOS versions for testing. I exclude the extraneous volumes from TM backups to save space and reduce disk activity. I also password-protect my TM volume.

 

[deeveedee]

WindowServer not responding ... maybe graphics driver problems, but sleep/wake problems for me are very hard to debug (almost like EFI and/or bootloader debugging).

Your real Mac is now using Open Core, so its split personality includes that of a hackintosh. It's the most delicate way that I know to welcome you to the dark side. You will now find that Open Core documentation is a good place to look for solutions like this.

 

[deeveedee]

... In this pc I had also updated the wifi and bluetooth 2.0 Airport board that came with this pc ...

Are you using "pc" as a generic way to refer to your Mac, or is it actually a pc "hackintosh?" If a hackintosh, you might find more help over at InsanelyMac. That's where my cousin spends most of her time.

 

[deeveedee]

Could anyone please help me with this issue? I made a detailed thread explaining my problem and DeltaMac was kind enough to give me some suggestions. My thread got merged here and I was just wondering what I need to do exactly. My post is on page 290 at the bottom if anyone needs to read it: https://forums.macrumors.com/thread...unsupported-macs-thread.2346881/post-32627431

You mention SIP in your other post, so is it correct to assume that you are grappling with a SIP issue? If so, OCLP allows you to modify SIP using the OCLP GUI (Settings > Security):

After you modify the SIP settings, "Build and Install Open Core" to apply the new settings. Then reboot. You are using Open Core, so you may find it necessary to "Reset NVRAM" when changing your Mac's EFI (e.g., when you change things in the Open Core config.plist). Open Core does usually delete old settings before applying new (in some cases only when told to do so), but Reset NVRAM if your SIP changes aren't applied.

You can learn more about SIP here. You may recognize the author of that blog.

EDIT: I don't know your background or level of experience with Open Core, so just ignore stuff in this that you don't understand and stick to the OCLP GUI and SIP blog if you need to.

 

[K two]

I'm going to respectfully disagree. I never grant more permissions to any processes/apps if I don't have to. If anything, I will only enable further restrictions. Just my personal preference. If it works without the relaxed security (which it should), leave it alone.

Also, I do modify TM preferences to exclude volumes that I don't want cluttering my TM storage. I boot multiple volumes with different macOS versions for testing. I exclude the extraneous volumes from TM backups to save space and reduce disk activity. I also password-protect my TM volume.

Definitely speeds up MA and no offence, the Security obsession is showng. Why is granting permissions some kind of a threat? Puzzling.

 

[deeveedee]

Suggestion - MA and TM s/b enabled in Privacy & Security > Accessibility and Full Disk Access in normal use.

Definitely speeds up MA and no offence, the Security obsession is showng. Why is granting permissions some kind of a threat? Puzzling.

Follow your logic and open full disk access to everything. Not trying to be smart, but explaining an opposing view point that contradicts yours does not need to be an obsession. It could just be another way to do something. No harm in offering users a choice, is there.

@K two I'd like to use this as a learning experience for me, since you're the 68000 and I'm the lowly 6502a. You made your "MA and TM ... Full Disk Access" recommendation directly to me (it was a reply directly to me) with literally the word "Suggestion" in your statement.

I took that to mean that I had a choice and that not choosing your recommendation was an option for me. I then respectfully replied (with the word "Respectfully" literally in my reply). Did I misinterpret your statement as a "Suggestion" when it was actually a command with no options? Forgive me for the remedial question, I'm learning and have grown tired of my slow uptake. I'm old and running out of time to learn these things. Thanks.

Oh, I nearly forgot ... I donated.

 

[deeveedee]

Posting this to disclose test results and not as a recommendation for anyone's production environment:

I am A/B'ing OCLP 0.6.8 and 1.0.1 root patches for Ventura as part of my own testing. I have had no problem alternating the application of Ventura MBP6,2 root patches using OCLP 0.6.8 and 1.0.1 (overwriting the existing root patches). I am leaving my Open Core EFI alone (as the one generated with OCLP 1.0.1, manually upgraded to Open Core 0.9.5, OCLP-Version = 1.0.1). No problems jumping back and forth between OCLP 0.6.8 and OCLP 1.0.1 post-install patches and I notice no difference with Ventura (not that I expected any).

I am currently running with OCLP 0.6.8 post-install patches on my MBP6,2 and all is good. This 2010 Mac is amazing thanks to OCLP. Devs have made the root-patching process as seamless as I think it can be. Well done.

 

[K two]

Follow your logic and open full disk access to everything. Not trying to be smart, but explaining an opposing view point that contradicts yours does not need to be an obsession. It could just be another way to do something. No harm in offering users a choice, is there.

@K two I'd like to use this as a learning experience for me, since you're the 68000 and I'm the lowly 6502a. You made your "MA and TM ... Full Disk Access" recommendation directly to me (it was a reply directly to me) with literally the word "Suggestion" in your statement.

I took that to mean that I had a choice and that not choosing your recommendation was an option for me. I then respectfully replied (with the word "Respectfully" literally in my reply). Did I misinterpret your statement as a "Suggestion" when it was actually a command with no options? Forgive me for the remedial question, I'm learning and have grown tired of my slow uptake. I'm old and running out of time to learn these things. Thanks.

Oh, I nearly forgot ... I donated.

Just a SUGGESTION - Found these settings to work just fine. Launch codes unmolested. Snark, intended. 😉

Enjoy