Only 1 fuck? Impressive. | Ólafur Waage

Ólafur's posts Post Back to profile

Only 1 fuck? Impressive.

fuckin' sixteen-bit machine ought to be able to handle a SIXTEEN-BIT DISPLACEMENT!!

Like 26 April at 8:37 | Open on mastodon.social

12 comments

Look at this compatibility workhorse.

; SFTFromFCB - the workhorse of this compatability crap. Check to see if
; the SFT for the FCB is Good. If so, make ThisSFT point to it. If not
; good, get one from the cache and regenerate it. Overlay the LRU field
; with PID

26 April at 8:38 | Open on mastodon.social

I feel you, I also hate to do this.

; While we hate to do this, we have to. The following data areas are
; expected to be in the CODE segment.

26 April at 8:39 | Open on mastodon.social

That damn C compiler, always up to no good.

* A note about the following " & 0xFF" stuff. This is
* to prevent the damn C compiler from converting bytes
* to words with the CBW instruction which is NOT correct

26 April at 8:40 | Open on mastodon.social

Very gross, effective? Not sure.

; gross but effective

26 April at 8:43 | Open on mastodon.social

Who doesn't love a gross hack.

; Gross hack: 99% of all disks have 512 bytes per sector. We test for this
; case and apply a really fast algorithm to get the desired results
;
; Divide method takes 158 (XOR and DIV)

26 April at 8:44 | Open on mastodon.social

And there we go, actually not bad for a source codebase. Go read it.

26 April at 8:44 | Open on mastodon.social

Graham Spookyland🎃/Polynomial

@olafurw they really love OEMs

A bunch of assembly code followed by this comment:

In the particular case of "finding" a char device set LOCUS to Unknown. This makes certain idiotic problems reported by a certain 3 letter OEM go away.

26 April at 8:46 | Open on chaos.social

Pilum

@gsuberland @olafurw That feels like there's been some unstated four-letter words about a certain three-letter OEM. 😁

26 April at 9:19 | Open on fribygda.no

Charlotte

@olafurw I'll admit a little envy seeing the swears still in there. I once managed to hold up a release of the Xbox OS due to a comment I accidentally checked in describing the resolution of Xbox 360 profile pictures as "crappy" and that triggered a red flag from the policheck source code scan. Ooops 😅

I still maintain that the images were crappy though. Like 128x128 resolution I think? 🙂

26 April at 9:32 | Open on toot.dusepo.co.uk

Stuart

@olafurw Found another one

Github screenshot showing search rules for file `v2.0/source/PROFIL.ASM` in the MS-DOS repo. Search query is “shit”, and the results show two results matching with the symbol “DOSHIT”.

26 April at 10:28 | Open on mastodon.social

@calamari I saw it and it's probably "DOS" "HIT" so I skipped it.

26 April at 11:58 | Open on mastodon.social

Stuart

26 April at 11:59 | Open on mastodon.social