Now that the TopSpeed TechKit with its #assembler is out in the world, I'm considering porting the #TASM and #MASM code in one or two of the open source #EPOC16 apps over to TSASM.

Hardly an urgent project, but it would mean that the apps could be built with one #compiler ecosystem with a single project file.

Of course, the code would still be restricted to the #16bit world, but it's no worse off than we already are in #Psion land.

#DOSBox #RetroDev #RetroComputing

Reading through the first manual in the SDK has reminded me what the "pure small memory model" is.

The ES register is never corrupted (DS=ES=SS).

#TopSpeed C implemented this, which was one of the main reasons why #Psion used it for the SDK.

I've heard that it's possible to implement this with #Borland C (and maybe #Watcom?), but I don't know how.

#16bit #retrocomputing #epoc16 #x86

Reading through the first manual in the SDK has reminded me what the "pure small memory model" is.

The ES register is never corrupted.

#TopSpeed C implemented this, which was one of the main reasons why #Psion used it for the SDK.

I've heard that it's possible to implement this with #Borland C (and maybe #Watcom?), but I don't know how.

#16bit #retrocomputing #epoc16

I've never had a proper look at this folder before. It's like some sort of parallel version of the SDK's include folder.

Some things seem newer, some older. Version numbers and file authors don't tie up. Some parts are broken up into separate files.

The folder conforms better to #Psion C standards. It includes a file called p_msdos.h, like you could use PLIB on something that isn't #EPOC16.

Is this the missing link to the long lost v1.00 of the SDK, designed for the MC range?

#retrocomputing

I'll also be making a "2.21" with a few fixes, such as checking for includes properly.

I'm going to boldly say that my 2.21 version is the one you should use, but of course I'll distribute the older versions. I've definitely had projects that will compile with 2.00 but not with 2.20. I think these projects are more likely to compile with 2.21.

#Psion #epoc16 #psion3 #retrodev #retrocomputing

#Psion poll!

I'm going to make a video about how to install the SIBO C SDK in #DOSBox, so that people can compile apps for #EPOC16 computers (Series 3/3a/3c/3mx, Siena, Workabout, MC range).

If you are one of the tiny number of people who might be interested in using this, which modern OS do you use?

I want to know so that I can tailor the tutorial.

#retrocomputing

As much as I'd like to base a #Psion SIBO C SDK tutorial around Linux, I think there are going to be more people out there running Windows or macOS.

Maybe I should do a poll. The Fediverse is representative of the sort of folk who would want to make new #EPOC16 software, right?

Right?!

👀

#retrocomputing

Stumbled across this.

12 years ago, someone wanted to build a "new" Series 3a with an FPGA.

They were talking to #Psion about getting hold of the source code for #EPOC16. Psion seemed willing to help, but concerned about "other intellectual property rights."

Good to see willingness, but my heart sank a little.

But... Looks like they were happy for the SDK to be freely available, so I'll look into that.

Also, I wonder if "Michael E" is still around?

#retrocomputing

https://web.archive.org/web/20110623141058/http://community.psion.com/discussions/f/151/t/7708.aspx

Wrote up a summary of the past year on Hackaday IO (@hackaday) because it was rattling around in my brain.

OK, *now* I'm going to rest.

#psion #retrocomputing #EDisAsm #sibolib #mame #PsiDrive #epoc16 #pda #vintagecomputing #retrodev #retrospective

https://hackaday.io/project/161291-the-last-psion/log/222163-a-long-overdue-update-pcbs-emulators-and-more

#GAC will actually run in #ZXemul, the #ZXSpectrum #emulator for #Psion #EPOC16 (it has full #Z80 emulation). But you really need a 3mx for ZXemul to run at full #Speccy speed, and it will guzzle battery.

Still, here it is running in #MAME, for anyone who wants to see emulator-ception.

#retrocomputing #retrogaming #GraphicAdventureCreator #TextAdventure

Anyone remember the Graphic Adventure Creator?

