Denial

Now for messing this up with an interrupt handler..

tunix-breakerror.png It LOADs but OPEN brings random BASIC errors out of nowhere (STATUS = 0). That's an inconvenience for BASIC coders. Time for the console switcher unless you want to do switches like this: OPEN31,31,0,"GM" (multi-tasking off) OPEN31,31,0,"PF" (fork new BASIC ...

Syscalls (via OPEN) can be nested. That's great news. Task switches work in BASIC but there's still no working LOAD but many solutions to the problem. The required boot loader won't kill any existing boot menus. As that's extra work I started the ROM in C (copies itself to RAM on startup) the Unix w...

There was more than one price to pay for that and not worth the result yet.

I have added some lines of C code in a separate file so one can see what I mean by saying "simple". That's why C was invented. What is also kinda simple is the banking – simple on paper. Some seemingly pointless doodling fixes a lot in advance. Anyway, this is getting addictive. Am trying ...

This is fun, especially with the latest VICE monitor update (build from source): vice-montior.png (I know your eyes are just having sex.) Instead of doing waiting lists for zombies implementing signals isn't much more complicated and the signal mechanism is a lot more versatile too. This needs some ...

beamrider wrote: ↑Thu Mar 28, 2024 2:41 am Out of interest and as something I've never really used. What's the benefits of using a monitor rather than just going straight to an assembler and using the VICE monitor.

It makes you a tough boy by over-complicating about everything? Something remotely ca65 compatible I'd find interesting.

I would start down at the metal. What's a transistor/gate. What does an adder look like. What's an ALU, data bus, address bus, control bus. Now that bits and bytes make sense, then I'd continue with assembly.

Any summary of this adventure? Somebody once asked me if I could teach him to programme. I asked "Do you know how a computer works?" "Yes! You grab the mouse *grab* and then you click here and here and…" It takes Harvard experience to teach adults like that.

First boot. Meaning userland C coding.

See the thread " Printing (unsigned) 16-bit numbers in Assembly, how? ". :wink: 8) Thanks! tnuix-with-numbers.png Oh impatience... This will take assigning LFNs to devices to make pipes. And a FIFO driver for inter-process communication perhaps. But sure as hell a RAM disk because sharing...

tunix-zombie.png Now for chasing zombies… how did printing decimals work again? In the operating system's choreography, a process doesn't simply terminate and vanish. Instead, it lingers due to a critical relationship with its creator: the parent process. The parent may opt to inspect the exit code...

That is actually the job of CLRCHN . Just the regular dumbing down before enlightenment hits. You're right. Thanks! The idea of just dropping the channels wasn't too appealing, so TUNIX closes every file with CLALL. I'm thinking maybe it's a good idea if processes get (and thus inherit) their own d...

And suddenly CLALL makes sense. There are no standard logical file numbers for console I/O. CLALL virtually does the necessary CHKIN/CKOUT as if there were local file numbers for keyboard and screen. That bit of explanation is missing in all docs I've seen so far.
Not a show stopper.

And there it is: the fork system call: Enough for today…