All Activity

Interesting! Ler me think and test it.

Tell us your story what you asked from AI. Tell us non-standard approach to the dialog. Ask a question how to use AI. Tell us what AI do you prefer and why. Show images created with AI. Tell us funny story related to AI.

I use it a lot for cover design and to know if the response is accurate or imagined.

I don't know if it would be interesting or not, but it would be good to know the monitor connections, an example done with ChapGPT as we discussed in the new IA channel.

@chris1111 Got them Thank you!!!

If I use an HDMI switch and connect one cable to the dedicated card (the RX 6400) for Windows and the other to the integrated graphics for Mac, will that work, or will I have to manually switch the video source for the Mac?

I send you the Disk GOldenGate in PM

@LockDown there are multiple such apps for Windows. You should be able to find one with a search. I'm not aware of similar apps for macOS, but they may exist, too. If you don't want to find the app, there are published test results that you can find with a search. EDIT: I stand corrected. I did measure Radeon dGPU power in macOS. See here.

@ird It's going to take me a little longer to test a 65W EliteDesk 800 G4 Mini with i5-8600, because the only such unit that I have includes a motherboard that I tinkered with while attempting to produce a 65W motherboard with RX 560x dGPU. I de-soldered / re-soldered components on this particular motherboard and while it "works", its multi-core performance is lousy. It appears that I have caused some kind of thermal problem in the CPU power MOSFETS. They get insanely hot during GB6 multi-core tests, so the motherboard (fortunately) throttles CPU speed and never achieves full multi-core performance. If someone else can test the EliteDesk 800 G4 Mini 65W with i5-8600 / 230W power supply, that would save me some trouble of piecing together a new test system. By the way, if you're curious about my attempts to create a 65W G4 Mini motherboard with RX 560x dGPU, the short answer is that I failed after multiple attempts. The long answer involves destroying one 65W motherboard, destroying one 35W motherboard, crippling another 65W motherboard (the one I was hoping to use for this GB6 test) and burning up a m.2 NVMe SSD. The benefit of this exercise is that I now own a soldering heat gun, learned how to de-solder and solder components with a heat gun and I created my own soldering hot plate. It was a rather time-consuming, expensive experiment.

OT What app to know how much power drawn?

macOS Tahoe 26.5.2 is just around the corner

Initial work to update the app to Golden Gate. macOS app and disks icons courtesy of @chris1111 EDIT: server error trying to upload the pics, sorry.

@kgp About This Hack needs to be updated to Golden Gate. New icon and the rest. Working on it.

@fantomas As @Slice said “Where user may exchange information about using different AI: Claude, ChatGPT, DeepSeek etc.” or something like this.

This time a sequential OTA update of just 10 GB! With macOS 27 beta 2 (26A5368g), Apple appears to have fixed the following issues on my MacBook Pro M1: Keyboard and trackpad now work immediately after waking from sleep or opening the lid. No Wi-Fi issues after waking from sleep or opening the lid. Secondary click now works perfectly when configured as "Click in Bottom Right Corner". Interestingly, Apple released Kernel Debug Kit macOS 26.7 build 26A5368g, apparently confusing macOS 27 beta 2 with macOS 26.7. The very bad part of this funny confusion at first glance: Any future Tahoe 26.7 KDK release is unlikely to carry a build number higher than 26A. Consequently, Kernel Debug Kit macOS 26.7 build 26A5368g - which actually belongs to macOS 27 beta 2 (Golden Gate) — would not be compatible with macOS Tahoe. If Apple keeps this naming scheme, OCLP's automatic KDK matching could become problematic beyond macOS Tahoe 26.6, as it may no longer be possible to reliably distinguish Tahoe 26.7 KDKs from Golden Gate KDKs based on build numbering alone. This assumes, of course, that macOS 26.7 will be the final major Tahoe release. 🤕 Whether this is an actual mistake or an intentional change in Apple's KDK naming scheme remains unclear. If intentional, OCLP and similar tools may eventually need to adjust their KDK matching logic accordingly. I have already submitted a Feedback Assistant report to Apple regarding this apparent KDK naming issue.

Kernel Debug Kit 26.6 build 25G5043d is also available on Dortania's KDK mirror, and OCLP correctly selects the direct KDK match for macOS 26.6 beta 2. Thanks to Apple for choosing the correct KDK nomenclature this time. 😄 Modern Audio, modern Wi-Fi, AirDrop, AirPlay, Screen Mirroring, Personal Hotspot, Continuity Camera, and sleep/wake continue working flawlessly with my BCM943602CDP. Interestingly, both Apple and Dortania's KDK mirror also expose Kernel Debug Kit 26.7 build 26A5368g. However, 26A5368g is in fact the build number of macOS 27 beta 2, which means Apple has apparently introduced yet another KDK nomenclature flaw by confusing macOS 27 with macOS 26.7. The very bad part of this funny confusion at first glance: Any future Tahoe 26.7 KDK release is unlikely to carry a build number higher than 26A. Consequently, Kernel Debug Kit macOS 26.7 build 26A5368g - which actually belongs to macOS 27 beta 2 (Golden Gate) - would not be compatible with macOS Tahoe. If Apple keeps this naming scheme, OCLP's automatic KDK matching could become problematic beyond macOS Tahoe 26.6, as it may no longer be possible to reliably distinguish Tahoe 26.7 KDKs from Golden Gate KDKs based on build numbering alone. This assumes, of course, that macOS 26.7 will be the final major Tahoe release. 🤕 Whether this is an actual mistake or an intentional change in Apple's KDK naming scheme remains unclear. If intentional, OCLP and similar tools may eventually need to adjust their KDK matching logic accordingly. I have already submitted a Feedback Assistant report to Apple regarding this apparent KDK naming issue.

Does Apple like spoilers?

https://swdist.apple.com/content/downloads/08/22/140-31668-A_UOOEA5WMR8/yx13s8l4tygi9n1ar7rxhrhpn9t04wvk1n/InstallAssistant.pkg <dict> <key>BUILD</key> <string>26A5368g</string> <key>VERSION</key> <string>27.0</string> [ 35 ] 2026-06-22 17:16:36 .. 140-31668 .. 27.0.0.26A5368g macOS Golden Gate Beta

I have included version 1.0.1 in the link from the first post. I have also uploaded it to GitHub (the source code will be made available soon). This version includes a kext I developed called BlueWakeFixup, which fixes the issue where Bluetooth does not turn on after the PC wakes from sleep on some Wi-Fi adapters, such as my BCM4352. I hope it will be useful to some people.

I just installed macOS Catalina 10.15.7 on my HP EliteBook 850 G7 laptop, because I'm doing some testing that may benefit from the older macOS and the first MBP16,2 Macs were shipped with Catalina. Not much of a surprise, but the installation was effortless and without any issues. macOS detected the recently released 10.15.8 / Safari updates and applied them without issues. The credit for this goes to the Open Core and Kext Devs who have continue to maintain backward compatibility. With exactly the same EFI, this laptop boots Catalina through Tahoe. Thank you OC Devs and all the supporting Devs who continue to provide us with the essential Kexts. You have made our hackintosh journeys possible. Posting this with Safari Version 15.6.1 (15613.3.9.1.16, 15613) in Catalina 10.15.8 and it still works! About This Hack EDIT: I'm using the same version of itlwm.kext (2.3.0) and Heliport (1.5.0) to enable Intel Wi-Fi across the different versions of macOS.

After InsanelyWine it comes InsanelyAI. https://www.insanelymac.com/forum/898-insanelyai/ P.S: I just made a copy of InsanelyWine forum (layout, permissions), tell me what we should put in the forum description.

You could review the Dortania link that I provided for you in my previous post. If you are considering the replacement to be temporary (I'm not so sure about that, but let's assume you're correct), then maybe you don't want to purchase another card. If the iGPU works well enough for you, that's clearly your lowest power option at the moment.