You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw this interesting bug a while ago but I didn't know how to reproduce it reliably until now.
Open DOS prompt on Windows 98/95. If you give your keystrokes enough delay, the cursor loves jumping backwards and does interesting things. What could this be?
Here's a little gif demo. Grab some popcorn.
I'll just dump a couple more observations...
You can see that when the glitch occurs, the previous command / stdin is partially reused:
On Windows 95, reading from console stdin (via type con) illustrates this:
On Windows 98, reading from console stdin (via type con) closes abruptly with random artifects:
Notice how the garbage text jumped back into the previous line. It's supposed to look like this: (typing the exact same thing in VirtualBox)
The text was updated successfully, but these errors were encountered:
Interesting find. This is probably a CPU bug, so I'd set a breakpoint in the keyboard interrupt trigger and in the cycle function and then step through it, inspect registers using cpu.debug.dump_regs and load a memory dump in IDA to get an idea of what the code is doing and where it goes wrong.
It seems like it could be related to the handling of carriage returns, since the cursor jumps to the beginning of the line.
Sorry I couldn't offer much help at the moment. I'm pretty inexperienced with assembly, so I had difficulty locating the code of interest starting from the keyboard handler routine. This sounds fun though, so I might give it a more persevering attempt when I have time later this year - if it's not fixed by then.
I saw this interesting bug a while ago but I didn't know how to reproduce it reliably until now.
Open DOS prompt on Windows 98/95. If you give your keystrokes enough delay, the cursor loves jumping backwards and does interesting things. What could this be?
Here's a little gif demo. Grab some popcorn.
I'll just dump a couple more observations...
You can see that when the glitch occurs, the previous command / stdin is partially reused:
On Windows 95, reading from console stdin (via
type con
) illustrates this:On Windows 98, reading from console stdin (via
type con
) closes abruptly with random artifects:Notice how the garbage text jumped back into the previous line. It's supposed to look like this: (typing the exact same thing in VirtualBox)
The text was updated successfully, but these errors were encountered: