MiST FPGA impressions

From behind: USB, Audio, VGA, USB-C, Power switch

I decided to be different and order a MiST instead of the now popular MiSTer FPGA.

This has MIDI connectors, 9-pin joystick ports and maybe a small prestige of being from the lineage of one of the first, if not the first, FPGA reconstructions of old 8/16-bit hardware. Nowadays it can pretend to be many different computers or game consoles, but in its origins MiST was closely tied to Atari ST.

At least for starters, I'm going to stick with the Atari ST cores for a while and not go too much core-hopping. This is meant to relieve me from a shattered focus, dammit.

Well, I have a SiDi FPGA that mostly does the same thing but it doesn't have the 9-pin and MIDI connectors. I'll discuss that in some other post.

The all-important MIDI ports. Front: LEDs, SD card slot, Buttons

And the usual disclaimer: No, FPGA is not emulation. Here a CPU does not play at being another CPU on software level. Electro-logically FPGA performs close to the way the original CPU, video and audio chips would. But it is not exactly same as having the original computer, and requires different thinking at places.

I ordered my MiST v. 1.6. from Lotharek. Physical impressions are very good. The case is smaller than I thought, like a small bible(?!) and it's very sturdy. While this new case didn't look super inviting in the photographs, in real life it looks and feels good. It's heavy and made out of thick matted metal sheet.

Being so small, in theory it could be placed inside an Atari ST case, but this is not really the intention, as it's not a replacement board. Atari/Amiga keyboard->USB conversions float around, I downloaded an Arduino Leonardo sketch for a loose Amiga 500 keyboard. It is more appropriate for an Amiga core, but not too far from an ST key layout.

If there's a nitpick it's that the earlier, minimalist case had more places for adding those Atari/Commodore badges and stickers.

Like so. SiDi FPGA to the right for size comparison

There are connectors all around: SD card at front, two 9-pin Atari joystick ports at right, 4xUSB-A, 3.5mm audio, VGA, USB-C for power and a physical power switch. Left side has two MIDI ports, the closest to front is MIDI out. Possibly it also doubles as thru as in Atari ST, but I am not yet sure about that.

The 9-pin connectors don't normally support 16-bit mice, but the MiSTery core can do this too.

