Mac OS X 10.5.2 Released, Biggest Update in Apple History

Following right on the heels of Windows Vista SP1 RTM, Apple has seemingly one-upped Microsoft by releasing OS X 10.5.2 – the biggest update to OS X ever – effective immediately and available to all.

The release documentation for the OS X 10.5.2 build can be found at the Apple site, and it contains all the gory details about this whopping update. It’s 343 MiB (for comparison, Vista SP1 x86/x64 RTM are 434/726 MiB, but they contain plenty more changes) and contains a number of important fixes.

At the moment, you can download the update via OS X’s “Software Update” feature or directly from Apple’s OS X downloads site here. Updates are also available for OS X Server, the direct download link can be found here (382 MiB).

10.5.2 ships with several important security updates that were not previously disclosed/patched as well – if you don’t intend on updating to 10.5.2 anytime soon, you should definitely grab the standalone security update found here.

15 Years to Pick an OS

For the last 15 years, I have been a Windows user and developer. I’ve owned several different computers, all running one version of Windows or another, and sometimes I’d even do a little bit of dabbling in Linux, but for the most part I’ve always felt that Windows could be better. The user interface lacks consistency, and personally I feel that with Windows Vista, things are going down hill.

I was set to build a new computer for myself at the end of February, but I realized soon after I had finished finalizing the specification that I would need to run Windows Vista 64-bit on it in order to take full advantage of my hardware. I’m not much of a fan of Windows Vista 64-bit, due to all of the issues between 32-bit and 64-bit executables and the headaches of 32-bit vs. 64-bit Internet Explorer. After considering many things, like what I plan on doing with my computer, I changed my mind on building that system, in fact I’ve completely crossed it off of my list.

Let me tell you, I never thought I’d see the day where I actually managed to pull this one off…

Continue reading

Apple’s New Animation Framework

Although we try our best to be impartial when it comes down to OS wars, and we have, throughout the years, presented the pros and cons of Windows, Linux, and other operating systems, you’ve probably noticed that NeoSmart Technologies isn’t too big on Apple. Well, color us purple, but this we have to talk about.

Apple [[AAPL]] has a new technology due to ship in Leopard that is pretty damn impressive to hear some of the developers (or at least those at liberty to discuss what they’ve been told) talk about it. According to this Wired News article, this framework will focus on making it easy for developers to add Next (Delicious) Generation graphics to their applications, bringing the concept of UI to a whole new playing field.

While it sounds just plain awesome, we can’t help but look at it with mixed feelings. Since this is Apple and not Microsoft we’re talking about, we’re pretty darn sure everything they say can and will be found in the RTM release of OS X Leopard *cough* WinFS *cough*, but whether or not it will revolutionize the concept of user interfaces everywhere remains to be seen.

Granted, the effects are supposed to be astounding. But that’s not the question, next-gen UIs (hereby dubbed “Desktop 2.0”) are almost always a matter of how and not what. As the Wired article states, these same “amazing” graphical innovations with the UI do already exist in certain programs (like Disco, the CD burning utility for OS X), the only difference is, Apple promises to make it much easier to get the same end results.

Continue reading

Why Apple Delayed Leopard for the iPhone

Yesterday’s news: Apple [[AAPL]] takes developers off of OS X 10.5 “Leopard” to hurry up and meet iPhone deadlines.

Today’s news: Why they did it.

This decision was not about (not) missing deadlines for contracts with Cingular, not allocating enough resources to iPhone in the first place, or otherwise neglecting to do the right stuff at the managerial level – iPhone was delayed, yet Apple chose to trade in an iPhone delay for a 4-month postponement of OS X Leopard. Why would they do that? Is iPhone really a bigger deal than OS X 10.5? Does Apple care more about the iPhone than Leopard?

Apple is notoriously quiet about the future of their products – especially their operating system, OS X. While Leopard is but a bump to the minor version of Mac OS 10, it’s supposed to be a big deal. It’s certainly hyped-up for a lot longer than the actual iPhone – both in and out of Apple. So why this “sudden” shift in priorities? The answer is rather clear, and even self-explanatory.

Continue reading

Apple’s Two Choices

Apple Computer Corp.Ever since Apple Computer Corporation [[AAPL]] decided to switch to the Intel platform, the online world’s been abuzz. Besides the hackers that put OS X on the normal PC, and those that put Windows on the iMac (which NeoSmart Technologies was proudly a leading factor in), it caused quite a stir in the business world. It meant that Apple was once again radically changing its business model to appeal to a bigger number of people.

Not even six months later, Apple had written and released their dual-booting platform to allow users to put Windows on their iMacs and/or MacBooks with much excitement and to general applause. And along the way it raised a very important question: Does Apple primarily sell the hardware or the software?

Continue reading

Making XP work with Apple’s EFI

