Hello,


Am 20.04.2025 um 12:53 schrieb Virgil Dupras:

> It's not a matter of whether the keyboard works or not on other
> systems, it's whether it supports the boot protocol, which is the only
> supported protocol for now. Full HID protocol is more complex.

But, if you ever experienced your keyboard not to work in the 
firmare/BIOS setup of a (not-so-recent machine) and another keyboard 
did, chances are high the first one does not support the boot protocol.

Also, when a keyboard has fancy features like dynamic LED backlight,

Hello Aaron,


Am 19.04.2025 um 21:49 schrieb Aaron Miller:

>> No need (unless you like to try it). When I find time, I'll have to 
>> rewrite that decompression logic to native GZIP and recompress all the 
>> ROMs and SD Card images.

> Anyway, I did a quick search on NPM to see what pure JavaScript gzip 
> decompression libraries are out there, and I think this could work: 
> https://github.com/imaya/zlib.js/blob/develop/src/gunzip.js

As I wrote before, Firefox added native GZIP support to

Hello,


Am 19.04.2025 um 00:04 schrieb Aaron Miller:

> I dug into this some more, and it turns out the ROM does get loaded but 
> on Firefox and LibreWolf there is some kind of strange problem where it 
> doesn't print "Collapse OS ok". The browser tab eats up a lot of CPU and 
> for some page loads but not others it spews out a bunch of "Attempting 
> to write to ROM at <address>" with either one address or a couple 
> alternating ones into the console logs (ctrl-shift-K in both browsers).
> 
> It works fine in Chromium.

Hello Aaron,


Am 18.04.2025 um 18:00 schrieb Aaron Miller:

> I just remembered the JS port was one of the first things I tried 
> related to Collapse OS or Dusk OS last May. I couldn't figure out how to 
> use it because I didn't know what ROM to use.
> 
> Would you be able to update your page sometime with the steps to produce 
> a ROM? Maybe also provide sample ROMs for newbies to get started with?

That surprises me. When you use it on the website 
(https://schierlm.github.io/CollapseOS-Web-Emulator/), it should load a

Hello Aaron,


Am 18.04.2025 um 05:55 schrieb Aaron Miller:

> I tried the C VM port in the latest tarball and it seems that none of 
> the alphabetical words like "dup", "drop", "over", "c," etc. can be 
> found. Only symbolic words like ".", "+", "-", ",", etc. can be found.

At some point in Collapse OS's past (after August 2022 when I last 
updated the Javascript port of it), Collapse OS switched from uppercase 
core words to lowercase ones.

I assume the switch happened after Collapse OS moved into the Dusk

Hello,

Am 16.04.2025 um 02:16 schrieb Virgil Dupras:

> ":" and "code" are completely different because the code that follows
> the former is compiled and the code that follows the latter is
> interpreted. For example:
> 
> : foo 42 . ;
> 
> doesn't print anything. You have to call "foo" to see something.
> 
> code foo 42 .
> 

Hello,


Am 15.04.2025 um 23:27 schrieb Drache:
> Hello all,
> 
> While going through the documentation and doing tests with Dusk, trying 
> to implement new words, I have come across various interrogations and 
> possibly an error or hole in the documentation of the x86 disassembler.
> 
> # X86 disassembly misunderstanding
> First of all while disassembling basic words such as "+", I've seen what 
> seems to be an error in the way the code has been disassembled.
> The output of "' + dis" is the following :

Hello Virgil,


Am 12.04.2025 um 13:20 schrieb Virgil Dupras:

> Making your own "ls" is an interesting exercise (and by the way, it's
> already in home/sh.fs), but is ultimately pointless because you aren't
> going to use it much.

That assumes that either you have memorized the names of all the files
you may want to ever load (or look at in case they are documentation),
or that you have a directory listing outside of Dusk OS to refer to, as
a cheat sheet.

Hello,


Am 24.03.2025 um 17:12 schrieb Virgil Dupras:

> You mean reply to a message that you haven't received in your inbox
> because you weren't subscribed at that time? Without a sourcehut
> account, you can't.

You can download the mailing list archive as .mbox, import it into your
email client (your email client must support import of .mbox files) and
then just reply to whatever message you want to reply to.

Hello Virgil,

Am 20.03.2025 um 12:30 schrieb Virgil Dupras:
> On Thu, 20 Mar 2025 09:15:34 +0100
> Carsten Strotmann <carsten@strotmann.de> wrote:
>> However I found that memtests reported 24MB of RAM, whereas Dusk OS
>> reports 30MB free. Dusk OS detects more memory than available.
>
> Dusk OS doesn't do any kind of memory probing on the "pc" target yet.
> This 32MB is arbitrary and the memory map used is just what OSDev
> mentions is the general convention among PCs.

Is the memory map used by Dusk OS documented anywhere? I skimmed over
the documentation and could not find it.