DEF SEG = 0

[relsoft]

When I call that, what happens when let's say I call
Peek(1024)? Where


Am I peeking at DATA + 1024?

thanks!!!

[Plasma]

It's just segment 0. So you are peeking at 0000:0400. (Which happens to be the start of the BIOS Data Area.)

[relsoft]

So I could read the BIOS by peeking? Yeeehaaaa!!!!

Do you have some info on what is inside the bios that I could read?

[Dr_Davenstein]

What the hell are you doing now? :lol:

[Plasma]

Well, the actual BIOS code is in segments F000-FFFF, but here's the info you can access from the BDA: http://www.phatcode.net/res/236/files/ht..._area.html

[relsoft]

What the hell are you doing now? :lol:

Oldskool crap. :*(

But I get pais for this. :*) hehehehehehe

[RyanKelly]

You should note that much of the BIOS data area is provided for backwards compatibility. Most new BIOS code and most emulator code simply updates the BIOS data area, but does actually use it the way earlier code did, so some tricks like poking character into the type ahead buffer don't work the way you might hope.

[Plasma]

While it's true that many entries in the BDA are no longer relevant, I have yet to see a BIOS or emulator that ignores the keyboard buffer in the BDA. This would break a ton of existing programs. Even NTVDM supports poking keystrokes to the buffer.

[RyanKelly]

Have you tried it recently? You can read the buffer, but in my last experiment with NTVDM, anything I poked into the buffer (along with adjusting the head and tail) had no effect on BIOS keyboard services. If you have an example that works, I'd like to see it.

[Plasma]

http://forum.qbasicnews.com/viewtopic.php?t=8632#98103