#topspeed — Public Fediverse posts

https://www.cyclingeu.com/880595/bmw-f-450-gs-autobahn-top-speed-acceleration-test-pov/ BMW F 450 GS || Autobahn Top Speed & Acceleration Test POV ##germany #AccelerationTest #AdventureBike #autobahn #Bicycling #BicyclingGermany #Biking #BikingGermany #BmwF450gs #BmwGs #BMWMotorrad #Cycling #CyclingGermany #CyclingSchwerinGermany #Deutschland #F450gs #GS450 #M48 #M48Garage #Montalban48 #NoSpeedLimit #PureSound #TopSpeed

We ran the numbers. Cale Makar is the NHL playoffs’ fastest defenseman

In game two of the Colorado Avalanche’s opening round series against the Los Angeles Kings on Apr…
#nflL #nflplayoffs #NFLPlayoffs #boston #CaleMakar #ColoradoAvalanche #defenseman #ErikKarlsson #Football #JakeSanderson #LosAngeles #LosAngelesKings #MikhailSergachev #NathanMcKinnon #NFL #NHL #NikitaZadorov #NoahHanifin #Ottawa #PittsburghPenguins #topspeed #TrevorMoore #VegasGoldenKnights
https://www.rawchili.com/nfl/878139/

We ran the numbers. Cale Makar is the NHL playoffs’ fastest defenseman

In game two of the Colorado Avalanche’s opening round series against the Los Angeles Kings on Apr…
#nflL #nflplayoffs #NFLPlayoffs #boston #CaleMakar #ColoradoAvalanche #defenseman #ErikKarlsson #Football #JakeSanderson #LosAngeles #LosAngelesKings #MikhailSergachev #NathanMcKinnon #NFL #NHL #NikitaZadorov #NoahHanifin #Ottawa #PittsburghPenguins #topspeed #TrevorMoore #VegasGoldenKnights
https://www.rawchili.com/nfl/878139/

We ran the numbers. Cale Makar is the NHL playoffs’ fastest defenseman https://www.rawchili.com/nfl/878139/ #boston #CaleMakar #ColoradoAvalanche #defenseman #ErikKarlsson #Football #JakeSanderson #LosAngeles #LosAngelesKings #MikhailSergachev #NathanMcKinnon #NFL #NFLPlayoffs #NHL #Nikita Zadorov #NoahHanifin #Ottawa #PittsburghPenguins #TopSpeed #TrevorMoore #VegasGoldenKnights

We ran the numbers. Cale Makar is the NHL playoffs’ fastest defenseman https://www.rawchili.com/nfl/878139/ #boston #CaleMakar #ColoradoAvalanche #defenseman #ErikKarlsson #Football #JakeSanderson #LosAngeles #LosAngelesKings #MikhailSergachev #NathanMcKinnon #NFL #NFLPlayoffs #NHL #Nikita Zadorov #NoahHanifin #Ottawa #PittsburghPenguins #TopSpeed #TrevorMoore #VegasGoldenKnights

Sebastian Jung überzeugt mit Top-Leistung und starker Laufleistung

Nachdem Sebastian Jung in Schalke, bei der 0:1 Niederlage erst nach 64 Minuten in die Partie kam, durfte…
#Bielefeld #Deutschland #Deutsch #DE #Schlagzeilen #Headlines #Nachrichten #News #Europe #Europa #EU #ArminiaBielefeld #FabianSchleusener #Germany #KarlsruherSC #Laufbereitschaft #Nordrhein-Westfalen #RafaelPinto #Schalke #SebastianJung #stephanambrosius #Topspeed
https://www.europesays.com/de/944497/

https://www.evshift.com/417779/2025-peugeot-408-gt-1-6-phev-225-ps-peugeot-408-gt-phev-hybrid-pov-autobahn-topspeed/ 2025 Peugeot 408 GT 1.6 PHEV 225 PS #peugeot #408 #gt #phev #hybrid #pov #autobahn #topspeed #autobahn #ElectricCars #ElectricVehicles #EV #Hybrid #Hybrids #peugeot #phev #PlugInHybrids #PlugInHybridsVehicles #pov #TopSpeed

https://www.fogolf.com/1172554/11-suvs-that-depreciate-fastest-over-5-years/ 11 SUVs That Depreciate Fastest Over 5 Years #depreciation #InfinitiQX80 #LuxurySUVs #MSRP #TigerWoods #TopSpeed

https://www.fogolf.com/1172554/11-suvs-that-depreciate-fastest-over-5-years/ 11 SUVs That Depreciate Fastest Over 5 Years #depreciation #InfinitiQX80 #LuxurySUVs #MSRP #TigerWoods #TopSpeed

I’ve just been thinking about this:

I have no idea how performant my car is because I’m practically only accelerating using #adaptiveCruiseControl. I also never switch out of #ecoMode.

#acceleration and #topSpeed have ceased being the least buying factor.

I’ve just been thinking about this:

I have no idea how performant my car is because I’m practically only accelerating using #adaptiveCruiseControl. I also never switch out of #ecoMode.

#acceleration and #topSpeed have ceased being the least buying factor.

I’ve just been thinking about this:

