Can't connect with bsdsocket.library error (WinUAE 2.5.0)

[arti]

Thank you Toni for another awesome release.

Is there any option needed to be checked for interet working ?

It doesn't work since 2.4.1. I am using AmiKIT.

[Toni Wilen]

Some security/firewall software blocking it because executable changed?

[Mozzerfan]

On my systems bsdsocket emulation doesn't work with winuae 2.5.0 when using z3-fastram > 128 MB.
It used to work ok with 2.4.1.

Edit: BTW Thank you Toni for your hard work on WinUAE.

[Toni Wilen]

Works for me.

Logs need and what "doesn't work" mean?

[Mozzerfan]

Originally Posted by Toni Wilen

Works for me.

Logs need and what "doesn't work" mean?

With a z3-mem setting of anything greater than 128mb the program that tries to connect to the internet forever tries to make a connection. I get no errormsg, nothing. For example, when I try to retrieve my email, all I get is trying to connect to etc. etc.

When I set the z3-mem at 128 mb, everything works normal again.
I can retrieve my email, I can surf the web etc. etc.

I attached the log-files.
The first is with 128 mb z3mem, the second is with 256mb z3mem.

Thanks for looking into this.

Edit: I have installed 2.5.0 on 3 different systems and all systems have this problem.
On my desktop PC I get a msg from aweb that a tcp/ip stack must be started first (with z3mem greater than 128mb). On my other 2 systems it just tries to make a connection.

[Toni Wilen]

Originally Posted by Mozzerfan

On my desktop PC I get a msg from aweb that a tcp/ip stack must be started first (with z3mem greater than 128mb).

Get a log using this system, use -bsdlog command line parameters, thanks.

[Mozzerfan]

Originally Posted by Toni Wilen

Get a log using this system, use -bsdlog command line parameters, thanks.

Done ! Thanks again Toni.

[Toni Wilen]

Hmm.. Perhaps you are hitting 32-bit Windows memory limits. (Memory reservation is now different)

Does it also work if you reduce other memory type like mainboard RAM to zero and keep Z3 RAM at 256M?

EDIT: Also add log using 256M config with 2.4.1. (no need for full log, boot without startup-sequence and quit emulation)

EDIT2: Seems to happen when more RAM is configured than reserved (Memory info in Memory panel). It should only reduce memory size, not cause strange side effects.. (Also reserved size is too small, it should have been about 700M, not 512M)

[Mozzerfan]

Originally Posted by Toni Wilen

Hmm.. Perhaps you are hitting 32-bit Windows memory limits. (Memory reservation is now different)

Does it also work if you reduce other memory type like mainboard RAM to zero and keep Z3 RAM at 256M?

EDIT: Also add log using 256M config with 2.4.1. (no need for full log, boot without startup-sequence and quit emulation)

EDIT2: Seems to happen when more RAM is configured than reserved (Memory info in Memory panel). It should only reduce memory size, not cause strange side effects.. (Also reserved size is too small, it should have been about 700M, not 512M)

Same happens with 2.5.0 with just 2mb chip and 256mb (or more) z3-ram.

I've attached the log with 2.4.1.

[Toni Wilen]

Thanks.

There was 2 bugs. (bsdsocket structures were done too early and got corrupted if memory config changed, 32-bit Windows reservation size was too small in 2.5.0 = 256M + some RTG RAM was not allowed)

http://www.winuae.net/files/b/winuae.zip should fix both.

[Mozzerfan]

Originally Posted by Toni Wilen

Thanks.

There was 2 bugs. (bsdsocket structures were done too early and got corrupted if memory config changed, 32-bit Windows reservation size was too small in 2.5.0 = 256M + some RTG RAM was not allowed)

http://www.winuae.net/files/b/winuae.zip should fix both.

bsdsocket emulation is now working with 256mb ram, but I think there are still some problems with mem-reservations. when I use 2mb chip with 256 mb z3-mem and 64 mb gfx mem, amigaos sees the gfxmem as fastram. when I type avail in shell or look with scout, I have 320 mb fastram.

I've attached the log.

edit: my laptop shows the correct memory size with this new beta.

Edit2:
I also have some gfx corruption. there are some white squares on the bottom right of the screen. I tried to capture them, but they don't show on the screen grab.

[Toni Wilen]

Originally Posted by Mozzerfan

bsdsocket emulation is now working with 256mb ram, but I think there are still some problems with mem-reservations. when I use 2mb chip with 256 mb z3-mem and 64 mb gfx mem, amigaos sees the gfxmem as fastram. when I type avail in shell or look with scout, I have 320 mb fastram.

Your config has 64M of "mainboard" RAM too.

[Mozzerfan]

Originally Posted by Toni Wilen

Your config has 64M of "mainboard" RAM too.

Oops, you're right. I thought I had the same config as my laptop.

So bsdsocket emulation works again.

For the gfx corruption I'll keep an eye on the 2.5.1 beta thread.

Thank you very much Toni !

Edit: Gfx corruption problem is solved. I've changed the graphics API in my config to Direct3D instead of DirectDraw. (I remember changing it to DirectDraw some time ago, I just have forgotten why. Anyway, everything works now).