TomGwozdz

Game dev by day. Work on retro-computing projects by night. Currently building the TG6502 single board computer. Also developing Blightmare!

Public Key

npub1dp5gnrj0qfvr0kpk2r9g0fnraz2pv4qfhu0cd52zxqjkxez4fgeqqzduwp

NIP-05 Address

tomgwozdz_at_oldbytes.space@momostr.pink

Profile Code

nprofile1qqsxs6yf3e8sykphmqm9pj585e3739qk2sym78ux69prqftrv3255vsppamhxue69uhkummnw3ezumt0d5q3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7qznck9

Publishing to

nostr.mom

relay.damus.io

nos.lol

Author Public Key

npub1dp5gnrj0qfvr0kpk2r9g0fnraz2pv4qfhu0cd52zxqjkxez4fgeqqzduwp

Show more details

Last Notes

2026-05-14 16:11:10 UTC

- reply

I wouldn't worry _too_ much about bugs. People are a lot more understanding of bugs in the context of a smaller/indie project. Its more important to just be reactive if/when they come up. Bugs happen.

2026-05-01 21:37:53 UTC

I need some floppy imaging advice. I have a Greaseweazle connected to a 3.5" drive. But the floppies I have to image are a bit fragile. When I try to read a whole disk, the first few tracks read fine, but then it starts getting more and more scratchy as it goes, so much so that it starts destroying the disk surface. If I clean the heads, its fine again, for a little while. Is there a way I can read a few tracks at a time so that I can clean the heads in between? Or is there another approach I can use to read these disks?

2026-03-09 15:59:24 UTC

- reply

Can you swap out some gameplay code for bossfight code whenever you encounter one?

2025-10-27 19:52:34 UTC

- reply

can you do some kind of in system programming so that you don’t have to remove the chip?

2025-06-12 18:38:45 UTC

Did someone trip over a network cable?
https://assets.oldbytes.space/assets.oldbytes.space/media_attachments/files/114/671/843/572/135/149/original/1aceff834d0d0d5b.png

2024-08-16 16:13:20 UTC

- reply

isn’t that lower decks?

2024-08-14 03:46:57 UTC

- reply

for lines, start with https://en.m.wikipedia.org/wiki/Bresenham%27s_line_algorithm. There’s an analogous algorithm for circles as well. If you want a decent low level intro to pixel graphics, this set of tutorials is decent: https://archive.gamedev.net/archive/reference/listed82.html?categoryid=130. It’s focused on DOS/VGA in Pascal and assembly but the concepts are more universal.

2024-08-12 01:33:42 UTC

- reply

actually, a funny story. I was reading the docs for this analyzer a while back, and I happened to run across a document that described how to “declassify” the analyzer. That is, how to make sure that no classified data leaks out if that analyzer was being used for classified projects and they need to dispose of it or something. The whole instructions were basically 1. Remove floppy disk. 2. Destroy floppy disk. 3. Done! :) it’s a bit more complicated with the more modern units since they have hard drives.

2024-08-12 01:27:50 UTC

- reply

I thought I had a floppy with some saved projects on it that I was gonna send along, but I couldn’t find it

2024-08-12 01:26:05 UTC

- reply

I don’t think the contents of that floppy were important. I think it was just the latest firmware update? You can probably just erase it. It doesn’t need anything other than the built in rom to boot and operate.

2024-08-11 01:13:56 UTC

- reply

here’s my current one.
https://assets.oldbytes.space/assets.oldbytes.space/media_attachments/files/112/940/730/585/891/559/original/7275f27f5b6d27da.jpeg

2024-08-11 01:08:16 UTC

- reply

lol yeah. The one I have to replace the one I sent you is a 16500C. It’s massive in comparison.

2024-08-11 01:07:35 UTC

- reply

yeah should be. As long as it fits in memory.

2024-08-11 01:06:19 UTC

- reply

I’m pretty sure the 16500 are the newer model. This one doesn’t take any cards, it’s all built in.

2024-08-11 01:04:31 UTC

- reply

yeah. If you’re doing state captures you’ll also want a clock line that defines the states. If you’re doing timing then I don’t think you need a clock? Since it’s just recording periodically like an oscilloscope. But you’d probably want state for most things since it uses less sample memory. Unless you need to capture the timing itself of course.

2024-08-11 00:55:19 UTC

- reply

the trigger system is probably the most complicated part. You can go very simple like trigger on a certain line going low or something. But you can also do things like wait for a specific address to show up, then wait for like 4 more reads. Then wait for a write to another address, then start recording for 10 cycles, etc. It’s very powerful. I’ve barely used all the features.

2024-08-11 00:50:08 UTC

- reply

yeah exactly

2024-08-11 00:47:19 UTC

- reply

yeah it has I think 4 or 8k samples worth? Which should get you a bunch of transactions. But you can get clever with it. I was once trying to look at video timing to make sure I got vsync and hsync pulses correct, but the whole frame was too big to fit in sample memory, but I was able to set up the triggers to count samples rather than record them so I basically got the counts of the high and low signals. So there’s ways to do some fancy things with it.

2024-08-11 00:42:30 UTC

- reply

the only limitation is the low sample memory. But you just have to be careful about what you capture. And be clever with your triggers.

2024-08-11 00:41:40 UTC

- reply

yeah it should do that just fine. I was using it on a full 6502 to see all the bus transactions and it handled it just fine.

2024-08-11 00:39:30 UTC

- reply

awesome! Glad to hear it!

2024-08-10 19:57:52 UTC

- reply

you might need to clean the mouse rollers if you use it. I never did though.

2024-08-10 19:54:39 UTC

- reply

I hope it survived the trip ok :)