Donated 15 euro. I just bought a picasso IV card so short on money.

Last edited by joeled on 02-Feb-2012 at 08:51 PM.

_________________
AmigaOS on Google+
AmigaOS on Facebook

@joeled, all
Thanks for the donations!

We're only EUR 39 short now, can we get it before midnight??

_________________

@Skuggan

I didn't think it would be possible to beat Djnick's record... speaking of which I wonder if he has received his system yet.

_________________

@djrikki
I had some talks with Nick about alternative ways to get him a system so he could avoid the huge tax that gets added once the system hits Serbia. Sadly they didn't work out so we will probably go for just the board and he can assemble his own system.

_________________

@Troels
But as far as i remember, we imho talk about plain mb+cpu+os4 from the begining, pluse money for fits the taxes for send that, that was not about full mobo initially. Did it was changed lately and you with nick was in hope for sending a full mobo ?

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@Skuggan

Good job on this. This is what we need in the community

@joeled

i got a cybervision if u want it, i can send it to you for free.
not sure what MK it is but i can check :)

_________________
See my blog and collection website! . https://www.blog.amigaguru.com

@Toaks

Check pm

_________________
AmigaOS on Google+
AmigaOS on Facebook

WOW!!!

Spotify is really a great thing to have...already use it now because of this thread.

BRING IT ON TO AOS

_________________
On Planet Boing Trevor is God

Argh!

We need 94 cent!

_________________
5*C-64, C128, A500, A1200 PPC, Micro-A1(sold).....and X1000

@Skuggan

Quote:

They will code the library and a small player. Then we can vuild a nice front end using the library or shared object.

Great! So much easier for them

And I didn't even get time to donate and it's already fulfilled

I'll put some money on DOpus Magellan then... it's kind of steep though..

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

@all

Great work everyone. Especially those who contributed most money. :)

We need a couple of more things:
Contact with developers who can support in the TCP/IP communication, accessing audio in most efficient way, and of course GUI building.

I'm thinking we should supply templates for all this. In this way they can get it all working faster.

One thing worries me. Some include files like nameser.h and nameser_compat.h is really outdated
and we are missing some key structs like addrinfo and relevant functions.

I have updated the files somewhat and got the despotify to compile to 98% but I'm guessing
the spotify will have this problem also.

Who of us is best in fixing these issues? Olaf?

@Skuggan

Try contacting ssolie. I bet he can fix you the different guys from the devs to help you.

_________________
I'm an antique. Don't light my fuse

@Skuggan

DeSpotify and Spotify is not made by the same people.

But yes outdated TCP/IP stack is most likely the biggest problem, but it is possible to work around like we talked about.

But I agree, the TCP/IP stack and the SDK needs to be updated, and Hyperion should do that.

Building a GUI that’s the easy part, the only problem is that needs to integrated whit there program in a model way so it can be part of the source code depository.

Last edited by NutsAboutAmiga on 04-Feb-2012 at 02:27 PM.
Last edited by NutsAboutAmiga on 04-Feb-2012 at 11:58 AM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@Skuggan

i have sent a mail to olaf (and sdk team) about this, i'll keep you posted.

_________________
See my blog and collection website! . https://www.blog.amigaguru.com

@Skuggan

Quote:

One thing worries me. Some include files like nameser.h and nameser_compat.h is really outdated and we are missing some key structs like addrinfo and relevant functions. I have updated the files somewhat and got the despotify to compile to 98% but I'm guessing the spotify will have this problem also. Who of us is best in fixing these issues? Olaf?

You rang?

I read about the problems on the internal OS4 beta testing list, after toaks posted them, and to make a long story moderately shorter, you're probably going to be out of luck. Problem is that the TCP/IP stack's public data structure definitions were frozen at the time the API was designed. Which was, uh, around the time "TCP Reno" was new and Ronald Reagan was approaching the end of his second term as President of the United State of America.

The good news is that the TCP/IP stack in OS4 isn't quite that old. The bad news is that the data structures are what they are, nothing more, nothing less. The reason why there is no "struct addrinfo" in "netdb.h" is that this sort of thing was years away from getting invented (IPv6 was 4-5 years away from being christened "IPng" back then).

Also, the name resolution API in the AmiTCP "bsdsocket.library" just does not carry anything even remotely like it. The API exposed by the AmiTCP name resolution functions is pretty close to the very earliest stub resolver code "spitballed" by Paul Vixie and friends.

So, in so many words, you're stuck with an API that is even older than NeXTstep, and that's something (there's no Spotify for NeXTstep, is there?). Not knowing the code you are trying hard to get working properly, I suspect that the only robust solution might be to use conditional compilation, like in the old days when "#ifdef AMIGA .. #endif /* AMIGA */" graced many a great application

@NutsAboutAmiga
Quote:

DeSpotify and Spotify is not made by the same people.

I dont know what you take me for but yes. I figured that out ages ago.

@olsen
Yes. the nameser.h is very old but there is alot of different versions. The best I could find was
from MacosX with no additional copyight text.
Its not like we can give up because of an obsolete include file.
I was more into if we should think this throught together.

@Skuggan

Quote:

@olsen Yes. the nameser.h is very old but there is alot of different versions. The best I could find was from MacosX with no additional copyight text.

Let's see... I suppose that might be the version that was produced by the ISC, aka the bind maintainers. It contains data structure definitions and constants for use with the stub resolver in libresolv.a. As such it is specific to the library being used. Since the AmiTCP API does not expose the same set of functions as are found in the common libresolv.a you will not be able to make use of them on the Amiga. This is also the reason why there is next to nothing useful in the AmiTCP "arpa/nameser.h" header file.

Quote:

Its not like we can give up because of an obsolete include file. I was more into if we should think this throught together.

Sure

Regarding the DNS API, the only relevant data structure definitions for use with the AmiTCP API are in "netdb.h". There is no other header file which would be helpful here.

@olsen

All the respect to you Olaf but we must see solutions instead of more problems.
Who is responsible for AmiTCP?
Can and will you assist the spotify team?

Right now I'm trying to connect the right people and arrange hardware setup for the developers.

@Skuggan

Quote:

Skuggan wrote: @olsen All the respect to you Olaf but we must see solutions instead of more problems.

"Find solutions", I suppose

Quote:

Who is responsible for AmiTCP?

Nobody. To the best of my knowledge, AmiTCP product development ceased completely more than a decade ago, and the product is no longer for sale.

To clarify, when I wrote about "AmiTCP", I was referring to the API definition introduced by the product, and not to the product itself.

The AmiTCP API is the de-facto standard for IPv4 networking client/server software on the Amiga (AmiTCP is to the Amiga what Winsock is to Windows). It defines what such software can do, and what it cannot do.

The issue here is the "what it cannot do" aspect. Unlike the Winsock API I mentioned above, nobody is in charge of laying down what the AmiTCP API should or should not provide. Due to compatibility concerns (practically all Amiga IPv4 networking software uses the AmiTCP API), it cannot be changed. The kind of functionality available in AmiTCP in the early 1990'ies is exactly what is available today in Amiga TCP/IP stacks such as MOSnet, NetStack and Roadshow, to name just three.

Quote:

Can and will you assist the spotify team?

Yes.

But there are pratical engineering limits to what can be done within the framework defined by the AmiTCP API which I cannot make go away.