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

🎉Website-Relaunch für Elterntalk NRW 🔄💻
Dank der Migration von WordPress zu #KirbyCMS besticht das System jetzt mit maximaler #Sicherheit, #barrierefreier Nutzererfahrung und #TopSpeed.
⏩ Mehr über den Web-Relaunch: https://www.visionbites.de/blog/website-relaunch-fuer-elterntalk-nrw
#visionbites #kirbycms #webrelaunch #webdevelopment #uxdesign #barrierefreieswebdesign #webdev
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.
Source: TOP SPEED Sportster S 2025. Harley Davidson. #raw #topspeed by Mike on Tour. Motorradreisen, Abenteuer + Reviews. Please don’t forget to give the Video a “Like” on Youtube and subscribe to the channel! 🎟️🤠📸 https://www.instagram.com/m_2_k/ Willst du eine Reiseserie durch die Westalpen sehen? https://www.youtube.com/playlist?list=PLpCECkSxriCjmybiFDWnlb_9jOgy4QS2O #panamerica #review #motorcycle #panamericast Das gesamte Review findest du hier […]
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.
BYD’s YangWang U9 hits an impressive 243 mph, setting new standards in electric supercar performance. Speed, power, and innovation combined. ⚡️🏎️
https://evfuture.io/from-192-mph-to-243-mph-the-yangwang-u9s-leap-in-speed/
#ev #evs #electricvehicle #electricvehicles #byd #yangwang #u9 #yangwangu9 #topspeed #evfuture
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.
(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
<blockquote><strong>Me: </strong>I could do with a quick win to get me going again.<br><br> <strong>Also me: </strong>I shall learn a proprietary object oriented dialect of C, where the only way to learn it is to plough through 1150 pages of documentation.</blockquote> <p>Psion doesn't have a formal name for the object oriented version of C that it created for EPOC16. I've been calling it "Psion OO C", but the main library that it uses is called <strong>OLIB</strong>, which contains the root class. The others are:</p> <ul><li><strong>HWIM: </strong>The OO graphics library</li><li><strong>FORM: </strong>On-screen formatting </li><li><strong>XADD: </strong>Additional graphics library for 3a onwards (but not the Series 3 "classic")</li></ul> <p>To Psion's credit, their OO ecosystem is well documented in the SIBO C SDK across 5 books (hence the 1150 pages mentioned above). Each of the libraries has its own, dedicated book. There's also an "Object Oriented Programming Guide" which acts as an introduction to the whole ecosystem. I don't have the latest versions of all of these books - they seem to be lost to time. But I have all the 3 and 3a features documented, plus (I think) all of the 3c/Siena extensions. (3mx-era EPOC16 remains sadly undocumented.)</p> <p>What's nice about Psion's approach to OO is that they assume no prior