du, although I’m pretty sure that someone has ported the du from BSD or GNU at some point. Either way, it hardly matters, because I don’t think anybody (but me) will ever use this program anyway. 😅
du, although I’m pretty sure that someone has ported the du from BSD or GNU at some point. Either way, it hardly matters, because I don’t think anybody (but me) will ever use this program anyway. 😅
du, although I’m pretty sure that someone has ported the du from BSD or GNU at some point. Either way, it hardly matters, because I don’t think anybody (but me) will ever use this program anyway. 😅
inetd …
inetd …
inetd …
You can take the data that I posted, convert it into a binary, and then run it under DOS:
https://movq.de/v/054fae119b/
And boom, you get the output from the video. 🤯
(It probably also works in DOSBox, but I wouldn’t do that. Who knows what other stuff this magic binary does. 😂)
You can take the data that I posted, convert it into a binary, and then run it under DOS:
https://movq.de/v/054fae119b/
And boom, you get the output from the video. 🤯
(It probably also works in DOSBox, but I wouldn’t do that. Who knows what other stuff this magic binary does. 😂)
You can take the data that I posted, convert it into a binary, and then run it under DOS:
https://movq.de/v/054fae119b/
And boom, you get the output from the video. 🤯
(It probably also works in DOSBox, but I wouldn’t do that. Who knows what other stuff this magic binary does. 😂)
WinScrollWindow() which scrolls/moves existing window content and then you only draw the new parts. Maybe I’ll do that in a later version. 😅
WinScrollWindow() which scrolls/moves existing window content and then you only draw the new parts. Maybe I’ll do that in a later version. 😅
WinScrollWindow() which scrolls/moves existing window content and then you only draw the new parts. Maybe I’ll do that in a later version. 😅
https://movq.de/v/9b1c7016f6/MVI_7449.MOV.mp4
To me, it’s just super cool that I’m able to write programs for OS/2. 😎 That operating system will always hold a special place in my heart, I guess. It ran on my Model 80 back then (and maybe even the Model 30, but I'm not 100% sure anymore) and thus a lot of my earliest memories about using computers are OS/2 related. (And DOS related, of course. I had a dual boot setup on the Model 80, believe it or not …)
Anyway, writing that little program got much easier after I’ve found this page which contains a lot of valuable information:
https://komh.github.io/os2books/
This is a collection of OS/2 books by a person who’s apparently quite active in the realms of ArcaOS (one of OS/2’s “descendants”).
https://movq.de/v/9b1c7016f6/MVI_7449.MOV.mp4
To me, it’s just super cool that I’m able to write programs for OS/2. 😎 That operating system will always hold a special place in my heart, I guess. It ran on my Model 80 back then (and maybe even the Model 30, but I'm not 100% sure anymore) and thus a lot of my earliest memories about using computers are OS/2 related. (And DOS related, of course. I had a dual boot setup on the Model 80, believe it or not …)
Anyway, writing that little program got much easier after I’ve found this page which contains a lot of valuable information:
https://komh.github.io/os2books/
This is a collection of OS/2 books by a person who’s apparently quite active in the realms of ArcaOS (one of OS/2’s “descendants”).
https://movq.de/v/9b1c7016f6/MVI_7449.MOV.mp4
To me, it’s just super cool that I’m able to write programs for OS/2. 😎 That operating system will always hold a special place in my heart, I guess. It ran on my Model 80 back then (and maybe even the Model 30, but I'm not 100% sure anymore) and thus a lot of my earliest memories about using computers are OS/2 related. (And DOS related, of course. I had a dual boot setup on the Model 80, believe it or not …)
Anyway, writing that little program got much easier after I’ve found this page which contains a lot of valuable information:
https://komh.github.io/os2books/
This is a collection of OS/2 books by a person who’s apparently quite active in the realms of ArcaOS (one of OS/2’s “descendants”).
https://infosec.exchange/@harrysintonen/112196893735638837
I quote in full:
> Probably the single most impressive entry from the #Revision2024 #demoparty : Remnants by Alcatraz
>
> Here's the whole intro executable for your convenience:
>
> 68f69f07b013cd10d6bac90391eee2f9bbf601b8cdccf7e7720e41f6c13f7508804702058047082d80ee4c608d28bffcffdf45fcd809df470880fd017503de4405d9edd913df45fef6c1407402dcc2dcc0de4706df45fbd8097404d9cad9e0df47c95629fed918d91a7bf85eb929006029fed902d80bd800d9500cd9187bf1df01d900b10729fed94004d900d9c1d84ffed9c1d84ffedeebdec1d918d95804d9c156d9c2d8c0d900d8c4d9f5d9e1d94702decadee9d910dbf1dbd1ddd929fe7ae15edbf1dac1ddd9d913d907decae2b761ddd9d85f02dfe09e7602e292890d61260245ffd1e8aa83c72881f980010f8521ffc30c00b84c3ed53eca3e09c237ff
>
> video: https://www.youtube.com/watch?v=A9jn6ExjDw8
>
> pouet: https://www.pouet.net/prod.php?which=96536
This is absolutely crazy. 🤯🤯🤯
https://infosec.exchange/@harrysintonen/112196893735638837
I quote in full:
> Probably the single most impressive entry from the #Revision2024 #demoparty : Remnants by Alcatraz
>
> Here's the whole intro executable for your convenience:
>
> 68f69f07b013cd10d6bac90391eee2f9bbf601b8cdccf7e7720e41f6c13f7508804702058047082d80ee4c608d28bffcffdf45fcd809df470880fd017503de4405d9edd913df45fef6c1407402dcc2dcc0de4706df45fbd8097404d9cad9e0df47c95629fed918d91a7bf85eb929006029fed902d80bd800d9500cd9187bf1df01d900b10729fed94004d900d9c1d84ffed9c1d84ffedeebdec1d918d95804d9c156d9c2d8c0d900d8c4d9f5d9e1d94702decadee9d910dbf1dbd1ddd929fe7ae15edbf1dac1ddd9d913d907decae2b761ddd9d85f02dfe09e7602e292890d61260245ffd1e8aa83c72881f980010f8521ffc30c00b84c3ed53eca3e09c237ff
>
> video: https://www.youtube.com/watch?v=A9jn6ExjDw8
>
> pouet: https://www.pouet.net/prod.php?which=96536
This is absolutely crazy. 🤯🤯🤯
https://infosec.exchange/@harrysintonen/112196893735638837
I quote in full:
> Probably the single most impressive entry from the #Revision2024 #demoparty : Remnants by Alcatraz
>
> Here's the whole intro executable for your convenience:
>
> 68f69f07b013cd10d6bac90391eee2f9bbf601b8cdccf7e7720e41f6c13f7508804702058047082d80ee4c608d28bffcffdf45fcd809df470880fd017503de4405d9edd913df45fef6c1407402dcc2dcc0de4706df45fbd8097404d9cad9e0df47c95629fed918d91a7bf85eb929006029fed902d80bd800d9500cd9187bf1df01d900b10729fed94004d900d9c1d84ffed9c1d84ffedeebdec1d918d95804d9c156d9c2d8c0d900d8c4d9f5d9e1d94702decadee9d910dbf1dbd1ddd929fe7ae15edbf1dac1ddd9d913d907decae2b761ddd9d85f02dfe09e7602e292890d61260245ffd1e8aa83c72881f980010f8521ffc30c00b84c3ed53eca3e09c237ff
>
> video: https://www.youtube.com/watch?v=A9jn6ExjDw8
>
> pouet: https://www.pouet.net/prod.php?which=96536
This is absolutely crazy. 🤯🤯🤯
At the moment, I mostly use one 128 MB CF card with OS/2 2.1 on it. That OS didn’t really have lots of network capabilities out of the box, so once again I’m using zmodem over a serial line to transfer data to/from other machines, just like I do with MS-DOS 5.0.
Tomorrow, I plan on doing some more work on my OS/2 GUI program. (Let’s see if I actually get to do it. 😂)
By the way, OS/2 2.0 turned 32 years today. 🥳
[](https://movq.de/v/7e6715e687/cf.ff.jpg)
[](https://movq.de/v/7e6715e687/pmworldglobe.ff.jpg)
[](https://movq.de/v/7e6715e687/zmodem.ff.jpg)
At the moment, I mostly use one 128 MB CF card with OS/2 2.1 on it. That OS didn’t really have lots of network capabilities out of the box, so once again I’m using zmodem over a serial line to transfer data to/from other machines, just like I do with MS-DOS 5.0.
Tomorrow, I plan on doing some more work on my OS/2 GUI program. (Let’s see if I actually get to do it. 😂)
By the way, OS/2 2.0 turned 32 years today. 🥳
[](https://movq.de/v/7e6715e687/cf.ff.jpg)
[](https://movq.de/v/7e6715e687/pmworldglobe.ff.jpg)
[](https://movq.de/v/7e6715e687/zmodem.ff.jpg)
At the moment, I mostly use one 128 MB CF card with OS/2 2.1 on it. That OS didn’t really have lots of network capabilities out of the box, so once again I’m using zmodem over a serial line to transfer data to/from other machines, just like I do with MS-DOS 5.0.
Tomorrow, I plan on doing some more work on my OS/2 GUI program. (Let’s see if I actually get to do it. 😂)
By the way, OS/2 2.0 turned 32 years today. 🥳
[](https://movq.de/v/7e6715e687/cf.ff.jpg)
[](https://movq.de/v/7e6715e687/pmworldglobe.ff.jpg)
[](https://movq.de/v/7e6715e687/zmodem.ff.jpg)
I have
~/music and then a folder for each artist. Each album gets its own subfolder. That’s pretty much it.[](https://movq.de/v/685da37314/s.png)
I usually use
mpd for playing, sometimes mpv. I could use something simpler, I guess, but I’ve been an mpd use since at least 2009 and it just works. (I used Audacious, XMMS2, and, well, WinAmp before that. And sometimes MP3Blaster at the end of the 1990ies, but at that time I didn’t have a lot of music on my PC anyway.)A long time ago, I had
.m3u playlists for each genre, but I found that I don’t use that a lot. I usually just play what I’d like to hear right now.As for tagging, I just do the basic things like artist, title, album name, so I get a somewhat meaningful display in
ncmpcpp:[](https://movq.de/v/a3bfaf1a70/s.png)
Virtually all the music on my hard disk is ripped from CDs that I physically own. The script that I use for ripping is *ancient*, like 17 years old. But it still works, so why bother. It apparently uses
icedax for querying the CDDB and the actual ripping, then oggenc for encoding.Probably the most elaborate/convoluted part of my sound setup is the use of LADSPA filters directly in PipeWire. I have crappy speakers and the filters do some EQ and maybe compression. That’s also super handy in today’s abundant video calls and also for watching movies. (I disable the filter chain if I switch to my headphones.)
https://www.uninformativ.de/blog/postings/2020-02-09/0/POSTING-en.html
I have
~/music and then a folder for each artist. Each album gets its own subfolder. That’s pretty much it.[](https://movq.de/v/685da37314/s.png)
I usually use
mpd for playing, sometimes mpv. I could use something simpler, I guess, but I’ve been an mpd use since at least 2009 and it just works. (I used Audacious, XMMS2, and, well, WinAmp before that. And sometimes MP3Blaster at the end of the 1990ies, but at that time I didn’t have a lot of music on my PC anyway.)A long time ago, I had
.m3u playlists for each genre, but I found that I don’t use that a lot. I usually just play what I’d like to hear right now.As for tagging, I just do the basic things like artist, title, album name, so I get a somewhat meaningful display in
ncmpcpp:[](https://movq.de/v/a3bfaf1a70/s.png)
Virtually all the music on my hard disk is ripped from CDs that I physically own. The script that I use for ripping is *ancient*, like 17 years old. But it still works, so why bother. It apparently uses
icedax for querying the CDDB and the actual ripping, then oggenc for encoding.Probably the most elaborate/convoluted part of my sound setup is the use of LADSPA filters directly in PipeWire. I have crappy speakers and the filters do some EQ and maybe compression. That’s also super handy in today’s abundant video calls and also for watching movies. (I disable the filter chain if I switch to my headphones.)
https://www.uninformativ.de/blog/postings/2020-02-09/0/POSTING-en.html
I have
~/music and then a folder for each artist. Each album gets its own subfolder. That’s pretty much it.[](https://movq.de/v/685da37314/s.png)
I usually use
mpd for playing, sometimes mpv. I could use something simpler, I guess, but I’ve been an mpd use since at least 2009 and it just works. (I used Audacious, XMMS2, and, well, WinAmp before that. And sometimes MP3Blaster at the end of the 1990ies, but at that time I didn’t have a lot of music on my PC anyway.)A long time ago, I had
.m3u playlists for each genre, but I found that I don’t use that a lot. I usually just play what I’d like to hear right now.As for tagging, I just do the basic things like artist, title, album name, so I get a somewhat meaningful display in
ncmpcpp:[](https://movq.de/v/a3bfaf1a70/s.png)
Virtually all the music on my hard disk is ripped from CDs that I physically own. The script that I use for ripping is *ancient*, like 17 years old. But it still works, so why bother. It apparently uses
icedax for querying the CDDB and the actual ripping, then oggenc for encoding.Probably the most elaborate/convoluted part of my sound setup is the use of LADSPA filters directly in PipeWire. I have crappy speakers and the filters do some EQ and maybe compression. That’s also super handy in today’s abundant video calls and also for watching movies. (I disable the filter chain if I switch to my headphones.)
https://www.uninformativ.de/blog/postings/2020-02-09/0/POSTING-en.html
My client does not make use of the hash, so it’s fine for me. Other clients might, though, and I wonder how they’ll react to a “fictional” hash. 🤔 Maybe @lyse or @prologic have an opinion here. 😃
Oh, I forgot to mention: The URL should be relative to the fields location, so it should be
prev = archive twtxt-archive.txt. (This is to allow for multi-protocol feeds.)
My client does not make use of the hash, so it’s fine for me. Other clients might, though, and I wonder how they’ll react to a “fictional” hash. 🤔 Maybe @lyse or @prologic have an opinion here. 😃
Oh, I forgot to mention: The URL should be relative to the fields location, so it should be
prev = archive twtxt-archive.txt. (This is to allow for multi-protocol feeds.)
My client does not make use of the hash, so it’s fine for me. Other clients might, though, and I wonder how they’ll react to a “fictional” hash. 🤔 Maybe @lyse or @prologic have an opinion here. 😃
Oh, I forgot to mention: The URL should be relative to the fields location, so it should be
prev = archive twtxt-archive.txt. (This is to allow for multi-protocol feeds.)
prev field in your feed’s headers is invalid. 😅First, it doesn’t include the hash of the last twt in the archive. Second, and that’s probably more important, it forms an infinite loop: The
prev field of your main feed specifies http://darch.dk/twtxt-archive.txt and that file then again specifies http://darch.dk/twtxt-archive.txt. Some clients might choke on this, mine for example. 😂 I’ll push a fix soon, though.For reference, the
prev field is described here: https://dev.twtxt.net/doc/archivefeedsextension.html
prev field in your feed’s headers is invalid. 😅First, it doesn’t include the hash of the last twt in the archive. Second, and that’s probably more important, it forms an infinite loop: The
prev field of your main feed specifies http://darch.dk/twtxt-archive.txt and that file then again specifies http://darch.dk/twtxt-archive.txt. Some clients might choke on this, mine for example. 😂 I’ll push a fix soon, though.For reference, the
prev field is described here: https://dev.twtxt.net/doc/archivefeedsextension.html
prev field in your feed’s headers is invalid. 😅First, it doesn’t include the hash of the last twt in the archive. Second, and that’s probably more important, it forms an infinite loop: The
prev field of your main feed specifies http://darch.dk/twtxt-archive.txt and that file then again specifies http://darch.dk/twtxt-archive.txt. Some clients might choke on this, mine for example. 😂 I’ll push a fix soon, though.For reference, the
prev field is described here: https://dev.twtxt.net/doc/archivefeedsextension.html
OS/2 2.1 and 3.0 just won’t boot from a CF disk, they’re stuck at (or before?) the boot loader, completely silent, nothing happens, nothing on screen. MS-DOS 5.0 on the same CF disk boots just fine, though, as does the exact same OS/2 2.1 installation from a hard drive.
Hm. 🤔
OS/2 2.1 and 3.0 just won’t boot from a CF disk, they’re stuck at (or before?) the boot loader, completely silent, nothing happens, nothing on screen. MS-DOS 5.0 on the same CF disk boots just fine, though, as does the exact same OS/2 2.1 installation from a hard drive.
Hm. 🤔
OS/2 2.1 and 3.0 just won’t boot from a CF disk, they’re stuck at (or before?) the boot loader, completely silent, nothing happens, nothing on screen. MS-DOS 5.0 on the same CF disk boots just fine, though, as does the exact same OS/2 2.1 installation from a hard drive.
Hm. 🤔
belegtzeichen.wav
belegtzeichen.wav
belegtzeichen.wav
It was indeed pretty hard to capture today’s sky with a camera. This comes somewhat close:
https://movq.de/v/3fc94ed911/a.jpg
It was indeed pretty hard to capture today’s sky with a camera. This comes somewhat close:
https://movq.de/v/3fc94ed911/a.jpg
It was indeed pretty hard to capture today’s sky with a camera. This comes somewhat close:
https://movq.de/v/3fc94ed911/a.jpg
[](https://movq.de/v/d4be7212d2/dusage%2Dboth.png)
This compatibility layer only applies to 16 bit OS/2 1.x programs:
https://en.wikipedia.org/wiki/Architecture_of_Windows_NT#OS/2_environment_subsystem
32 bit OS/2 2.x programs don’t run:
[](https://movq.de/v/d4be7212d2/dusage%2Dos2v2%2Don%2D2k.png)
I wonder how many text mode 16 bit OS/2 programs still existed when Windows 2000 came out. 🤔 Was it really worth keeping this subsystem around for so long?
[](https://movq.de/v/d4be7212d2/dusage%2Dboth.png)
This compatibility layer only applies to 16 bit OS/2 1.x programs:
https://en.wikipedia.org/wiki/Architecture_of_Windows_NT#OS/2_environment_subsystem
32 bit OS/2 2.x programs don’t run:
[](https://movq.de/v/d4be7212d2/dusage%2Dos2v2%2Don%2D2k.png)
I wonder how many text mode 16 bit OS/2 programs still existed when Windows 2000 came out. 🤔 Was it really worth keeping this subsystem around for so long?
[](https://movq.de/v/d4be7212d2/dusage%2Dboth.png)
This compatibility layer only applies to 16 bit OS/2 1.x programs:
https://en.wikipedia.org/wiki/Architecture_of_Windows_NT#OS/2_environment_subsystem
32 bit OS/2 2.x programs don’t run:
[](https://movq.de/v/d4be7212d2/dusage%2Dos2v2%2Don%2D2k.png)
I wonder how many text mode 16 bit OS/2 programs still existed when Windows 2000 came out. 🤔 Was it really worth keeping this subsystem around for so long?
Another weird thing: I realized that I kept pressing the strings *waaaaay* too hard to that guitar. This screws up the intonation completely (notes getting higher). I almost thought the instrument was broken. 😅
Guitars are super delicate things …
Another weird thing: I realized that I kept pressing the strings *waaaaay* too hard to that guitar. This screws up the intonation completely (notes getting higher). I almost thought the instrument was broken. 😅
Guitars are super delicate things …
Another weird thing: I realized that I kept pressing the strings *waaaaay* too hard to that guitar. This screws up the intonation completely (notes getting higher). I almost thought the instrument was broken. 😅
Guitars are super delicate things …
Switching between my upright bass and that thing is a wild ride. The difference in string gauges is so massive. 🥴 Feels like trying to play on an egg slicer.
[](https://movq.de/v/6c44db4855/1.ff.jpg)
[](https://movq.de/v/6c44db4855/2.ff.jpg)
[](https://movq.de/v/6c44db4855/3.ff.jpg)
Switching between my upright bass and that thing is a wild ride. The difference in string gauges is so massive. 🥴 Feels like trying to play on an egg slicer.
[](https://movq.de/v/6c44db4855/1.ff.jpg)
[](https://movq.de/v/6c44db4855/2.ff.jpg)
[](https://movq.de/v/6c44db4855/3.ff.jpg)
Switching between my upright bass and that thing is a wild ride. The difference in string gauges is so massive. 🥴 Feels like trying to play on an egg slicer.
[](https://movq.de/v/6c44db4855/1.ff.jpg)
[](https://movq.de/v/6c44db4855/2.ff.jpg)
[](https://movq.de/v/6c44db4855/3.ff.jpg)
I was toying with OS/2 when I noticed that my hard disk was getting a bit full. I’m not aware that something like
ncdu or just du exists in OS/2 Warp 4’s *base system* (I’m sure there’s software like that already available, but I was too lazy to search), so I quickly cobbled a little program together that sums up directory sizes. And there you have it, an installation of Carmageddon was lurking on the disk, weighing in at 200 MB. 🥴[](https://movq.de/v/57f01ccd46/IMG_7415%2Dsmall.jpg)
Being able to cross-compile this from Linux still blows my mind.
Anyway, here’s my tool: https://uninformativ.de/git/dusage
Let’s see, this might be a good opportunity to make an OS/2 GUI version of this. 🤔 I’ve never done that and this might be doable (unlike other stuff I’ve recently tried).
I was toying with OS/2 when I noticed that my hard disk was getting a bit full. I’m not aware that something like
ncdu or just du exists in OS/2 Warp 4’s *base system* (I’m sure there’s software like that already available, but I was too lazy to search), so I quickly cobbled a little program together that sums up directory sizes. And there you have it, an installation of Carmageddon was lurking on the disk, weighing in at 200 MB. 🥴[](https://movq.de/v/57f01ccd46/IMG_7415%2Dsmall.jpg)
Being able to cross-compile this from Linux still blows my mind.
Anyway, here’s my tool: https://uninformativ.de/git/dusage
Let’s see, this might be a good opportunity to make an OS/2 GUI version of this. 🤔 I’ve never done that and this might be doable (unlike other stuff I’ve recently tried).
I was toying with OS/2 when I noticed that my hard disk was getting a bit full. I’m not aware that something like
ncdu or just du exists in OS/2 Warp 4’s *base system* (I’m sure there’s software like that already available, but I was too lazy to search), so I quickly cobbled a little program together that sums up directory sizes. And there you have it, an installation of Carmageddon was lurking on the disk, weighing in at 200 MB. 🥴[](https://movq.de/v/57f01ccd46/IMG_7415%2Dsmall.jpg)
Being able to cross-compile this from Linux still blows my mind.
Anyway, here’s my tool: https://uninformativ.de/git/dusage
Let’s see, this might be a good opportunity to make an OS/2 GUI version of this. 🤔 I’ve never done that and this might be doable (unlike other stuff I’ve recently tried).