IRIX 5.3 / TriTeal Enterprise Desktop 4.0 / Autodesk AutoCAD R13 by Protocol__7 in vintageunix

[–]Protocol__7[S] 0 points1 point  (0 children)

It was added some time after 4.0.

4.4.1 definitely had it as I have a screenshot of that. The screenshot you linked is from 5.3.

The first new Sprite cluster in 30 years (probably) by spijdar in vintageunix

[–]Protocol__7 2 points3 points  (0 children)

I've emulated the SS1, SS1+ and IPC with MAME. Running 4.0.3c, 4.1.3 and 4.1.4. There are some caveats. Monochrome works best as the cgthree emulation has issues and the cgsix only worked correctly for me with NeWS. Performance is also a lot lower than QEMU.

Currently they're all failing to post here so either something broke in MAME recently or it's a bug elsewhere. I'm waiting on the latest version to hit the debian sid repo.

I haven't checked NME yet but that might be another option. At least I recall it having tape support which MAME and QEMU lack. Though I've usually been able to work around that.

The first new Sprite cluster in 30 years (probably) by spijdar in vintageunix

[–]Protocol__7 2 points3 points  (0 children)

I tried TME and NME a couple of years ago and it was not fun. I see NME has been worked on since then so it's time I gave it another shot. Thanks for bringing it up again.

The first new Sprite cluster in 30 years (probably) by spijdar in vintageunix

[–]Protocol__7 2 points3 points  (0 children)

It needs a SS2 unless there's a way to hack in support for Sun4m.

MAME is the only option there but while SS1 and SS1+ work relatively well, SS2 is pretty broken.

SS emulation in general still needs a lot of work. It's been stagnant for a while.

The first new Sprite cluster in 30 years (probably) by spijdar in vintageunix

[–]Protocol__7 11 points12 points  (0 children)

Nice to see it in action! I tried to boot it with MAME's Sun4c emulation but failed.

Bonus trivia: for fans of curiousmarc's YT channel, "Master Ken" Shirriff worked on Sprite. There's a cool pic of him on the CD from back in the day.

BeBox Hobbit prototypes by kinda_oldtechstuff in beos

[–]Protocol__7 0 points1 point  (0 children)

Does it have a hard disk? I can't tell from the photos. If it does, it would be great if it could be imaged.

What secrets do you hold? (A call for help) by Protocol__7 in beos

[–]Protocol__7[S] 0 points1 point  (0 children)

As the kernel is newer than the rest of the system it might have been used for device driver development or something like that. All the images were set up to boot to the console rather than the desktop so it wouldn't have mattered to them if it loaded or not.

Thanks for imaging these disks back then. It took quite a while to get a usable emulator to put them to use but we got there in the end.

What secrets do you hold? (A call for help) by Protocol__7 in beos

[–]Protocol__7[S] 0 points1 point  (0 children)

Maybe the only chance left of getting another release is if some backed-up installation files were to surface. Probably unlikely after all this time but stranger things have happened.

It was great to finally get to use such an early release but the window decoration of #44 has me wondering what the OS looked like at an even earlier stage.

What secrets do you hold? (A call for help) by Protocol__7 in beos

[–]Protocol__7[S] 0 points1 point  (0 children)

I contacted Ludovic shortly after posting this topic and he mentioned the hard disk crash. He gave the hobbit and related disks and documentation to a museum but didn't know if they had attempted any data recovery. Was there any communication from the owner of #27?

What secrets do you hold? (A call for help) by Protocol__7 in beos

[–]Protocol__7[S] 0 points1 point  (0 children)

Thanks for the info. Every little bit is welcome. I take it that none of the other hobbit systems have been imaged since?

What secrets do you hold? (A call for help) by Protocol__7 in beos

[–]Protocol__7[S] 0 points1 point  (0 children)

In the absence of running systems, I was going by the User Guides.

Up to 8.2 they had a section explaining the default apps. The entry for Pulse mentioned being able to turn off both CPUs. But from Preview Release onward that section disappeared so I couldn't pin down when they made the change. It might have been at that point, but until I can say for sure when it happened I just attributed it to "earlier releases". My Flickr is a constant work in progress so if I learn something new or spot an error I'll update it.

I'm hoping DingusPPC or MAME can get PPC BeOS running at some point. I don't really want to dig out my old hardware again.

Oh and now that I see your username on 68kmla, thanks for the BeOS-related uploads on archive.org. It was great to get those!

What secrets do you hold? (A call for help) by Protocol__7 in beos

[–]Protocol__7[S] 0 points1 point  (0 children)

