Search results

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.

Made an instrumented build and it claims everything is fine. What I really need is some documentation on AWACS. Can't find it in any of the Apple Technical Notes (in particular where it sits in the 5500/6500 memory map in O'Hare and any weirdness about it, SRS support, etc.)

Welcome. Got a Tek X term around here.

Took it out and no difference. Sigh. Going to have to make an instrumented build of the awacs driver and see where it chokes.

Yowza. Break out the capacitors and soldering irons for those SE/30s, though. The Monitor /// makes me sad because mine was stolen out of my storage unit in a burglary. The actual Apple /// itself was probably too heavy for them to lift, fortunately.

Aww. Very kind of you to say.

Welcome.

A blown Maxell ruined my Apple Network Server prototype (unfortunately before I got it). https://oldvcr.blogspot.com/2021/10/shiner-esb-apple-network-server.html

STacy owner myself, though I haven't done much with it lately.

Excellent!

I'd like to look at porting Disk Jockey Jr to PowerPC so that I can run it on my G5 (more convenient), and it should work assuming it's C and doesn't use any weirdo APIs, but https://diskjockey.onegeekarmy.eu/djjr gives me a 404?

Looks like it's the same file as the AWACS driver on my mute 6500, so more analysis is required. Currently I'm theorizing there is a difference between the 275 and 300MHz boards and the ones 250MHz and below.

Very nice! I have a similar TAM (G3, CS2 NIC, 9.2.2, repaired buzz-free base). A periodic goal of mine is a "fast booter" (or a really thinned boot floppy) so I can play CDs in it without having to wait for the full MacOS to come up.

Oh, I ran into that when developing inetb. When threads terminated abnormally (like, I forcibly killed them) it made a mess in net_server, which inevitably needed to be restarted (but at least it could be restarted). I had to figure out a way to gracefully tell threads to go away even when they...

Thanks much. I'll compare this with my system. I'm wondering if I should just pull the cache and see what it does with that.

Well, the rockiness here is the TLS bolt-on -- it really strains the BeOS' stack allocations and its multithreaded nature means things can stomp on it. Stripping out the crashtastic JavaScript and a few other changes improved the core browser's stability markedly.

Who says you can't do TLS on BeOS ... in NetPositive itself? It's a little rocky, but it works! Downloads in the article. It builds with Metrowerks cc/BeOS CodeWarrior, but not sure which was the more appropriate prefix ...

Actually, @wottle, another request. Can you send me what you have in /boot/beos/system/add-ons/kernel/drivers/bin/awacs ? I would like to compare that file with the one on this system just to make sure they're identical. How much L2 do you have?

That's very frustrating (for me). Your screenshot says you have a 250MHz system with 64MB of RAM. Any L2? I have a 6500/275 with 128MB of RAM and 1MB of cache, so I need to narrow some of these issues down. Maybe there's a logic board difference. There isn't a Gopher client on BeOS ... yet ;)...

Do you have sound on your TAM? My 6500 doesn't with BeOS, and I'm trying to see if it's unique to it or all Gazelle boards. (I do have a TAM also, but it runs 9.2.2, and I don't feel like putting 8.6 on it just to try this out. The BeOS launcher doesn't work with OS 9.) I've collected BeOS...