Great!
I really want that cart, but I'm not skilled in hardware, so what can I do?
Is it possible to contact a hardware company that could make such board? (any suggestion?)
Is that documentation enough and complete?
I am tired of producing obsonet sincr denyonet is already ready. Especially konamiman knows that The Pcbs are soldered and jack tresoor is making the cases ready.
Meanwhile I am busy to get the mac-addresses for it.
I wondere why we invest always a lot of money for MSX and it is not enough !
@sunrise: I think that you should not worry. Denyonet is a much better product than Obsonet, and you are producing a very high quality product, with professional PCB, case and box; not to mention that it handles TCP/IP internally which results in a much faster networking transfer speed. I would say these are very different products. And of course I recommend anyone to wait for a Denyonet instead of building a Obsonet (and I know both products very well).
Just a remark: caro, I see in the screenshoots that you are using "InterNestor Lite for Obsonet 1.02". I hope you know that this version is discontinued, you should use InterNestor Lite 2 instead (with ObsoNET BIOS 1.1) that implements the TCP/IP UNAPI specification and will let you use the latest networking applications developed.Yes, I know, but on mine YAMAHA YIS503III with the external disk drive FD-051 MSXDOS2 is not loaded.
I wil buy one for sure ...I realy like to connect my MSX with a Denyonet.. Hopefully it will avilible for us!!
@konamiman & caro
1) Why isn't there any IRQ connected on the ObsoNet? Wouldn't it help to get a better throughput?
2) Did the original ObsoNet had IRQs?
3) Does the ObsoNET BIOS uses IRQs? Is it possible to support both interrupt-driven and polling versions?
BTW: great work, caro!
@sd_snatcher: IRQ was not used because it would have implied a complication in hardware and software with no real benefit. InterNestor Lite uses polling, handling one packet on each timer interrupt; this gives a maximum processing rate of about 33KByte/sec (the maximum datagram size handled by INL is 576 bytes), do you really think that a MSX is capable of handling much more than this?
Denyonet is a completely different story, as it deals with the packet processing in hardware and applications must simply process the received data (or generate and send new data) as fast as they can/want.
@konamiman:
Humm, but wouldn't the Turbo-R or even turbo-Z80 machines be able to perform much better? I kinda like the ObsoNet idea because it's simple and the RTL8019 is cheap, still somewhat easy to find in any pile of ISA network cards, and can be DIY produced by the laserprinting process. :)
For the future use, I have added in the circuit an opportunity of work on hardware interruptions.
@caro: wonderful! Thanks!