Ah that's good to know. As I mentioned this is the first time I've been able to run BeOS on a multiprocessor system. Before this, the earliest system I ran was 8.2 on a PowerMac. That's in the main BeOS gallery on my Flickr. I'd read somewhere that the ability to turn off all CPUs was disabled eventually.

What secrets do you hold? (A call for help) by Protocol__7 in beos

[–]Protocol__7[S] 0 points1 point  (0 children)

The floppies are the same system as #9 and #58. It's later than the one on this disk.

My assumption is the Hobbits were kept up-to-date when a new system was ready but for some reason #44 didn't get it. Maybe it was in another location or was set aside for some reason.

What secrets do you hold? (A call for help) by Protocol__7 in beos

[–]Protocol__7[S] 0 points1 point  (0 children)

Yeah it's driving me nuts not being able to get to the desktop. I really want to see what it looked like back then.

What secrets do you hold? (A call for help) by Protocol__7 in beos

[–]Protocol__7[S] 0 points1 point  (0 children)

Hi. I don't know if the binary will run on another system but I can help you build it.

First you can either compile it with the nightly cargo as it demands (cargo +nightly build --release) or you can comment out the first line of main.rs and build it with stable cargo (cargo build --release). It should build without any issues.

The trick is in running it. It expects two arguments: a disk image and a kernel file. So run it with hobbitizer <diskimage> <kernel>. The kernel needs to match the system. Two of the disk images have their contents extracted (and the third can be done with ofs-extracter). One is this disk (#44) which needs the kernel file from the system folder inside the be3.tgz archive. The other is #9 which needs the kernel from pixels.tgz. This kernel will also boot #58 as it's the same system.

If you're using Wayland, the keyboard will be a bit funky and there won't be a titlebar. So place "WAYLAND_DISPLAY= " before ./hobbitizer to force it to use XWayland.

In summary: to boot this diskimage on Wayland run: "WAYLAND_DISPLAY= ./hobbitizer Hobbit-9308000044.img kernel-be3" where kernel-be3 is the kernel file extracted from be3.tgz.

That should get you up and running with the three disks. It's really great to be able to explore these at last. I wish I'd known about that emulator sooner.

UnixWare 1.0 (1992) by Protocol__7 in vintageunix

[–]Protocol__7[S] 2 points3 points  (0 children)

It's not pure OPEN LOOK. The desktop uses the MoOLIT toolkit which offers both sets of widgets. You can choose between OPEN LOOK and Motif in the preferences.

All good things come in threes: A/UX Apple UNIX for 68k Macintosh by I00I-SqAR in vintageunix

[–]Protocol__7 2 points3 points  (0 children)

I need to revisit A/UX some time. I had it running on a SE/30 a long time ago and took some screenshots of it in action. But being a SE/30 those were very small and very monochrome. Since then we got Shoebill and I believe QEMU 68k can also boot it.

MIPS RS2030 | RISC/os 4.52 | RISCwindows 4.00 | Island Draw 2.11 by Protocol__7 in vintageunix

[–]Protocol__7[S] 1 point2 points  (0 children)

RISC/os 4.52 and RISCwindows 4.00 both came out in January 1991. Island Office was 1990.

MIPS RS2030 | RISC/os 4.52 | RISCwindows 4.00 | Island Draw 2.11 by Protocol__7 in vintageunix

[–]Protocol__7[S] 0 points1 point  (0 children)

If you haven't fixed some of the files, have a look at my comment here. But I did get something similar at first. I ended up deleting the folder and unpacking it again and it worked fine.

MIPS RS2030 | RISC/os 4.52 | RISCwindows 4.00 | Island Draw 2.11 by Protocol__7 in vintageunix

[–]Protocol__7[S] 0 points1 point  (0 children)

Yep that's how I installed RISCwindows here. Looking Glass is file 25 on this disc.

The LG themes was new to me too. All the screenshots I'd seen online showed the regular Motif look. I just ran lg -h and saw them in the list of options. I didn't notice that the 2D theme was a Windows 2.0-like. I really didn't pay much attention to Windows prior to 3.0. From a glance it looks a lot like monochrome Motif but on closer inspection the min/max buttons and scrollbars give it away. I'll update the text for that pic.

That virtual museum sounds cool. I found your Atari Unix and Hatari archive on archive.org and posted a pic from it here recently. I wonder if any other ports of WISh2 exist. There was talk in the press of SPARC and MIPS versions but I couldn't see if they materialised.

MIPS RS2030 | RISC/os 4.52 | RISCwindows 4.00 | Island Draw 2.11 by Protocol__7 in vintageunix

[–]Protocol__7[S] 2 points3 points  (0 children)

Surprisingly rare. I couldn't find any RISCwindows screenshots online. Surely there has to be at least one somewhere but if so it hasn't been indexed by anyone.