Ethernet cartridge for MSX
Sounds like a nice Ethernet UNAPI BIOS could be made for this toy... any volunteer? 
Note anyway, that by using the Ethernet UNAPI you are not using the embedded TCP/IP processing capabilities of the W5100. But it would be a good start anyway.

Note anyway, that by using the Ethernet UNAPI you are not using the embedded TCP/IP processing capabilities of the W5100. But it would be a good start anyway.
Great project! The PCB looks fantastic. And by the way, I love your telly. I grew up with one like this in the eighties.
Great prototype you have made! 
Nice!

Nice!
I like 2..
I'm currently busy with streaming radio. 
But it's a lot of work. So if you have info about it... please let me know.
So nice to have a mp3 player.

But it's a lot of work. So if you have info about it... please let me know.

So nice to have a mp3 player.
Great!!!! I like one ^^! But I will buy the next batch: the coders first
Very nice! finally an ethernet interface for MSX. I know there were some others (obsonet e.g.), but they never were mass-produced. Even Sunrise hasn't finished their Dumas interface yet. Please keep it as simple as it gets... no rs232 built within or so...
Hopefully you can give order information soon.
Hopefully you can give order information soon.
This is fantastic!! I would like to buy one as soon as possible
Unfortunately there are only 5 now and there is no real software yet, indeed it would be better to give programmers a bit priority. I think i should make a new picture of the final version...
UNAPI would be a good solution to make existing software running with this card, maybe some parts of the 'low level' header should be recomposed again in software because it is removed by hardware... Existing software expects more data about protocol information and maybe checksum.
To make advantage of the performance, software should leave more to the hardware. The way of thinking is a bit different, this cartridge must be told what to expect or what to send. Software which only listens to the ethernet won't receive anything, a protocol and port must be specified first, then the cart can be set up to 'listen' mode. This for four protocols and ports at the same time. If something is received or the controller has finished sending data, it can give an interrupt or the user can poll status registers. In this case, software does not have to check the port number or protocol.
I have spend some time with ethernet viewers as 'Commview' and 'Show traffic' to find out what's happening with shoutcast. I think a lot of overhead in the TCP protocol will also disappear, like ACK, SYN and SYN ACK to keep the connection alive, these things are time consuming for a Z80. Streaming audio is probably more difficult than a DHCP tool, i have tried a few things weeks ago but no response from the server. It seems the PC sends a TCP package of 0 bytes to the server to initiate shoutcast (?). I did not receive anything from the server, after that time i focused on hardware again.
UNAPI would be a good solution to make existing software running with this card, maybe some parts of the 'low level' header should be recomposed again in software because it is removed by hardware... Existing software expects more data about protocol information and maybe checksum.
To make advantage of the performance, software should leave more to the hardware. The way of thinking is a bit different, this cartridge must be told what to expect or what to send. Software which only listens to the ethernet won't receive anything, a protocol and port must be specified first, then the cart can be set up to 'listen' mode. This for four protocols and ports at the same time. If something is received or the controller has finished sending data, it can give an interrupt or the user can poll status registers. In this case, software does not have to check the port number or protocol.
I have spend some time with ethernet viewers as 'Commview' and 'Show traffic' to find out what's happening with shoutcast. I think a lot of overhead in the TCP protocol will also disappear, like ACK, SYN and SYN ACK to keep the connection alive, these things are time consuming for a Z80. Streaming audio is probably more difficult than a DHCP tool, i have tried a few things weeks ago but no response from the server. It seems the PC sends a TCP package of 0 bytes to the server to initiate shoutcast (?). I did not receive anything from the server, after that time i focused on hardware again.
Nice!!
Me like spl. Coders first.
I will be really hapy If will be Internestor compatible with an UNAPI bios






Me like spl. Coders first.
I will be really hapy If will be Internestor compatible with an UNAPI bios







By DD
Expert (88)
12-05-2009, 16:07