Macintel Articles @ NeoSmart:

What’s wrong with us!? With me? Windows was my first OS, yet it never crossed my mind to modify Windows to work on EFI? Instead I’ve been taking the super-long, weary, and winding road of getting an iMac to become BIOS compatible. Well, I’m back on familiar terrain, modding XP is where I think I can make it work. Instead of using BIOS emulators or chain-bootloaders and what not, how about just making XP run on EFI? What is NTLDR??

To put it real simple, the NTLDR is activated by the BIOS in order to boot an NT-based OS. NT based OSes include Windows XP, our current focus. NTLDR requires a bootsector in the MBR. EFI requires that a null MBR exist, so using fixntfs as highlighted in my previous post activates the MBR, and allows the booting of XP. After you activate NTLDR, ntdetect.com is run, which gathers hardware information and creates the low-level hardware information layer, which in turn is where Windows XP sends its BIOS-related commands! From Wikipedia:

NTLDR runs ntdetect.com, which gathers information about the computer’s hardware (if ntdetect hangs during hardware detection there is a debug version called ntdetect.chk which can be found on Microsoft support […] Starts ntoskrnl.exe, passing to it the information returned by ntdetect.com.

Continue reading

Hardware Hacks: Macintel XP

Macintel Articles @ NeoSmart:

What started off as a simple post with my ponderings has kicked off quite a stir and now I am deeply motivated to find a fix.. Call it OCD, call it perfectionism, call it (uber)geekiness, I need to find out what can be done to make it work….

Hardware Background

What I am trying to do here is to find a way to do this short of adding another motherboard to the box. Obviously a cheap hardware solution is better than an extremely time consuming software fix, which is still better than buying another mobo just for Windows :) OK.. First let’s establish some facts on the mobo used in the MacBook Pro and the iMac Core Duo (sorry about the naming confusion earlier guys!).

  1. Intel makes the chips. 100% of them. Nothing on it is made by Mac. Maybe programmed by Mac, but not made by Mac. Why? The only reason they switched to Intel was because the cost of making anything compared to Apple’s share of the market nowhere near justified the price. So Apple uses boards made by Intel. Not even customized Intel boards, because that was their gripe with IBM. Apple just doesn’t have enough demand for them to give them customized chips. Also Intel stated that the boards for Apple were just like any other board.
  2. EFI. Currently the biggest obstacle. Intel stated it uses standard boards for Apple (see point 1). From what I have managed to gather the only Intel board with EFI support is the 945 chipset. Not even the 955 or 975 has EFI support. All 945 chipsets currently sold to the public (besides Apple obviously) use BIOS, not EFI. Now that is something interesting to take note of!
  3. The rest of the hardware is one hundred percent PC (ergo, Windows) compatible.

So VERY simply from what I have been able to determine… Mac programmed the EFI and flashed it to a EPROM/Chip on a mobo that supports EFI and/or BIOS. The solution to booting XP on a Macintel is one step:

  1. Grab the BIOS chip from a 945 motherboard and replace the EFI Chip on the 945 in the iMac with it…

But, there are obviously (immediately visible) issues.

  1. It’s an original Intel mobo, not a rebranded (like Chaintech or Abit) so it should technically work….
  2. But at the same time it is a desktop chip which means you lose the APM (advanced power management) features for a Mac.. Or do you?
  3. Well, even assuming it works and you get BIOS onto that mobo of yours (no mean task by itself); congratulations you now have a PC. Not a Macintel. A PC!!!!

Obviously that is not what we want…. But then there is more that can be done to make it work… Now I *presume* OS X won’t boot on a non-EFI platform.. But I highly doubt that Apple would be so naive as to use security via obscurity. After all, soon enough EFI is coming to the PC world too (hurry up Dell!). I believe the key to stopping people from using Macintosh on a PC is the TPM chips encrypted with Apple’s private key. But nevertheless, it boils down to one question: When they compiled the BSD kernel for Mac OS X for Macintel, did they just add EFI support or actually go back and strip out BIOS commands?

Logic would say that they only added EFI and not removed BIOS, simply for compatibility reasons; and should they ever want a BIOS Macintel, they have the compatible code already. What’s more, to actually remove BIOS support from the BSD kernel is like finding needle splinters in a haystack. So long as the code is in an IF bracket that is only activated if BIOS=true it doesn’t slow done the operating system any. So assuming the above is true, you should be able to boot Mac OS X on a BIOS’d version of an iMac or MacBook. Now what if it isn’t true? This is a “guaranteed to work & much work required solution.”

  1. Get a blank EPROM BIOS/EFI chip.. Or just wipe an existing 945 chip clear.
  2. Use asm to write a very simple menu where upon boot you are asked to select EFI or BIOS.
  3. Copy the original EFI code and the legacy BIOS code to the chip. They should fit, it’s a 4MB chip.
  4. Upon selecting EFI or BIOS you get forwarded to the respective code.

