Welcome, Guest. Please login or register.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Prodatron

Pages: 1 2 3 [4] 5 6 7 8 9 10 11 ... 17
Hardware / Re: Wiznet 5100/5300 /etc and Enterprise
« on: 2015.July.05. 14:27:32 »
But I think SymbOS needs generic, SymbOS-platform-independent DHCP implementation anyway user can modify settings also other platforms may not have this job done already, etc etc ...
Yes, exactly. As soon as there is EXOS support for EPNET it makes sense to set the IP and DNS config there (including DHCP usage).
On the MSX there is a tool for MSX-DOS for this task as well, but it is optional.
The Amstrad CPC probably won't have this (at the beginning).
So it's necessary to have it in SymbOS, too. DHCP is a nice "nice to have" feature :) but it makes the whole solution more completed.

Hardware / Re: Wiznet 5100/5300 /etc and Enterprise
« on: 2015.July.05. 13:34:52 »
Great, thanks LGB and Bruce for the clarification! These are good news, transfering data will be very fast!
I am currently working on the DHCP implementation, but as soon as it makes sense I can start with the W5300 driver for the Enterprise.

Hardware / Re: Wiznet 5100/5300 /etc and Enterprise
« on: 2015.July.04. 22:26:29 »
I am a little bit confused as well. Currently I can't find any information about address-auto-incrementation. Wouldn't that mean, that even when reading/writing from/to the RX/TX buffer you have to update the address after each word? That would slow it down indeed. It's not a tragedy, but I wonder, why they should have leave this feature. The W5100 supports it, so I can't believe that they forgot it for the W5300.

Regarding fast data transfer:
That was my first thought if auto-incrementation would work:

LD C,dataport
LD HL,destination (256 byte aligned)
repeat {
INC L:INI:DEC L:DEC L:INC C:INI:INC L:DEC C  ;16microseconds/word = 8microseconds/byte (CPC; no idea about the exact EP timing)

Usually you only have 5 microseconds/byte (CPC way), but I think it would be still ok. Without auto-incrementation it would be indeed slower by a factor of maybe 4 or so?

Hardware / Re: Wiznet 5100/5300 /etc and Enterprise
« on: 2015.July.04. 18:42:11 »
My idea would be to do some kind of self modification on start-up for the I/O ports used inside the code (after the detection when you know what they would be modified to ...).
This is what I would do in any case. At least my W5100 driver for the Amstrad CPC (which would use indirect I/O as well) only has two routines, which really have to deal with the base I/O port: setup the address and return the data port; one for register memory access, one for RX/TX buffer access. The W5300 shouldn't be much more complex. So such an I/O port "relocator" is not a problem at all.

Hardware / Re: Wiznet 5100/5300 /etc and Enterprise
« on: 2015.July.04. 17:59:15 »
Isn't there a map of all known I/O ports for the EP? Or are I/O ports handled in a dynamic way all the time for additional hardware expansions?
On the CPC and even the MSX (but they usually use their memory mapped based slot system) I/O addresses of hardware expansions are always fixed, and we have this table to prevent conflicts between existing and new hardware.
But it's not a problem to detect the I/O port while booting SymbOS or to add them to the Network Daemon setup tab.

Hardware / Re: Wiznet 5100/5300 /etc and Enterprise
« on: 2015.July.01. 14:23:38 »
Congratulation Bruce! These are fantastic news!
I want to play battleship on my EP against another Z80, soon :P

Programming / Re: SymbOS
« on: 2015.June.29. 00:07:24 »
SymbOS 3.0 beta with ethernet network support is available now. You can download the full package here:


It seems that network support is introducing a complete new world for a multitasking environment on a 8bit Z80 machines. The amount of possibilities is still crazy and so we have quite a lot of new apps, which have been added during the last weeks.

The package includes the following:


What is included

- SymbOS 3.0 beta
- Control Panel
- SymShell 2.0 beta

- DenYoNet driver
- Localhost driver

- Battleship
- Symple messenger

- SymTel
- WGet
- NsLookUp
- NetStat
- Nettest

For more information please read the included #readme.txt.

Programming / Re: SymbOS
« on: 2015.June.27. 23:21:21 »
I would appreciate it a LOT when you would do W5300 emulation in XEP128! Even if it wouldn't be 100% accurate it still helps us so much to speed up ethernet support for the EP! The modifications, which would then be needed for Bruces' upcoming hardware would be only limited to the little low-level driver routines, so that's not a problem at all. It's always cool to have the software already finished, before the hardware is available :P I am very interested in the exact data how to access the emulated W5300 and in writing and testing a driver with the help of your emulator! (I was already writing a driver for a planned Amstrad CPC W5100 project, which doesn't exist yet :) )
Regarding interrupts:
No, good news, SymbOS doesn't use them as well. It polls the active sockets, and with the W5300 it will be the same. So no sweat here! :)

Tomorrow we will have a beta release of several SymbOS network stuff, so the timing is great! :D

Programming / Re: SymbOS
« on: 2015.June.19. 12:20:16 »
I only thought that I can detect somehow that SymbOS tries to test if joystick presents
Ah, I got you. SymbOS checks, if it always returns X+1,Y+1 from the mouse. When it receives 16times a movement of X+1,Y+1, then it is sure, that a joystick is connected and not a mouse.

Programming / Re: SymbOS
« on: 2015.June.19. 10:56:09 »
That's true, it detects the mouse during startup. It has to decide if it will handle the signals from control port 1 as coming from a joystick or from a mouse. If it's a mouse, it will stay in mouse mode, otherwise it will stay in joystick mode. For the MSX version I added a key combination to start this detection later again. It seems, that I have to do the same for the EP now, too :)
I never had this problem with MSX emulators btw. Here you always choose in the settings, what is connected at which control port (joystick or mouse or nothing). Can't you do the same in Xep128?

Programming / Re: SymbOS
« on: 2015.June.15. 21:29:22 »
So do you emulate these 6 ports exactly (maybe only in TCP mode)?

Programming / Re: SymbOS
« on: 2015.June.15. 21:09:51 »
IIRC Bruce is using the indirect access, which is working with I/O ports. Did you already ask Bruce how it will be accessed?

Programming / Re: SymbOS
« on: 2015.June.15. 20:39:03 »
You already implemented W5300 support in your new emulator?? When you send me the specs we can try some tests! :)