Originally made for the #Amstrad #CPC, my experience of it was from a #YourSinclair covertape.

Anyway, it's been on my list to attempt porting it to #Psion #EPOC16 for ages. It's not top priority, but the machine is perfectly designed for playing #textadventure games (see @root42's escapades with #Infocom).

Be great if it could decompile and play old games, too.

#retrocomputing #Psion3 #adventure

https://en.wikipedia.org/wiki/Graphic_Adventure_Creator
https://gac.interface1.net/

The thing is, my "copy" of the #Psion #EPOC16 SDK is a mish-mash. The software and source code is v2.20. But the documentation is mostly v2.30 with smatterings of v2.10 and v2.01.

This is the first time I've found a major difference between versions.

Also, there is a chance that, somewhere out there, there is a software update to v2.30 that lines up with the docs.

There's also a chance that there was an update to the SDK that includes the 3mx, but I've never seen it.

Some of the old #Psion #EPOC16 C code I'm trying to compile mentions the file `s_.h`. It's not in the SDK, although it is mentioned in the SDK.

It's something to do with resource files.

Can't find it bloody anywhere!

#RetroComputing #RetroDev

Thanks to the excellent search skills of @galaxis, I now have Elvis 1.8p4 without the #EPOC16 patch. Comparing the two, the changes are:

1. EPOC16 specifics and workarounds, as expected. (`#ifndef EPOC`, etc.)
2. All the man pages have been removed.
3. A new "libc" folder filled with wrappers for Psion's plib.
4. Most strings have been replaced with references to a resource file. Why? The EPOC16 version could be regionalised!
5. Edited files have been changed from UNIX to DOS linebreaks.

The people have spoken! The Elvis #EPOC16 code will be uploaded as-is, possibly broken but ready to be given some TLC!

So, next question (and I think I already know the answer).

Would it be worthwhile finding the original unmodified Elvis code, uploading that to GitHub, then branching it and copying the EPOC16 modifications over the top?

That way we can get an idea of the changes needed to make a *NIX app run on EPOC16.

#RetroComputing #RetroDev #Vi #Vim #Psion

I have (I think) the source for the last version of Elvis (a #Vi clone) for #EPOC16. I can't currently get it to compile with the #Psion SDK, even with modifications to the TopSpeed project file (like a makefile).

Should I upload it to GitHub as-is, seemingly unusable but could be worked on? Or should I only release a compilable version once I've got it working?

#RetroComputing #RetroDev #Vim

Started to build up a framework of files to supplement the #Psion SIBO C SDK for modern compilation.

First one... A half-decent gitignore file.

https://github.com/PocketNerdIO/edisasm/blob/main/.gitignore

It would be half the length if DOSBox Staging generated lower-case files by default.

#RetroComputing #RetroDev #EPOC16 #EDisAsm #git

Some more #Psion C code rescued!

Nfsc is a VT100 terminal emulator for #EPOC16. The source code was tucked away in my archive. It's GPLv2, so I thought I'd make sure it was out there for the world to see.

#RetroComputing #RetroDev #16bit

https://github.com/PocketNerdIO/nfsc

Trying to give #EDisAsm a proper help menu, which requires compiling a resource (.RSC) file.

After much faffing, I've got compiled a basic .RSC file, and added its .RSG (header) file to the project. All compiled OK. Copied the app and .RSC to the DOS #EPOC16 emulator and...

DOES ANYONE REMEMBER HOW TO DO THIS?

I'm currently trawling through old code and the SDK docs.

#RetroComputing #RetroDev #Psion

Today, I'm getting distracted, trying to compile Elvis (an old #Vi spin-off) for #Psion #EPOC16.

Bearing in mind I'm running the original toolchain that this was developed with, this should Just Work™️. However... ERROR.

There are no instructions for compilation, so I don't know if there's a special order I need to do things in.

#RetroComputing #RetroDev #TopSpeedC #Vim