>> ClassicHasClass said:

Let me just make sure I understand - you used the archive.org copy? I'm starting to wonder if there is something going on apart from the driver at this point. Click to expand...

Yes. Installed from the CD image burned from archive.org (5.0.3 Pro PPC and Intel: https://archive.org/download/BeosVersion5.0.3IntelAndPpc). I had to install it on an external BlueSCSI on my PowerMac 6500 because the CD wouldn't work in the TAM. But I then took the image and successfully used it on my 6400/200, my TAM, and my 5500/225, all work properly with sound.

I'm assuming sound works otherwise on the machine - boot up chime and in MacOS?

Yes, all well on the MacOS side. I might use your image on the scratch partition and see if there is any difference.

Progress!

What you have is the Gobe 5.0.3 release; I used Be's official 5.0. I installed what you did on another partition. There was still no sound through the main speakers, but ... the front headphones work! Well, sort of. They're very scratchy like the sound is being overdriven but BeBeep and BeStartup are recognizable and at the proper pitch. Turning down the master and mixer volumes just made them scratchy at lower volume. Also, restarting `media_server` causes it to go into a crash loop.

But, anyway, this is a start. I compared `/boot/beos/system` on both partitions. There are different files in `add-ons/media/{decoders,extractors,writers}`, different `add-ons/media/{decoder,extractor}.media_addon`s and different `csedv-c.so`, `libbe.so` and `libroot.so` (and `.xMAP`s). I have AWACS register documentation, but not for the 5500/6500, so I need to sit down and look at how the Linux driver handles the headphone port since that appears to be the gap that's missing.

Still, @wottle, thanks for the starting point!

We have audio on the internal speakers now. I'm doing some fiddling, but it did require hacking the AWACS driver. It does look like there are internal differences with later Gazelle systems. More soon.

Here is a patched driver for other mute 6500s. Conclusion: there are at least two 6500 versions, and later ones have an external SRS module which requires setting the parallel output bits on the AWACS.

>> ClassicHasClass said:

Here is a patched driver for other mute 6500s. Conclusion: there are at least two 6500 versions, and later ones have an external SRS module which requires setting the parallel output bits on the AWACS. The strange case of BeOS, SRS and the silent Power Mac 6500 Tonight's story time: the Power Macintosh that wouldn't make any sound in BeOS R5, how I figured out the problem, and how I hacked the sound... oldvcr.blogspot.com Click to expand...

Would you mind if I throw that in my disk image with 5.0.3 so people could switch out if they have no audio?

Sure, go for it! I don't know what it will do on other Macs, though, so they should definitely only use it if necessary.

Yeah, I'll leave the standard one in place, but put a folder on the root with a readme that explains why they might want to switch it out.

>> wottle said:

So, I recently learned that the TAM (Twentieth Anniversary Mac) can run BeOS. The person who was running it said you can run BeOS Pro on the TAM, so I figured I'd give it a go. Well, similar to my challenging experience getting it installed on my PowerMac 6400, I struggled a bit and figured it would be good to document my challenges and how I ultimately ended up getting it installed. The main challenge I've seemed to have is getting machines to recognize the BeFS partitions on the CDs. First, if you are planning on burning the BeOS CDs, I recommend using the .bin/.cue versions here . And using an old Windows machine with a CD burner at slow speeds to increase your chances of success. Don't use the .iso. I don't think it properly sets up the multiple partitions. I believe you also need to run MacOS 7/8 to get the OS chooser to work properly. Also, it helps if you have unpartitioned space on your hard drive (or a dedicated HD). I was never able to get the TAM to recognize the CD in the BeOS boot loader. However, the CD was fine because I was able to run it on my 6400. After many attempts, I had a thought that I should try creating a blank 2GB drive on my RaSCSI, see if I could install onto that, and then plug the RaSCSI into the TAM and see if the BeOS Boot loader recognized it. So, I initialized the RaSCSI HD image in the BeOS Drive Setup app, then installed 5.0.3 to it. I booted the 6400 from the RaSCSI to ensure it was functional, then connected it up to the TAM. And it worked! Pretty cool to see the TAM running BeOS. So, if you are wondering, BeOS supports install onto SCSI drives (somehow I had gotten it into my head that it only could be installed on the IDE drive). And RaSCSI worked perfectly with it. Next, I need to get some mp3s loaded onto it and hear them in the fantastic sound system. Also, I am going to download the HDA and throw it on a BlueSCSI and see if that works. If so, I could probably upload the BeOS image somewhere to save people the trouble of the install. Just download the HDA, throw it on a SD card, add the _OS Chooser_ extension to your system folder, and reboot. Will let you know how the test goes. Click to expand...

I just finished retro rebuild of Power Mac 7600 with BlueSCSI and am workign through my issues of getting the Mac to see the BeOS hard drive to select it as startup drive from my Mac OS 7.5.3 installation.

>> lundpk said:

I just finished retro rebuild of Power Mac 7600 with BlueSCSI and am workign through my issues of getting the Mac to see the BeOS hard drive to select it as startup drive from my Mac OS 7.5.3 installation. Click to expand...

I didn't think you would be able to see the BeOS drive from in MacOS. You should run the BeOS launcher to restart and mount the BeOS drive and boot to it.

>> wottle said:

I didn't think you would be able to see the BeOS drive from in MacOS. You should run the BeOS launcher to restart and mount the BeOS drive and boot to it. Click to expand...

I read something about an OS Chooser extension being installed - but I am not sure it was installed automatically. Might need to manually do that.

"The BeOS OS Chooser extension allows users to select whether to start the BeOS or the Mac OS each time they boot their Macintosh."

>> lundpk said:

I read something about an OS Chooser extension being installed - but I am not sure it was installed automatically. Might need to manually do that. "The BeOS OS Chooser extension allows users to select whether to start the BeOS or the Mac OS each time they boot their Macintosh." Click to expand...

I thought I included the BeOSTools image in that macintosh garden upload. But it seems the garden is down at the moment. Alternmatively, you could get the BeOS partition from the garden link, and it looks like there is a preloaded 7.6 image with the BeOS tools (OS chooser and BeOS launchers) here: https://68kmla.org/bb/index.php?threads/emulation-infinite-mac.45621/post-528489

EDIT: the garden is back. Yes, grab download #2 from the link above (https://macintoshgarden.org/apps/beos-503) and drop that on your BlueSCSI. In that HD image is the OS chooser and BeOS Launcher. That should allow you to boot to the BeOS hard drive on the BlueSCSI. Should work just fine from your 7.5.3 install.

>> wottle said:

I thought I included the BeOSTools image in that macintosh garden upload. But it seems the garden is down at the moment. Alternmatively, you could get the BeOS partition from the garden link, and it looks like there is a preloaded 7.6 image with the BeOS tools (OS chooser and BeOS launchers) here: https://68kmla.org/bb/index.php?threads/emulation-infinite-mac.45621/post-528489 EDIT: the garden is back. Yes, grab download #2 from the link above ( https://macintoshgarden.org/apps/beos-503 ) and drop that on your BlueSCSI. In that HD image is the OS chooser and BeOS Launcher. That should allow you to boot to the BeOS hard drive on the BlueSCSI. Should work just fine from your 7.5.3 install. Click to expand...

Indeed this worked. Ethernet configured, but secure web browsing is painful. I know there are some software sites for BeOS, but may take some tinkering (ha ha) to get files over to BeOS partition.

I've got a partial solution to the HTTPS problem here, but it's dreadfully slow on my BeBox. (It might be better on a faster Mac.)


I still need to finish that Gopher client for BeOS.