Post subject: Re: Emulator to install Rhapsody x86 with? Posted: Wed May 13, 2009 6:59 pm
I got a free Thinkpad 760ED from a friend and successfully installed OpenStep 4.2 and Rhapsody DR x86 on it. It was extremely painful as i had to use someone else's floppy drive to write the driver and install disks. Otherwise i would heartily recommend finding one of those excellent laptops and giving it a shot yourself. Its a lot of fun to say the least. (also it will make your EeePC-owning friends jealous at your not so portable netbook skillz)
Post subject: Re: Posted: Sat Jun 20, 2009 6:02 pm
Amateur Beta Collector
Joined Sat Jun 20, 2009 2:48 pm
Favourite OS Windows 2000 Professional SP4
I'm not sure because I haven't installed it for some time but I think it runs in QEMU, and if it doesn't work in QEMU then try Bochs, I'm pretty sure it works in one of the two. It's limited and VERY picky about the hardware it runs on though, and sometimes it takes a couple of tries to get it installing properly so if you use QEMU, don't use the KQEMU module. Also if you're running QEMU on Windows I highly recommend QEMU Manager which makes it much more usable.
Rhapsody could also run a selection of existing Mac OS programs through the "Blue Box" emulation layer. Compared to the "invisible" blue box in OS X, Rhapsody's Blue Box was "noticeable" as it opened a Classic like program and there was no Carbon to help port existing Mac software to the new OS without the Blue Box.
IIRC (and don't quote me), a real copy of MacOS was run between the app you wanted to run and Rhapsody, similar to Classic on OSX which uses a copy of OS9 to run older apps.
When I tried it, i was able to complete the setup procedure in Bochs (both VMWare and VirtualPC failed, and in that period I didn't know VirtualBox existed), but it was painfully slow and the screen was in black&white (I haven't realised yet why).
Post subject: Re: Posted: Mon Jul 20, 2009 2:17 pm
Amateur Beta Collector
Joined Sun Sep 07, 2008 3:37 pm
Not to mention that apart from Aqua and the newer core* kits its API is pretty much the OS/NS API with the classnames adjusted. There's even bits of OpenStep resources in the OS if you poke around long enough.
Apple *never* changed the class names - everything's still NS-so-and-so, and even new features still adopt this prefix (like NSPredicate, for example).