I have no idea how performant my car is because I’m practically only accelerating using #adaptiveCruiseControl. I also never switch out of #ecoMode.

#acceleration and #topSpeed have ceased being the least buying factor.

I’ve just been thinking about this:

I have no idea how performant my car is because I’m practically only accelerating using #adaptiveCruiseControl. I also never switch out of #ecoMode.

#acceleration and #topSpeed have ceased being the least buying factor.

the most innovative is probably the naming ID.EVERY1 (haha get it? everyONE) well... can it fly? no
https://youtu.be/my3kVExPfg8 #omg #germany #vw the most boring possible #presentation of a new #car #ev possible

#NetRange 250km (155 miles)
#ReleaseDate 2027
#MotorPower 70 kW (95 PS / 94 HP)
#TopSpeed 130 km/h (81 mph)
Price ~ 20000 bucks

the most innovative is probably the naming ID.EVERY1 (haha get it? everyONE) well... can it fly? no
https://youtu.be/my3kVExPfg8 #omg #germany #vw the most boring possible #presentation of a new #car #ev possible

#NetRange 250km (155 miles)
#ReleaseDate 2027
#MotorPower 70 kW (95 PS / 94 HP)
#TopSpeed 130 km/h (81 mph)
Price ~ 20000 bucks

the most innovative is probably the naming ID.EVERY1 (haha get it? everyONE) well... can it fly? no
https://youtu.be/my3kVExPfg8 #omg #germany #vw the most boring possible #presentation of a new #car #ev possible

#NetRange 250km (155 miles)
#ReleaseDate 2027
#MotorPower 70 kW (95 PS / 94 HP)
#TopSpeed 130 km/h (81 mph)
Price ~ 20000 bucks

the most innovative is probably the naming ID.EVERY1 (haha get it? everyONE) well... can it fly? no
https://youtu.be/my3kVExPfg8 #omg #germany #vw the most boring possible #presentation of a new #car #ev possible

#NetRange 250km (155 miles)
#ReleaseDate 2027
#MotorPower 70 kW (95 PS / 94 HP)
#TopSpeed 130 km/h (81 mph)
Price ~ 20000 bucks

the most innovative is probably the naming ID.EVERY1 (haha get it? everyONE) well... can it fly? no
https://youtu.be/my3kVExPfg8 #omg #germany #vw the most boring possible #presentation of a new #car #ev possible

#NetRange 250km (155 miles)
#ReleaseDate 2027
#MotorPower 70 kW (95 PS / 94 HP)
#TopSpeed 130 km/h (81 mph)
Price ~ 20000 bucks

For the first time in ages, I've had a good afternoon writing code!

I've been working on #ecobj. I can now analyse six OMF record types (well, five and a bit) using some rough-and-ready Pascal. And I've started to get a picture of how the original ECOBJ.EXE moves the records around.

As far as I know, there are 10 record types that ECOBJ.EXE handles. So I'm over halfway there. Sort of.

Using the #TopSpeed Object Disassembler (TSDA) has really helped to make sure I'm heading in the right direction. #DOSBox makes this easy by letting me send the output from TSDA.EXE to a file, so I can view it on Linux.

For the first time in ages, I've had a good afternoon writing code!

I've been working on #ecobj. I can now analyse six OMF record types (well, five and a bit) using some rough-and-ready Pascal. And I've started to get a picture of how the original ECOBJ.EXE moves the records around.

As far as I know, there are 10 record types that ECOBJ.EXE handles. So I'm over halfway there. Sort of.

Using the #TopSpeed Object Disassembler (TSDA) has really helped to make sure I'm heading in the right direction. #DOSBox makes this easy by letting me send the output from TSDA.EXE to a file, so I can view it on Linux.

For the first time in ages, I've had a good afternoon writing code!

I've been working on #ecobj. I can now analyse six OMF record types (well, five and a bit) using some rough-and-ready Pascal. And I've started to get a picture of how the original ECOBJ.EXE moves the records around.

As far as I know, there are 10 record types that ECOBJ.EXE handles. So I'm over halfway there. Sort of.

Using the #TopSpeed Object Disassembler (TSDA) has really helped to make sure I'm heading in the right direction. #DOSBox makes this easy by letting me send the output from TSDA.EXE to a file, so I can view it on Linux.

For the first time in ages, I've had a good afternoon writing code!

I've been working on #ecobj. I can now analyse six OMF record types (well, five and a bit) using some rough-and-ready Pascal. And I've started to get a picture of how the original ECOBJ.EXE moves the records around.

As far as I know, there are 10 record types that ECOBJ.EXE handles. So I'm over halfway there. Sort of.

Using the #TopSpeed Object Disassembler (TSDA) has really helped to make sure I'm heading in the right direction. #DOSBox makes this easy by letting me send the output from TSDA.EXE to a file, so I can view it on Linux.

For the first time in ages, I've had a good afternoon writing code!

I've been working on #ecobj. I can now analyse six OMF record types (well, five and a bit) using some rough-and-ready Pascal. And I've started to get a picture of how the original ECOBJ.EXE moves the records around.

As far as I know, there are 10 record types that ECOBJ.EXE handles. So I'm over halfway there. Sort of.

Using the #TopSpeed Object Disassembler (TSDA) has really helped to make sure I'm heading in the right direction. #DOSBox makes this easy by letting me send the output from TSDA.EXE to a file, so I can view it on Linux.

https://www.evshift.com/359291/nissan-rogue-plug-in-hybrid/ Nissan Rogue Plug in Hybrid #2026NissanRoguePlugInHybrid #acceleration #car #CarNews #CARS #ElectricCars #ElectricVehicles #EV #FirstLook #Hybrid #Hybrids #LaunchEvent #news #nissan #NissanRogue #NissanRogueHybrid #NissanRoguePlugInHybrid #NissanRogueReview #Plug #PlugInHybrids #PlugInHybridsCars #rogue #SP #SuperchargedPetrolhead #superchargedpetrolhead #TopSpeed #Walkaround

https://www.evshift.com/353489/2026-tesla-model-y-performance-now-has-627hp-review-on-autobahn/ 2026 Tesla Model Y Performance now has 627HP! // REVIEW on AUTOBAHN #2026TeslaModelYPerformance #627HP #autobahn #ElectricCars #ElectricVehicles #EV #GermanAutobahn #Model #ModelY #ModelYPerformance #ModelYReview #NewTeslaModelY #Performance #review #Tesla #TeslaModelY #TeslaModelYFacelift #TeslaModelYJuniper #TeslaModelYPerformance #TeslaModelYPerformance2026 #TeslaModelYReview #TeslaSuv #TeslaSUV2026 #TeslaSuvInterior #TeslaSuvModelY #TeslaSuvModels #TeslaSuvY #TopSpeed

https://www.evshift.com/332338/2021-toyota-rav4-phev-306-ps-toyota-rav4-toyotarav4-hybrid-topspeed-autobahn-mpg-verbrauch/ 2021 Toyota RAV4 PHEV 306 PS #toyota #rav4 #toyotarav4 #hybrid #topspeed #autobahn #mpg #verbrauch #autobahn #ElectricCars #ElectricVehicles #EV #Hybrid #Hybrids #mpg #phev #PlugInHybrids #PlugInHybridsCars #rav4 #TopSpeed #Toyota #toyotarav4 #Verbrauch

TOP SPEED Sportster S 2025. Harley Davidson. #raw #topspeed
https://themotorbikechannel.com/top-speed-sportster-s-2025-harley-davidson-raw-topspeed/?fsp_sid=37486

TOP SPEED Sportster S 2025. Harley Davidson. #raw #topspeed
https://themotorbikechannel.com/top-speed-sportster-s-2025-harley-davidson-raw-topspeed/?fsp_sid=37486

https://www.alojapan.com/1318258/i-took-japans-bullet-train-for-the-first-time-shinkansen-pros-cons/ I Took Japan’s Bullet Train for the First Time: Shinkansen Pros, Cons #BulletTrain #BusinessInsider #cons #country #downside #FamousShinkansen #FirstTime #hour #Japan #mile #Osaka #ShinkansenPros #Tokyo #TokyoTopics #TopSpeed #TwoAndAHalfHourTrip #東京 #東京都 2025-02-10T11:40:02Z Share Facebook Email X LinkedIn Copy link lighning bolt icon An icon in the shape of a lightning bolt. Impact Link Save Saved Read in app This story is available e

https://www.alojapan.com/1318258/i-took-japans-bullet-train-for-the-first-time-shinkansen-pros-cons/ I Took Japan’s Bullet Train for the First Time: Shinkansen Pros, Cons #BulletTrain #BusinessInsider #cons #country #downside #FamousShinkansen #FirstTime #hour #Japan #mile #Osaka #ShinkansenPros #Tokyo #TokyoTopics #TopSpeed #TwoAndAHalfHourTrip #東京 #東京都 2025-02-10T11:40:02Z Share Facebook Email X LinkedIn Copy link lighning bolt icon An icon in the shape of a lightning bolt. Impact Link Save Saved Read in app This story is available e

Someone asked me some questions on the #Psion Series 3, so I thought I'd post my response here in case anyone else is interested. #LongRead

Emulator

You've got two options. The first is the original "emulators" written by Psion, S3AEMUL.EXE and S3CEMUL.EXE. They both run in DOS and emulate the 3a and 3c. But they're less of an emulator than a runtime environment for #EPOC16 (the OS). There's good and bad to this. You can run S3AEMUL and S3CEMUL straight in #DOSBox and it will talk to your host OS's filesystem (Windows, Linux, macOS, whatever). You need to map an M: drive in DOSBox for the internal storage, but once that's done you can copy files straight into that folder on your host OS and run them in the emulators. The downside is that it's not true hardware emulation. You won't get a good judge of the speed of a real device, and some syscalls aren't implemented so will fail or crash the #emulator. They're bundled with the SDK (see below).

The alternative is #MAME. This is the closest to proper hardware emulation you're going to find. You can either dump your own ROMs using a tool called #EDisAsm, or you can find them in the usual MAME ROM repos. The one thing that is notably missing is RS232 emulation from the later models, because we haven't been able to find any documentation on the silicon, but it's working fine with the 3a.

