osx working

[Pierrestro]

[MesaBlack]

what version is it running?

[joevt]

Jaguar installer CD can boot up to the language selection screen.

There's way too many graphical glitches to consider OS X working. The menu bar and progress window are offset vertically by many pixels. There's a newline after every 'n' character. etc.

There's probably some CPU issues as well. I believe the graphical issues must be CPU related.

[MesaBlack]

do you have the chance to take any screenshots of those anomalies?

[joevt]

The attached screenshots are from booting Mac OS X 10.2 Installer CD in DingusPPC Beige G3 with 768 MB of RAM and a AtiMach64Gx with 6 MB of VRAM.

Mac OS X has windows that don't fit in a 640x480 display. I think the AtiMach64Gx needs to have the Apple monitor sense codes detection fixed. Then a larger display can be connected correctly.

The screenshots show a variety of issues. The issues are not always the same. The menu bar is always in the wrong position but it isn't always in the same position. Some screenshots show text as being drawn correctly. Other screenshots show text having new lines for certain characters such as "S", "C", "I", and "P".

The menus are drawn in the wrong vertical location and may not always be visible so it's difficult to choose a separate app such as Disk Utility from the Installer menu for example.

Does Mac OS X use a lot of floating point CPU instructions for drawing? Maybe there's some non-deterministic results happening for some of the instructions?

Mac OS X 10.2 Installer Screenshots 640x480.zip

[MesaBlack]

How have things been going? (screenshots if possible)

[dingusdev]

Not a lot of progress here. Someone was able to create a disk image for Mac OS X 10.2, but it barely functions. Most of the time, it crashes during bootup. When it doesn't, the menu bar and desktop aren't rendered correctly. It's also very prone to crashing anyway.

[MesaBlack]

[MesaBlack]

were you in touch with them, or did you just come across the image?

[dingusdev]

I've been in touch with Mihai, and he's done some fixes, but there's plenty we'll have to fix up first.

[mihaip]

Both https://infinitemac.org/run?disk=Mac+OS+X+10.2 (pre-installed 10.2 HD) and https://infinitemac.org/run?cdrom=https%3A%2F%2Farchive.org%2Fdownload%2Fapple-mac-os-x-10.2.0-build-6c115%2Fdisk1.iso&machine=Power+Macintosh+G3+%28Beige%29 (10.2 install CD) are DingusPPC-powered but are flaky for different reasons (the first due to the instability that @dingusdev mentioned, the second because chunk downloads from archive.org often time out).

[MesaBlack]

welp

[MesaBlack]

maybe a 512kb option to suggest to infinitemac while this is being fixed?

[joevt]

maybe a 512kb option to suggest to infinitemac while this is being fixed?

RAM limit is not the reason OS X isn't working yet. We have tested Macs in dingusppc with 1 GB of RAM. The TNT machines can go up to 1.6 GB of RAM though Mac OS 9 is limited to 1.5 GB and won't let you use the extra 128 MB.

[MesaBlack]

does this mean a crash? (beige power mac g3, 10.2)

[dingusdev]

Effectively, yes. I don't know what causes it, though we did find a clue that suggests it may be a timing issue.

[MesaBlack]

[MesaBlack]

ok now it's this

What do I do here, @dingusdev and @mihaip?

Here's a screenshot from 5 days later:

[dingusdev]

I guess you can input in root or whatever the default account is on Mac OS X. That said, it looks like some backend stuff has happened here.

[MesaBlack]

I can't type anything in the password window....

[dingusdev]

Should just be able to hit enter, assuming the root account is enabled. Otherwise, this one seems to be an InfiniteMac issue.

[MesaBlack]

what do I type in the "login" bubble? @mihaip, I think we got something up here. Dingus here brought up the possibility of this being an infinite mac issue.

[mihaip]

Keyboard input normally works with DingusPPC under Infinite Mac (e.g. you can see it under 9.2.2 with the same Beige G3 emulated machine). If you're getting the login prompt that means that the WindowServer/GUI crashed during the boot process. At that point all bets are off as far the state of the machine and emulator.

[MesaBlack]

ok.

but oh-

I think the windowserver/gui didn't crash here. here it is