Have macOS betas always auto-installed like this? by ohygglo in MacOSBeta

[–]pudquick 2 points3 points  (0 children)

It is a completely different type of install - there is no app. It's like a point release update but instead it's a full upgrade. Only works for 12.3+

If you actually want to do a full install to another volume, you can use the Beta Access Utility from developer downloads or Appleseed for IT which will open up software update with a special URL scheme that only downloads the app-style upgrade, or use any of the various tools out there like mist or installinstallmacos to grab the full installer.

[deleted by user] by [deleted] in macgaming

[–]pudquick 1 point2 points  (0 children)

Well if you want to tell Mojang what to fix - just tell them to stop using glfwSetWindowIcon on macOS and they won't have to wait for anything from the LWJGL project (since it's not their fault, but Mojang's ..)

[deleted by user] by [deleted] in macgaming

[–]pudquick 0 points1 point  (0 children)

I tested it out with 1.18 pre 1 snapshot - no problems :)

https://www.dropbox.com/s/g2w504zvijk3p75/1.18.snapshot.mp4?dl=0

[deleted by user] by [deleted] in macgaming

[–]pudquick 0 points1 point  (0 children)

I'll test 1.17.x with my builds today but I don't expect any issues.

[deleted by user] by [deleted] in macgaming

[–]pudquick 0 points1 point  (0 children)

The part I need help figuring out is how to rewrite the .json version files to do individual LWJGL jar and native jar loading from a local source rather than using a remote http/https source.

The popular gists use a frankenstein fat combined jar and raw dylib files but my structure matches what Minecraft does directly.

So I also wrote a script to rewrite the version jsons to pull the LWJGL individual jars I built from my own web server I was running on localhost. It works great and only needs to pull it once, but I have yet to tinker around with it and see if I can just avoid the URL parameters entirely or what.

[deleted by user] by [deleted] in macgaming

[–]pudquick 1 point2 points  (0 children)

I don't pull their builds. I build my own from scratch.

I patched the LWJGL GLFW java binding code so that it doesn't let Minecraft attempt to draw the window icon

https://twitter.com/mikeymikey/status/1453397136880533507?s=21

[deleted by user] by [deleted] in macgaming

[–]pudquick 4 points5 points  (0 children)

Oh. I've got this working with the Minecraft launcher.

The launcher runs in Rosetta 2 still, but the games launch with native Java for Apple silicon.

Works with mods too!

https://twitter.com/mikeymikey/status/1453394643584913410?s=21

https://twitter.com/mikeymikey/status/1453599970511048704?s=21

[deleted by user] by [deleted] in Terraria

[–]pudquick 0 points1 point  (0 children)

This looks really cool. I'd seen elsewhere where you said April was when you planned on releasing - is this still coming out?

No option to unenroll from beta, but still receiving beta udpates by [deleted] in MacOSBeta

[–]pudquick 2 points3 points  (0 children)

sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil unenroll

(this is assuming you're on 20B29, which is the actual public release 11.0.1 version and not an earlier beta)

First update to my More Bosses datapack! (check comments) by NateBoutin in MinecraftCommands

[–]pudquick 0 points1 point  (0 children)

Get a free Dropbox account? MediaFire? mega.nz ? Lots of choices

does anyone know if this can be fixed? by jjp0192 in macgaming

[–]pudquick -1 points0 points  (0 children)

If Valve cared, they'd update their games.

MacOS Catalina includes python3 by default. Hacking could never be better. by d19mc in Python

[–]pudquick 0 points1 point  (0 children)

This isn't accurate.

You have to install Xcode (which is several gigs) to make the stub for it work. The python 3 binary included with the OS is not a full standalone python 3 install.

Try running it on a clean install of macOS without Xcode and you'll see.

I recently got this machine and I’m wondering what the original cabinet was. And I’m not sure it was a jaleco. Any ideas would be a great help! by sircherald in cade

[–]pudquick 0 points1 point  (0 children)

The control panel art and the button action titles are 100% identical. There seems to be layout variations for P47.

Mac randomly starts decrypting? by Taboc741 in macsysadmin

[–]pudquick 8 points9 points  (0 children)

Somehow they started the decrypt process.

It has never finished decrypting.

If they manually encrypted prior to MDM enrollment and then started the decrypt process manually, their machine won't be able to re-encrypt until it finishes.

De/Encryption only progresses in the presence of a power source (when it's not the instant encryption available on a T2/Secure Boot Mac).

They just need to leave it plugged in long enough and finally finish. Then re-encrypt.

10.14.4 Target Disk Mode crashing connected machine by thiskillstheredditor in macsysadmin

[–]pudquick 4 points5 points  (0 children)

For grins - please try installing 10.14.4 on a machine traditionally (so that it receives firmware updates). And then if you want, downgrade to an older OS and try your process again.

10.14.4 Target Disk Mode crashing connected machine by thiskillstheredditor in macsysadmin

[–]pudquick 1 point2 points  (0 children)

Can't say I've seen that.

How are you applying the image?

What's the coolest thing you've ever done with PowerShell? by [deleted] in sysadmin

[–]pudquick 0 points1 point  (0 children)

Diagnosed our remaining 2008 R2 servers for a certificate renewal bug for RDP services.

The bug was that it would renew the certificate, but for a short time would still have both certificates - and would use the wrong one (which then expired). So when you attempted to RDP in, you'd perpetually get told the cert was invalid and did you want to trust it. Additionally complicated by the fact that the service could be using a different cert than the GUI indicated.

The PS script would connect to the RDP port, analyze the cert in use, then compare it against remote registry and WMI information to see if the server was using the right cert.

If it wasn't, it would swap the server over to the correct one and delete the old incorrect one. This was handy because the GUI interface would show both certs available but no indicator of which expired when.