Toolchain

At the moment you have only one option - the Psion SIBO C SDK with the #TopSpeed C Compiler. You're going to need DOSBox (I personally prefer DOSBox Staging). It's all available on the Internet Archive in one easy download, including all the documentation you will need.

https://archive.org/details/psion-sibo-c-sdk

From there, you have a few libraries you can use. There CLIB, which is a pure ANSI C implementation, designed to easily port apps - don't use it, it's slow and you'll be missing a lot of features. Then there's PLIB, which is Psion's C dialect - very nice to use, and you can put together a C app pretty quickly. Finally, there's OLIB, which is Psion's proprietary OO C - it feels very clunky, but once you get over that it can be very powerful.

EPOC16 apps are restricted to a very pure version of the small memory model, but you can split code up into libraries known as DYLs.

In the past I've written code using VS Code, which can be made to play nicely with the SDK's header files. I've not got it working with NeoVim and clangd yet, but it should be possible with cmake.

The SDK comes with a debugger (SDBG.EXE), a DOS GUI app. If you run SDBG.EXE in DOSBox Staging, run the Psion3a MAME emulation, and enable RS232 over TCP on both, you can use SDBG to send apps to MAME. If you enable symbols, you can step through the code. It's rudimentary by modern standards, but it works pretty well.

I say "at the moment" because I'm slowly rewriting the tools in the SDK. I already have a new working version of #CTRAN, the preprocessor for Psion OO C, but I'm a long way from a compiler. There have been efforts to coax gcc into compiling for SIBO/EPOC16, but I think they have stalled for now.

If you want some examples of EPOC16 C and OO C code, take a look at these:
https://github.com/thelastpsion/edisasm
https://github.com/thelastpsion/pyramid
https://github.com/thelastpsion/nfsc
https://github.com/nickmat/Psion3-Wari
https://github.com/nickmat/Psion3-Vector

Device

The 3mx is the best choice. It's significantly faster than the earlier models (27.6 MHz vs 7.6 MHz), has a switchable backlight, the fastest RS232 and the best version of EPOC16. I "daily drive" one for journalling, adventure games, and a few other small tasks. After that I'd say the 3c (beware - they were covered in soft-touch rubber, so will need cleaning) and the 2MB 3a. The latter is the most common. Most 3c units came with a backlight, except for the early UK ones. The 3a doesn't. Arguably the non-backlit screens have better contrast so you don't need the backlight so much in lower light, but the backlight has obvious benefits.

#RetroComputing #RetroDev #16bit

Someone asked me some questions on the #Psion Series 3, so I thought I'd post my response here in case anyone else is interested. #LongRead

Emulator

You've got two options. The first is the original "emulators" written by Psion, S3AEMUL.EXE and S3CEMUL.EXE. They both run in DOS and emulate the 3a and 3c. But they're less of an emulator than a runtime environment for #EPOC16 (the OS). There's good and bad to this. You can run S3AEMUL and S3CEMUL straight in #DOSBox and it will talk to your host OS's filesystem (Windows, Linux, macOS, whatever). You need to map an M: drive in DOSBox for the internal storage, but once that's done you can copy files straight into that folder on your host OS and run them in the emulators. The downside is that it's not true hardware emulation. You won't get a good judge of the speed of a real device, and some syscalls aren't implemented so will fail or crash the #emulator. They're bundled with the SDK (see below).

The alternative is #MAME. This is the closest to proper hardware emulation you're going to find. You can either dump your own ROMs using a tool called #EDisAsm, or you can find them in the usual MAME ROM repos. The one thing that is notably missing is RS232 emulation from the later models, because we haven't been able to find any documentation on the silicon, but it's working fine with the 3a.

Toolchain

At the moment you have only one option - the Psion SIBO C SDK with the #TopSpeed C Compiler. You're going to need DOSBox (I personally prefer DOSBox Staging). It's all available on the Internet Archive in one easy download, including all the documentation you will need.

https://archive.org/details/psion-sibo-c-sdk

From there, you have a few libraries you can use. There CLIB, which is a pure ANSI C implementation, designed to easily port apps - don't use it, it's slow and you'll be missing a lot of features. Then there's PLIB, which is Psion's C dialect - very nice to use, and you can put together a C app pretty quickly. Finally, there's OLIB, which is Psion's proprietary OO C - it feels very clunky, but once you get over that it can be very powerful.

EPOC16 apps are restricted to a very pure version of the small memory model, but you can split code up into libraries known as DYLs.

In the past I've written code using VS Code, which can be made to play nicely with the SDK's header files. I've not got it working with NeoVim and clangd yet, but it should be possible with cmake.

The SDK comes with a debugger (SDBG.EXE), a DOS GUI app. If you run SDBG.EXE in DOSBox Staging, run the Psion3a MAME emulation, and enable RS232 over TCP on both, you can use SDBG to send apps to MAME. If you enable symbols, you can step through the code. It's rudimentary by modern standards, but it works pretty well.

I say "at the moment" because I'm slowly rewriting the tools in the SDK. I already have a new working version of #CTRAN, the preprocessor for Psion OO C, but I'm a long way from a compiler. There have been efforts to coax gcc into compiling for SIBO/EPOC16, but I think they have stalled for now.

