#160 WING ZERO PORTABLE#
Joe on 2023 Cyberdeck Challenge: KOAT0 Portable Terminal.hartl on Going To Extremes To Block YouTube Ads.
Mungojerry on Impulse Buying A 3040 CNC Machine, What Could Go Wrong?.YGDES on Text Compression Gets Weirdly Efficient With LLMs.Timo on Luna 25’s Demise: Raising Fundamental Questions About Russia’s Space Program.Tenaja on Going To Extremes To Block YouTube Ads.Le Roux Bodenstein on Going To Extremes To Block YouTube Ads.imqqmi on Going To Extremes To Block YouTube Ads.Smart Garbage Trucks Help With Street Maintenance 40 Comments However, it’s going to return the same results for other potential sets of four keys on the keyboard, which could explain the behaviour you’re seeing. It’s a clever way to distinguish between 4 different keys using only 2 tests. Since the display is operating in 80×25 text mode (2 bytes per character), this would be equivalent to moving left or right 2 characters (-4 or +4), or up or down 1 line (-160 or +160). The net result is that BX will have one of four different values depending on which key was pressed: 4, 160, -4, or -160. the jz causes the next instruction to be skipped if either UP or LEFT is pressed.
“and al, 0x14” clears the zero flag if DOWN or RIGHT is pressed, and sets it UP or LEFT is pressed. the JP instruction causes the next instruction to be skipped if parity is set, meaning either left or right is pressed. “and al, 0x1E” sets the parity flag if LEFT or RIGHT is pressed, and resets it if UP or DOWN is pressed. These are scan codes, and the codes for the arrow keys are as follows: > we found different keys responded on machines with different keyboards we’re curious how it does its keyboard input Posted in Games Tagged assembler, qr code, snake Post navigation We would be interested to hear the views in the comments of readers who know something about x86 assembly, to help explain these points. Also we think it has the Snake bug where turning back on yourself means instant game over.
#160 WING ZERO CODE#
To achieve a working game in so little code is an impressive feat, and since we found different keys responded on machines with different keyboards we’re curious how it does its keyboard input. The web version is more usable, and allows us to investigate its operation more thoroughly. We followed the compilation instructions and got it running on our Manjaro installation, with the result of a somewhat unplayable but recognisable Snake, we’re guessing because it was written for a slower platform. It fits far better in a QR code than the previous effort, but perhaps more useful is a web page demo which runs an in-browser DOS compatibility library. We’re not sure that many of you have recognised the need in your life for an x86 machine code program encoded into a QR code, but following on from someone else work has created a super-tiny Snake clone in assembly which comes in at only 85 bytes long.
0 kommentar(er)