Programming / Re: SymbOS
« on: 2015.June.15. 00:25:48 »
During the last days a lot stuff happend. The Network Daemon is now fully configurable, and the new "Driver" tab shows the status of the LEDs of the currently used MSX W5100 card. EdoZ made a little video for demonstating this:


You can see, how especially TX, RX and Link react on EdoZ char typing in the Telnet console.
At the same time Trebmint completed a huge part of the network support in the Unify IDE. That made it possible to write a simple but fully working internet messenger, called the "Simple Messenger", for SymbOS with Unify, which only consists of 30 lines of code - the initial development took 5 minutes

And so today we were able to have this very special moment: I started two instances of the messenger as a server on my 8bit machine in Germany, and EdoZ from The Netherlands and NYYRIKKI from Finland connected as clients from their Z80 computers directly over the internet. So I had two chat sessions running on my Z80. As this worked well, NYYRIKKI and EdoZ opened a direct chat session as well. All three MSX were connected to each other at the same time!

(click to enlarge)

(click to enlarge)

TBH we had a lot fun again today!

But as I want to have it running everywhere I also created the "localhost" driver this week. It already supports TCP and a fake kind of DNS, which is fine for 90% of the apps.
This was a test on the Amstrad CPC:

Let's keep this all finished for a beta release end of this month And I am looking forward so much to the EP ethernet hardware!! (since April all work on this project is completely platform independant, so every line of code is for the EP as well!).

Other topics / Re: MSX Computers
« on: 2015.May.25. 22:33:31 »
Yes, thanks. It seems to be a bit strange, but I can imagine it's because of backward compatibility (on MSX2, with MSX) and similar things.
Even the MSX1 is already able to handle the whole slot system (as subslots are handled by the expansion hardware AFAIK). In theory it would be possible to have an MSX1 running SymbOS with the G9K graphic card and 1MB ram. We never tried it, and the loader will stop when detecting only an MSX1, but it should work.

Pages: 1 2 3 [4] 5 6 7 8 9 10 11 ... 17