If you want some examples of EPOC16 C and OO C code, take a look at these:
https://github.com/thelastpsion/edisasm
https://github.com/thelastpsion/pyramid
https://github.com/thelastpsion/nfsc
https://github.com/nickmat/Psion3-Wari
https://github.com/nickmat/Psion3-Vector

Device

The 3mx is the best choice. It's significantly faster than the earlier models (27.6 MHz vs 7.6 MHz), has a switchable backlight, the fastest RS232 and the best version of EPOC16. I "daily drive" one for journalling, adventure games, and a few other small tasks. After that I'd say the 3c (beware - they were covered in soft-touch rubber, so will need cleaning) and the 2MB 3a. The latter is the most common. Most 3c units came with a backlight, except for the early UK ones. The 3a doesn't. Arguably the non-backlit screens have better contrast so you don't need the backlight so much in lower light, but the backlight has obvious benefits.

#RetroComputing #RetroDev #16bit

Someone asked me some questions on the #Psion Series 3, so I thought I'd post my response here in case anyone else is interested. #LongRead

Emulator

You've got two options. The first is the original "emulators" written by Psion, S3AEMUL.EXE and S3CEMUL.EXE. They both run in DOS and emulate the 3a and 3c. But they're less of an emulator than a runtime environment for #EPOC16 (the OS). There's good and bad to this. You can run S3AEMUL and S3CEMUL straight in #DOSBox and it will talk to your host OS's filesystem (Windows, Linux, macOS, whatever). You need to map an M: drive in DOSBox for the internal storage, but once that's done you can copy files straight into that folder on your host OS and run them in the emulators. The downside is that it's not true hardware emulation. You won't get a good judge of the speed of a real device, and some syscalls aren't implemented so will fail or crash the #emulator. They're bundled with the SDK (see below).

The alternative is #MAME. This is the closest to proper hardware emulation you're going to find. You can either dump your own ROMs using a tool called #EDisAsm, or you can find them in the usual MAME ROM repos. The one thing that is notably missing is RS232 emulation from the later models, because we haven't been able to find any documentation on the silicon, but it's working fine with the 3a.

Toolchain

At the moment you have only one option - the Psion SIBO C SDK with the #TopSpeed C Compiler. You're going to need DOSBox (I personally prefer DOSBox Staging). It's all available on the Internet Archive in one easy download, including all the documentation you will need.

https://archive.org/details/psion-sibo-c-sdk

From there, you have a few libraries you can use. There CLIB, which is a pure ANSI C implementation, designed to easily port apps - don't use it, it's slow and you'll be missing a lot of features. Then there's PLIB, which is Psion's C dialect - very nice to use, and you can put together a C app pretty quickly. Finally, there's OLIB, which is Psion's proprietary OO C - it feels very clunky, but once you get over that it can be very powerful.

EPOC16 apps are restricted to a very pure version of the small memory model, but you can split code up into libraries known as DYLs.

In the past I've written code using VS Code, which can be made to play nicely with the SDK's header files. I've not got it working with NeoVim and clangd yet, but it should be possible with cmake.

The SDK comes with a debugger (SDBG.EXE), a DOS GUI app. If you run SDBG.EXE in DOSBox Staging, run the Psion3a MAME emulation, and enable RS232 over TCP on both, you can use SDBG to send apps to MAME. If you enable symbols, you can step through the code. It's rudimentary by modern standards, but it works pretty well.

I say "at the moment" because I'm slowly rewriting the tools in the SDK. I already have a new working version of #CTRAN, the preprocessor for Psion OO C, but I'm a long way from a compiler. There have been efforts to coax gcc into compiling for SIBO/EPOC16, but I think they have stalled for now.

If you want some examples of EPOC16 C and OO C code, take a look at these:
https://github.com/thelastpsion/edisasm
https://github.com/thelastpsion/pyramid
https://github.com/thelastpsion/nfsc
https://github.com/nickmat/Psion3-Wari
https://github.com/nickmat/Psion3-Vector

Device

The 3mx is the best choice. It's significantly faster than the earlier models (27.6 MHz vs 7.6 MHz), has a switchable backlight, the fastest RS232 and the best version of EPOC16. I "daily drive" one for journalling, adventure games, and a few other small tasks. After that I'd say the 3c (beware - they were covered in soft-touch rubber, so will need cleaning) and the 2MB 3a. The latter is the most common. Most 3c units came with a backlight, except for the early UK ones. The 3a doesn't. Arguably the non-backlit screens have better contrast so you don't need the backlight so much in lower light, but the backlight has obvious benefits.

#RetroComputing #RetroDev #16bit

Someone asked me some questions on the #Psion Series 3, so I thought I'd post my response here in case anyone else is interested. #LongRead

Emulator

