Ask Woz Anything on Slashdot

[D Finnigan <dog_cow@macgui.com>]

Here's your chance to ask the Woz some questions for an interview on
Slashdot.

To kick-off our [Slashdot's] 15th anniversary month, Woz has agreed to take
some time to answer a few of your questions; as with other Slashdot
interviews, you're invited to ask as many questions as you'd like, but
please ask them in separate posts. We'll be running a number of other
special interviews this month, so keep your eyes open.

http://apple.slashdot.org/story/12/10/01/1527257/ask-steve-wozniak-anything


Here is a sample question posted by cje:

"Anybody who programmed the Apple II back in the 1980s is familiar with the
interleaving "venetian blind" effect due to the relationship between
locations in both the text/low-resolution and high-resolution video RAM and
their actual locations on-screen. I seem to remember reading that this was a
conscious design choice by you early on and that it resulted in somewhat
simpler hardware. Can you shed some light on how the Apple II's graphics
structure came to be?

I spent so much time writing code to generate lookup tables to map locations
in video RAM to their on-screen counterparts that at one point I had the
hexadecimal 6502 machine language sequence memorized. This, sadly, is now
gone (replaced by quotes from Seinfeld reruns and meaningless football
statistics.)"

-- 
]DF$
Apple II Book: http://macgui.com/newa2guide/
Mac GUI Vault: http://macgui.com/vault/
Usenet Archive: http://macgui.com/usenet/