MsxHub first beta release. Call for help | MSX Resource Center (Page 2/5)

Expert (112)

21-08-2018, 08:02

That scrambled output is very strange. It looks like the problem starts happening in the "User-Agent" line, right when the string for the UNAPI version is printed. I think there is a bug at the function that's fetching the UNAPI version string. For some reason it's working on my card but it's not in GR8NET... I'll have to investigate it further...

By fr3nd

Expert (112)

21-08-2018, 08:10

Manuel wrote:

What's next? And xboard client for MSX?

xboard sholdn't be very difficult to implement (if it's using http instead of https). A client for playing GO would be a nice too

I've always wondered why there isn't more internet-related software for the MSX... we've had network cards for a long time, however there isn't a lot of software available.

By Sylvester

Hero (579)

21-08-2018, 08:35

Found the problem for the GR8NET, in the get_unapi_version_string() function i removed the buffer from:

sprintf(unapiver, "v%i.%i", version_main, version_sec);

Then everything works. The buffer contains the strange chars, don't know what it should display with other network cards. It now shows "v0.7" in my version.

By Sylvester

Hero (579)

21-08-2018, 08:54

Ah, I see in the specs it should contain a name:

An API specification must have an alphanumeric identifier composed of up to 15 characters. Allowed characters are letters (having an ASCII code below 128), digits, and the following ones: - _ / . ( )
The API identifier is case-insensitive, so for example, "ETHERNET" is the same as "Ethernet".

So it looks like this isn't correctly implemented in the GR8NET because it contains some random chars including control chars.

By fr3nd

Expert (112)

21-08-2018, 09:35

I see.. thanks for the help! I've compiled a GR8NET specific version of the client app while I think for a definitive solution. Find it here:

http://msxhub.com/hub-gr8.com

By Sylvester

Hero (579)

21-08-2018, 09:40

I asked Eugeny (creator of GR8NET) to have a look at it why the identifier doesn't work.

By fr3nd

Expert (112)

21-08-2018, 10:53

Sylvester wrote:

I asked Eugeny (creator of GR8NET) to have a look at it why the identifier doesn't work.

Thanks!

By ToriHino

Paladin (828)

21-08-2018, 19:46

fr3nd wrote:

I see.. thanks for the help! I've compiled a GR8NET specific version of the client app while I think for a definitive solution. Find it here:

http://msxhub.com/hub-gr8.com

This link doesn't work, i took however the latest one from GitHub and that works fine for GR8NET.

By Sylvester

Hero (579)

21-08-2018, 21:37

Cool, Eugeny just released a new update.bin firmware file that fixes the problem.

The debug now shows: GR8NET LAN adapter build 20180821 v0.7

So you could update the readme with a FAQ that if people have a GR8NET and get garbage when performing hub /d list, they should update the firmware to 20180821 or newer

By karloch

Prophet (2159)

22-08-2018, 02:22

Sylvester wrote:

Cool, Eugeny just released a new update.bin firmware file that fixes the problem.

The debug now shows: GR8NET LAN adapter build 20180821 v0.7

So you could update the readme with a FAQ that if people have a GR8NET and get garbage when performing hub /d list, they should update the firmware to 20180821 or newer

So far so good! Working like a charm in the GR8NET after this update:

It is a bit annoying that every package install as a directory in root; but I love the package manager idea and it looks promising!