(As a side note I'm getting pain from typing all these caps-sprinkled names...)

What it does not have is an HDMI, but that's not important to me now.

The front panel also has three buttons, Reset, OSD (On-Screen Display) and User button. OSD is equivalent to invoking the display menu with F12. Holding it down can switch the RGB scanline doubler on and off, which can be useful if flipping between displays.

Atari ST up and running

Despite having existed for quite some time, picking up MiST is not instant plug and play, as a few things need to be learned. The MiST builders aren't responsible for explaining how the particularities of each hardware platform work, so instructions for enabling a full Atari ST experience might be scattered here and there.

Also, because MiSTer exists, it's challenging to google for MiST information, because the results are almost always mixed with MiSTer experiences. Some information is appropriate for both, but not all.

But it's quite easy to get the Atari ST core and floppy disk images running. These have extension .st. The .msa and .stx and others won't be accepted by the MiST!

I should have ordered the SD Card that was suggested, it would have saved an hour of looking around. Yet I was lucky to have a card that has worked so far. It's also wise to keep a copy of the contents on Linux/PC filesystem, but so far I've not lost any information.

For Atari ST, the FAT32-formatted card will have three files, core.rbf, disk.st and tos.img, as explained in the instructions.

The first boot looked a little different.

The core and the disk.st is supplied by the MiST Github starting page, but the Atari operating system (TOS) image needs to be acquired elsewhere. Needless to say, whatever its name, it has to be renamed to tos.img or it won't be found.

The TOS version ought to match the chipset the MiST is intended to represent, for example TOS 1.62 for Atari STE, whereas Atari STFM might benefit from a TOS 1.04. Alternative TOS versions can be mounted from the MiST interface itself.

Whatever core is going to boot, also needs to be named core.rbf. After initial tests I moved on to the MiSTery core, which enables a couple of additional things, such as a faster STEroids mode and the aforementioned 9-pin mouse support. This STEroids mode is not as compatible as the others, but switching it on and off is very simple.

For those who are used to emulators and the short cuts they offer, the FPGA gives a reality check. Things can occasionally be slow, disks boot, take pauses and turn and turn, just like with the original computer.

GEM desktop on mono 640x400 mode

Switching to 68020 CPU and using MegaSTE 16Mhz speed is not going to make it lightning fast. Even the Mistery core STEroids mode will fall short of Hatari's 32MHz mode. I think it's about 3x the speed of a normal ST. That Dread game demo is going to run smoother.

Although I love how austere the GEM desktop looks like, I have to admit it is sluggish in 8MHz. The STEroids mode makes it much better.

Display

As mentioned, there is no HDMI option. The VGA is more lenient than with a real Atari STE, so I could get a picture out of the HP Elite (supports 50 and 60hz), also the mono image, which a real Atari STE refused to do with that display.

I made a VGA-to-RGB adapter for the Commodore 1084S monitor using a VGA terminal block, and soldered the cables to a 6-pin DIN.

VGA terminal block AKA breakout

There's only R,G,B, Horizontal Sync, Vertical Sync and Ground to solder.

A tube display is still big part of my retro experience, so I'm happy to see that bright, rock solid image on the 1084S. A 50/60Hz switcher program produces the expected result. Protracker 2.0 extends to the border as it should. 

The STEroids mode doesn't replicate all the border-defying tricks, so the ST/STE chipset setting is required.

Batman the Movie was the first ST game I owned. Don't ask.

MiST won't know what display is connected. To activate RGB requires configuring a file called mist.ini, which is placed at the root of the SD card alongside with the core.rbf, disk.st and tos.img. Every time the MiST is reset, it reads the mist.ini and sets things up accordingly.

A minimal mist.ini for connecting MiST with Commodore 1084S 6-pin DIN analog RGB, could be as follows:

[mist]
scandoubler_disable=1
csync_disable=1

The first runs supported cores in 15kHz, the second outputs separate hsync and vsync in 15KHz.

Note: SCART cables often go the route of using the CSYNC pin, but if the SCART is again fed back to the 6-pin DIN using an adapter, then it is very unlikely to work with a 1084. Some versions of the 1084 display have a dedicated SCART connector, and I'd expect SCART cables to work there.

The normal VGA is not without its uses, as the 1084 cannot act as a mono monitor. I remember there are software "mono emulators" but please, no.

Mono mode on the Elo display

An older Elo industrial screen produced a "real" borderless 640x480 resolution at 35KHz/71.4Hz, into which the 640x400 mono image fits with black stripes at top and bottom. Using auto-adjust, it even went beyond its own manual clock parameter range and showed the pixels 1:1 with no moire effect.

I did have to kick the auto-adjust key every time MiST was even soft reset, though. With color resolutions of 320x200 and 640x200, no such luck, the modes have borders which means the entire screen can't scale appropriately.


Keyboard and mouse

Keyboard is quite an important part of the "feel" for the system. My new Keychron keyboard gave some problems, occasionally going permanently off-line when doing a soft reset, and things like that. It might be because of too little power from the PSU. It's not a huge thing as I would never dedicate it to a retro computer anyway.

An older Blackstorm behaved better, but something more appropriate may be needed eventually; a lot of software benefits from a numeric keypad. For the KCS Omega sequencer graphic editor it is a must, as it enables the quick looping. Flight simulation software often have view selection around numpad keys. Many of the hard disk patched games have an numpad * as exit option.

As I had a loose Arduino Leonardo AND a loose Amiga 500 keyboard, I could try a project for connecting them. There's a number of projects that do a similar thing, I downloaded this and it worked.

This was not entirely without problems (It's not an ST keyboard after all) but something to look at more closely later. I used the .ino as is and connected the wires. Depending on Arduino model, soldering may not even be needed. 

Amiga keys, ST core

Sadly it doesn't always come online, but re-plugging the USB a few times live it does go online and doesn't seem to drop off after that. It could be due the way Leonardo HID works, and not much can be done to it.

The SiDi FPGA behaves better with the Amiga keyboard, haven't tried it so often but so far it has always worked. Upgrading to newer MiST firmware didn't help. But, as I said, I'll look into it later.

One of the advantages of the MiSTery core over a standard ST core is that it supports a 9-pin mouse. So I can stick in a mouse that works with Atari ST and use that for more authentic feel. Atari/Kempston joysticks, such as TAC-2, are simple and supported across all relevant cores.

With a USB mouse, a mouse wheel simulates cursor up and down, this is handy but the ratio is a little weak, I go three nudges and the key is invoked maybe once. There could be an adjustment somewhere, but it's also possible MiST doesn't have it.

Atari ST, Hatari and hard disk images

The basic use for MiST Atari ST core is to collect a bunch of .st floppy disk images to the SD card and then select them using the OSD menu.

How to enable hard disk images? It gets trickier. There's a number of routes and I took what looked like the simplest. It may not be the best.

The language will be heavy with acronyms and jargon.

Just as the floppy disk images, there is a different kind of image file that can be put inside the SDcard to represent a hard disk, and it can be selected from the MiST menu.

The easiest route is to use Hatari ST emulator on Linux. It again requires the TOS images in order to work.

The emulator includes a tool for creating a hard disk image from the command line:

atari-hd-image 256 myimage.img ATARI

With this method, 512 is maximum, for two 256 partitions, but I didn't get that to work. So I use a 256MB image with single partition. Hatari can then "browse" that image from the Hard Disks submenu, using the ACSI HD 0 slot.

Hatari Hard Disks menu

The image needs the extension .hd otherwise MiST won't see it. Hatari doesn't seem to care about the extension but I used .img as most instructions had it that way. In case of such superstition just rename the file afterwards.

But this only implies the hard disk is now available, not that it is usable by the ST filesystem. Atari ST software is needed to perform the formatting. 

From the Internet, find an AHDI driver disk image that has AHDI.PRG and HDX.PRG. This is likely another .st floppy image, such as AHDI6061.ST which can be mounted using Hatari as drive A while the hard disk image is still attached. 

The disk ought to boot the AHDI.PRG from AUTO folder. The floppy likely has a number of tools. The HDX.PRG is used to format and partition the previously created hard disk image inside Hatari ST emulation.

An Atari STE chipset and TOS 2.06 might be a good combo for this. Ramp the CPU speed to 32Mhz to make the OS a little faster.

HDX.PRG formatting the drive image. It will take a while.

When using HDX only the ACSI drives are visible, so if there's a Hatari Gemdos folder drive available, it won't be accidentally formatted(!)

HDX probably suggests four partitions, this doesn't need to be the case, and I didn't even get it to work. At least I only succeeded with single partition drives.

Remember that for an ST, 250 is quite a huge size anyway, and MiST can attach two of them at any time.

The drive now exists and files can be written to it. Hatari can also be used to copy files and folders to the new hard disk image, inside Gem. These are copied from another "hard disk" image which is simply your PC/Linux folder mapped as a hard disk in Hatari.

The AHDI driver is still needed, and again, my first attempt at making the drive bootable did not succeed. So far I've simply used the floppy boot in the MiST with the AHDI.PRG in auto folder to have a system that recognizes a hard drive. This will be visible as C.

The alpha and omega of 16-bit sequencers: KCS Omega + Tiger

I got the Atari ST sequencer KCS Omega from ST Format magazine's January 1994 issue 54 coverdisk. Little did I know it would be my only commercial-level sequencer until mid-2000s. Also, I didn't know I would be ignorant about some of its more interesting features until recently.

Many go vintage, modular or just any DAWless setup. But others are also digging up their old Atari STs and Amigas to relive a workflow from the mid-1990s, or to engage with a distraction-free environment. 

Although it can take some effort to have an Atari ST set up and working these days, I guarantee a session won't start with downloading updates.

KCS Omega was the brainchild of one Emile Tobenfeld, who under the moniker Dr. T had already conceived MIDI products for Commodore 64 in the 1980s. In a way KCS Omega repackaged some of the same ideas and functionalities for the 16-bit range of computers, and put a graphic editor, Tiger, on top of it.

According to his FAQ, Tobenfeld had left the company in 1993. In a couple of years all the platforms on which KCS products had proved popular (C64, Atari ST, Amiga), had fallen out of favor, and Windows/Mac platforms eventually emerged as the victors in the productivity arms race.

Diverting opinions will arise. "Wasn't Cubase the thing on Atari?" anyone even modestly informed will ask. KCS Omega is comprehensive, quite fast and supports a number of workflows, and there are often multiple ways to achieve the same outcome. I'll maybe compare them later but at this moment KCS feels better than Cubase 3.1. To me, knowing the idiosyncrasies of KCS is like belonging to some arcane secret society. I don't even know enough to tell everything.


Tiger

In the mid-1990s, I mostly used the Tiger graphic editor, thinking this was the only way to use KCS for song building. Coupled with a Yamaha DX11, with its multitimbral, velocity-controlled FM operators, I could create quirky digital soundscapes by adding and duplicating note clusters and fiddling with their velocity stems. Add a Sequential Circuits Drumtraks and rudimentary rhythmic electronic music could be made. And that was that for a long time.

I did note that Tiger was an add-on to the "real" KCS Omega, but I didn't pay much attention to the central sequencer. I felt it was only a multi-tracker for recording MIDI live, and wasn't entirely wrong.

(The screenshots are from Hatari ST emulator for clarity)

Tiger: Fast editing of the velocity stems

First things first: I've noticed that at some occasion MIDI doesn't clearly output on channel 1, unless I switch the track channel to something else and then back at 1. Top where it says C< 1A>. So, trying to test gear and connection, this is a thing that can happen.

Tiger is a quite versatile piano roll editor even now, and certainly the most friendly way in into the intricacies of KCS. I can set quantize/snap on with that icon at the bottom right corner, then add notes with the pencil tool (2nd bottom left) and just kick Play.

With Add/Drop Tracks dialog, multiple tracks can be viewed and edited in parallel, and zoomed horizontally. The multiview likely works better on a high resolution monitor. The relative size of the areas can be adjusted by dragging the symbol at the top right of the track window, but this isn't visualized, it just happens. Clicking it switches between full view and the multi-view. Right-clicking the corner removes the sub-view. The combined views can also be stored and recalled.

Tiger makes use of a 2-button mouse. The four icons at the bottom left are for Left Mousebutton, and generally affect, or select, a bunch of notes or larger areas. They are: Erase selected notes, Draw Note, Paste, Set Range. If none are highlighted, it's possible to select individual notes or drag a selection rectangle.

Repeat Time from Repeats menu

The seven icons at the right side are for Right Mousebutton, and apart from the Play icon, they affect an individual note. So, if Play is selected on the the right, the right button always plays from the cursor position. The others are Draw note (again), Erase Note, Alter Note Position, Alter Note Pitch, Alter Note Velocity, Alter Note Duration.

It's a pity these only affect a single note, but I also understand the need for simplicity. I suppose the purpose with these right button tools is to nudge individual notes that result from a recorded live play.

So there are two Draw Note tools assigned to the left/right buttons, and the properties can be changed from a menu item.

A clone repeat time can be set from the Repeats menu. (960 units = 1 bar by default). I can then select a number of notes and use Control+Arrow keys to duplicate them around the track. Another option is to fill the track with the selection, so making a metronome track is very quick. 

Pressing keys on the numeric keypad, I can instantly loop a number of bars starting from the one under the mouse cursor. This is very useful.

Selected notes and a range. Double cursor? It's an emulator screenshot.

There are menu functions for selecting all notes, notes of a certain pitch, notes above or below a certain pitch, and all these selections can be filtered with the selected range. Handily, the selected notes can be moved around with cursor keys, and most of the keyboard is dedicated for altering position (QWERTY row, esp. Q/W-O/P are useful), duration (- and +) and velocity (ASDFGH row).

Various reversals can be made to the selected notes. Reverse the entire order, or only pitches, durations or velocities. One more way to tease out small creative discoveries.

Quantization is a normal sequencer function, it's fairly straightforward here. Recording and quantizing naively, I often end up notes in crassly wrong positions. I found it better to first fix things as much as possible by hand, then quantize if still necessary. 

On occasions I de-quantize parts of materials by moving them ever so slightly, just to avoid snapping everything to rigid 16/16 precision. Adding notes without the quantize is a fun exercise too. Doing this to multiple tracks can easily make a techno/dance/electro song very, very wonky, so use with care.

"Paste at Selection" menu item was confusing at first, as I naturally expected it to paste my previously copied material at a particular point. But this function pastes the copied notes on every selected note, using them as starting point for any pitch difference the original notes might have had. Use the paste icon at bottom left to do a normal paste.

If I drag a number of notes around, they will auto-play (optionally). I used to think this as a distraction, but it becomes a friend eventually, and ideas may come out of it. When playing with a sampler, drum kit or phrase set that triggers different sounds from different note pitches, moving the selection up and down can lead to serendipitous discoveries.

A CC track, and the menu item for adding one

Admittedly, dragging a number of notes around in the graphic editor will reveal the slow speed of an Atari ST GEM and this software. There are also ways to avoid dragging notes around, it's such a post-2000s way of thinking anyway.

Tracks have controller tracks for Program Change, Velocity, Aftertouch, Breath Control, Foot Pedal and Volume, which can be easily invoked. Note velocities are very smooth to change on the VE track, by just holding the mouse key and dragging over the stems in that window.

A CC controller track can also be added, for making Control Change messages. For example, Cutoff and Frequency are some typical CCs to send via MIDI. 

I had to use 2nd mouse button to draw on the CC track. Holding control and clicking, an interpolated slide can be created between two points in time. A segment can be erased by first dragging it over then using the "eraser" icon. (The first at bottom left). This style of editing doesn't work on the velocity stems, they are tied to the notes.

Finding out which CC values are present in a track seems to be impossible from Tiger, once the CC track view is closed. But the KCS Track Editor will list CCs among events, and from there it's also possible to delete all CCs or particular CCs with a filter. Or, indeed, adjust the CC values.

Track Edit, Sequences and the Open Mode

The main screen of KCS Omega is a 48-track MIDI event and note recorder, which functions much like a physical tape recorder might work. If the record button is on, you can auto-record just by pressing a key on the MIDI keyboard. After the recording has reached the end of the track length, a new track is created the recording continues on that, until the process is stopped or the tracks run out.

It can be handy to turn on "Mute new tracks" if the intent is to record the same melodies again and again. It's also possible to undo and re-record the currend (failed) recording.

After a bunch of material has been created this way, it can be edited in the KCS event editor or in the Tiger.

Only recently I've understood what the Open mode and the associated Play Screen could do for me. I didn't likely even see the Play Screen many times in the 1990s, so well it is hidden.

The Main screen

Firstly, I have to click EDIT or press F1 in the main screen to get to the Track Edit screen. From there, I can click on Open Mode. There, again clicking on Play Screen the modest-looking black screen opens, and the pull-down menus disappear.

But how do I add a new track in the first place, if I'm not using the live recording? This was always a little mysterious. Well, in a Track Edit screen, it's possible to click on one of those empty boxes in the grid at the bottom right of the screen. This provisionally creates a track, but I need to manually give some TIME to the only event on the list, otherwise the track won't really exist.

After this, I can again go to Tiger via the main screen and start adding notes there.

Looking at Sequence #2 events, and calculating its end point.

But anyway. If I have a number of tracks, I need to convert the tracks into sequences, and only afterwards I can trigger these sequences live in the Play Screen, aligned into the next measure.

Tracks can be sent from Tiger to become sequences. There it's wise to use the range selector and send that range.

In the case I've accidentally sent a track that only has 2 bars of material, but the track has the length of 8 bars. I can either delete that and use the range-select method, or fix the end point. In the Sequence screen I can go to the last event, which is DE. If I intend the sequence to have 4 bars, I make sure the DE lands at 5:1:1. There's actually a calculator that can help do this computation. 

This rather unimpressive screen is at the heart of KCS.

But wait, there's more.

When the tracks are converted into sequences, they can be turned on by pressing their corresponding key, starting from 1-9 and continuing on to A-Z. After these have been exhausted, 00-99 can be invoked from the numeric keypad, but these may be considered more like secondary material.

And this is actually the reason it's called a Keyboard Controlled Sequencer. D'oh.

And it doesn't end there. Sequences can contain events that trigger other sequences according to various logics, all of which I have not yet even discovered. The simplest way is to add a sequence launch value into the sequence event list (1-9, A-Z etc). The column where it usually says "ON" for a note (TYP), the number or letter of the sequence can be inserted. It can be transposed (NOTE) and played in a different relative velocity (VEL) and repeated a number of times (DUR).

If a W is added to the duration, this means the play waits until the sequence has finished, before playing the next one. If non-waiting sequence is triggered at the same time, it also plays alongside. The W option makes song construction clearer, but honestly a paper plan might help.

If a sequence containing these events is launched from the Play Screen in Open Mode, the sequence itself will trigger the other sequences, relative to its start. In theory, the sequences can produce a cascade of further sequences, but it may be wiser to keep these commands inside one sequence.

Also, the direct launching of sequences is still possible, even if the song is centrally automated.

All content from this range, from all tracks, can be dumped onto a new sequence

I now consider the tracks as more like sketches and snippets, and the Sequences are the real thing, a material from which a song can be constructed either by meticulously chaining them together using command sequences, or by playing them live on the Play Screen. In turn the outcome can be recorded elsewhere, or the MIDI output can be fed back into the Atari and recorded on a new track.

If each sequence only contains a particular instrument, then it's not much different to mixing, muting and soloing the tracks on the main screen. It can make sense to combine multiple tracks into one sequence, which is best done from the Tiger. For example, these could be intro, verse, chorus, bridge and outro. Then the sequences are more comparable to patterns in Soundtracker-type software.

Even though it clearly says "All Tracks", it still confused me that the function sends also the non-visible tracks to the sequence. A defined range from all tracks can be sent to a single sequence, and they get a proper end point for looping automatically. I clarified this to myself using the diagram below:

So, the resulting sequence has elements from all three tracks. I can chop the Tiger-created multitracks into components that have different instrumentation, or traditional song structures. This way, entire song components can be triggered by a single key, and not just mix channels in and out. Other single-track sequences could be launched in order to add nuance or variety. 

Importantly, currently muted tracks are not incorporated into the "All Tracks to Sequence", which can be helpful when building combinations.

Thought needs to go into what would work as a playable sequence. It's easy to paint oneself in the corner by creating tracks, combining them into sequences, and then find out later that for example a bassline needs adjusting. If this is done in the Tiger, the tracks need to be translated into sequences where ever the bassline was used. It may be better to wipe out the sequences and start again.

But if the bassline was kept as a separate sequence, then only the source track for it needs to be changed and translated. Or, using the event editor directly the sequence contents can be changed, closest thing to that instancing of notes I discussed prior.

Using randomized sequence play is an interesting feature, and it can be combined with non-random elements. However, in my experience the randomizer can generate tiny delays between sequences. It's still possible I made some mistake, but if it's a lag in the program I perhaps wouldn't record the audio output, but record the MIDI somehow and then adjust any problems in it.


Is it perfect?

I've now made it sound KCS Omega is some kind of hidden ultimate sequencer, with no flaws in sight. No mistake, it is a clever piece of software, but some aspects do show its age.

As I'm working with a limited package, there's no way to arrange tracks and elements visually in a song scale. The KCS can be expanded with the MPE, Multi Program Environment. The Tiger editor in fact is one MPE, Mixer and Programmable Variation Generator are also not included.

As a remedy, learning to trigger sequences as KCS events can be helpful, or the song can be created ad hoc in the Open Mode play screen.

Partly because of the MPE model, the overall UI is made from separate screens, and while producing focus, it can also create confusion as one key makes something in one screen and something else in a different context. Some commands invoke dialogues, messages and alert windows, some remain silent.

Although the Tiger is quite good graphic editor, it is a little rough at the edges. I can't drag the select box to up and left, I always need to create it from top left to bottom right direction.

Much of this can be avoided by adopting the keyboard shortcuts, which are numerous. 

Copying notes as an instance cannot be done, what I mean that note changes would affect all similar instances. Technically, it is possible to get around this by planning ahead and reusing short note tracks in a KCS event list, triggering them as sequences.

However I'd still need to translate a sequence back into a track before it can be edited in Tiger. Of course a sequence event list can be directly altered manually, technically enabling instances.

The overall structure of tracks and sequences as separate entities does bring some leverage, but it can also produce these situations where I can see "I ought to have" done things differently at a previous stage.

What seems missing is any notion of an "instrument", as events brutally address a MIDI channel and that's it. This can be exactly the kind of simplicity one goes looking after in an old sequencer, but it also means there's no meta-level for making sweeping changes to the instruments.

Don't expect the MIDI to play seamlessly while operating the drop down menus, only the Open Mode play screen is free from menus. There's a setting to make the menus dependent on mouse press, but that can be also annoying. Tiger does decently while adjusting notes, which is enough.

Apart from all this, KCS Omega can be slow at times, especially if Tiger has many notes to draw. A faster ST helps, it won't hurt the tempo/MIDI timings.

Working in 2026

I tried KCS Omega on Atari Falcon, where the legacy video modes would give me med/mono resolution via VGA, and some speed boost. However the Tiger seemed to trash the screen memory in uncomfortable ways, making icons and UI invisible, otherwise it looked very nice. 

Turning the blitter off did not help. The glitching could be due to the Multi-Program Environment memory allocation scheme, as the main KCS works.

Also, the fan inside Falcon is so loud it would annoy me. An Atari ST is silent.

Just to show how the mono resolution looks like

I have an Atari STE with ACSI2STM, a tiny board that helps plug a Micro-SD card into the hard drive socket of the Atari. (This is not compatible with the Falcon.)

KCS Omega does not have an installer. The folder and containing sub-folders and files can be copied directly to the SD card filesystem, and run from there. 

If the files are inside a .msa or .st disk image type image, then Hatari ST emulator can be helpful, as it can open these images as disks. 

In Hatari, a folder in the Linux filesystem can be designated as a simulated hard drive, and when the files are copied in the Atari GEM in the emulator to that virtual hard drive, the files will appear on the Linux filesystem instantly. It's a clumsy way to move the KCS files out of the disk images, but it only needs to be done once. Then they can be copied over to the ACSI2STM SD card.

One more Hatari screenshot

This version of KCS Omega and Tiger fit into one floppy, so a HxC floppy emulator can also work.

A little bird tells that holding SHIFT when starting the KCS, will load the Tiger automatically. One of those little masonic rituals.

Atari STE resuscitation

Atari 520STE

I thought that because of the Atari Falcon, I wouldn't need the Atari STE so much. After all, Falcon can be connected to a VGA and it has more processor power and features. Yet, this split focus resulted in not using either of them much.

Recently I got hold of an ACSI2STM, a tiny board that goes into the hard drive port of the Atari ST and the SD card contents show up as a number of hard drives. It cannot even be used with the Falcon as it doesn't have a similar port.

ACSI2STM

ACSI2STM is mainly what this blog post was supposed to be about. But it turned out the Atari STE needed some care. Before attaching the new drive, I wanted to see if the computer works at all. This led to various tiny fixes and upgrades.

I don't treat the STE as a museum piece, the case and various metal parts inside are already damaged, screws are lost and so on. But I'd like it to work and preferably without too much hassle.

RAM/ROM and boot-up

The STE already had 4MB SIMMs on board, but one of them was giving grief so I had to downgrade to 2MB, removing two of them.

For a 2MB configuration, the first and third socket from back to front, needs to be occupied with 1MB SIMMs (30pin, 70ns ideally).

Not the cleanest sight. 2MB of SIMMs in correct position. Case damage at top left.

I first thought the computer was more thoroughly knackered: 4 bombs appeared no matter what happened during the memory test. But it turns out the boot doesn't continue after the test if there is no boot drive.

The image below shows what can happen in a memory test: The test is nominally passed, but the screen memory was garbled at one time so the Atari logo and the test bar are no longer fully visible. The four bombs have also arrived, but this isn't really because of the test itself.

Memory test complete, failed completely.

This was confusing until I connected a Lotharek HxC floppy emulator as a dummy drive, which helped the computer go past that stage. If the ACSI2STM is online, a floppy drive is no longer needed. But it was good to learn this.

I could configure the HxC to run a disk image properly, but I ignored it for now. If it can help achieve a faster boot time, I could look into it.

How a happy memory test looks like, 2MB

I have previously upgraded to TOS 2.06 ROM, which goes against that idea of compatibility I mentioned above. Even software that looks like it plays nice with the OS, might be broken with 2.06.

But I like that I can finally select all files, or switch between text/icons view using keyboard shortcuts. Files can be viewed using a mask, and other small additions are in place. The memory check, although not infallible, is also included. The glitches with loading the DESKTOP.INF are gone and I don't need any kind of STE_FIX.PRG inside the AUTO folder.

Working 4MB of SIMMs

2MB is quite enough. Even if HD-modified and patched games and software are rather needy compared to the original requirements, none don't seem to require 4MB. Still, I ordered 4 x 1MB SIMMs to complete the picture.

Display

I've connected the STE to a Commodore 1084S monitor. The composite video cable picture is ok-ish for many low resolution games, but quite atrocious for the 640x200 mode, and the tiniest system font is almost unreadable even as black-on-white.

ST-to-1084S monitor 6-pin DIN plug is not a common thing. Scart cables are numerous so I ordered one of them instead and a Female Scart-to-DIN6 to complete it, because this 1084 doesn't have a Scart in.

Then it turned out it doesn't quite work that way. It was ok for an MSX2 Scart RGB cable I have made, but the Atari ST Scart cable I received wouldn't work this way.

Working!

So I ended up soldering my own cable after all, using the DIN13 part from the composite cable and a Six-pin DIN for the RGB end. It's a minimal version, with Atari STE the audio can be left out, but soldering the DIN13 is still annoying.

I struggled multiple times with supposedly fool-proof diagrams, yet still mirroring and mis-matching cables. So I do not even dare to supply my own diagram, as I could end up messing it up anyway.

I left out the 120Ohm resistors, as the brightness and contrast can be adjusted on a 1084. The resulting image is very crisp on the 1084S.

A VGA-cable for mono mode is a possibility, but I don't currently have a display that could do the required 70Hz. For displaying colour in VGA, the requirements are even more stringent, 15KHz horizontal and 50/60 horizontal.

Mouse and keyboard

I have a couple of working Amiga/ST compatible mice and an original Atari mouse in a bad condition. The two non-Atari mice didn't give problems, and I was actually surprised how smooth the Wizard mouse is.

Quite good mouse, but I couldn't get it to open.

I can also use the Micromys adapter I have lying around (C64/Amiga/Atari ST), but it looks like I've misplaced my best PS/2 mouse. Fortunately I have a couple of USB Logitechs (M-BJ58) that work with a further PS/2 adapter, but the wheel will be useless.

The mouse and the additional adapters dangle uncomfortably from under the computer, and I felt the 2nd mousebutton failed occasionally, and some times even the entire Micromys went offline.

Then I remembered the ST ports can become loose, and sure enough the port was wiggly.

The underside of the keyboard circuit board

The keyboard comes off easily enough. I've sometimes thought of modding it into a separate keyboard, but the mouse and joystick port position makes this less practical. Besides I believe it's better off integrated anyway, less loose parts the better for storage.

For the purposes of inspecting and fixing the ports, the arrangement is really annoying. I have to open the whole keyboard case, and only after that the mouse port can be resoldered. There are like 30 tiny screws to remove and to be put back together again.

And the topside

While at it, I removed any dust that might affect the key bubbles, and as I had to take them loose anyway (they drop off) their positions are swapped and I also got to wipe the entire board.

As a result the numpad 2 key, which was slightly unresponsive, now works better.

Zooming into the broken solders

The above picture shows the damaged solder in the mouse port, compared to the game port which is intact. I ought to have taken a more precise picture, but the cracks are already visible here.

If I read this correctly, it is indeed the right mouse button pin which is most loose, and losing the 5V/GND might easily disturb the Micromys adapter.

I did consider wiring the mouse port entirely to the back of the case, but after drilling in a DB9 to the corner I chose not to do this now, because it's better to plan it more. I may come back to this.

After the resoldering the mouse worked fine. I'll use the 9-pin Wizard mouse at least until problems arise.

Keep those rubber bubbles carefully in place when reassembling

For a while, I had swapped the keyboards between the Falcon and the STE. Not sure why, I suppose the STE keyboard worked better and I wanted to benefit from that when the Falcon was timely. Neither have Scandinavian keys. I put the keyboards back into their correct homes.

Power Supply Unit

One more thing, a PSU replacement. I have no reason to think the old PSU is giving up, but I felt better doing this as a clean-looking replacement was available and they might disappear eventually.

The Atari ST PSU replacement from 16-32bit.eu

This should produce less heat than the old one. I was also persuaded by the included USB port, which can power the ACSI2STM – yes it needs that current to work. I guess the 5V could have been taken from the board, but this is a straightforward solution.

The old PSU

The PSU replacement needed some soldering, but nothing too difficult.

Four screws are removed, the connector to the motherboard (with the 5V/12V/GND wires) is removed, then the board can be pulled up and the two mains leads can be soldered off. I didn't even use a pump, just gently pulled the wires out one by one while heating the other side.

PSU removed

After the whole board is loose, the motherboard connector wires are soldered off. All cables are soldered back to the new board, one by one starting again from the 5V/12V/GND wires. 

Obviously refer to the instructions from the seller.

Replaced!

The result looks cleaner, whatever magic may be inside those boxes.

So, off to the world of Single Tasking.

Hedgren Next SCRIPT bag

Next SCRIPT

Nearly five years after getting the Samsonite Vectura bag, its zippers started blowing up. This was likely accelerated by stuffing in things that didn't fit properly.

Instead of going to the camping direction with the new bag, I bought something that looked like a modest upgrade from the Samsonite, yet knowing also that certain equipment will fit better inside.

Hedgren Next SCRIPT 15,6" (HNXT05-003) is more rectangular than the Samsonite was, the inside totaling to about 29 x 42 x 17 cm. The nominal volume is actually less (20,7 vs 22 liters), but the longer inside height already means the light collapsible chair fits much better. It looks like the bag has a better posture than the Samsonite.

Weight should be 1kg, I didn't measure it myself. It's not extremely lightweight, but I have the Black Diamond BBEE 11 for very minimalist packing.

I adore my 64

Funnily enough, I had a hunch a breadbox Commodore 64 would fit inside comfortably, and it did. It would go in the old Samsonite, but uncomfortably.

There's an RFID-protected container as a bonus, not that I'd like to keep my cards there, but it's nice to know.

It was by no means required for sealing the deal, but the Hedgren also has the USB outlet for a power bank, just like the Samsonite did. I almost never used this feature, to be honest. The functionality has been thought out better, the cable goes to a clearly separated compartment instead of just to the bottom of the bag.

The rubbery bottom of the bag protects it from water (or spilt drinks from seeping through the bag), but overall I don't think it's especially water-protected. All in all it's more of a flight bag than an outdoors bag.

The USB is still of the A-variety

There's many, many more zippered containers, pockets upon pockets, a laptop and a tablet compartment, a holder for a bottle outside, and a system for setting the bag up with the long handle of an airport roller bag, though I don't think I will need that. I only now realized the Samsonite also had this "smart sleeve".

Pencil holders are missing, but to be honest it would be better to have a separate box for them anyway.

The large number of compartments is not always a positive thing, as it takes some time getting used to. It can take time to find an item, and if one slot has been filled then the one on top of it may no longer be as usable. This points to a solution where some pockets would be better left for card-thin items.

Light collapsible chair+Trangia 27 set+gas+1,5l bottle of water+utensils+cups, all fit rather nicely, leaving space for food and additional bottles.

Keychron K2 HE SE Wood Black

Keychron K2 HE

I'm surprised to find out it's been nearly six years since I've changed my main keyboard, as can be seen in this old blog post. Perhaps it's time to reflect on keyboard choices.

The HyperX Alloy Origins Core was by no means a bad keyboard, the HyperX Red switches seem to have a good reputation and it was not showing signs of breaking up.

But it was slightly noisy, and to be really nit-picky, the accumulated dirt at the base showed easily on it, the LEDs basically highlighting the gunk.

Back then I considered TenKeyLess (TKL) as the sweet spot between keyboard minimalism and useless numeric keypads. I've since felt I could go with a more minimal layout, the 75%. There's always the Mac Mini keyboard, but it was troubling not to have proper HOME/END, PGUP/PGDN, Print Screen keys, and no separate DEL/BS keys.

So, enter Keychron K2 HE. There are various Keychron models, ranging from low to high profile, minimal to full layout, but overall the boxy shape, old fashioned keys, I just knew I wanted it. There is something vaguely 1970s about it, maybe the wood details and no-nonsense font connects it to those old Sol-20 terminal computers. It also weighs nearly one kilogram.

I hesitated when I saw it was marketed as "wireless", not something I look for in keyboards. But after I learned there is a cable data mode (it's not just for charging) I was fully sold. The USB cable was included. There are BT and 2.4GHz modes.

The wood panels are a nice touch

From a minimal experience I'm not going to comment how well it works with games. It was fine for Manic Miner on a Spectrum emulator. The magnetic switches mean there's no added tactile sensation for the key presses, but I've not given much thought about such matters. HyperX didn't do that really either, and here the feel is already nicer if only for the better sound. I guess I've simply become used to the lack of a definite "click" feel in keyboards. It was already so in Atari ST days.

There is an app that can help configure and calibrate the keyboard, but I've not looked at it, as I'd need to fire up my Mac to do it. Obviously it won't work on Linux. Supposedly each individual key can have a different sensitivity. Also, the lights options are very limited from the keyboard itself, but I was able to find a muted non-animated lighting which was fine for me.

By default, there are the Macintosh style Hannunvaakuna symbols instead of ALT and ALT GR. Just as I was about to write about this strange choice, I noticed there were extra keycaps included in the package, such as a black ESC instead of the default light brown one. A nice gesture.

Included tools, the receiver and extra keys

In that old blog post I still lamented the HyperX would not transmit as many keys at once as one Blackstorm keyboard did, possibly some kind of side effect of not using it on Windows or Mac, can't remember. I can observe the Keychron passes this arbitrary "qwertyuiop" test, meaning I can push the whole row simultaneously and all keys will be transmitted.

And yes, my 65% Blackstorm has an even smaller footprint than this Keychron, but I now consider the Blackstorm woefully noisy. I believe 65% would be too minimal for my needs.

Here the transition from TKL to 75% means there are no Scroll Lock and Pause keys. Thankfully Print Screen exists, it has a "crop" symbol on it. DEL is not as comfortably positioned, but can be learned. Positively, HOME and END are in a nice location and PGUP and PGDN are close at hand.

For my current setup, it's good to have the cable on the left side

Then to my only real gripe so far.

Insert is missing, which is concerning when using tracker music software. Instead of the dedicated light-key, I'd rather have INS. The light-key doesn't even appear to register as an event in the system, as xev indicates, so it likely cannot be customized from the system either. Wasting one key to an operation I don't really need that often, is a crime.

Also, for some older Keychron keyboards, fn+DEL functions as INS, but no such luck with this one. Reading about it, it does sound like a minor scandal. 

Whereas the included extra keys felt like a nice gesture, now I'm a little soured they didn't include an INS too. In fact Keychron doesn't appear to sell individual keys.

I was prepared to say I've learned my lessons as a keyboard buyer, but had I spotted the lack of Insert key I might even have diverted my money elsewhere.

But all is not lost. I installed input-remapper on Linux Mint and recorded the Crop key and made it into KEY_INSERT. Easy enough.

input_remapper

I usually adjust quite fast to minor changes in keyboard layouts, but I note the INS and DEL pair are somewhat far from cursor keys. Perhaps some Sinclair QL style remapping of modifier+cursor keys to perform as INS and DEL and learn a genuinely quirky practice?

I still needed Control+Crop key to function as PrintScreen, as the Crop key now performs as INS. This had to be remapped to KEY_SYSRQ which does not sound very intuitive but wasn't hard to find out. The Autoload needs to be turned on for the changes to work after reboot.

So, despite this gripe the Keychron might be the best keyboard I've ever had. Of course, time will tell if it will break apart or start misbehaving.

Primus Firestick

Primus Firestick in pristine, unused condition

Primus Firestick always looked like fun, but also expensive for what it is: fairly standard screw-on gas burner with a design gimmick.

One day I saw this for 40€, passed it, then realized it comes with a carry bag and the Primus piezo igniter (easily 16€ by itself), went back another day and picked it up.

Already when taking it out of the box, it looks flimsier than in the photographs and the tripod "flaps" don't seem to reach very far.

Box contents, there's also a manual.

The cap needs to be removed to open the flaps, which is simple enough, but putting it back together needs a tiny amount of practice. Yes, it opens hassle-free and "automatically", but is that a major draw?

The loose cap can be considered at least a minor design flaw, it might have been a better to have it hinge on one of the flaps or something.

For a first quick test, I warmed a Duossal's worth of pea soup, and the Primus did just fine.

Jalostajan Hernekeitto, mmm...

When put together, the Firestick is not only compact but the round form is quite convenient for carrying. I'm tempted to carry it as is, but because the burner component needs protection and the cap could come loose, it's better to keep it in the bag. The bag is also a good place for the piezo igniter.

If I have to compare this to "Furno 360", the Firestick is likely not as powerful, but it takes a little less space.

At first it was puzzling that I needed to turn the valve quite a lot before the gas even begins to flow. But the valve is quite generous, a quarter-turn isn't going to send the burner into a fit. This is quite pleasant, much better than in my Primus Mimer stove.

The jagged parts don't connect with a normal pot

A little wind didn't create a problem, but on more open ground the Firestick turned out to be quite sensitive to even normal wind, when attempting a low flame. But this is quite common with burners, especially the taller screw-on models. Heating water with a full-on blast is unlikely to be a problem.

Yet I'm starting to think one of those collapsible windshields might make sense. And yes, Trangia storm cookers have solved this already.

The pot holds firmly enough, even though the tripod parts don't connect in the most ideal way. It might be there is a specific Primus pot or cup that connects better into it.

Fire Maple Feast Heat Exchanger

Notably this is the second system I've bought that has some problems with the Fire Maple Feast Heat Exchanger pot. It looks like the Firestick flaps nearly fit inside the opening inside the exchanger, but it doesn't without squeezing the flaps inward a little. So it can become "locked", which depending on the situation might be a good or a bad thing. I'm inclined to think it might be a bad thing.

Boohoo, it's dirty already

If the idea of the design is that the flap outsides would retain their color better than in other models, no such luck, the burn colorization attacked it the first time. The cap obviously remains clean.

So, yet another burner that's unlikely to pull much weight in winter conditions, but hey, the Primus piezo igniter is quite good.