quietust wrote:
Technically, you could get away with just using $4016 D1/D2 for output and $4017 D1/D2 for input without conflicting with any controllers, and you'd get Famicom compatibility as a bonus (using its smaller expansion port).
dwedit wrote:
The Miracle Piano Teaching System game uses the strobe signal of controller port 1 to send midi data to the instrument.
It looks like using the 8-bit data bus will work. I think I'm going to try to use that, as it's much faster.
tepples wrote:
The problem with a telnet client is the difficulty of text entry: The NES (as sold in Latin-alphabet countries) has no alphabetic keyboard.
That is a problem, as using an on-screen keyboard is really annoying.
bunnyboy wrote:
You will find the net stack far more difficult than the hardware or low level driver software. UDP and DHCP are pretty basic but TCP is way complex. If you are using a proxy you can cut out some of the stuff like reordering but it is still messy. Frequently games will use UDP and add their own system to make sure messages are received, but web browsers/servers and telnet clients fully use TCP.
Luckily, the full net stack is more in what I'm experienced, as opposed to the low-level hardware stuff. There's some a few good embedded stacks out there, such as the one for Contiki. Still, you're right, it's going to be quite a challenge working with the limited NES power.