Notices by Foone🏳️‍⚧️ (foone@digipres.club)

ran though about 300 iterations and the word table never gets filled in. on either implementation, the original or mine.

I understand this code way less than I thought

@lucas @mcc amen.

@CenturyAvocado @philpem I think that's because I set my account to private.

I suspect the tables aren't getting filled in correctly. I'm gonna need to set some breakpoints in both the python and DOS implementations and compare the current state of the tables.

ugh. my kingdom for a automatable dosbox debugger

after fixing some bugs, I am now correctly decompressing an entire 8 bytes!

@lunarood would you like to make a contract?

if you decompress a file and it gets smaller, you fucked up.

(or it has really high entropy and your compression algorithm has a big header)

it "decompressed" to the compressed input, but with 3 bytes missing from the beginning and an extra "G" at the end.

alright, I ported over enough of the decompression algorithm for it to run for the first time!

Did it work? NO OF COURSE NOT! but running is at least PROGRESS

@KormaChameleon heh. no, I think it's just that they assembled it to an OBJ and used it in both programs

@tezoatlipoca the only rule of of x86 assembly is to have fun and be yourself

okay it was recompiled/reassembled: some globals are in different locations.

but it's 100% the same code.

@r 1000:cd0b in bible builder, 1000:9ca4 in captain bible

I finally went and confirmed something I assumed:

The compression routines from Bible Builder and Captain Bible are identical. like, I'm not even sure they were even recompiled identical.

@smh nah. Not needed. This is a medical issue I know the bounds of well enough.

@jschwart I never finished cleaning it up into a releasable state, but I will if I ever get back to it

@jschwart I wrote a bunch of now abandoned code that uses it, yeah. I was embedding Borland Turbo C compilation into a docker container

I should build an x86 usb device. It's stupid because I literally am on an x86 machine, but SOMEONE didn't think 16bit backwards compatibility was important. Philistines!

My everything hurts, I'm starving and can't eat, my brain is fogged, and I have a lot of stuff to do today that's important.

Clearly it's time to write my own x86 emulator, again

@janamarie this looks fun