You've got two options. The first is the original "emulators" written by Psion, S3AEMUL.EXE and S3CEMUL.EXE. They both run in DOS and emulate the 3a and 3c. But they're less of an emulator than a runtime environment for #EPOC16 (the OS). There's good and bad to this. You can run S3AEMUL and S3CEMUL straight in #DOSBox and it will talk to your host OS's filesystem (Windows, Linux, macOS, whatever). You need to map an M: drive in DOSBox for the internal storage, but once that's done you can copy files straight into that folder on your host OS and run them in the emulators. The downside is that it's not true hardware emulation. You won't get a good judge of the speed of a real device, and some syscalls aren't implemented so will fail or crash the #emulator. They're bundled with the SDK (see below).

The alternative is #MAME. This is the closest to proper hardware emulation you're going to find. You can either dump your own ROMs using a tool called #EDisAsm, or you can find them in the usual MAME ROM repos. The one thing that is notably missing is RS232 emulation from the later models, because we haven't been able to find any documentation on the silicon, but it's working fine with the 3a.

Toolchain

At the moment you have only one option - the Psion SIBO C SDK with the #TopSpeed C Compiler. You're going to need DOSBox (I personally prefer DOSBox Staging). It's all available on the Internet Archive in one easy download, including all the documentation you will need.

https://archive.org/details/psion-sibo-c-sdk

From there, you have a few libraries you can use. There CLIB, which is a pure ANSI C implementation, designed to easily port apps - don't use it, it's slow and you'll be missing a lot of features. Then there's PLIB, which is Psion's C dialect - very nice to use, and you can put together a C app pretty quickly. Finally, there's OLIB, which is Psion's proprietary OO C - it feels very clunky, but once you get over that it can be very powerful.

EPOC16 apps are restricted to a very pure version of the small memory model, but you can split code up into libraries known as DYLs.

In the past I've written code using VS Code, which can be made to play nicely with the SDK's header files. I've not got it working with NeoVim and clangd yet, but it should be possible with cmake.

The SDK comes with a debugger (SDBG.EXE), a DOS GUI app. If you run SDBG.EXE in DOSBox Staging, run the Psion3a MAME emulation, and enable RS232 over TCP on both, you can use SDBG to send apps to MAME. If you enable symbols, you can step through the code. It's rudimentary by modern standards, but it works pretty well.

I say "at the moment" because I'm slowly rewriting the tools in the SDK. I already have a new working version of #CTRAN, the preprocessor for Psion OO C, but I'm a long way from a compiler. There have been efforts to coax gcc into compiling for SIBO/EPOC16, but I think they have stalled for now.

If you want some examples of EPOC16 C and OO C code, take a look at these:
https://github.com/thelastpsion/edisasm
https://github.com/thelastpsion/pyramid
https://github.com/thelastpsion/nfsc
https://github.com/nickmat/Psion3-Wari
https://github.com/nickmat/Psion3-Vector

Device

The 3mx is the best choice. It's significantly faster than the earlier models (27.6 MHz vs 7.6 MHz), has a switchable backlight, the fastest RS232 and the best version of EPOC16. I "daily drive" one for journalling, adventure games, and a few other small tasks. After that I'd say the 3c (beware - they were covered in soft-touch rubber, so will need cleaning) and the 2MB 3a. The latter is the most common. Most 3c units came with a backlight, except for the early UK ones. The 3a doesn't. Arguably the non-backlit screens have better contrast so you don't need the backlight so much in lower light, but the backlight has obvious benefits.

#RetroComputing #RetroDev #16bit

Someone asked me some questions on the #Psion Series 3, so I thought I'd post my response here in case anyone else is interested. #LongRead

Emulator

You've got two options. The first is the original "emulators" written by Psion, S3AEMUL.EXE and S3CEMUL.EXE. They both run in DOS and emulate the 3a and 3c. But they're less of an emulator than a runtime environment for #EPOC16 (the OS). There's good and bad to this. You can run S3AEMUL and S3CEMUL straight in #DOSBox and it will talk to your host OS's filesystem (Windows, Linux, macOS, whatever). You need to map an M: drive in DOSBox for the internal storage, but once that's done you can copy files straight into that folder on your host OS and run them in the emulators. The downside is that it's not true hardware emulation. You won't get a good judge of the speed of a real device, and some syscalls aren't implemented so will fail or crash the #emulator. They're bundled with the SDK (see below).

The alternative is #MAME. This is the closest to proper hardware emulation you're going to find. You can either dump your own ROMs using a tool called #EDisAsm, or you can find them in the usual MAME ROM repos. The one thing that is notably missing is RS232 emulation from the later models, because we haven't been able to find any documentation on the silicon, but it's working fine with the 3a.

Toolchain

At the moment you have only one option - the Psion SIBO C SDK with the #TopSpeed C Compiler. You're going to need DOSBox (I personally prefer DOSBox Staging). It's all available on the Internet Archive in one easy download, including all the documentation you will need.

https://archive.org/details/psion-sibo-c-sdk

From there, you have a few libraries you can use. There CLIB, which is a pure ANSI C implementation, designed to easily port apps - don't use it, it's slow and you'll be missing a lot of features. Then there's PLIB, which is Psion's C dialect - very nice to use, and you can put together a C app pretty quickly. Finally, there's OLIB, which is Psion's proprietary OO C - it feels very clunky, but once you get over that it can be very powerful.

EPOC16 apps are restricted to a very pure version of the small memory model, but you can split code up into libraries known as DYLs.

