#plptools — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #plptools, aggregated by home.social.
-
One of the best things about working on #plptools is that I get to work with developers who have far more experience in commercial software development than I do. I'm learning all the time and feel really grateful for it.*
On the flipside, it's solidified my want to work on the new #Psion #SIBOSDK by myself. I don't want collaborators for that project right now. Helpful hints and guidance is very much welcome, but I want to grow with this project in my own way. And yes, that will mean the development of the SDK will be slower. This might seem selfish in the grand scheme of FOSS development, but I know is the right thing for me right now.
* To be clear, I'm not a useless third wheel on the project. I have my things I'm good at. And I have ✨opinions✨! But still, always learning!
-
One of the best things about working on #plptools is that I get to work with developers who have far more experience in commercial software development than I do. I'm learning all the time and feel really grateful for it.*
On the flipside, it's solidified my want to work on the new #Psion #SIBOSDK by myself. I don't want collaborators for that project right now. Helpful hints and guidance is very much welcome, but I want to grow with this project in my own way. And yes, that will mean the development of the SDK will be slower. This might seem selfish in the grand scheme of FOSS development, but I know is the right thing for me right now.
* To be clear, I'm not a useless third wheel on the project. I have my things I'm good at. And I have ✨opinions✨! But still, always learning!
-
One of the best things about working on #plptools is that I get to work with developers who have far more experience in commercial software development than I do. I'm learning all the time and feel really grateful for it.*
On the flipside, it's solidified my want to work on the new #Psion #SIBOSDK by myself. I don't want collaborators for that project right now. Helpful hints and guidance is very much welcome, but I want to grow with this project in my own way. And yes, that will mean the development of the SDK will be slower. This might seem selfish in the grand scheme of FOSS development, but I know is the right thing for me right now.
* To be clear, I'm not a useless third wheel on the project. I have my things I'm good at. And I have ✨opinions✨! But still, always learning!
-
One of the best things about working on #plptools is that I get to work with developers who have far more experience in commercial software development than I do. I'm learning all the time and feel really grateful for it.*
On the flipside, it's solidified my want to work on the new #Psion #SIBOSDK by myself. I don't want collaborators for that project right now. Helpful hints and guidance is very much welcome, but I want to grow with this project in my own way. And yes, that will mean the development of the SDK will be slower. This might seem selfish in the grand scheme of FOSS development, but I know is the right thing for me right now.
* To be clear, I'm not a useless third wheel on the project. I have my things I'm good at. And I have ✨opinions✨! But still, always learning!
-
One of the best things about working on #plptools is that I get to work with developers who have far more experience in commercial software development than I do. I'm learning all the time and feel really grateful for it.*
On the flipside, it's solidified my want to work on the new #Psion #SIBOSDK by myself. I don't want collaborators for that project right now. Helpful hints and guidance is very much welcome, but I want to grow with this project in my own way. And yes, that will mean the development of the SDK will be slower. This might seem selfish in the grand scheme of FOSS development, but I know is the right thing for me right now.
* To be clear, I'm not a useless third wheel on the project. I have my things I'm good at. And I have ✨opinions✨! But still, always learning!
-
#plptools, the #Psion comms suite for Linux and other *NIX-related OSes (see below), is currently going through an overhaul.
We're currently wading through almost 30 years of technical debt, improving thread safety and code readability. Slowly, we're reintroducing abandoned features and adding new ones.
My co-conspirators @jbmorley and @captfab have done the bulk of the work on this. I've been doing a lot of testing with physical hardware, as well as working on the ports and getting a better understanding of the current build system (autotools with gnulib) to get a clearer idea of whether it still works for the project today.
Primary supported OSes:
- Linux
- macOS
Secondary supported OSes (stable, but support will be slower):
- #FreeBSD 14.x
- #NetBSD
- #HaikuOS (With caveats - Haiku's USB serial is broken, but the the main Git branch of plptools has a workaround. Regular hardware RS232 works well.)
Coming soon:
- #OpenBSD (mostly works, but some stability issues in plpftp)
- FreeBSD 15.0 (won't compile, possibly an issue with gnulib)
In the distant future:
- Windows
The current main branch feels stable to us (more stable than the last release). If you want to give it a go, you can get it from here:
-
#plptools, the #Psion comms suite for Linux and other *NIX-related OSes (see below), is currently going through an overhaul.
We're currently wading through almost 30 years of technical debt, improving thread safety and code readability. Slowly, we're reintroducing abandoned features and adding new ones.
My co-conspirators @jbmorley and @captfab have done the bulk of the work on this. I've been doing a lot of testing with physical hardware, as well as working on the ports and getting a better understanding of the current build system (autotools with gnulib) to get a clearer idea of whether it still works for the project today.
Primary supported OSes:
- Linux
- macOS
Secondary supported OSes (stable, but support will be slower):
- #FreeBSD 14.x
- #NetBSD
- #HaikuOS (With caveats - Haiku's USB serial is broken, but the the main Git branch of plptools has a workaround. Regular hardware RS232 works well.)
Coming soon:
- #OpenBSD (mostly works, but some stability issues in plpftp)
- FreeBSD 15.0 (won't compile, possibly an issue with gnulib)
In the distant future:
- Windows
The current main branch feels stable to us (more stable than the last release). If you want to give it a go, you can get it from here:
-
#plptools, the #Psion comms suite for Linux and other *NIX-related OSes (see below), is currently going through an overhaul.
We're currently wading through almost 30 years of technical debt, improving thread safety and code readability. Slowly, we're reintroducing abandoned features and adding new ones.
My co-conspirators @jbmorley and @captfab have done the bulk of the work on this. I've been doing a lot of testing with physical hardware, as well as working on the ports and getting a better understanding of the current build system (autotools with gnulib) to get a clearer idea of whether it still works for the project today.
Primary supported OSes:
- Linux
- macOS
Secondary supported OSes (stable, but support will be slower):
- #FreeBSD 14.x
- #NetBSD
- #HaikuOS (With caveats - Haiku's USB serial is broken, but the the main Git branch of plptools has a workaround. Regular hardware RS232 works well.)
Coming soon:
- #OpenBSD (mostly works, but some stability issues in plpftp)
- FreeBSD 15.0 (won't compile, possibly an issue with gnulib)
In the distant future:
- Windows
The current main branch feels stable to us (more stable than the last release). If you want to give it a go, you can get it from here:
-
#plptools, the #Psion comms suite for Linux and other *NIX-related OSes (see below), is currently going through an overhaul.
We're currently wading through almost 30 years of technical debt, improving thread safety and code readability. Slowly, we're reintroducing abandoned features and adding new ones.
My co-conspirators @jbmorley and @captfab have done the bulk of the work on this. I've been doing a lot of testing with physical hardware, as well as working on the ports and getting a better understanding of the current build system (autotools with gnulib) to get a clearer idea of whether it still works for the project today.
Primary supported OSes:
- Linux
- macOS
Secondary supported OSes (stable, but support will be slower):
- #FreeBSD 14.x
- #NetBSD
- #HaikuOS (With caveats - Haiku's USB serial is broken, but the the main Git branch of plptools has a workaround. Regular hardware RS232 works well.)
Coming soon:
- #OpenBSD (mostly works, but some stability issues in plpftp)
- FreeBSD 15.0 (won't compile, possibly an issue with gnulib)
In the distant future:
- Windows
The current main branch feels stable to us (more stable than the last release). If you want to give it a go, you can get it from here:
-
#plptools, the #Psion comms suite for Linux and other *NIX-related OSes (see below), is currently going through an overhaul.
We're currently wading through almost 30 years of technical debt, improving thread safety and code readability. Slowly, we're reintroducing abandoned features and adding new ones.
My co-conspirators @jbmorley and @captfab have done the bulk of the work on this. I've been doing a lot of testing with physical hardware, as well as working on the ports and getting a better understanding of the current build system (autotools with gnulib) to get a clearer idea of whether it still works for the project today.
Primary supported OSes:
- Linux
- macOS
Secondary supported OSes (stable, but support will be slower):
- #FreeBSD 14.x
- #NetBSD
- #HaikuOS (With caveats - Haiku's USB serial is broken, but the the main Git branch of plptools has a workaround. Regular hardware RS232 works well.)
Coming soon:
- #OpenBSD (mostly works, but some stability issues in plpftp)
- FreeBSD 15.0 (won't compile, possibly an issue with gnulib)
In the distant future:
- Windows
The current main branch feels stable to us (more stable than the last release). If you want to give it a go, you can get it from here:
-
I currently have #Obsidian installed via #ArchLinux's repos. I've just noticed that it depends on FUSE 2†, and I'm not sure why.
I have read that the AppImage version needs it, but I thought that's more because of AppImage than Obsidian.
So, questions:
- Any idea why Obsidian needs FUSE at all? Is it just Arch, or universal?
- How to people feel about the #Flatpak version of Obsidian?
- If you're running Obsidian on Arch, are you using the one from the repos or the Flatpak version?
† I noticed this because we're currently trying to migrate #plptools from FUSE 2 to FUSE 3, and I was wondering what other things on my system depended on FUSE 2.
-
I currently have #Obsidian installed via #ArchLinux's repos. I've just noticed that it depends on FUSE 2†, and I'm not sure why.
I have read that the AppImage version needs it, but I thought that's more because of AppImage than Obsidian.
So, questions:
- Any idea why Obsidian needs FUSE at all? Is it just Arch, or universal?
- How to people feel about the #Flatpak version of Obsidian?
- If you're running Obsidian on Arch, are you using the one from the repos or the Flatpak version?
† I noticed this because we're currently trying to migrate #plptools from FUSE 2 to FUSE 3, and I was wondering what other things on my system depended on FUSE 2.
-
I currently have #Obsidian installed via #ArchLinux's repos. I've just noticed that it depends on FUSE 2†, and I'm not sure why.
I have read that the AppImage version needs it, but I thought that's more because of AppImage than Obsidian.
So, questions:
- Any idea why Obsidian needs FUSE at all? Is it just Arch, or universal?
- How to people feel about the #Flatpak version of Obsidian?
- If you're running Obsidian on Arch, are you using the one from the repos or the Flatpak version?
† I noticed this because we're currently trying to migrate #plptools from FUSE 2 to FUSE 3, and I was wondering what other things on my system depended on FUSE 2.
-
I currently have #Obsidian installed via #ArchLinux's repos. I've just noticed that it depends on FUSE 2†, and I'm not sure why.
I have read that the AppImage version needs it, but I thought that's more because of AppImage than Obsidian.
So, questions:
- Any idea why Obsidian needs FUSE at all? Is it just Arch, or universal?
- How to people feel about the #Flatpak version of Obsidian?
- If you're running Obsidian on Arch, are you using the one from the repos or the Flatpak version?
† I noticed this because we're currently trying to migrate #plptools from FUSE 2 to FUSE 3, and I was wondering what other things on my system depended on FUSE 2.
-
I currently have #Obsidian installed via #ArchLinux's repos. I've just noticed that it depends on FUSE 2†, and I'm not sure why.
I have read that the AppImage version needs it, but I thought that's more because of AppImage than Obsidian.
So, questions:
- Any idea why Obsidian needs FUSE at all? Is it just Arch, or universal?
- How to people feel about the #Flatpak version of Obsidian?
- If you're running Obsidian on Arch, are you using the one from the repos or the Flatpak version?
† I noticed this because we're currently trying to migrate #plptools from FUSE 2 to FUSE 3, and I was wondering what other things on my system depended on FUSE 2.
-
There's one feature I'd love emu2 to have: Serial support.
Then I'd be able to run MCLINK in a Linux or Haiku terminal.
Yes, I know I'm one of the #plptools maintainers. But plptools doesn't yet have all the features of MCLINK and PsiWin.
For now, DOSBox does the job. But I've seen the future.
-
There's one feature I'd love emu2 to have: Serial support.
Then I'd be able to run MCLINK in a Linux or Haiku terminal.
Yes, I know I'm one of the #plptools maintainers. But plptools doesn't yet have all the features of MCLINK and PsiWin.
For now, DOSBox does the job. But I've seen the future.
-
There's one feature I'd love emu2 to have: Serial support.
Then I'd be able to run MCLINK in a Linux or Haiku terminal.
Yes, I know I'm one of the #plptools maintainers. But plptools doesn't yet have all the features of MCLINK and PsiWin.
For now, DOSBox does the job. But I've seen the future.
-
There's one feature I'd love emu2 to have: Serial support.
Then I'd be able to run MCLINK in a Linux or Haiku terminal.
Yes, I know I'm one of the #plptools maintainers. But plptools doesn't yet have all the features of MCLINK and PsiWin.
For now, DOSBox does the job. But I've seen the future.
-
There's one feature I'd love emu2 to have: Serial support.
Then I'd be able to run MCLINK in a Linux or Haiku terminal.
Yes, I know I'm one of the #plptools maintainers. But plptools doesn't yet have all the features of MCLINK and PsiWin.
For now, DOSBox does the job. But I've seen the future.
-
EDIT: Solved! Thank you to @penguin42 for the guidance. I now have an aarch64 VM running Debian and "host-only" networking so I can SSH in easily. My next challenge will be to do the same with Arch or Alpine, and get serial over TCP or a UNIX socket working.
#HIVEMIND: Does anyone have any tips on running ARM VMs on AMD64? Preferably both 32 and 64-bit.
I've got a few apps (#plptools, the new #SIBOSDK) that I'd like to be able to compile and test while on-the-go.
I'm guessing something like #qemu would do the job, but I don't know where to begin.
-
EDIT: Solved! Thank you to @penguin42 for the guidance. I now have an aarch64 VM running Debian and "host-only" networking so I can SSH in easily. My next challenge will be to do the same with Arch or Alpine, and get serial over TCP or a UNIX socket working.
#HIVEMIND: Does anyone have any tips on running ARM VMs on AMD64? Preferably both 32 and 64-bit.
I've got a few apps (#plptools, the new #SIBOSDK) that I'd like to be able to compile and test while on-the-go.
I'm guessing something like #qemu would do the job, but I don't know where to begin.
-
EDIT: Solved! Thank you to @penguin42 for the guidance. I now have an aarch64 VM running Debian and "host-only" networking so I can SSH in easily. My next challenge will be to do the same with Arch or Alpine, and get serial over TCP or a UNIX socket working.
#HIVEMIND: Does anyone have any tips on running ARM VMs on AMD64? Preferably both 32 and 64-bit.
I've got a few apps (#plptools, the new #SIBOSDK) that I'd like to be able to compile and test while on-the-go.
I'm guessing something like #qemu would do the job, but I don't know where to begin.
-
EDIT: Solved! Thank you to @penguin42 for the guidance. I now have an aarch64 VM running Debian and "host-only" networking so I can SSH in easily. My next challenge will be to do the same with Arch or Alpine, and get serial over TCP or a UNIX socket working.
#HIVEMIND: Does anyone have any tips on running ARM VMs on AMD64? Preferably both 32 and 64-bit.
I've got a few apps (#plptools, the new #SIBOSDK) that I'd like to be able to compile and test while on-the-go.
I'm guessing something like #qemu would do the job, but I don't know where to begin.
-
EDIT: Solved! Thank you to @penguin42 for the guidance. I now have an aarch64 VM running Debian and "host-only" networking so I can SSH in easily. My next challenge will be to do the same with Arch or Alpine, and get serial over TCP or a UNIX socket working.
#HIVEMIND: Does anyone have any tips on running ARM VMs on AMD64? Preferably both 32 and 64-bit.
I've got a few apps (#plptools, the new #SIBOSDK) that I'd like to be able to compile and test while on-the-go.
I'm guessing something like #qemu would do the job, but I don't know where to begin.
-
Current main projects:
- #ecobj: Another piece of the #Psion SIBO SDK rewrite puzzle.
ECOBJ.EXEtakes an Intel OMF file (.OBJ) for a class and moves the class descriptor data into the code segment. I think I might be able to get this working by the end of the year. - Get my website running #GoHugo (this is almost done!).
- #CTRAN: Still haven't started writing unit tests. Also, complete a full write-up of what it took to get the thing working.
- Research into compilers: I'm nowhere near ready to start yet, but I'm learning as much as I can.
Upcoming projects:
- #siboimg: Rewrite in Pascal, and add the ability to create and modify FEFS images.
- #plptools: I'd like to see two-way transfer working for EPOC16 -- I'm sure I'll need the help of the rest of the maintainers to get this working. I can't do much with the #HaikuOS port until the USB serial drivers are "fixed" (hardware flow control added) -- I don't think I have the skills for this, so it'll have to wait until some kind soul has the time to work on it.
- #PsiDrive: Add a ~17V boost converter to allow writing to Flash SSDs.
- NAS/home server: Rebuild or replacement of DEATH, my Microserver gen8. It's been over 18 months since DEATH's RAID died. It's lead me to thinking that maybe I don't need the sort of server I thought I need. TBD.
Maybe next year, maybe not:
- New Psion SSD with RP2350: I doubt I'll get anything made, but I'd like to experiment to see what can be done with the protocol.
- Rewrite the rest of the SIBO C SDK tools.
- Compiler: Recreation of the JPI/Clarion TopSpeed C compiler, targeting the SIBO/EPOC16 platform (8086 and V30). I was hoping to get going with this around July this year, but it just didn't happen. This is my Everest. I know I'm not ready yet. I need to train for it.
- Vine: New word processor for EPOC16. Trying to start this project in 2023 lead me to rewriting the SDK, so we're quite some way away from getting this done.
- Research into Objective-C: Not Foundation, just the syntax. For compiler shenanigans.
I've really struggled to get going with projects this year. That's fine, these things happen. But I'd like to find better ways to cope next year so that I can make a little more progress.
- #ecobj: Another piece of the #Psion SIBO SDK rewrite puzzle.
-
Current main projects:
- #ecobj: Another piece of the #Psion SIBO SDK rewrite puzzle.
ECOBJ.EXEtakes an Intel OMF file (.OBJ) for a class and moves the class descriptor data into the code segment. I think I might be able to get this working by the end of the year. - Get my website running #GoHugo (this is almost done!).
- #CTRAN: Still haven't started writing unit tests. Also, complete a full write-up of what it took to get the thing working.
- Research into compilers: I'm nowhere near ready to start yet, but I'm learning as much as I can.
Upcoming projects:
- #siboimg: Rewrite in Pascal, and add the ability to create and modify FEFS images.
- #plptools: I'd like to see two-way transfer working for EPOC16 -- I'm sure I'll need the help of the rest of the maintainers to get this working. I can't do much with the #HaikuOS port until the USB serial drivers are "fixed" (hardware flow control added) -- I don't think I have the skills for this, so it'll have to wait until some kind soul has the time to work on it.
- #PsiDrive: Add a ~17V boost converter to allow writing to Flash SSDs.
- NAS/home server: Rebuild or replacement of DEATH, my Microserver gen8. It's been over 18 months since DEATH's RAID died. It's lead me to thinking that maybe I don't need the sort of server I thought I need. TBD.
Maybe next year, maybe not:
- New Psion SSD with RP2350: I doubt I'll get anything made, but I'd like to experiment to see what can be done with the protocol.
- Rewrite the rest of the SIBO C SDK tools.
- Compiler: Recreation of the JPI/Clarion TopSpeed C compiler, targeting the SIBO/EPOC16 platform (8086 and V30). I was hoping to get going with this around July this year, but it just didn't happen. This is my Everest. I know I'm not ready yet. I need to train for it.
- Vine: New word processor for EPOC16. Trying to start this project in 2023 lead me to rewriting the SDK, so we're quite some way away from getting this done.
- Research into Objective-C: Not Foundation, just the syntax. For compiler shenanigans.
I've really struggled to get going with projects this year. That's fine, these things happen. But I'd like to find better ways to cope next year so that I can make a little more progress.
- #ecobj: Another piece of the #Psion SIBO SDK rewrite puzzle.
-
Current main projects:
- #ecobj: Another piece of the #Psion SIBO SDK rewrite puzzle.
ECOBJ.EXEtakes an Intel OMF file (.OBJ) for a class and moves the class descriptor data into the code segment. I think I might be able to get this working by the end of the year. - Get my website running #GoHugo (this is almost done!).
- #CTRAN: Still haven't started writing unit tests. Also, complete a full write-up of what it took to get the thing working.
- Research into compilers: I'm nowhere near ready to start yet, but I'm learning as much as I can.
Upcoming projects:
- #siboimg: Rewrite in Pascal, and add the ability to create and modify FEFS images.
- #plptools: I'd like to see two-way transfer working for EPOC16 -- I'm sure I'll need the help of the rest of the maintainers to get this working. I can't do much with the #HaikuOS port until the USB serial drivers are "fixed" (hardware flow control added) -- I don't think I have the skills for this, so it'll have to wait until some kind soul has the time to work on it.
- #PsiDrive: Add a ~17V boost converter to allow writing to Flash SSDs.
- NAS/home server: Rebuild or replacement of DEATH, my Microserver gen8. It's been over 18 months since DEATH's RAID died. It's lead me to thinking that maybe I don't need the sort of server I thought I need. TBD.
Maybe next year, maybe not:
- New Psion SSD with RP2350: I doubt I'll get anything made, but I'd like to experiment to see what can be done with the protocol.
- Rewrite the rest of the SIBO C SDK tools.
- Compiler: Recreation of the JPI/Clarion TopSpeed C compiler, targeting the SIBO/EPOC16 platform (8086 and V30). I was hoping to get going with this around July this year, but it just didn't happen. This is my Everest. I know I'm not ready yet. I need to train for it.
- Vine: New word processor for EPOC16. Trying to start this project in 2023 lead me to rewriting the SDK, so we're quite some way away from getting this done.
- Research into Objective-C: Not Foundation, just the syntax. For compiler shenanigans.
I've really struggled to get going with projects this year. That's fine, these things happen. But I'd like to find better ways to cope next year so that I can make a little more progress.
- #ecobj: Another piece of the #Psion SIBO SDK rewrite puzzle.
-
Current main projects:
- #ecobj: Another piece of the #Psion SIBO SDK rewrite puzzle.
ECOBJ.EXEtakes an Intel OMF file (.OBJ) for a class and moves the class descriptor data into the code segment. I think I might be able to get this working by the end of the year. - Get my website running #GoHugo (this is almost done!).
- #CTRAN: Still haven't started writing unit tests. Also, complete a full write-up of what it took to get the thing working.
- Research into compilers: I'm nowhere near ready to start yet, but I'm learning as much as I can.
Upcoming projects:
- #siboimg: Rewrite in Pascal, and add the ability to create and modify FEFS images.
- #plptools: I'd like to see two-way transfer working for EPOC16 -- I'm sure I'll need the help of the rest of the maintainers to get this working. I can't do much with the #HaikuOS port until the USB serial drivers are "fixed" (hardware flow control added) -- I don't think I have the skills for this, so it'll have to wait until some kind soul has the time to work on it.
- #PsiDrive: Add a ~17V boost converter to allow writing to Flash SSDs.
- NAS/home server: Rebuild or replacement of DEATH, my Microserver gen8. It's been over 18 months since DEATH's RAID died. It's lead me to thinking that maybe I don't need the sort of server I thought I need. TBD.
Maybe next year, maybe not:
- New Psion SSD with RP2350: I doubt I'll get anything made, but I'd like to experiment to see what can be done with the protocol.
- Rewrite the rest of the SIBO C SDK tools.
- Compiler: Recreation of the JPI/Clarion TopSpeed C compiler, targeting the SIBO/EPOC16 platform (8086 and V30). I was hoping to get going with this around July this year, but it just didn't happen. This is my Everest. I know I'm not ready yet. I need to train for it.
- Vine: New word processor for EPOC16. Trying to start this project in 2023 lead me to rewriting the SDK, so we're quite some way away from getting this done.
- Research into Objective-C: Not Foundation, just the syntax. For compiler shenanigans.
I've really struggled to get going with projects this year. That's fine, these things happen. But I'd like to find better ways to cope next year so that I can make a little more progress.
- #ecobj: Another piece of the #Psion SIBO SDK rewrite puzzle.
-
Current main projects:
- #ecobj: Another piece of the #Psion SIBO SDK rewrite puzzle.
ECOBJ.EXEtakes an Intel OMF file (.OBJ) for a class and moves the class descriptor data into the code segment. I think I might be able to get this working by the end of the year. - Get my website running #GoHugo (this is almost done!).
- #CTRAN: Still haven't started writing unit tests. Also, complete a full write-up of what it took to get the thing working.
- Research into compilers: I'm nowhere near ready to start yet, but I'm learning as much as I can.
Upcoming projects:
- #siboimg: Rewrite in Pascal, and add the ability to create and modify FEFS images.
- #plptools: I'd like to see two-way transfer working for EPOC16 -- I'm sure I'll need the help of the rest of the maintainers to get this working. I can't do much with the #HaikuOS port until the USB serial drivers are "fixed" (hardware flow control added) -- I don't think I have the skills for this, so it'll have to wait until some kind soul has the time to work on it.
- #PsiDrive: Add a ~17V boost converter to allow writing to Flash SSDs.
- NAS/home server: Rebuild or replacement of DEATH, my Microserver gen8. It's been over 18 months since DEATH's RAID died. It's lead me to thinking that maybe I don't need the sort of server I thought I need. TBD.
Maybe next year, maybe not:
- New Psion SSD with RP2350: I doubt I'll get anything made, but I'd like to experiment to see what can be done with the protocol.
- Rewrite the rest of the SIBO C SDK tools.
- Compiler: Recreation of the JPI/Clarion TopSpeed C compiler, targeting the SIBO/EPOC16 platform (8086 and V30). I was hoping to get going with this around July this year, but it just didn't happen. This is my Everest. I know I'm not ready yet. I need to train for it.
- Vine: New word processor for EPOC16. Trying to start this project in 2023 lead me to rewriting the SDK, so we're quite some way away from getting this done.
- Research into Objective-C: Not Foundation, just the syntax. For compiler shenanigans.
I've really struggled to get going with projects this year. That's fine, these things happen. But I'd like to find better ways to cope next year so that I can make a little more progress.
- #ecobj: Another piece of the #Psion SIBO SDK rewrite puzzle.
-
#plptools update!
Ports
The #HaikuOS port works with on-board serial ports. However, USB RS232 adapters do not work. This is because of an issue with the
usb_serialdriver in Haiku. DTR and RTS can't be set reliably, and RTS and CTS can't be detected.There is still one small issue with the Haiku port. A GNU regex test in
./configureis segfaulting. This can be bypassed, but we want it fixed. That involves delving into autotools, so we'll see how I get on!Both the #FreeBSD and #NetBSD ports are working! With a combination of brute force and the help of a few FediFolk, these now compile. (I did think that the NetBSD port was severely broken, but I was just using the wrong serial device. Sigh.)
MacOS is still stable and happy.
We're not planning on adding any more ports unless people really beg!
Bugs
Just a handful of small fixes, like
plpftpnot segfaulting any more when you press CTRL-C. I might have introduced a new bug into plpftp regarding Daylight Savings... I'll try to fix that soon. In my defence, Psion's implementation of DST is, to put it politely, rudimentary. -
#plptools update!
Ports
The #HaikuOS port works with on-board serial ports. However, USB RS232 adapters do not work. This is because of an issue with the
usb_serialdriver in Haiku. DTR and RTS can't be set reliably, and RTS and CTS can't be detected.There is still one small issue with the Haiku port. A GNU regex test in
./configureis segfaulting. This can be bypassed, but we want it fixed. That involves delving into autotools, so we'll see how I get on!Both the #FreeBSD and #NetBSD ports are working! With a combination of brute force and the help of a few FediFolk, these now compile. (I did think that the NetBSD port was severely broken, but I was just using the wrong serial device. Sigh.)
MacOS is still stable and happy.
We're not planning on adding any more ports unless people really beg!
Bugs
Just a handful of small fixes, like
plpftpnot segfaulting any more when you press CTRL-C. I might have introduced a new bug into plpftp regarding Daylight Savings... I'll try to fix that soon. In my defence, Psion's implementation of DST is, to put it politely, rudimentary. -
#plptools update!
Ports
The #HaikuOS port works with on-board serial ports. However, USB RS232 adapters do not work. This is because of an issue with the
usb_serialdriver in Haiku. DTR and RTS can't be set reliably, and RTS and CTS can't be detected.There is still one small issue with the Haiku port. A GNU regex test in
./configureis segfaulting. This can be bypassed, but we want it fixed. That involves delving into autotools, so we'll see how I get on!Both the #FreeBSD and #NetBSD ports are working! With a combination of brute force and the help of a few FediFolk, these now compile. (I did think that the NetBSD port was severely broken, but I was just using the wrong serial device. Sigh.)
MacOS is still stable and happy.
We're not planning on adding any more ports unless people really beg!
Bugs
Just a handful of small fixes, like
plpftpnot segfaulting any more when you press CTRL-C. I might have introduced a new bug into plpftp regarding Daylight Savings... I'll try to fix that soon. In my defence, Psion's implementation of DST is, to put it politely, rudimentary. -
#plptools update!
Ports
The #HaikuOS port works with on-board serial ports. However, USB RS232 adapters do not work. This is because of an issue with the
usb_serialdriver in Haiku. DTR and RTS can't be set reliably, and RTS and CTS can't be detected.There is still one small issue with the Haiku port. A GNU regex test in
./configureis segfaulting. This can be bypassed, but we want it fixed. That involves delving into autotools, so we'll see how I get on!Both the #FreeBSD and #NetBSD ports are working! With a combination of brute force and the help of a few FediFolk, these now compile. (I did think that the NetBSD port was severely broken, but I was just using the wrong serial device. Sigh.)
MacOS is still stable and happy.
We're not planning on adding any more ports unless people really beg!
Bugs
Just a handful of small fixes, like
plpftpnot segfaulting any more when you press CTRL-C. I might have introduced a new bug into plpftp regarding Daylight Savings... I'll try to fix that soon. In my defence, Psion's implementation of DST is, to put it politely, rudimentary. -
#plptools update!
Ports
The #HaikuOS port works with on-board serial ports. However, USB RS232 adapters do not work. This is because of an issue with the
usb_serialdriver in Haiku. DTR and RTS can't be set reliably, and RTS and CTS can't be detected.There is still one small issue with the Haiku port. A GNU regex test in
./configureis segfaulting. This can be bypassed, but we want it fixed. That involves delving into autotools, so we'll see how I get on!Both the #FreeBSD and #NetBSD ports are working! With a combination of brute force and the help of a few FediFolk, these now compile. (I did think that the NetBSD port was severely broken, but I was just using the wrong serial device. Sigh.)
MacOS is still stable and happy.
We're not planning on adding any more ports unless people really beg!
Bugs
Just a handful of small fixes, like
plpftpnot segfaulting any more when you press CTRL-C. I might have introduced a new bug into plpftp regarding Daylight Savings... I'll try to fix that soon. In my defence, Psion's implementation of DST is, to put it politely, rudimentary. -
-
-
-
-
-
#NetBSD people! I need some help. (EDIT: Answer found! Thank you, @kaveman !)
I'm trying to update the port of an old piece of software (#plptools), but I'm having issues with linking it to readline.
It's detecting libedit first, even though FSF readline is installed. The following does nothing:
CPPFLAGS="-I/usr/pkg/include/readline/" LDFLAGS="-L/usr/pkg/lib/" ./configureAdding
LIBS="-lreadline"throws an error early on in./configure, saying that it can't findlibreadline.so.8.Do you have any advice at all?
The GitHub issue is here: https://github.com/plptools/plptools/issues/22#issuecomment-2954149613
-
#NetBSD people! I need some help. (EDIT: Answer found! Thank you, @kaveman !)
I'm trying to update the port of an old piece of software (#plptools), but I'm having issues with linking it to readline.
It's detecting libedit first, even though FSF readline is installed. The following does nothing:
CPPFLAGS="-I/usr/pkg/include/readline/" LDFLAGS="-L/usr/pkg/lib/" ./configureAdding
LIBS="-lreadline"throws an error early on in./configure, saying that it can't findlibreadline.so.8.Do you have any advice at all?
The GitHub issue is here: https://github.com/plptools/plptools/issues/22#issuecomment-2954149613
-
#NetBSD people! I need some help. (EDIT: Answer found! Thank you, @kaveman !)
I'm trying to update the port of an old piece of software (#plptools), but I'm having issues with linking it to readline.
It's detecting libedit first, even though FSF readline is installed. The following does nothing:
CPPFLAGS="-I/usr/pkg/include/readline/" LDFLAGS="-L/usr/pkg/lib/" ./configureAdding
LIBS="-lreadline"throws an error early on in./configure, saying that it can't findlibreadline.so.8.Do you have any advice at all?
The GitHub issue is here: https://github.com/plptools/plptools/issues/22#issuecomment-2954149613
-
#NetBSD people! I need some help. (EDIT: Answer found! Thank you, @kaveman !)
I'm trying to update the port of an old piece of software (#plptools), but I'm having issues with linking it to readline.
It's detecting libedit first, even though FSF readline is installed. The following does nothing:
CPPFLAGS="-I/usr/pkg/include/readline/" LDFLAGS="-L/usr/pkg/lib/" ./configureAdding
LIBS="-lreadline"throws an error early on in./configure, saying that it can't findlibreadline.so.8.Do you have any advice at all?
The GitHub issue is here: https://github.com/plptools/plptools/issues/22#issuecomment-2954149613
-
#NetBSD people! I need some help. (EDIT: Answer found! Thank you, @kaveman !)
I'm trying to update the port of an old piece of software (#plptools), but I'm having issues with linking it to readline.
It's detecting libedit first, even though FSF readline is installed. The following does nothing:
CPPFLAGS="-I/usr/pkg/include/readline/" LDFLAGS="-L/usr/pkg/lib/" ./configureAdding
LIBS="-lreadline"throws an error early on in./configure, saying that it can't findlibreadline.so.8.Do you have any advice at all?
The GitHub issue is here: https://github.com/plptools/plptools/issues/22#issuecomment-2954149613
-
#HaikuOS users with USB RS232 adapters! I need some help.
I'm trying to get an old piece of software working with Haiku that uses serial comms (see #plptools). I'm having some issues with DTR/DSR/RTS/CTS checking and setting, but it would be great if someone else can check my findings.
See this link for more information on my tests and results: https://discuss.haiku-os.org/t/porting-plptools-to-haiku/16849/7
Are you able to replicate what I'm seeing?
-
#HaikuOS users with USB RS232 adapters! I need some help.
I'm trying to get an old piece of software working with Haiku that uses serial comms (see #plptools). I'm having some issues with DTR/DSR/RTS/CTS checking and setting, but it would be great if someone else can check my findings.
See this link for more information on my tests and results: https://discuss.haiku-os.org/t/porting-plptools-to-haiku/16849/7
Are you able to replicate what I'm seeing?
-
#HaikuOS users with USB RS232 adapters! I need some help.
I'm trying to get an old piece of software working with Haiku that uses serial comms (see #plptools). I'm having some issues with DTR/DSR/RTS/CTS checking and setting, but it would be great if someone else can check my findings.
See this link for more information on my tests and results: https://discuss.haiku-os.org/t/porting-plptools-to-haiku/16849/7
Are you able to replicate what I'm seeing?
-
#HaikuOS users with USB RS232 adapters! I need some help.
I'm trying to get an old piece of software working with Haiku that uses serial comms (see #plptools). I'm having some issues with DTR/DSR/RTS/CTS checking and setting, but it would be great if someone else can check my findings.
See this link for more information on my tests and results: https://discuss.haiku-os.org/t/porting-plptools-to-haiku/16849/7
Are you able to replicate what I'm seeing?
-
#HaikuOS users with USB RS232 adapters! I need some help.
I'm trying to get an old piece of software working with Haiku that uses serial comms (see #plptools). I'm having some issues with DTR/DSR/RTS/CTS checking and setting, but it would be great if someone else can check my findings.
See this link for more information on my tests and results: https://discuss.haiku-os.org/t/porting-plptools-to-haiku/16849/7
Are you able to replicate what I'm seeing?
-
Current main projects:
- #plptools: Resurrecting old ports (#FreeBSD, #NetBSD) and working on a new port to #HaikuOS. It's an opportunity to get more familiar with the code and maybe find bugs along the way.
Upcoming projects:
- #CTRAN: Still haven't started writing unit tests. Also, complete a full write-up of what it took to get the thing working.
- Get my website running #GoHugo.
- Rebuild of DEATH, my Microserver gen8, probably with #FreeBSD. (Yes, it's been over a year since DEATH's RAID died.)
- Pick another SIBO SDK tool to rewrite. (Probably EMAKE or RCOMP.)
- Add a 17V boost converter to #PsiDrive.
- Make #fefstool create FEFS images. (I'm half-tempted to rewrite fefstool in Pascal to make it easier for me to finish.)
You'll notice that some of these projects have been sitting for a while. I've struggled to get going with things this year. I'm hoping that working though plptools will give me some mental energy to get going with other things.
-
Current main projects:
- #plptools: Resurrecting old ports (#FreeBSD, #NetBSD) and working on a new port to #HaikuOS. It's an opportunity to get more familiar with the code and maybe find bugs along the way.
Upcoming projects:
- #CTRAN: Still haven't started writing unit tests. Also, complete a full write-up of what it took to get the thing working.
- Get my website running #GoHugo.
- Rebuild of DEATH, my Microserver gen8, probably with #FreeBSD. (Yes, it's been over a year since DEATH's RAID died.)
- Pick another SIBO SDK tool to rewrite. (Probably EMAKE or RCOMP.)
- Add a 17V boost converter to #PsiDrive.
- Make #fefstool create FEFS images. (I'm half-tempted to rewrite fefstool in Pascal to make it easier for me to finish.)
You'll notice that some of these projects have been sitting for a while. I've struggled to get going with things this year. I'm hoping that working though plptools will give me some mental energy to get going with other things.
-
Current main projects:
- #plptools: Resurrecting old ports (#FreeBSD, #NetBSD) and working on a new port to #HaikuOS. It's an opportunity to get more familiar with the code and maybe find bugs along the way.
Upcoming projects:
- #CTRAN: Still haven't started writing unit tests. Also, complete a full write-up of what it took to get the thing working.
- Get my website running #GoHugo.
- Rebuild of DEATH, my Microserver gen8, probably with #FreeBSD. (Yes, it's been over a year since DEATH's RAID died.)
- Pick another SIBO SDK tool to rewrite. (Probably EMAKE or RCOMP.)
- Add a 17V boost converter to #PsiDrive.
- Make #fefstool create FEFS images. (I'm half-tempted to rewrite fefstool in Pascal to make it easier for me to finish.)
You'll notice that some of these projects have been sitting for a while. I've struggled to get going with things this year. I'm hoping that working though plptools will give me some mental energy to get going with other things.
-
Current main projects:
- #plptools: Resurrecting old ports (#FreeBSD, #NetBSD) and working on a new port to #HaikuOS. It's an opportunity to get more familiar with the code and maybe find bugs along the way.
Upcoming projects:
- #CTRAN: Still haven't started writing unit tests. Also, complete a full write-up of what it took to get the thing working.
- Get my website running #GoHugo.
- Rebuild of DEATH, my Microserver gen8, probably with #FreeBSD. (Yes, it's been over a year since DEATH's RAID died.)
- Pick another SIBO SDK tool to rewrite. (Probably EMAKE or RCOMP.)
- Add a 17V boost converter to #PsiDrive.
- Make #fefstool create FEFS images. (I'm half-tempted to rewrite fefstool in Pascal to make it easier for me to finish.)
You'll notice that some of these projects have been sitting for a while. I've struggled to get going with things this year. I'm hoping that working though plptools will give me some mental energy to get going with other things.
-
Current main projects:
- #plptools: Resurrecting old ports (#FreeBSD, #NetBSD) and working on a new port to #HaikuOS. It's an opportunity to get more familiar with the code and maybe find bugs along the way.
Upcoming projects:
- #CTRAN: Still haven't started writing unit tests. Also, complete a full write-up of what it took to get the thing working.
- Get my website running #GoHugo.
- Rebuild of DEATH, my Microserver gen8, probably with #FreeBSD. (Yes, it's been over a year since DEATH's RAID died.)
- Pick another SIBO SDK tool to rewrite. (Probably EMAKE or RCOMP.)
- Add a 17V boost converter to #PsiDrive.
- Make #fefstool create FEFS images. (I'm half-tempted to rewrite fefstool in Pascal to make it easier for me to finish.)
You'll notice that some of these projects have been sitting for a while. I've struggled to get going with things this year. I'm hoping that working though plptools will give me some mental energy to get going with other things.