Now where to find someone that knows asm that well? Intel, AMD, Apple, Soyo, Award, or AMI would be my guess, but why should they make it anyway? Yeah, so the above was how to do a hardware base solution for XP on Macintel. Why a Hardware Solution is Best

  1. You don’t mess with HD images to get XP installed.. You just get the BIOS working then install from CD
  2. Minimal trouble for the final user… Just get a chip, replace, and boot.
  3. Most likely to work and “failproof”

Why NOT a Hardware Solution

  1. End users will have to buy a chip.. And as far as I know, they are hard to get.
  2. Takes the most time to get working, and most amount of “Hackers’ R&D”
  3. Immediate compatibility with any BIOS based programs.

Actually, so long as Mac OS X runs on BIOS as well as EFI it’s quite easy to implement… If it doesn’t.. Well I told you what needs to be done, the problem is implementing it.

Windows XP on Mac?

This solution is outdated. Use EasyBCD instead.

Macintel Articles @ NeoSmart:

The Problems

  • Macintosh uses a different MBR
  • MacBooks use EFI, XP x86 uses BIOS
  • The modified Darwin Bootloader is made for EFI w/ EFI supporting operating systems

OK… So step by step. Where is the BIOS used? For what? How? The OS sends low-level calls to the BIOS that tell it exactly how to deal with the hardware. Now I don’t have the Windows XP source code at hand.. so all I can tell you for a fact is that NTLDR uses it to access the drive at first to boot Windows, and Windows uses it at *least* once more when it is mounting the drives.

The Required Programs and Stuff

  • Acronis Disk Director Bootable CD
  • Acronis True Image
  • Another computer with a clean install of XP. No programs installed at all.
  • A MacBook obviously!
  • A Windows Vista DVD (not for installation purposes!)
  • Vista boot files
  • bcdedit.exe
  • BCDedit restore file

Most of the problems can be theoretically quickly dealt with.

  1. Using the Bootable Acronis Disk Director CD on the MacBook, shrink the Mac partition. Create a new partition of type NTFS/HPFS in the remaining space.
  2. Setup a clean version of XP on a PC.
  3. Extract Boot.7z to the root drive of your XP installation.. So you have C:\Boot\
  4. Copy bcdedit.exe to the root drive of your XP installation. C:\BCDedit.exe
  5. Copy MacBook.bcd to the root drive of your XP installation
  6. Use sysprep to “reseal” your XP install and remove all hardware info from the setup
  7. Use Acronis TrueImage CD to make an image of your XP install.
  8. Use the bootable Acronis True Image CD to recreate the image on the partition you just made on your MacBook.
  9. Use the Bootable Vista DVD to boot on the MacBook.
  10. Select “Repair Startup” -> Next -> CMD -> Run too.
  11. Browse to drive C:\Boot (which is the partition you created on the MacBook and then extracted the Acronis TrueImage file to). (cd C:\boot)
  12. Run “fixntfs.exe -lh” without the quotes
  13. Browse back to drive C:\ (cd \)
  14. Run “bcdedit.exe /import MacBook.bcd” without the quotes
  15. Eject the CD and restart.
  16. In Mac now, hack the Darwin Bootloader to add another entry that chainloads Drive(0) Partition(2). With GRUB it would look something like this… I’m not sure if Darwin is the same, but this step is very simple, and has nothing to do with EFI.

    title Windows XP rootnoverify (hd0,1) chainloader +1
  17. Restart
  18. By selecting “Windows XP” on the Darwin Bootloader you should be chainloaded to the Vista bootloader, which should in turn boot the entry “NeoSmart Windows XP”
  19. If everything has gone well, XP will boot!!

Macicide

Mac Mini

Mac is committing suicide. Dramatic? Maybe, but nevertheless 100% true. In several bold strokes, they have practically killed off their fan club. Between leaving PPC, going on a rampage asking webmasters to pull vids of MacIntels, telling fans to stop complaining, and becoming another Microsoft.. Then there was the whole issue with the iPod Nano screens that scratch and tear, that are useless if you expected such a costly investment to last longer than a couple of days, and even more was the ardent denial of bad engineering. Then this (from CNET News):

Consumers who buy a Mac Mini this week may or may not end up with a machine that’s faster than the desktop Apple Computer was selling in prior weeks. The company confirmed to CNET News.com that it has started offering machines that in some cases have improved processing powers and other enhancements.

This is tantamount to saying ‘We will ship a couple of better Minis in a basket of rotten eggs. Keep buying, you might get lucky.’ No contender has ever stooped so low before. Yep, not even ‘big bad Microsoft’ Apple is going down, and the coroner’s preliminary report is suicide, er, Macicide.

Source: CNET News