In the past I've written code using VS Code, which can be made to play nicely with the SDK's header files. I've not got it working with NeoVim and clangd yet, but it should be possible with cmake.

The SDK comes with a debugger (SDBG.EXE), a DOS GUI app. If you run SDBG.EXE in DOSBox Staging, run the Psion3a MAME emulation, and enable RS232 over TCP on both, you can use SDBG to send apps to MAME. If you enable symbols, you can step through the code. It's rudimentary by modern standards, but it works pretty well.

I say "at the moment" because I'm slowly rewriting the tools in the SDK. I already have a new working version of #CTRAN, the preprocessor for Psion OO C, but I'm a long way from a compiler. There have been efforts to coax gcc into compiling for SIBO/EPOC16, but I think they have stalled for now.

If you want some examples of EPOC16 C and OO C code, take a look at these:
https://github.com/thelastpsion/edisasm
https://github.com/thelastpsion/pyramid
https://github.com/thelastpsion/nfsc
https://github.com/nickmat/Psion3-Wari
https://github.com/nickmat/Psion3-Vector

Device

The 3mx is the best choice. It's significantly faster than the earlier models (27.6 MHz vs 7.6 MHz), has a switchable backlight, the fastest RS232 and the best version of EPOC16. I "daily drive" one for journalling, adventure games, and a few other small tasks. After that I'd say the 3c (beware - they were covered in soft-touch rubber, so will need cleaning) and the 2MB 3a. The latter is the most common. Most 3c units came with a backlight, except for the early UK ones. The 3a doesn't. Arguably the non-backlit screens have better contrast so you don't need the backlight so much in lower light, but the backlight has obvious benefits.

#RetroComputing #RetroDev #16bit

Bentley Continental GT Speed #photography #autoworldbrussels #belgie #belgien #belgium #brussels #museum #auto #bruxelles #brüssel #car #cars #highlight #autoworld #historic #collection #bentley #continental #gt #speed #performance #luxury #wealthy #money #21 #wheels #topspeed (Flickr 20.12.2022) https://www.flickr.com/photos/7489441@N06/52576088081

Bentley Continental GT Speed #photography #autoworldbrussels #belgie #belgien #belgium #brussels #museum #auto #bruxelles #brüssel #car #cars #highlight #autoworld #historic #collection #bentley #continental #gt #speed #performance #luxury #wealthy #money #21 #wheels #topspeed (Flickr 20.12.2022) https://www.flickr.com/photos/7489441@N06/52576088081

Bentley Continental GT Speed #photography #autoworldbrussels #belgie #belgien #belgium #brussels #museum #auto #bruxelles #brüssel #car #cars #highlight #autoworld #historic #collection #bentley #continental #gt #speed #performance #luxury #wealthy #money #21 #wheels #topspeed (Flickr 20.12.2022) https://www.flickr.com/photos/7489441@N06/52576088081

Bentley Continental GT Speed #photography #autoworldbrussels #belgie #belgien #belgium #brussels #museum #auto #bruxelles #brüssel #car #cars #highlight #autoworld #historic #collection #bentley #continental #gt #speed #performance #luxury #wealthy #money #21 #wheels #topspeed (Flickr 20.12.2022) https://www.flickr.com/photos/7489441@N06/52576088081

Bentley Continental GT Speed #photography #autoworldbrussels #belgie #belgien #belgium #brussels #museum #auto #bruxelles #brüssel #car #cars #highlight #autoworld #historic #collection #bentley #continental #gt #speed #performance #luxury #wealthy #money #21 #wheels #topspeed (Flickr 20.12.2022) https://www.flickr.com/photos/7489441@N06/52576088081

REPOST (JAN 2024): My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion #TopSpeed #compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

This is an old blog post from the beginning of the year. If you've been following my journey in recreating #CTRAN, this was written a week before I decided to take the plunge.

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

