Hyperion Entertainment Message Boards

In System Info it says NULL for "MAC Address" and "MAC Address 2" so I guess there's something wrong with the network card? What should I do now? Contact my dealer about it?

The description of this card should show up once connected in the primary network options . Well, it doesn't. The only cards listed are: dummy0, ip6_vti0, ip6tn10, ip_vti0, tun10. And none of them works :-( It always fails during DHCP configuration although my network is configured to use DHCP and ...

Ok, I've now arrived at the network configuration screen. Two questions about that: 1) Where does the network cable go? There are two connectors for that on my X5000. One is at the top next to the USB ports and the other is below the sound board, probably from an additional network card inside the X...

So where have all the download links to Ubuntu for the X5000 gone? I wanted to install Ubuntu on my X5000 according to the following tutorial: https://amigax5000.blog/2017/07/23/installing-linux-on-the-x5000/ ...but the links to the image files are all dead. Also the links to the image files in this...

@broadblues: Thanks for the pointer!

What's the best way to generate strong random numbers on OS4? It needs to be applicable for cryptography-related contexts so things like srand(time(NULL)) and rand() obviously don't fit because they are never random enough. MorphOS has random.library which does a pretty good job here. Is there an OS...

I've fixed both STRINGA_MaxChars and REQS_MaxChars entries to make it clear that space for the nul-terminator needs to be included in the character count. In other words, both xenic and broadblues are wrong, just to make that clear again in case people dig up this thread later. No need to make thin...

broadblues wrote:so if you need to enter 10 chars then REQS_MaxChars must be 11 (and the buffer must be 12 )

Why must the buffer be 12 bytes to enter 10 chars? Does it write two null terminators?

xenic wrote: I don't see the problem.

The problem is that the documentation is wrong. Of course it would be utter non-sense to change the behaviour of REQS_MaxChars and break binary compatibility but the documentation needs to be fixed because what it currently states is wrong.

I think the autodoc on REQS_MaxChars is wrong. It says: Maximum number of characters in string gadget. Must not be larger than size of REQS_Buffer - 1. Defaults to 127. In reality, however, REQS_MaxChars seems to require the buffer size of REQS_Buffer and not the buffer size of REQS_Buffer minus 1. ...