ZephyrZ80 @ZephyrZ80@mastodon.technology

Does anyone have any experience switching to i3 from xfwm on a linux install? Want to know if I should expect any oddness that wouldn't exist on a fresh install.

Also, tiling window managers are neat.

Has anyone ever been as far decided as to go do write an OS for an 8-bit computer system?

Wrote some programs for a fictional/virtual processor system, the TC-DCPU. I've made programs that can auto-find devices, read data from the clock device, and query the floppy disk's geometry. Going to work on trying to write to the disk tomorrow, see how that goes. If it works well, I'll probably work on a program to format a disk image to a custom filesystem I made.

New blog post: https://zephyrz80.blogspot.com/2018/12/hp-125-floppy-drive-emulation.html

Either way, found the documentation I needed. Probably going to make a device to act as either an 82901 emulator, or a general storage device for my project computers. Using an SD card as the storage media, a switch to control mode, and a thumbwheel to select between 8 'disks' on the SD card while the 'standard' mode will use the rest of the SD card for use with my project computers.

So last night I found out that HP sometimes sucked at documentation. Had to look through the service manual for the HP-9895A floppy drive unit to get information on the command set used with the HP-82901 and similar units, so I can make an emulator to work as a boot device for my HP-125. The command set's successor, CS/80, got its own manual so I'm a bit frustrated the original command set doesn't.

So I went ahead and wrote up a spec that's a hybrid of two other filesystems. It's simple to implement on an 8-bit system, and allows for large files for later projects. Each I-Block can define a file 36MB in size, but I-Blocks can be chained together in a linked-list to allow files up to 8.5GB in size. It can even address a 2TB volume right out of the gate. All of this with pretty small overhead for each file, and very little overhead for the filesystem itself.

Just when I thought I've for sure decided on a filesystem for my computer projects, I find an old obscure one that's simple, efficient, and flexible, that I can mod to include some of my favorite features of LEAN, since 'stock' the older filesystem includes irrelevant data. So now I'm wondering if I should stay with LEAN, or modify the 'new' one and use it instead.

Is it bad to spend multiple hours looking through options for a power switch on a project?

I made a 4-bit CPU in Logisim, mostly to try and figure out how to make the sequencer portion of a CPU's control unit. Though I went with a microcode type of CU instead of 'random logic'. Still, a neat thing to play with. Might try for a full 16-bit CPU.

Okay, so I thought of something yesterday: I have copies of the Block II Apollo Guidance Computer schematics, and I have logisim on my desktop. Should be possible to recreate it in logisim.

So I have a half-baked idea of using either audio casettes or 8-track cartridges for data storage for my 8-bit project computers. Ideally I'd like to use that as a form of removable media instead of using modern stuff like SD or CF cards.

When you want an old finnish computer that takes 20+ minutes to make a chess move: https://www.youtube.com/watch?v=sMgWpz5V1qg

So yesterday was an exercise in semi-productive procrastination. Rather than working on my Z80 computer, I instead studied GPIB for use in my later 1802 computer project.

New blog post after too many months. https://zephyrz80.blogspot.com/2018/10/eeprom-programmer-pt2.html

On a scale from one to ten, how bonkers would it be for an 8-bit computer to have an 80GB hard disk for storage?

I decided to make an 8x8 glyph set for a planned text-only video card. It will display 30 rows of 40-column text, have the fixed 128-character glyph set pictured, with another 128 characters that can be set in software for programs that need it.

This is my semi-final draft for a 4x6 glyphset that would be placed in the fixed character ROM. Obviously with the non-printable ASCII control codes replaced with math and graphical glyphs.

The text-only display would make the software easier, since you can just send ASCII character bytes to the card and have it be drawn automatically, rather than having to form the bit-pattern for a character in software. I could also have the ability to have 128 software defined characters, by having a Character Generator RAM in addition to the Character Generator ROM for the typical ASCII set.