Mac OS 9 Discussion > Mac OS 9, Hacks & Upgrades
BlueBox in Mac OS X DP2
zsn0w:
Hi all,
I am trying to get the BlueBox (and I guess by extension Classic mode) in Mac OS X Developer Preview 2 updated to 9.1 so I can run Photoshop 7. It comes on 9.0. I can install 9.1 no problem, but then, after a restart, it will not boot. It just sits at the Happy Mac icon. I tried copying the "MacOSROM" file from a 10.0 Cheetah install to replace the one that DP2 uses thinking that may be the issue, but then it just yells at me that the ROM is corrupt or missing, so that won't work (maybe I could take the one from the public beta or DP3 or 4? but I know at least in DP3 it's still only running 9.0 out of the box). Anyone have any thoughts on what the issue could be? It seems to me like there's not a huge difference between 9.0 and 9.1 besides the Window menu being added, but I have never really used 9.0 much, it's always been 8.6, 9.1, or 9.2 for me.
My next thought is that there might be a "classic support" file somewhere like there is in the released versions of OS X that is getting wiped or upgraded with the install that BlueBox can't handle/operate without the original of? Could there be some extra extension doing it? I would think that that would cause the freeze to occur once the Mac OS 9.1 screen comes up, not the happy Mac screen?
Is there a way to manually update components of 9.0 to 9.1 on at a time to test compatibility of different things and get it to a point where I can install Photoshop 7?
Any help or suggestions are appreciated.
Thanks,
Zack
Knezzen:
This is unknown territory for me, but someone here will probably be able to help you out :)
IIO:
as you know, photoshop 7 would also run in a proper OS like 10.4.11, but i take it that there must be a reason to use it in blueblox under pre 10.0 :)
i can only guess. as there is probably no checksum validation or something in that field, maybe it is enough to change the version number of the Classic ROM and some other system files? so that they look like the ones from 9.0?
Jubadub:
Check for any files inside your System Folder with the name "Classic Support yadda yadda" or similar. These are created, and added, by Classic on most Mac OS X versions. I don't know if Cheetah's Classic uses those, but it's worth a look.
I don't expect the MacOSROM file to have anything to do with giving you the Classic/BlueBox support you need. But I could be wrong.
Also, rather than using Cheetah, try a closer relative: check things with the BlueBox/Classic for Mac OS X DP3, DP4 and also Mac OS X Public Beta.
--- Quote from: IIO on March 16, 2024, 08:17:47 PM ---i take it that there must be a reason to use it in blueblox under pre 10.0 :)
--- End quote ---
It's the latest version that still retains Mac OS UI and UX! (Personally, though, I prefer Mac OS 9.2.2 for that.)
zsn0w:
As Jubadub said, the reason to use BlueBox in DP2 is that it retains the Mac OS UI and UX (and thus graphical speed as well), while also offering some advantages over OS 9. I enjoy the file navigation in OS X, but I also enjoy the more spatial approach in 9 for some things. Rhapsody and the OS X DPs has a sort of mixture of the two that is really nice to use - you start in a column browsing folder viewer, but double clicking any folder will break out a new window and act like classic Mac OS file browsing. Having unix underneath everything is nice for me when dealing with file storage and organization. I also just like the quirkiness of it and feel that it fits my PowerBook G3 well.
I haven't had a ton of time to mess with this since my initial post - St. Patrick's Day always has me pretty busy, and then today the starter on my car died, so I'll be removing the old one and replacing it whenever the part arrives. Hopefully this weekend I can work on this some more.
What I did find out was that DP2 doesn't seem to create a copy of the BlueBox base image in a folder for each user like OS X Server 1.0 does. Instead, it creates an alias in that spot to the instance of the image that it copies somewhere else. I cannot for the life of me figure out where. The alias just appears broken under OS 9, OS X, and Rhapsody. I think it's saved at the root of the drive somewhere maybe, but I don't know for sure. I've done some decently thorough searching through all the files (including hidden ones) without luck. This makes it slightly harder to experiment on the system. If I run the update in the BlueBox image, I have no way to edit it after the fact, because I can't find it and copy it off of the drive to mount it! I can, however, mount the base image that it uses to create the individual user instances. Would it be valuable for me to upload that somewhere? I did try to mount and update that, then re-zip it, but that results in the MacOS app on DP2 to freeze before it even opens the window - worse than when I updated it from within the running BlueBox image which resulted in freezing at the Happy Mac icon. There are "Classic Support" files in there. I'm thinking I could try to just copy the one from BlueBox's original image in the place of the 9.1 one after the update. I don't know if that will allow 9.1 to boot or not.
I'm still thinking if there's some process to manually update 9.0 to 9.1 by just replacing all the necessary files, that may be the best route. I've never heard of that done before, but I don't see why you couldn't do it given how modular and straightforward OS 9 seems to be from a system file perspective.
Navigation
[0] Message Index
[#] Next page
Go to full version