Recent content by Pernod

So it's actually a serial mouse, according to the service manual based on the Alps UDA020134A which I can't find any info on, so no idea what it's transmitting. It sounds like the mouse pointer can be moved with keyboard cursor keys though, so hopefully not a major issue for me.

What does the mouse actually plug into, is it connected to the keyboard or main machine? It looks like we have the keyboard schematic but no mention of mouse input, just the keyboard matrix.

With the latest news of the Triple X booting I'd like to return to my emulation but am stuck without keyboard/mouse input. Can anyone dump the internal ROM from the D8749HD MCU in their keyboard? Has anyone dumped one of these before, what's required?

Hi Alessandro, I think you'd struggle to insert the cable the wrong way around. You can see there are notches at different positions from either end to prevent incorrect insertion, the actual cable generally feeds away from the computer. Will you be using this with a BBC Micro or BBC Master...

Using the HxC Floppy Emulator from https://hxc2001.com/download/floppy_drive_emulator/ you can convert SCP to RAW sectors file format (not Raw Kyroflux file format).

Has anyone else looked at these? The MUSE ROM looks suspiciously bad, it has a reset vector of $F837 that doesn't look like valid setup code. The other ROMs look good, and have decoded the CHR ROM to reveal two character sets.

Can you attach them here, may be interesting to others.

As there seems to be no attempt to access the floppy drive at all how confident are we about the jumpers W5-W8 being configured correctly? I believe my emulation accesses the Winchester on LUN0 and the according to the manual the OMTI ships with floppy assigned to LUN2. The jumper allocations...

Can you post your key disk floppy image? I'm curious to see what's actually on there. I'm also trying to work up some motivation to emulate the OMTI specific SCSI commands. At the moment it just sends commands &C0 Define Flexible Disk Format and &C2 Assign Disk Parameters, then no further...

If you can sniff it then it's probably burning!

Just a thought ... your photos of the key disk screen don't show the red arrow to insert disk as in my video, so either you managed in multiple photos to snap whilst not shown as it's flashing, or it's detected the disk being present.

My emulation is now public as I feel it's at a solid checkpoint now, see https://github.com/mamedev/mame/blob/master/src/mame/misc/triplex.cpp

I think I now fully understand the palette, can you confirm the initial shade of blue is correct? I'd always assumed it was the darker blue that was shown whilst the video RAM was being used for data transfer between CPU's.

As I suspect @Witchy will have had a busy day today I'll post 1.2 on his behalf. I wouldn't expect the ROM to be the cause of any issues as it passes the checksum test.

Out of curiosity which disk image are you using, presumably one from https://bitsavers.org/bits/Torch/ ? And presumably the MFM_D5146 image? I'd be interested in seeing what the SysV_Portable image does on actual hardware, as emulation gives an 'Icon file corrupted' dialog.