(Yes, I did say in the article that I definitely wouldn't be writing a compiler. I did say that.)

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC #compilers #ObjectOriented

REPOST (JAN 2024): My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion #TopSpeed #compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

This is an old blog post from the beginning of the year. If you've been following my journey in recreating #CTRAN, this was written a week before I decided to take the plunge.

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

(Yes, I did say in the article that I definitely wouldn't be writing a compiler. I did say that.)

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC #compilers #ObjectOriented

REPOST (JAN 2024): My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion #TopSpeed #compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

This is an old blog post from the beginning of the year. If you've been following my journey in recreating #CTRAN, this was written a week before I decided to take the plunge.

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

(Yes, I did say in the article that I definitely wouldn't be writing a compiler. I did say that.)

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC #compilers #ObjectOriented

REPOST (JAN 2024): My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion #TopSpeed #compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

This is an old blog post from the beginning of the year. If you've been following my journey in recreating #CTRAN, this was written a week before I decided to take the plunge.

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

(Yes, I did say in the article that I definitely wouldn't be writing a compiler. I did say that.)

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC #compilers #ObjectOriented

REPOST (JAN 2024): My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion #TopSpeed #compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

This is an old blog post from the beginning of the year. If you've been following my journey in recreating #CTRAN, this was written a week before I decided to take the plunge.

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

(Yes, I did say in the article that I definitely wouldn't be writing a compiler. I did say that.)

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC #compilers #ObjectOriented

Here's something I wish would be open sourced.

The #TopSpeed C #compiler is an integral part of the #Psion SIBO C SDK.

Old timers might remember JPI as a group of developers who left #Borland in 1987, after Borland decided not to use the team's new compiler technology. They took their code with them, and it became the TopSpeed compiler.

From what I gather, the TopSpeed compiler IP is now owned by #SoftVelocity, the company who now also owns Clarion. I emailed them about 6 years ago, asking them if they would consider open sourcing the compiler code. I got no response, which I guess is to be expected.

I even found someone who had a copy of the source code (written in Modula-2), but they understandably wouldn't give it to me without the IP owner's approval.

This is the situation with so many bits of software (including the SIBO C SDK tools) from this time. We are lucky that copies of the applications still exist, otherwise the job of building C software for #EPOC16 would be significantly more difficult. But it is likely that the original source code, along with many other codebases, will disappear thanks to copyright laws that don't support digital preservation.

#retrocomputing #vintagecomputing #digipres

Here's something I wish would be open sourced.

The #TopSpeed C #compiler is an integral part of the #Psion SIBO C SDK.

Old timers might remember JPI as a group of developers who left #Borland in 1987, after Borland decided not to use the team's new compiler technology. They took their code with them, and it became the TopSpeed compiler.

From what I gather, the TopSpeed compiler IP is now owned by #SoftVelocity, the company who now also owns Clarion. I emailed them about 6 years ago, asking them if they would consider open sourcing the compiler code. I got no response, which I guess is to be expected.

I even found someone who had a copy of the source code (written in Modula-2), but they understandably wouldn't give it to me without the IP owner's approval.

This is the situation with so many bits of software (including the SIBO C SDK tools) from this time. We are lucky that copies of the applications still exist, otherwise the job of building C software for #EPOC16 would be significantly more difficult. But it is likely that the original source code, along with many other codebases, will disappear thanks to copyright laws that don't support digital preservation.

#retrocomputing #vintagecomputing #digipres

Here's something I wish would be open sourced.

The #TopSpeed C #compiler is an integral part of the #Psion SIBO C SDK.

Old timers might remember JPI as a group of developers who left #Borland in 1987, after Borland decided not to use the team's new compiler technology. They took their code with them, and it became the TopSpeed compiler.

From what I gather, the TopSpeed compiler IP is now owned by #SoftVelocity, the company who now also owns Clarion. I emailed them about 6 years ago, asking them if they would consider open sourcing the compiler code. I got no response, which I guess is to be expected.

I even found someone who had a copy of the source code (written in Modula-2), but they understandably wouldn't give it to me without the IP owner's approval.

This is the situation with so many bits of software (including the SIBO C SDK tools) from this time. We are lucky that copies of the applications still exist, otherwise the job of building C software for #EPOC16 would be significantly more difficult. But it is likely that the original source code, along with many other codebases, will disappear thanks to copyright laws that don't support digital preservation.

#retrocomputing #vintagecomputing #digipres

Here's something I wish would be open sourced.

The #TopSpeed C #compiler is an integral part of the #Psion SIBO C SDK.

Old timers might remember JPI as a group of developers who left #Borland in 1987, after Borland decided not to use the team's new compiler technology. They took their code with them, and it became the TopSpeed compiler.

From what I gather, the TopSpeed compiler IP is now owned by #SoftVelocity, the company who now also owns Clarion. I emailed them about 6 years ago, asking them if they would consider open sourcing the compiler code. I got no response, which I guess is to be expected.

I even found someone who had a copy of the source code (written in Modula-2), but they understandably wouldn't give it to me without the IP owner's approval.

This is the situation with so many bits of software (including the SIBO C SDK tools) from this time. We are lucky that copies of the applications still exist, otherwise the job of building C software for #EPOC16 would be significantly more difficult. But it is likely that the original source code, along with many other codebases, will disappear thanks to copyright laws that don't support digital preservation.

#retrocomputing #vintagecomputing #digipres

Here's something I wish would be open sourced.

The #TopSpeed C #compiler is an integral part of the #Psion SIBO C SDK.

Old timers might remember JPI as a group of developers who left #Borland in 1987, after Borland decided not to use the team's new compiler technology. They took their code with them, and it became the TopSpeed compiler.

From what I gather, the TopSpeed compiler IP is now owned by #SoftVelocity, the company who now also owns Clarion. I emailed them about 6 years ago, asking them if they would consider open sourcing the compiler code. I got no response, which I guess is to be expected.

I even found someone who had a copy of the source code (written in Modula-2), but they understandably wouldn't give it to me without the IP owner's approval.

This is the situation with so many bits of software (including the SIBO C SDK tools) from this time. We are lucky that copies of the applications still exist, otherwise the job of building C software for #EPOC16 would be significantly more difficult. But it is likely that the original source code, along with many other codebases, will disappear thanks to copyright laws that don't support digital preservation.

#retrocomputing #vintagecomputing #digipres