Slashdot Mirror
EFI Modifications Leaves iMac Unbootable?
jerbare writes "In attempting to run Linux and Windows on the new iMac Core Duo, people experimenting with configuring the EFI Console/Boot loader have found they can no longer boot the machine at all. Dave Schroeder of appleintelfaq.com comments, 'We have already irreversibly lost a couple of iMacs trying to load various EFI modules'. Instructions for breaking the iMac's are presently located at the bottom of the comments."
Reminds me of a situation I faced back in the day when I was a tech at a small mom-and-pop computer repair establishment. We received a shipment of motherboards, and found out that the BIOS on every single one of them was corrupt. Since the boards wouldn't even post, the traditional remedy of flashing the BIOS via a bootable floppy was not available. Normally, we would have just boxed up the boards again and returned them for replacements, but we desperately needed those boards to fill orders.
Well, desperate times call for desperate measures...
I got to thinking, "you know...once you've started booting to an OS, that BIOS chip isn't even being used anymore....hmmm". With this in mind, I pulled a working BIOS from another board, swapped it out with the bad BIOS, and powered the system on, booting from the BIOS flash floppy. Once the board had booted to the flash program, I carefully pulled the good chip back out, and put in the bad chip. I then ran the flash program to overwrite the bad BIOS.
Long story short, it worked like a charm. I managed to revive every board in the bad shipment without incident using this unorthodox technique.
Anyway, it should be possible to rig up a similar arrangement here, although as I am unfamilliar with EFI, I'll leave the details up to someone else.
____
~ |rip/\/\aster /\/\onkey
Instructions for breaking the iMac's are presently located at the bottom of the comments.
Uhh, thanks.
Religion for nerds. Stuff that really matters
i bet this means even more people will jump off the cliff trying to install windows, and break even more iMacs.
Does that void the warranty? I bet it does. There you have it. Instructions on getting equipment to hold your desk down for the bargain price of $1300
I could turn a PowerMac into an expensive doorstop ...
James P. Barrett
I have a feeling that a virtualization/emulation with hardware graphics support will be available within 6 months that'll make dual booting pointless. I have a feeling that dual-booting OS X with XP or Vista will not work because it's got EFI/BIOS issues and the hard drive formatting issue. And any number of issues that haven't come up yet.
Unbootable iMacs support an even wider selection of games than do bootable iMacs.
+1, damn clever hardware hackery.
You cannot truly appreciate Dilbert until you read it in the original Klingon.
If you can get it to boot at all, try reinstalling from the 10.4.4 media. That's supposed to fix some changes in the EFI.
i am confident that a workaround will eventually be developed. if it takes destroying a few macs, so be it...
I might have been living under a rock, but how is the state of Linux on these new Intel Macs? Just being curious here, because I havent seen any real talks about it here (maybe I haven't fine read threshold -1 yet).
Dvorak on Doomtech
Isn't this kind of like trying to open the mummy's tomb? Nothing good can come out of it.
This is an early warning!
Wait for virtualization so all of Microsoft's inherent evil can be sandboxed into a self-destructing disk image of darkness and peril.
Great. How about attacks on EFI by malware? An iMac costs just a few hundred bucks. Bad enough. But, what about those shiny new Itanium systems with EFI for 10 grants per box?
Just substitute Apple for Microsoft, Mac for Xbox and Internet for Xbox Live in the following...
Denial Of Service - Putting people at threat:
When you screw this up, do you still get the sad mac?
Hexy - a strategy game for iPhone/iPod Touch
**WARNING** The following instructions will render the iMac Core Duo (Intel) TOTALLY USELESS. There is NO KNOWN METHOD OF RESTORING the iMac Core Duo to a previous functioning state. **WARNING**
/Volumes/EFI; sudo mount_msdos /dev/disk0s1 /Volumes/EFI)
/Volumes/EFI/BIOS32/Bin/GraphicsConsole.efi
I AM NOT KIDDING. THE FOLLOWING METHODS WILL PUT THE IMAC IN A STATE OF DISREPAIR BY AN END USER, EVEN WITH ACCESS TO THE INTERNAL HARDWARE.
With that said, here is how I killed the iMac Core Duo:
1. Downloaded EFI sample implementation and unzipped
2. Moved the 'Binary' folder to the hidden EFI partition (sudo mkdir
*NOTE: this partition appeared EMPTY*
3. 'blessed'
4. Rebooted in to GraphicsConsole
5. Attempted to load an EFI 'Driver' via GraphicsConsole (I forget the process, but it was a submenu. The drivers I attempted were AtapiPassThru.efi and Partition.efi)
6. Reboot and stare at your new broken iMac Core Duo. It's dead, Jim...
Just as Dave mentioned, unplugging the Hard Drive, removing the battery and leaving the iMac without power WILL NOT RESET IT TO ITS FACTORY DEFAULTS.
Because settings are stored in NVRAM, POWER IS NOT REQUIRED TO KEEP THE SETTINGS INTACT.
http://en.wikipedia.org/wiki/Flash_memory
BECAUSE THE APPLE EFI SOFTWARE DOES NOT LOAD THERE IS NO WAY TO 'ZAP' or 'FLASH' THE NVRAM TO DEFAULTS.
The caps are really necessary, folks. Apples implementation of EFI allows software to modify the computers ability to boot - or NOT.
I am unsure if modifying Apple boot software voids the warranty. I was fortunate to get a replacement iMac, but I did not explain what I did to render it unable to boot. Because of that, I'm staying anonymous...
I’ve done the exact same thing to bypass security features on SPARCstations. Try it sometime—it’s fun!
Tangent: you don’t need to understand Chinese to understand the instructions on that page. ;)
Join Tor today!
Does anyone know how well PearPC runs on these things?
This guy's the limit!
Substitute "user" with Malware.
Download the EFI software from Intel: Or include an copy in the malware.
a sudo command: Or use an escalation of privilege vulnerability
and reboot : Err, not that difficult to achive in software.
It's a fairly well known trick, although you're correct that it's a little bit dangerous. But when you fiddle around with BIOS mods, it comes in handy to have a removable BIOS chip for just that reason.
http://www.google.com/search?q=bios+hot+swapping
- Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
When the iMac is in this broken state, it doesn't boot, chime, show anything on the screen, or read from media.
;-)
Can't exactly "reinstall from the 10.4.4 media".
Zapping NVRAM (still supported with cmd-opt-P-R), removing the motherboard battery and letting it sit with AC for an extended period, and disconnecting the hard drive all do not revive the machine.
with research like this they could be onto a MAJOR Windows security breakthrough...
"MAD MAC III: Beyond DumpsterDome."
Coming soon to your local theater.
Hello. Just to give a bit of an update on this issue...
The iMacs in question were rendered unbootable by trying to load additional modules from Intel's EFI Sample Implementation. It is not known which module is at fault currently.
Once the iMac is unbootable, it doesn't chime, boot, attempt to access media, or display an image on the screen. Attempts to zap NVRAM (cmd-opt-P-R is still supported for this task on Intel-based Macs), remove the motherboard battery and leave the AC power disconnected for an extended period of time, and disconnecting the hard disk do not resolve the issue.
At present, we seem to have a number of difficult situations that prevent the installation of Windows directly on Intel-based Macs:
1. Apple did not include its own EFI shell or other tools to access the EFI with the Intel-based Macs, so the tools used have consisted of Intel's EFI Sample Implementation, and Tianocore's EFI Developer Kit.
2. Apple's EFI implementation does not include CSM (Compatibility Support Module), the BIOS backward compatibility layer necessary for booting 32-bit versions of Windows (pre-Vista), such as Windows XP.
3. 32-bit versions of Windows do not currently support booting an EFI machine. (And the Gateway Media Center machine with EFI people keep talking about boots Windows XP Media Center Edition 2005 in BIOS compatibility mode, not with EFI.)
4. Windows XP 64-bit and Windows Server 2003 64-bit support EFI, but the Intel Core Duo is a 32-bit architecture.
5. Windows Vista does support EFI, but the EFI booter (cdboot.efi) currently does not appear to be functioning, and/or it is looking for, and not finding, information that it is looking for on the installation DVD. It does display the typical Windows "Please press any key to boot from the CD..." message. However, the DVD does not appear to contain the necessary EFI boot partition, and EFI does not support UDF volumes and El Torito booting. (Yes, this is a DVD obtained via official channels.)
6. Mac OS X's startup disk control panel presents a Windows Vista installation on a FAT/FAT32 volume as a valid bootable volume, but Windows Vista does not support booting from a FAT/FAT32 partition, only NTFS. Mac OS X can read NTFS volumes, but not write to them. This is currently the stage we're at now. No, I haven't tried "just hooking up a drive with Vista installed" (as many have asked elsewhere) or forcibly creating an NTFS partition whose contents are an already-installed instance of Vista.
7. grub, elilo, etc., all do not work on the Intel-based Macs at this time.
Eventually, whatever method boots Windows natively will have to have a nice wrapper put around it to make it easy for a normal person to do so, and easily dual boot in addition.
To regurgitate what I've said a bit elsewhere, the real benefit to most people will come from running Windows alongside Mac OS X in a "virtual machine" environment, in a window or even full screen, with, for example, a hotkey to switch back and forth between Mac OS X and Windows. To many users who prefer Mac OS X, particularly in enterprise, academic, and research environments, but who also have the occasional applications (usually administrative) that require Windows, this configuration would be a holy grail of sorts. And in this configuration, Windows wouldn't be running in emulation, but it would be running at essentially the native speed of the underlying hardware (with the exception of graphics and disk I/O performance). It will be *much* faster than any emulation ever has been, and there will no doubt be several open source (qemu, xen, wine) and commercial (vmware, Virtual PC) that will allow running Windows (or Windows software) in various capacities. Intel's Virtualization Technology (VT), allowing multiple operating systems to run in separate hardware "partitions" on one
"Apples implementation of EFI allows software to modify the computers ability to boot - or NOT. "
Enough of this firmware is flash-based that software can trash it to the point that it no longer boots from optical media. Key-mashers need to understand that EFI *precedes* the Apple Option-key tricks, so if EFI is hung you are crap out of luck. Unless there's some jumper inside the case which resets EFI to a factory state, that EFI will have to be pulled and reflashed.
We're going to pretend Apple doesn't really release mistakes like this and that there's a failsafe for restoring the EFI. Otherwise, you potentially have the mother of all DRM traps in front of you.
"Made up/misattributed quote that makes me look smart. I am on
Actually, if you RTFC (RTF Comments) which are at the end of the article (as it says in the story) you'll find that you can completely screw your new Intel Mac into not booting. Not even running the OS X install CD will fix it. Here's one of the comments describing the problem:
infested with jello like fishes no melotron wishes
Is the EFI cachable? And if so, wouldn't it be possible to create a custom boot which cached custom EFIs so you could experiement without overwriting the nvram/eeprom/whatever? Alternatively, if everything else is the same between intelMacs and typical PCs, wouldn't you be able to cache an EFI to boot MacOS?
https://www.eff.org/https-everywhere
Because the nature of the effort was to boot XP, they are no longer booting Windows instead of no longer booting OS X.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
That whole "escalation of Priviledge" link would be a lot scarier if it didn't have so many items that required things like physical access or a user markign scripts setuid, or have been fixed for a year or two now by regular OS patches.
At least there is the wall of trying to find an escallation attack that will work, which is one step ahead of other systems.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
For those that would die defending it, Freedom
has a sweet taste that the protected will never know.
Wouldn't it be easier just to install Linux?
Why the heck would anyone buy grossly over priced Apple hardware to run Linux and Windows?
P.S. my posting security image word was "beaver", do I win a prize?
somewhere in this thread are various instructions on how to fix it.
You have to hope that there is simply some unknown way to reset the PRAM short of taking the system in. I would guess this is not caused by an DRM code, but it does show you an interesting issue with any DRM code that would happen to act this way. These people were not exactly trying to commit piracy when they did this but would DRM code not still lock them down? For that matter if a virus writer can duplicate the conditions that would trip off this are a like DRM lock down I can just imagine the glee with which they would create the code. What concerns me is that there appears to be an easy code based way to cause a hardware failure in these macs. I know on my ASUS system that the CMOS has a form of protection that will at least alert me should something try to write to this layer. I would also think a permanent fall back system would be helpful. Maybe something that just read one usb port or something like that for an update.
Try This:
1. Remove the primary battery on the notebook
2. Open up the notebook and remove it's internal battery.
3. Power on the notebook (without it's batteries installed).
4. With the notebook on, turn it off by removing the power cord.
5. Leave notebook sit for at least 1 hour, the longer the better.
Now plug the notebook back in and turn it on, if it starts up and displays an error message saying it's lost it's CMOS settings or something like that then your good to go.
iPaperweight.
G-Force music visualization
Ok, great, so we can't break the Intel Mac by putting Windows on it because just attempting to infect it with that viral disease of an operating system breaks the Mac. What about installing Linux? Yes, I know OS X has all the benefits of Unix with a prettier GUI and all that nice stuff (and I really do think it's the best OS on the market right now)... But I like to have MULTIPLE FLAVORS of Unix based systems on my computer... I know they also stated that you couldn't boot from Grub or LILO. So does that mean no Linux either? I wanted to get one and quadruple boot it with OS X, Ubuntu, Linspire, and Windows (yes, it's a viral OS, but I do play SOME games, and occasionaly for testing I need Windows). Guess I'll just wait until the 12" notebooks come out and just get that for OS X (although, by then it'll probably be hacked), but I have a desktop that's powerful enough--I just need a laptop for mobility, so smaller/less powerful is better for me.
Read my blog posts on usability.
WTF? It certainly wasn't very wise to muck with the EFI before being able to save a copy of the EFI.
Obviously, that is what should've been done first. Do these ibricks allow booting into single user mode? [before killing it, of course] Perhaps one could get an EFI dump in there? [then muck with other EFI modules]
See, at least I'm not pretending to be teh hacker.
Mike
By following these steps, the iMacs that had difficulty with certain EFI modules appear to have been restored to a functioning state:
1. Disconnect the internal hard disk
2. Disconnect the iMac from AC power
3. Plug in AC while holding the power button
4. Power up the iMac and zap NVRAM (cmd-opt-P-R)
The hard disk can be reformatted and the operating system restored.
Until and unless Apple publishes a spec for how to modify the EFI, this is in the "you broke it, tough shit" category.
-jcr
The only title of honor that a tyrant can grant is "Enemy of the State."
Could it be that the TPM module is being used to verify the state of the EFI?
It would make sense to me, that one of the most fundamental aspects of a Trusted Platform Module would be to ensure that the platform is booting in a state you can trust, and not booting on some hacked EFI pointing to (and enabling) devices that the user has no idea are installed. As this is Apple's (or any major vendor to my knowledge) first foray into the TPM arena, perhaps this is part of that whole security featureset that you paid for but can't work with, I'm in the same boat, and would like to feel free to try Darwin in other incarnations as well as use the equipment for Windows and prove to my friends outright why Apple is such the superior gear.
Is there any way we can map the calls made on the system bus during the complete post? Do we have ANY information on how TPM is being used here?
There's a glaring hole in the documentation imho a long way from the 1984 ad...http://www.uriah.com/apple-qt/1984.html but there always seems to be someone's visage up on that screen no matter how you slice it.
cyberbianif I claimed I was emperor just because some watery tart lobbed a scimitar at me they'd put me away!
I got tired of mucking around with all the electronic gobbldeygook connected to EFI, so I just tore all that shit out and bolted on a good old-fashioned Holley 4bbl carburetor...
Next step is a hood scoop and a bigger hard drive...
I know of, actually witnessed, one where the chip blew off a piece of the case and continued to function. One sixth of a hex inverter was gone with that chunk of plastic, but the other five were OK. My EE coworker kept the chip and had it mounted.
Good judgement comes from experience, and experience comes from bad judgement.
- W. Wriston, former Citibank CEO
I was thinking of something (cartridge ripping) back in the Atari days and then had this thought.
:)
Is it rip a standard BIOS like Award or Phoenix off the chip and onto disk and then use EFI to boot the Award/Phoenx code "like an operating system" for instance -THEN use that to boot the XP Code?
ie: EFI boots (modified?) Award, Award Boots XP.
That way we can break several laws at once too
also:
Back in the atari days you had those neat pass-thru cartridges to put between the game and the actual system - possible with bios chips too?
Lk4
"It's what you learn after you know it all that counts", Earl Weaver - Legendary Coach of the Baltimore Orioles
iVoodoo ;P
From Dave Schroeder posted 01/23/06
By following these steps, the iMacs that had difficulty with certain EFI modules appear to have been restored to a functioning state:
- Disconnect the internal hard disk
- Disconnect the iMac from AC power
- Plug in AC while holding the power button
- Power up the iMac and zap NVRAM (cmd-opt-P-R)
The hard disk can be reformatted and the operating system restored.Mod parent up.
This basically is the answer to the question behind the first ~100 or so posts (mine included).
So it's not an irrecoverable "bricking" problem, but it does get close.
I wonder if it's possible, rather than reformatting the HD, to put it into another machine and just wipe the partition with the bad NVRAM image on it. Not that it really matters in a test environment (which I hope is the only place anyone would ever try this), where you'd probably want to reformat and reinstall anyway, but I just wonder if it's possible.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
The "rip out the battery and let it disspate" doesn't work.
Because the settings are being written to a segment of RAM that holds settings even when no power is applied.
Chas - The one, the only.
THANK GOD!!!
Like so?...
Ladies and Gentleman, on behalf of Captain Temptest and his crew may we welcome you aboard Routine Scientific Survey Flight Nine.
Before we enter into an outgoing take-off scenario it is space fleet command regulations that we take you through emergency procedures.
Firstly, may we respectfully point out that the use of all audio visual recording devices, including flash photography, is strictly prohibited on board this flight.
Secondly, may we point out the emergency exits. They are located here, here and here.
In the event of cabin decompression, oxygen masks will come down from the overhead compartments. Place them over your mouth and nose and breathe normally.
Finally the POLARITY REVERSAL DRILL. If you look below you/ahead, you will see the Klystron Generator.
On it is marked "KLYSTON GENERATOR. DANGER. DO NOT REVERSE POLARITY"
Polarity is reversal is a very dangerous procedure that's why we tell you not to do it. However, in the unlikely event of entering a polarity reversal situation, we ask you to follow this simple drill:
Your backwards chip comment brought back memories... A friend had one of the original Pentium (50? 75?) that had the floating point math bug. He got the replacement from Intel, and yanked the old chip off his motherboard. When he went to install the new chip, he saw that it would fit two ways, and there really wasn't a "key" pin to line up. So, back in went the old CPU to test which way was right. Lets just say the old CPU died a horrible, extremely hot, death. The new CPU installed (180 degree rotated, of course), and all was good.
It simply opens the door for a home based business selling BIOS chips!
This doesn't worry me as much as a multi-tiered internet. Now that's fucking war!
Rick B.
Controlling the hardware platform has allowed Apple to concentrate a lot of effort on fast, efficient drivers, which compensates a lot for the XNU kernel's ineffiency. Still, I personally consider it to be slow (perhaps ponderous would be a better word) but on modern hardware it's fast enough for most people. I'd say the same about most versions of windows, incidentally.
Your comment about the benjamins, though, is right on. Apple's rolling in iPod money right now.
Here's a link to a PDF describing Intel's virtualization technology and how to make it go. Everyone get to work.
Well, Apple did say that they wouldn't prevent Windows users from using that operating system on Macs. Then again, they didn't say it'd be easy. Anyway, since when does Microsoft include drivers with Windows for Macintosh hardware? Now I know why they used EFI instead of BIOS.
02BD6C88 7B 7B 7E 7E 20 20 2F 2D 2D 2D 2D 2D 5C 20 20 20 {{~~ /-----\
02BD6C98 7B 7B 7E 7E 20 2F 20 20 20 20 20 20 20 5C 20 20 {{~~ / \
02BD6CA8 7B 7B 7E 7E 7C 20 20 20 20 20 20 20 20 20 7C 20 {{~~| |
02BD6CB8 7B 7B 7E 7E 7C 20 53 20 54 20 4F 20 50 20 7C 20 {{~~| S T O P |
02BD6CC8 7B 7B 7E 7E 7C 20 20 20 20 20 20 20 20 20 7C 20 {{~~| |
02BD6CD8 7B 7B 7E 7E 20 5C 20 20 20 20 20 20 20 2F 20 20 {{~~ \ /
02BD6CE8 7B 7B 7E 7E 20 20 5C 2D 2D 2D 2D 2D 2F 20 20 20 {{~~ \-----/
02BD6CF8 43 6F 70 79 72 69 67 68 74 28 43 29 20 32 30 30 Copyright(C) 200
02BD6D08 31 20 41 70 70 6C 65 20 43 6F 6D 70 75 74 65 72 1 Apple Computer
02BD6D18 2C 20 49 6E 63 2E 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D , Inc.----------
It took me three months to bring up the Mac OS on the Atari ST. It was kludgy and had bugs, sure, but it ran MacWrite and MacPaint, which was pretty much what was out there back then. That was with one person working on it.
...
On the EEPROM issue, why don't people just burn a write-once PROM that can't be reprogrammed, or, just bend up the PROGRAM* pin (same effect, really) ?
I also wonder why an EEPROM with twice the space could not be used, and a simple switch on the top address pin used to select which "BIOS" to use. Or, tweak something like LILO to set an available pin somewhere during boot to do the same.
Didn't take all that much time for Phoenix, et al, to clean-room reproduce the IBM PC ROM. (Admittedly, it did ship with a nice listing and the functions were straightforward). I would be really surprised if implementing the PC BIOS on the iMac proves very hard.
Just my opinion, as usual
-- Dave
From Dave Schroeder
posted 01/24/06
Actually, to those people who think Apple is using TPM/Trusted Computing to actively *prevent* anything other than Mac OS X from booting on the Intel iMacs, you are categorically, one hundred percent wrong.
Apple has done NOTHING to prevent other OSes from booting, as long as there are booters that support Apple's EFI implementation.
There will be Linux distributions, BSD distributions, and Darwin distributions that will definitely run on Intel-based iMacs once EFI (and Apple's EFI implementation specifically) is properly supported in their bootloaders. And it will be.
Apple is doing NOTHING to actively prevent or allow the booting of alternate operating systems, period. Including Windows.
Now, you might say, accurately, that Apple is doing nothing to help, either. But it has no need for legacy BIOS, and EFI is the firmware of the (foreseeable) future on PC platforms as well. It's just that Apple is really on the cutting edge here, and is, again, the first manufacturer to deploy a technology in a widespread, mainstream way. In this case, it's EFI.
Can a novice or recreational user easily get it to boot other OSes without some further development of, e.g., bootloaders? No. But that will happen, and it's only a matter of time.
I just wanted to clarify this point, because Apple is certainly not going to disallow Linux, *BSD, Darwin, OpenDarwin and other UNIX variants from booting on Intel-based Macs, and it's not doing anything specific to prevent Windows from booting, either. It's also not doing anything specific - indeed, anything at all - to SUPPORT Windows booting on these machines.
Apple knows full well that people will be running Windows in virtualization on these things, and that will be *far* more useful to *far* more people than dual booting, and it's certainly not going to be stopping that, so why would they stop people from booting Windows and only Windows natively? Think for a second, people.
Now, the REVERSE is true, however: Apple IS using TPM to tie Mac OS X to Apple hardware. But it is NOT using TPM to *prevent* other OSes from being run on Apple hardware.
- Dave Schroeder
das@doit.wisc.edu
http://das.doit.wisc.edu/
There is a company that makes a bios saftey backup bridge device You plug it into your mother board and you plug the chip into the device. You can keep a backup copy of your bios chip and switch back and forth. Check out RD1-1M BIOS Savior [RD1-1M] 14.00EUR Click to enlarge What is a RD1-1M BIOS Savior? Have you ever updated your PC BIOS? Have you ever experienced or heard about what BIOS update failure may cause? RD1 BIOS Savior is a tool which enables you to update the BIOS safely. Once you backup your current BIOS data into the RD1 BIOS Savior!, even if you fail on BIOS updating several times, the system will reboot simply by shifting the switch. RD1 BIOS Savior is nicely packaged as shown on this right. The RD1-1M Bios Savior comes with: - Installation manual - Flash Eprom 1 Mbit bios chip with DIL socket - Bioschip-selection switch: you select the bios to start your computer ! - Backplate to install the switch in the pc case - DIL Extractor for easy bioschip extraction - Sticky label with Bios Savior Logo - And everything in an Anti-static package - Size: 160 x 132 x 23 mm This RD1-1M Bios Savior is 100% compatible with DIL bios chips which has a capacity memory of 1 Mbit and runs on 5 volts.
Dave,
I'm a former Atari ST user... and I have fond memories of MagicSac and Spectre GCR, though I couldn't afford one at the time (I was just a broke teenager).
Anyways, back on topic -- I suspect everyone is going to exhaust trying to hack XP on to one of the new Intel Macs via software before going the hardware route.