Rat-Hole Mac OS

Rat-Hole Mac OS

May 31 2021

Rat-Hole Mac OS

  1. Rat-hole Mac Os Update
  2. Rat-hole Mac Os Update
  1. The large gap between OS X and Windows is widening as well as Microsoft seems to have lost the ability to actually improve their product. Windows just keeps getting bigger without getting materially better. Mac OS 10.4 (Tiger) was released over 3 years ago and it blows the doors off of Vista. Mac OS 10.5 Leopard was released in October 2007.
  2. EdgeSounds RatHole v3.6.1 for MAC OS X EdgeSounds RatHole has a very simple user interface. All you have to do is to anchor files that you want to compress or decompress with the mouse, drag and drop them onto the RatHole's screen. Windows version: Drag and drop files to the Drop Target pane.

Lost 6 hours of my life tracking down this issue, and of course in the end it turns out to be my user error, although as always as a developer you challenge whether it needed to be this hard to debug.

Objective

Apr 30, 2015 Let Microsoft’s wrong choice of a CEO lead them further down the rat hole that Ballmer T. Clown began digging years ago. Related article: Desperate Microsoft announces tool for porting iOS apps. The Best Ways To Block Mouse/Rat Holes. Keep Rats Out of Your House.In this video we test different methods for blocking rodent access holes. List of Equipme. What Does a Rat Hole Look Like. Typical Rat Burrow. The first distinct sign of a rat hole is the size of the entrance. The entrance will be roughly 2-4 inches in diameter and smooth and compacted from the rodents going in and out of the burrow. You’ll also notice fresh dirt just out of the entrance in a fan-shape created when the rodents.

What was I trying to achieve was to create mac app bundle to put in a dmg to distribute my java desktop app. In Eclipse, generated a Mac app bundle using the export task.

Into Finder, double clicked the app and nothing happens. A quick search around Console, shows:

A quick google makes suggestions like there’s no main entry point defined in the jar file

This however is a rat-hole, there is indeed no main entry point defined in the manifest but a few more searches reveal the package isn’t invoked using java -jar xx.jar, it’s invoked using java -cp xx.jar mainEntryPoint. So we check the Info.plist in the app bundle, and find the main class is defined. So what’s going wrong?

Rat-Hole Mac OS

This article http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/packagingAppsForMac.html seems to imply a tool is needed at Java 7, so yep, great but why wouldn’t that be in eclipse already, i.e. why would eclipse claim to produce an app bundle if it did it the wrong way? Is it? Time to go build one manually and see.

Manually creating an App Bundle, Java 7 (1.7.0_45-b18), Mac OS X 10.9.2

Downloaded appbundler-1.0.jar from https://java.net/projects/appbundler/downloads, as described in the Oracle article above and put it in a test directory.

Set up the build.xml file from the various entries on the java.net and Oracle articles referenced above and running ant causes a no such file exception. It’s looking for an Info.plist file to be in the build directory. Odd, this isn’t mentioned anywhere!

Helpful: http://supunmali-myexperience.blogspot.co.uk/2012/10/jar-bundler-mac-os-x.html, resolved by setting JAVA_HOME but then I hit another problem:

If you’re not an experience Ant user (and I am not!), what this means is I forgot a target statement in the build.xml file, here’s the file I used at this stage which worked ….. or so I thought, it certainly allowed Ant to build the app bundle.

And this gave me:

Frustratingly, trying to launch the generated .app bundle, I got exactly the same errors. What was going on here? I checked the Mac OS X Gatekeeper security level, it’s set to allow apps downloaded from anywhere so this should work!

Solution

There are many articles on various things which cause the 10810 error, from process table full to permissions and missing libraries.

What a huge diversion all these ratholes are you can go down. This is all so sketchy, returning errors meaning “unknown error”, meaningless “return code 1” in the syslog.

Bottom line is: do not try and follow the examples, work stuff out. Mine was failing because ……. I had assumed the main method name needed specific in the mainclassname statement, as is shown in the Oracle example. As soon as I made it the class name, and not the method it worked. i.e.

Should I post this? After all it was my error in specifying it wrongly. Yes, because if anyone else is searching for answers in this murky, poorly documented space, made messy by Apple divorcing Java without a properly focused handing of the baton to Oracle….. this might just help!

I’m now scared … Mac, Sandbox, App Store: And the world just got infinitely more complicated …. http://www.intransitione.com/blog/take-java-to-app-store/

Having used a hackintosh (Surface Pro) as a secondary machine to my Mac, I don't recommend it for everyone.

* You won't be able to update to the latest patches without possibly breaking the build. There's a possibly you need to re-hack your device every year. Xcode is tied directly to Mac OS X builds. For example, you can't download 8.1 unless your own Sierra right now.

Rat-hole Mac Os Update

Rat-hole mac os update

* WiFi / Bluetooth didn't work for my particular hackintosh, but it'll be better for others.

* Graphics were a bit buggy (again not a problem depending on the device).

* Login would fritz out on occasion so I'd have to boot into safe mode to fix it. Could be my particular device, but random problems are common with hackintoshs.

* When it worked it was amazing, touchscreen worked as well.

* iMessage / FaceTime will not work unless you hack it and provide it your Mac's serial number. Do this at your own risk. This could essentially break iMessage on your original mac. I think I ended up emailing them or something to get it looked into / fixed.

* App Store has some issues as well as lot of things are tied into the serial number of the Mac.

* If you enjoy fiddling and hacking on things, I'd recommend this. It was a good learning experience for me and I don't regret it, but I wouldn't want to do it again. I ended up having to modify some kernel files to get some things working. Basically a lot of tinkering from one patch to another.

Rat-hole Mac Os Update

Having done it once, I wouldn't go the hackintosh route again. While I enjoyed the process, the amount of time I spent to get it work wasn't worth it for me. If price was an issue, it's definitely a good route.

Rat-Hole Mac OS