This - having your game frozen but still visible in a mummified state behind an incomprehensible wall of DOS4GW error report, leaving you stranded in an uncanny DOS prompt that’s the wrong size (Credit to Gered at blarg.ca/2019/10/20/a...) - ThreadSky

About ThreadSky

davidxnewton.bsky.social • 34 days ago

This - having your game frozen but still visible in a mummified state behind an incomprehensible wall of DOS4GW error report, leaving you stranded in an uncanny DOS prompt that’s the wrong size (Credit to Gered at https://blarg.ca/2019/10/20/amazing-3-d-games-adventure-set)

Comments

dosnostalgic.bsky.social•34 days ago

philbennett3d.bsky.social•34 days ago

Very accurate; glad to see it wasn't just me...

comchia.bsky.social•34 days ago

I actually like that big DOS font, even used it in an RPG project in PyGame, but yeah, total nightmare fuel when DOS is acting up.

eggbetr.net•34 days ago

dos error screens are a classic

morhook.bsky.social•34 days ago

Classic VGA mode 0x13 (0x10) and using normal 240x200 (0xa0000000 Address).

jcdenton.xyz•34 days ago

As a kid I learned how to set the display mode in QBASIC and I still remember setting SCREEN 13.

morhook.bsky.social•34 days ago

Yeaps. From QBasic you can still call VGA mode also!

ktpanda.org•34 days ago

I was going to say something like "Oh of course, EBX is 82914001, it should be 82914002" but I noticed EBP is only 28 when it's usually close to ESP. Since it's saved to the stack on entry to most functions, my guess is there was an overrun in a stack allocated buffer that clobbered the saved value.

ktpanda.org•34 days ago

Then the parent function tries to access one of its parameters at [EBP+8] or something, causing it to crash.

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply