Eudora problem with Windows7?
in [Eudora]
|
From: EricF on 12 Feb 2010 20:36 I have Eudora 7.1.0.9 running on 64bit Windows7. I have an intermittent problem, thought it was fixed but I was wrong. I get errors when I open Eudora and it starts downloading email. There are 3 email addresses it works with on 2 different domains. I get a permission denied error. Here is the log emtry (with email addys disguised). 4324 8: 0.41 Dialog: "Could not connect to "x.net"\r\n" 4324 8: 0.41 Dialog: "\r\n" 4324 8: 0.41 Dialog: "Cause: permission denied (10013)" 912 8: 0.41 Dialog: "Could not connect to "x.net"\r\n" 912 8: 0.41 Dialog: "\r\n" 912 8: 0.41 Dialog: "Cause: permission denied (10013)" 3580 8: 0.41 Dialog: "Could not connect to "mail.y.net"\r\n" 3580 8: 0.41 Dialog: "\r\n" 3580 8: 0.41 Dialog: "Cause: permission denied (10013)" I am able to access email after this in pop peeper, a lightweight email reader I also use. But Eudora will not work until a reboot the machine. I don't think it is the ISP or the network. The error 10013 is a socket error ... Permission denied. An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST). Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4.0 with SP4 and later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4.0 with SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option. Any clue? Most of the time it just works. TIA Eric
From: Han on 12 Feb 2010 21:14 eric(a)invalid.com (EricF) wrote in news:hl4vmh$2ml$2(a)news.eternal-september.org: > I have Eudora 7.1.0.9 running on 64bit Windows7. I have an > intermittent problem, thought it was fixed but I was wrong. > > I get errors when I open Eudora and it starts downloading email. There > are 3 email addresses it works with on 2 different domains. I get a > permission denied error. Here is the log emtry (with email addys > disguised). > > 4324 8: 0.41 Dialog: "Could not connect to "x.net"\r\n" > 4324 8: 0.41 Dialog: "\r\n" > 4324 8: 0.41 Dialog: "Cause: permission denied (10013)" > 912 8: 0.41 Dialog: "Could not connect to "x.net"\r\n" > 912 8: 0.41 Dialog: "\r\n" > 912 8: 0.41 Dialog: "Cause: permission denied (10013)" > 3580 8: 0.41 Dialog: "Could not connect to "mail.y.net"\r\n" > 3580 8: 0.41 Dialog: "\r\n" > 3580 8: 0.41 Dialog: "Cause: permission denied (10013)" > > I am able to access email after this in pop peeper, a lightweight > email reader I also use. But Eudora will not work until a reboot the > machine. I don't think it is the ISP or the network. > > The error 10013 is a socket error ... > > Permission denied. > > An attempt was made to access a socket in a way forbidden by its > access > permissions. An example is using a broadcast address for sendto > without broadcast permission being set using setsockopt(SO_BROADCAST). > > Another possible reason for the WSAEACCES error is that when the > bind > function is called (on Windows NT 4.0 with SP4 and later), another > application, service, or kernel mode driver is bound to the same > address with exclusive access. Such exclusive access is a new feature > of Windows NT 4.0 with SP4 and later, and is implemented by using the > SO_EXCLUSIVEADDRUSE option. > > Any clue? Most of the time it just works. > > TIA > > Eric Are you running Eudora as administrator? I think you should, under Win7. -- Best regards Han email address is invalid
From: EricF on 13 Feb 2010 01:37 In article <Xns9D1DD80ED786Cikkezelf(a)207.246.207.161>, Han <nobody(a)nospam.not> wrote: >eric(a)invalid.com (EricF) wrote in >news:hl4vmh$2ml$2(a)news.eternal-september.org: > >> I have Eudora 7.1.0.9 running on 64bit Windows7. I have an >> intermittent problem, thought it was fixed but I was wrong. >> >> I get errors when I open Eudora and it starts downloading email. There >> are 3 email addresses it works with on 2 different domains. I get a >> permission denied error. Here is the log emtry (with email addys >> disguised). >> >> 4324 8: 0.41 Dialog: "Could not connect to "x.net"\r\n" >> 4324 8: 0.41 Dialog: "\r\n" >> 4324 8: 0.41 Dialog: "Cause: permission denied (10013)" >> 912 8: 0.41 Dialog: "Could not connect to "x.net"\r\n" >> 912 8: 0.41 Dialog: "\r\n" >> 912 8: 0.41 Dialog: "Cause: permission denied (10013)" >> 3580 8: 0.41 Dialog: "Could not connect to "mail.y.net"\r\n" >> 3580 8: 0.41 Dialog: "\r\n" >> 3580 8: 0.41 Dialog: "Cause: permission denied (10013)" >> >> I am able to access email after this in pop peeper, a lightweight >> email reader I also use. But Eudora will not work until a reboot the >> machine. I don't think it is the ISP or the network. >> >> The error 10013 is a socket error ... >> >> Permission denied. >> >> An attempt was made to access a socket in a way forbidden by its >> access >> permissions. An example is using a broadcast address for sendto >> without broadcast permission being set using setsockopt(SO_BROADCAST). >> >> Another possible reason for the WSAEACCES error is that when the >> bind >> function is called (on Windows NT 4.0 with SP4 and later), another >> application, service, or kernel mode driver is bound to the same >> address with exclusive access. Such exclusive access is a new feature >> of Windows NT 4.0 with SP4 and later, and is implemented by using the >> SO_EXCLUSIVEADDRUSE option. >> >> Any clue? Most of the time it just works. >> >> TIA >> >> Eric > >Are you running Eudora as administrator? I think you should, under Win7. > I am not running Eudora as administrator. But as I said, the problem is very intermittent. I think I went 6 days before encountering this error most recently. If I needed to run this as admin, I would think I'd see the problem more frequently. Thanks, Eric
From: the.hunter on 16 Feb 2010 16:59 > An attempt was made to access a socket in a way forbidden by its access >permissions. An example is using a broadcast address for sendto without >broadcast permission being set using setsockopt(SO_BROADCAST). me too, with windows 7 I have problems. When I click on Check Mail, Eudora jams for 1 minute or more, then it downloads mail regularly. I use some different accounts.
From: John H Meyers on 16 Feb 2010 17:24
Formerly: >> An attempt was made to access a socket in a way forbidden by its access >> permissions. An example is using a broadcast address for sendto without >> broadcast permission being set using setsockopt(SO_BROADCAST). On 2/16/2010 3:59 PM: > me too, with windows 7 I have problems. When I click on Check Mail, > Eudora jams for 1 minute or more, then it downloads mail regularly. > I use some different accounts. Did you get a "socket error"? Then it's not a "me too." Perhaps it's an issue where the standard OpenSSL library employed by Eudora takes a long time to initialize in Windows 7 (but only requires one initialization, then sails through for as long as you continue using Eudora): http://eudorabb.qualcomm.com/showthread.php?t=14440 -- |