- #Not genuine mac os 9 install disk how to#
- #Not genuine mac os 9 install disk full#
- #Not genuine mac os 9 install disk code#
- #Not genuine mac os 9 install disk Pc#
In addition, you can also access Linux GUI apps on your PC so that is an added advantage.
#Not genuine mac os 9 install disk how to#
Internal TrackpadīInterfaceSubClass 1 Boot Interface Subclassīus 002 Device 004: ID 05ac:8205 Apple, Inc.So in this article, we bring you a detailed guide on how to install Chrome OS on PC with Play Store support.
#Not genuine mac os 9 install disk full#
IdProduct 0x007a Classic Attache Flash Driveīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīDeviceProtocol 0 Full speed (or root) hubīInterfaceProtocol 0 Full speed (or root) hubīus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 002 Device 003: ID 05ac:030a Apple, Inc. This advances the mini's boot process significantly, and should not cause any problems later in the boot process.Ĭode: Bus 001 Device 002: ID 154b:007a PNY Classic Attache Flash DriveīDeviceClass 0 (Defined at Interface level)
So far, I have managed to disable loading the PowerMgr plugin from the device tree.
(Don't forget the leading whitespace!) "nopNNN" is another special case – it removes code, rather than inserting.
#Not genuine mac os 9 install disk code#
But you can also supply arbitrary assembly code in Apple-like syntax. These convenience commands take care of register saving for you (r0-r31 and the LR are saved in the "red zone" below the stack pointer). Otherwise, any arbitrary string can be logged by prepending the argument with a colon. Using ":r3" as the command will log the return value. Exported symbols are no help.) For most C functions, "FuncName-0x4" will allow you to log the function return (before the blr). (Functions, by the way, can be identified only if MacsBug symbols are present. Locations are relative either to the start of the end of a function. *sigh* No other choice then!Ĭode: patchpef.py INPUT OUTPUT Still, I'll see if I can get ahold of an ExpressCard/PCCard with FireWire or borrow a FireWire Mac-OS-9-capable Mac first. I had to replace its hard drive before to see if the Mini was even functional (it was a risky purchase that thankfully worked out), so that's why I know.īy the way, you are right It's the same type of hard disk as the Wallstreet's: 2.5" Parallel ATA (PATA) / IDE.Īnd, really? PATA HDDs will just fit in the Wallstreet's CD slot? I did wonder before, but was never sure, nor ever felt the need to do that, but I guess I have a reason now. I considered that as soon as I was done with my previous post, although I shiver at the thought of doing that again, because the screws that are still left in it (many are missing) are really almost losing their "grip-ability" due to how worn out the screw heads of each screw are, and also because I lack some screwdrivers & other tools that are more proper to reach the Mini's hard disk, meaning the Mini gets damaged each time I do this. Here is some reference output from QEMU with 1.75 GB RAM:ĪAPL,debug bit settings (-OR- bits together):Ģ = Print formatted Mac OS tables (except config/universal info).Ĩ = Dump Mac OS tables (except config/universal info).ġ0 = Print node names while copying the device tree.Ģ0 = Print property info while copying the device tree.Ĩ0 = Print interrupt tree traversal info.ġ000 = Load EtherPrintf utility via parcel for post FCode debugging.Ģ000 = Print BOOTP/DHCP/BSDP information.Ĩ000 = Mark Toolbox image as non-cacheable.ġ0000 = Print parcel info while copying the device tree.Ģ0000 = Print information on device tree data checksums.ġ000000 = Enable the Nanokernel debugger.Ģ000000 * = Display the Nanokernel log during boot.ġ0000000 = Dont attempt to unhibernate system.Ĥ0000000 = Halt after end of FCode (useful if outputting to screen). Both of these files have their COMPATIBLE field set properly, so you might find them a bit easier to run. The second does the same, while calling CompBootStack instead of CompBootStackOld. Here are two new ROMs to probe the crash site. Sub.w #BootGlobalsSize,d0 leave room for QuickDraw stuff. Sub.l a0,d0 get (top useable - sys heap start)Īdd.l a0,d0 get sys heap + (top - sysHeap)/2 Function: computes the boot time stack pointer = sysZone + (BufPtr-sysZone)/2 - space for QD Outputs: A0 - location of stack pointer at boot time