@mdhughes oh, and thanks for the help with my BASIC game! you were right about DIMs
@mdhughes i am assuming eventual primitive clean room conditions, perhaps the recovery and maintenance of what few electron microscopes are left
have you heard of sam zeloof? we can do intel 4004's in the backyard as of now
@ozzelot @xChaos well i am really just imagining kansas city encoding:
https://en.wikipedia.org/wiki/Kansas_City_standard
so i think it may accommodate recording technologies that we would normally consider quite poor!
long play records--can you press them at home? i would ordinarily imagine them to be worth using for long-term, high integrity data storage?
@xChaos this is a strategic question for me, yes--i am imagining a 'left wing' long termism, to put it quickly.
i encountered something like this while studying hegel--italian fascists also loved him, it seems.
maybe a built in EEPROM flasher--and the permacomputer will be geocached/time capsuled with a stash of EEPROMs?
i wonder what the most ubiquitous form of audio playback device is now
probably people's phones... i ask because i am trying to think of a way to help the permacomputer project store data in a format that would be used day-to-day.
the requirement of long-term data integrity is not a requirement, that will require some other medium. this question concerns more short- to medium-term storage.
ideally you would have a long term, well-engineered master copy, and then many cheaper, lossier copies made off that.
i figure something analogous to a cassette tape could work--audio data transfer is easily implemented in TTL circuitry, so it would make the permacomputer much simpler.
i wonder how one might store audio in the future? after a technological and ecological decline? maybe a lil mp3 player with a universal adaptor for any kind of drive, flash memory, smart card... old laptop hard drive?
i was originally gonna keep the 80s microcomputer/BASIC type-in noodlings separate from the people's permacomputer project.
but i may collapse parts of the 6502 hardware build i am doing into the permacomputer project.
it seems this would contradict the latest direction that the project took--the path the permacomputer project has gone down has been rather unpredictable. it often oscillates between several opposing recommendations for action, such as whether it is a good idea to actually commit to providing some specific hardware.
i do encourage you to follow along, it has been very exciting so far
If you’ve already set up an adventure log for this year’s #DecemberAdventure and you want me to include it in the big list of adventure logs drop me a link to it!
New #RC2014 boards that arrived today work exactly as planned. That's a huge relief having changed a lot since the last revision.
Spent a lot of time on the firmware today. Happy to report that it is making progress... bars
![an under-exposed shot of a PCB which has an over-exposed oled display on it. the PCB has a small square flat chip and big DIP chip. also, micro SD card socket, small chips and a programmer sticking out of one side. an under-exposed shot of a PCB which has an over-exposed oled display on it. the PCB has a small square flat chip and big DIP chip. also, micro SD card socket, small chips and a programmer sticking out of one side.](https://assets.oldbytes.space/assets.oldbytes.space/media_attachments/files/113/551/809/845/810/632/original/93fe4c8218e57ad1.jpg)
![similar photo to the previous one, except instead of the big black chip, there is a green PCB with 31 LEDs on them. 5 of the red LEDs are lit, although none of the white or green are. similar photo to the previous one, except instead of the big black chip, there is a green PCB with 31 LEDs on them. 5 of the red LEDs are lit, although none of the white or green are.](https://assets.oldbytes.space/assets.oldbytes.space/media_attachments/files/113/551/810/038/796/664/original/095317209bca46db.jpg)
![bare blue PCB on a blue ESD mat. none of the through-hole components have been attached so you can still see the RC2014 logo below where the OLED display will go. bare blue PCB on a blue ESD mat. none of the through-hole components have been attached so you can still see the RC2014 logo below where the OLED display will go.](https://assets.oldbytes.space/assets.oldbytes.space/media_attachments/files/113/551/810/318/832/508/original/cc4d5c39036e1a5d.jpg)
![the rear of the blue PCB with a prominent RC2014 logo on it. above that it says 39SF040 Programmer. below the logo are simple instructions to program the ROM or to dump it. the rear of the blue PCB with a prominent RC2014 logo on it. above that it says 39SF040 Programmer. below the logo are simple instructions to program the ROM or to dump it.](https://assets.oldbytes.space/assets.oldbytes.space/media_attachments/files/113/551/810/519/685/950/original/55cd9477195ebc1f.jpg)
#lispyGopherClimate #archived #now ! https://archives.anonradio.net/202411270000_screwtape.mp3 every Wednesday 000UTC
#climateCrisis #haiku by @kentpitman
#lisp #mathematics #writing #lambdaMOO #MOOing generally:
My #lispmoo2 and remembering #softwareIndividuals
In paradise sushi!
telnet lambda.moo.mud.org 8888
co guest
@join screwtape
We'll look at Cat's gopher given enough time
the music this week is the silence in between my thoughts
![LISPY
GOPHER
SHOW
The gopher on top of a building reaching down to the lisp alien's extended nose.
A portrait of Erik Sandewall.
FLAME WAR IS ON! on another wall.
LISPY
GOPHER
SHOW
The gopher on top of a building reaching down to the lisp alien's extended nose.
A portrait of Erik Sandewall.
FLAME WAR IS ON! on another wall.](https://mastodon.sdf.org/system/media_attachments/files/113/551/935/837/548/198/original/79d2001db282acfc.png)
alright the 6502 thingo is going ahead.
i purchased the following
- 2 x MC6847 video display generators (keeping a spare on hand)
- 1 x T48 (TL866 compatible??) EEPROM programmer
- large amount of 74LS00 NANDs
i already have:
- 2 x 61256 32K SRAMs
- 1 x AT28C256 32K EEPROM
- 1 x ACIA
- 1 x VIA
-*-
links:
https://pmig96.wordpress.com/2020/07/15/mc6847-test-circuit/
https://github.com/adumont/hb6502?tab=readme-ov-file#memory-map
-*-
memory map:
address | component |
---|---|
$0000-$3FFF | RAM (16KB) |
$4200-$4203 | ACIA |
$6000-$600F | VIA |
$8000-$FFFF | ROM (32KB) |
-*-
honourable mention:
As a necessary prerequisite to getting some of my VM/OS goals accomplished, I'll need something akin to a standard library for doing stuff like printing numbers and such.
In this case, my formatting library takes its inspiration directly from ANS Forth's numeric conversion primitives.
![A screenshot of my text editor, editing a file called `fmt.inclib`. The assembly listing shows the definition of the `FmtHold` function, along with its auto-documentation comment header. The auto-documentation follows the Commodore-Amiga autodocs schema and conventions, except that the CPU registers describe RISC-V registers instead of PowerPC or 68K. A screenshot of my text editor, editing a file called `fmt.inclib`. The assembly listing shows the definition of the `FmtHold` function, along with its auto-documentation comment header. The auto-documentation follows the Commodore-Amiga autodocs schema and conventions, except that the CPU registers describe RISC-V registers instead of PowerPC or 68K.](https://hackers.town/system/media_attachments/files/113/551/042/979/755/059/original/ef77708a037cc5d1.png)