(This is a guest post by Antoni Sawicki aka Tenox)
Apps for Windows NT RISC… Alpha AXP, MIPS and PowerPC. Happy downloading.
(This is a guest post by Antoni Sawicki aka Tenox)
Apps for Windows NT RISC… Alpha AXP, MIPS and PowerPC. Happy downloading.
YES it’s real!
I’m using the Linux subystem on Windows, as it’s easier to build this Qemu tree from source. I’m using Debian, but these steps will work on other systems that use Debian as a base.
First thing first, you need to get your system with the needed pre-requisites to compile:
apt-get update;apt-get upgrade apt-get install build-essential pkg-config libz-dev libglib2.0-dev libpixman-1-dev libfdt-dev
Great with those in place, now clone Artyom Tarasenko’s source repository
git clone --branch 40p-20190406-aix-boots --single-branch https://github.com/artyom-tarasenko/qemu.git
Since the frame buffer apparently isn’t quite working just yet, I configure for something more like a text mode build.
././configure --target-list=ppc-softmmu --disable-sdl --disable-vnc --disable-gtk --disable-gnutls --disable-nettle --disable-gcrypt --disable-spice --disable-numa --disable-libxml2 --disable-werror
Now for me, GCC 7 didn’t build the source cleanly. I had to make a change to the file config-host.mak and remove all references to -Werror. Also I removed the sound hooks, as we won’t need them. remove the following lines:
Now you can build Qemu. it’ll happily build in parallel so feel free to build using the -j parameter with how many cores you have. I have 32, so I use
Okay, all being well you now have a Qemu. Now following the steps from
Artyom Tarasenko’s blog post, we can get started on the install!
First we create a 8GB disk
qemu-img create -f qcow2 aix-hdd.qcow2 8G
Next we need the custom BIOS with serial as the console.
You’ll need some AIX. I tried a 3.2.5 CD-ROM and it didn’t pick up, but AIX 4.3.3 did.
Now with all those bits in place, it’s time to run Qemu.
./ppc-softmmu/qemu-system-ppc -M 40p -bios q40pofw-serial.rom -serial telnet::4441,server -hda aix-hdd.qcow2 -vga none -nographic -net none -cdrom Volume_1.iso
Now telnet to your localhost on port 4441 and you will see the console doing it’s BIOS initialize and eventually drop to the OK prompt.
One trick I’ve found is that from the Open Firmware prompt you can find out what partitions are recognized from the firmware. If it see’s partitions then there is some hope that the image you have is valid enough to boot. In the last few days I’ve found quite a few AIX images, which are lacking the partition table, and unable to boot.
simply type in boot cdrom:2 to kick off the installer. It may take a minute or so for the installer to kick off.
If all goes well, you’ll see the BIOS reload itself, then after a minute you’ll be prompted to press 1 to select the console
It doesn’t echo, don’t panic!
Next select your language. I’m doing English.
Next it’ll ask about installation type. Default ought to be fine.
Because this will destroy the contents of the disk (which doesn’t matter as it’s blank) it’ll prompt for confirmation.
After this it’ll begin the installation. Depending on how fast your disk & CPU is this will take a while.
For me, the installation took about 11 minutes. This is using my Xeon E5-2667 v2. It took 17 minutes on my 2006 Mac Pro, with X5365’s it .
After it’s done, right around the 96% time it’ll reboot back to the BIOS
Once you are back at the OK prompt, you can now boot disk:
it’ll look like it’s hung for a minute, then it’ll start booting from disk!
Once the OS is booted up, you select the terminal type. I’m using putty but I’ll select the vt100. Of note the function keys are selected by hitting escape and then the number key. So F3 is ESC 3.
I’m just going to finish the install, as we can always run smitty to mess with the system more, but right now I’m just interested in a base install of the BOS (Base Operating System, and IBM ISM).
A few moments later, you’ll get dumped to the login prompt.
By default there is no password, so just login as root, and there you go, your very own virtual AIX 4.3 system.
# uname -a AIX localhost 3 4 000000004C00
So there you go! All thanks to Artyom’s hard work!
I just got another PowerBook, and the disk had been wiped by the prior user, and all it did was boot up to the blinking mac face. So not very useful. I did luckily buy some CD’s from a user on reddit a few months ago, so I had 10.4 install DVD, and an install of 9.2.2 for the emac.
Now the OS 9, is an install disc, not one of the recovery discs, and naturally the aluminum powerbooks don’t boot OS 9, so I’m kind of out of luck for getting Classic working, or so I had thought. I copied the System Folder from the CD onto the hard disk, and told the classic applette to boot it, and it updated some system files, and then gave me this fine message:
So this got me thinking, back in the Sheepshaver days when trying to boot from an ISO as a disk file, it fails the same way because the image is read/write. If it’s read-only it does boot up however. So I used disk util, and made a new read-only disk image from a directory, and pointed it to a directory that I’d moved the CD’s system folder, desktop to. After mounting the read only image, it booted!
Now for the best part, I then kicked off the installer from the CD, and had it install a copy of OS 9, onto the OS X disk.
It’s worth noting that just about every optional install fails. It’ll come back with an error, and you can skip the component. It’s probably just easier to install the minimal OS image.
But rest assured it really does install.
After the install you can eject the CD, unmount the read-only copy and tell the classic to stop and then boot from the new installed copy of OS 9 on the OS X disk. It didn’t interfere with my OS X from booting, although the ‘sane person’ would probably have disk image make a small (1gb) read/write virtual disk, and have the installer install to that.
So to recap, copy the system folder from the CD onto read-write media, and let classic update it. get it to the point that it’s not happy about being mounted read-write. Move it to a read-only disk image and have classic boot from that, and then run the OS 9 installer to install itself to whatever target disk you need or want.
I’ve run Netscape 4, IE 3 & 4, QuickTime 4, and the SIMS version 1 (the OS 8/9 carbon version). using 10.4.0 on an aluminum powerbook.
I don’t know if anyone else has done this, I couldn’t find any real concrete guides for installing OS 9 from OS X. So here we go.
Wow the time sure flies!
(Video in MPEG-1/Audio MPEG-2 care ofÂ JSMpeg).
I know it's terrible quality but finding video from these old Apple events seems to have been recorded on VHS, and then re-recorded using the 'best' video capture technology for under $100 of the era leading to some really poor quality.Â Such is the internet I guess.
I didn't buy a first generation but I did have a 2nd generation 333Mhz green iMac to run OS X Server 1.0 ... Who wasn't excited for the prospects of the next millenium?
In my last trip to the United States, I scored yet anotherÂ PowerMac G5, a model 7,2 which is one that is capable of running OS X 10.2.7 for the G5.Â It was the proverbial dream come true, used by an elderly man to keep track of photos in iPhoto, which he used maybe a handful of times a year.
Needless to say, he wasn’t too pleased that his copy of Snow Leopard didn’t work on the machine, and he dumped the G5 for a much quieter MacBook.
At any rate, it also included an Apple Studio Display.Â I found another Cinema Display in the used hardware market for $25, which even though the display works the screen was damaged at some point and shows scratches on the surface when the display is a solid colour.
At any rate, the machine was deadly slow to boot, I upgraded the RAM from 256MB to 1.2GB, and replaced the ancient disk for aÂ SAMSUNG SSD PM830 2.5 256GB flash drive.Â Now it’ll boot up in under 30 seconds from the graphics initialization.
That makes this the only machine I have capable of running MacOS 9, although in emulation under OS X 10.2.Â I have the Jaguar DVD set, but Classic mode was removed in 10.5.Â It was the ending of the PowerPC era, just as 10.6 was the last version to ship with Rosetta.
Its a fun machine from the era of the introduction of personal 64bit RISC computing to the home user, although too bad the full industry didn’t catch up until later, just as 32bit desktop computing had a few stumbles out of the gates.
Interestingly enough a lot of the same weirdness of missing bits I saw on the x86, is also on the PowerPC.
There is no nice installer, the CD image actually boots MacOS 8.6 which currently won’t run on Qemu.Â However Darwin 1.0 uses MacOS 9, which will.Â There is not install program for Darwin, rather you need a secondary disk, that is partitioned so the volume manager will pick it up, and then you restore a backup onto the target disk.Â Naturally the restore program from 0.3 won’t work, but the 1.0 will under the G4 Cube MacOS 9 CD-ROM install.
Also I couldn’t figure out the boot parameters soÂ I used Steve Troughton Smith’s BootX loaderÂ https://github.com/steventroughtonsmith/BootXÂ to get the OS booted.
qemu-system-ppc.exe -L pc-bios -drive file=..\darwin03.qcow2,index=0,format=qcow2,media=disk -drive file=BootX_custom.dmg,index=2,format=raw,media=disk -prom-env “boot-device=ide1:2,\BootX” -prom-env “boot-args=-v rd=hd0 debug=0xffe kdp=2” -prom-env “boot-file=ide0:8,\mach_kernel” -M g3beige
It’s a little convoluted but it does work.
I put together a binary package for Qemu on sourceforge here:Â Darwin03-PowerPC_qemu-2.11_04_22_2018.7z
Currently there is no networking, I’m guessing I need drivers from OS X 1.x but Ive had really bad luck with the mouse to try to open a terminal window to see if the newÂ sungem NIC is functional at all.
That’s right, the ADB is usable enough now to type and move the mouse, meaning that OS X Server can now be installed within Qemu!
It’s incredibly slow, and the mouse is incredibly jumpy, but it’s actually running!
Basically, like A/UX, you boot up into MacOS to partition the drive.
qemu-system-ppc-screamer.exe -L pc-bios -m 256 -M mac99 -prom-env “boot-args=-v” -prom-env “auto-boot?=true” -prom-env “vga-ndrv?=true” -hda 2GB.vmdk -cdrom “Mac OS X Server 1.2, MOSX_Booter.iso” -sdl -device usb-mouse -device adb-keyboard -boot d
And then kick off the installer:
Which really isn’t much to do, other than tagging the partition, and prepping the machine to reboot.
Qemu doesn’t emulate the NVRAM, so it’ll complete with this ‘non fatal’ ‘fatal error’
After that, boot into the OS X Server kernel, and continue the install:
qemu-system-ppc.exe -L pc-bios -prom-env “boot-args=-v rd=sd0″ -drive file=2GB.vmdk,index=1,format=vmdk,media=disk -M g3beige -cpu g3 -drive file=”Mac OS X Server 1.2, MOSX_Booter.iso”,index=0,format=raw,media=cdrom -prom-env “boot-device=cd:9,\\:tbxi” -m 256 -net none
It will then format the disk, and copy over the base operating system.Â After that it’s time to shutdown, and reboot the VM.Â I couldn’t figure out a pure hard disk boot, but again using the CD-ROM, you can just tell it to pull the root from the hard disk.
qemu-system-ppc.exe -L pc-bios -prom-env “boot-args=-v rd=hd0″ -drive file=2GB.vmdk,index=1,format=vmdk,media=disk -M g3beige -cpu g3 -drive file=”Mac OS X Server 1.2, MOSX_Booter.iso”,index=0,format=raw,media=cdrom -prom-env “boot-device=cd:9,\\:tbxi” -m 256 -net none
And after this, it’ll want to reboot again.Â Launch it up and now we get the initial setup
And with that out of the way, we can logon!
And after a while, it’ll load up the desktop
As mentioned above, the mouse is incredibly jittery.Â Doing anything graphical is very difficult. But here we are, running OS X/Rhapsody for the PowerPC!
Because the mouse is VERY jumpy at the moment, Im going to make some pre-configured disk images available because running the disk tool under OS 9 is a major pain.Â The first image has only been partitioned, while the second has completed the ‘text mode setup’, aka a minimal install.
And that’s it for now!
It’s the ‘classic’ MacOS. And it requires Code Warrior 10 to build. Apparently its for the PowerPC only, although I haven’t tried to compile it yet, as I foolishly just upgraded to 10.5 on my PowerPC, which of course has no classic support.
It’s a nice present from Night Dive studios.Â I know that many people are mad at their reboot being consumed by feature bloat, but at least they aren’t going down into obscurity.
As always, enjoy!
I was pretty amazed to see it even get this far.Â Credit to Steve Troughton Smith for his patched BootX, which gets the boot process this far.Â It’ll actually start the NeXTSTEP style install, but the keyboard won’t work either USB or ADB.Â Oh well.
..\qemu-system-ppc.exe -L .. -m 256 -drive file=MacOSXServer10.iso,index=0,format=raw,media=cdrom -drive file=BootX_custom.dmg,index=2,format=raw,media=disk -drive file=bla.disk,index=1,format=qcow2,media=disk -prom-env “boot-device=ide2:2,\BootX” -prom-env “boot-args=-v rd=sd0 debug=0xffe kdp=2” -prom-env “boot-file=ide0:11,\mach_kernel” -g 800x600x8 -device adb-keyboard -device adb-mouse -cpu G3 -M g3beige
I saw this floating around on some web site… And I thought I’d take a look! Â Well it’s exactly what it sounds like, an ancient MS-DOSÂ text base database from the fine folks at Folio who would later on sell off, merge and become part ofÂ LexisNexis.
And what fine things were there in 1993?
Let’s not forget the false hope and promise of the IBM/Apple/Motorola PowerPC that was going to save us all, and give us the grand unifying microkernel OS of them all, PINK.
The IBM Power Personal Systems Division is introducing and demonstrating technologies featured on its family of personal workstations. Â The Personal Workstations marry Â the high-performance PowerPC RISC microprocessor with industry-standard PC components. Â The PowerPC is featured with new human interfaces, integration of multiple operating systems environments on a single platform, and the latest in operating system, multimedia and collaborative computing technologies. Â OEMs, IHVs and ISVs can explore how they can use these technologies.
Yeah, as we all know Windows NT for the PowerPC wasn’t a thing until late 1995, then killed off in 1997, Solaris saw a single release, MacOS stayed hybrid 68000/PowerPC until the acquisition of NeXT, and then was the basis of Rhapsody/OS X 1.0 and then OS X 10.0 . Â A/IX easily transitioned from the POWER to the PowerPC, while OS/2 only went as far as a limited beta, and PINK/Taligent just never happened. Â Although thanks to hard ware assisted virtualization (VT-x/AMD-V) it really didn’t matter as we can run pretty much whatever OS we wish at pretty close to native speeds. Â The line between Type-1 & Type-2 hypervisors has been blurred to the point of really not mattering anymore.
If anyone cares, I extracted the temperamental disk image asÂ F93.ZIP