Notices by Tube🌞Time (tubetime@mastodon.social), page 15

looks like a coin cell mod.

which brings me back to here. does this mouse, despite the connector difference, use the same protocol?

however, they have RJ11 connectors and the keyboard (which is where the mouse plugs in) just has a mini-DIN connector. uh oh.

i've also got some Sun mice. an M3 and an M4.

ahh well, i'll just file some grooves.

time to build an adapter. the connector is RJ11 (technically 6P4C) but it has these pins sticking out, presumably so you can't plug it into a phone jack.

looks like it is essentially the same protocol as the version of the mouse (type 4?) designed for the SPARCstation. the output is open collector, inverted async serial, 5 byte.

well it found the keyboard!

couldn't find a Sun 13W3 cable adapter so I'm doing this to get to VGA.

adapter!

well, it tries to boot from the CDROM but suffers a BAD TRAP. not sure why, maybe i need to update the IDPROM contents.

i've also installed a ZuluSCSI. this neat little board is a lot cheaper than a SCSI2SD. i'm going to try and install Solaris using a CDROM ISO file. CD6_512.iso is placed on the SD card. it'll be ID 6, 512 bytes per sector.

four months later :blobsweats: i made the Video Snake Oil board that can adapt 13W3 (any type!) to VGA. you just wire up the little pads to whatever your machine needs.

forgot to add that i needed to do a "set-defaults" and a "setenv diag-switch? false"

wrote a little FORTH program to update the contents of the IDPROM, and it looks like it has a valid host id now.

yeah i am guessing the machine type in the IDPROM is invalid so the installer runs the wrong code.

that did the trick. the SIMM sockets were very stuck. welcome to S O L A R I S!

it seems to run with 12MB RAM. no more parity errors this time. but now the installer hates my SCSI drive (a ZuluSCSI).

filesystem creation failed for / 🤔

that wasn't the solution lol :blobsweats: there's no more zululog.txt error but the superblock isn't getting written correctly. 6D B6 DB 6D is the test pattern written by the format command. could be somehow corrupting it during the write?

spinning rust refuses to boot when the SCSI ID is set to 0. I can set it to 1 and it will boot partway but the fstab is configured for 0 so it won't work.