Hi. You also might like to know about https://schismtracker.org which tries very hard to work like Impulse Tracker (especially if you enable its "classic mode")
And maybe if you are a text mode linux user who liked Impulse Tracker, you will also enjoy this: https://github.com/geocar/mm/
This was eerie to read. I was very much Alan, only I reported to duty Monday morning because I thought, or rather knew, that's what was expected of me from my parents and from society.
This definitely gave me "road not taken" vibes and made me reconsider where I'd be, and more importantly how happy I'd be, if I'd done as Alan did.
Also, confusingly, I feel like I'm Alan all over again. I've been thinking of a massive career change (AKA, goose farming from the meme) a lot of recently due to AI sucking the fun out of my career.
v~~ Nonfiction, 2nd-person account about real Impulse Tracker ~~v
C. 1994-1996, one of my high-school friends won some mod contests. His weapon of choice was IT. Flying fingers making tiny tweaks, relistening over-and-over again in snappy DOS 80x50 text mode on a donated IBM PS/1. I don't know how IT got PC speaker emulation down, but they did IIRC through some sort of high precision timer magic such that it didn't need a sound card per se. Mouse support either ate up 4(?) characters in the normal 256 chars glyph space or it used the 512 glyph mode that commercial DOS utilities and the legacy FreeBSD text console mouse device used... basically by copying whatever glyphs would be under/around the mouse cursor to each sacrificial replacement glyph and dynamically drawing a fraction of a mouse cursor over each, and then writing the magic text chars to the text buffer.
> I don't know how IT got PC speaker emulation down, but they did IIRC through some sort of high precision timer magic such that it didn't need a sound card per se
> basically by copying whatever glyphs would be under/around the mouse cursor to each sacrificial replacement glyph and dynamically drawing a fraction of a mouse cursor over each, and then writing the magic text chars to the text buffer.
Exactly correct.
> legacy FreeBSD text console
I never knew that. I wrote one for Linux because I like the visual feedback of what row I'm on by the mouse cursor changing.
Cool beans. "Magic" isn't literal. No magic, any time. ;) It's also probably in one of my vintage PC programming books or vintage programming text file collection. It reprograms timer0 (the system timer) of the 8254 and chains the interrupt handler for IRQ 0 (interrupt 8), and then bangs data out the speaker port relatively fast compared to "dumb" beeps.
Text mouse cursor: I think I first came across this trick in the 1st ed of PC Intern.
Artifact on "normal" default VGA text mode 3: the right-most pixel is duplicated from an 8x16 source glyph is displayed as an 9x16 sprite on a 720x400 (pixels) hardware frame buffer, so the cursor trick periodically has a stair-step artifact when in-between characters. The pixel is duplicated so box and line drawing and other glyphs can be gapless, and it's 9 pixels wide as characters look better than squished into 8x16. The source glyph in the table remains 8 pixels wide because it's exactly one byte wide (1 bit per pixel), because 9 pixels would take up 32 more bytes in the standard glyph table (or 64 bytes more in a 512 character table). This won't happen in 8 pixel wide glyph modes like 80x50 X 8x8 (640x400 - mode 66h) IT uses.
TIL: Linux may have a text mouse console driver that works, I'm guessing, with a coordination between kernel settings and gpm.
It's an old/good trick. The linux kernel offers an ioctl to set the font tables, and has for years. I think the kms people want to remove them which is a little sad.
Until then you can also use a tool called SVGATextMode to set the registers and get 80x50 or even a 160x100. I still think text-mode is great. I don't know very much about FreeBSD; I last used OpenBSD almost 20 years ago. Before Linux my unix was Solaris or SCO.
These days, I have a tegra (nvidia arm64) system and it still has a x86 vga bios in there(!!!) so linux actually ships an x86 emulator to "read" the outb/w instructions. Amazing.
And maybe if you are a text mode linux user who liked Impulse Tracker, you will also enjoy this: https://github.com/geocar/mm/
This definitely gave me "road not taken" vibes and made me reconsider where I'd be, and more importantly how happy I'd be, if I'd done as Alan did.
Also, confusingly, I feel like I'm Alan all over again. I've been thinking of a massive career change (AKA, goose farming from the meme) a lot of recently due to AI sucking the fun out of my career.
v~~ Nonfiction, 2nd-person account about real Impulse Tracker ~~v
C. 1994-1996, one of my high-school friends won some mod contests. His weapon of choice was IT. Flying fingers making tiny tweaks, relistening over-and-over again in snappy DOS 80x50 text mode on a donated IBM PS/1. I don't know how IT got PC speaker emulation down, but they did IIRC through some sort of high precision timer magic such that it didn't need a sound card per se. Mouse support either ate up 4(?) characters in the normal 256 chars glyph space or it used the 512 glyph mode that commercial DOS utilities and the legacy FreeBSD text console mouse device used... basically by copying whatever glyphs would be under/around the mouse cursor to each sacrificial replacement glyph and dynamically drawing a fraction of a mouse cursor over each, and then writing the magic text chars to the text buffer.
You can check!
https://github.com/jthlim/impulse-tracker/blob/main/SoundDri...
No magic I can see.
> basically by copying whatever glyphs would be under/around the mouse cursor to each sacrificial replacement glyph and dynamically drawing a fraction of a mouse cursor over each, and then writing the magic text chars to the text buffer.
Exactly correct.
> legacy FreeBSD text console
I never knew that. I wrote one for Linux because I like the visual feedback of what row I'm on by the mouse cursor changing.
Text mouse cursor: I think I first came across this trick in the 1st ed of PC Intern.
Artifact on "normal" default VGA text mode 3: the right-most pixel is duplicated from an 8x16 source glyph is displayed as an 9x16 sprite on a 720x400 (pixels) hardware frame buffer, so the cursor trick periodically has a stair-step artifact when in-between characters. The pixel is duplicated so box and line drawing and other glyphs can be gapless, and it's 9 pixels wide as characters look better than squished into 8x16. The source glyph in the table remains 8 pixels wide because it's exactly one byte wide (1 bit per pixel), because 9 pixels would take up 32 more bytes in the standard glyph table (or 64 bytes more in a 512 character table). This won't happen in 8 pixel wide glyph modes like 80x50 X 8x8 (640x400 - mode 66h) IT uses.
TIL: Linux may have a text mouse console driver that works, I'm guessing, with a coordination between kernel settings and gpm.
Until then you can also use a tool called SVGATextMode to set the registers and get 80x50 or even a 160x100. I still think text-mode is great. I don't know very much about FreeBSD; I last used OpenBSD almost 20 years ago. Before Linux my unix was Solaris or SCO.
These days, I have a tegra (nvidia arm64) system and it still has a x86 vga bios in there(!!!) so linux actually ships an x86 emulator to "read" the outb/w instructions. Amazing.