snow leopard support?

[zankou]

out of curiosity, has almostvpn been tested with snow leopard?

[andrei....@gmail.com]

Not yet. I will post "Snow Leopard" status some time next week.

[andrei....@gmail.com]

Got my copy of Snow Leopard!!! Did some preliminary testing and it
looks like AlmostVPN does work. Will test some more over next few
days and update this post with results.


Andrei Tchijov
Leaping Bytes, LLC

[Doug Morack]

Any update?

On Aug 31, 10:34 pm, "and...@leapingbytes.com"

[Eelco]

I can confirm AVPN does work on snow leopard. However the prefpane is
32bits so to access it preferences has to restart in 32bits mode.

On Sep 1, 4:34 am, "and...@leapingbytes.com"

[Eelco]

When I access a web service that I tunnel using AVPN it will not work
the first time I try to load it. After that it works fine. I did not
have this issue with Leopard but it occurs with Snow Leopard now.

On Sep 1, 4:34 am, "and...@leapingbytes.com"
<andrei.tchi...@gmail.com> wrote:

[Andrei Tchijov]

Sorry for delay. Labor day weekend mini-vacation.

Does it happen every time you trying to access the service in question?

Could you please e-mail your almostvpn.log to sup...@leapingbytes.net
(this file could be found in ~/Library/Application Support/
AlmostVPNPRO )?

Andrei
Leaping Bytes, LLC

[Eelco]

This happen every time I try to access a HTTP service (I have several
in my profile and it happens on every one of them within a single
connection). I will sent you the logging later. I need some time to
remove some addresses.

I have also seen a crash with the following line in the logging

---
Invalid memory access of location b2f5cb2c eip=0100d018
---

I am running on 64bits (also with Java).

Thanks,
Eelco

---

[Andrei Tchijov]

Hi,

1) When you replace IP addresses, it will be nice if you do it in
consistent way ( so everywhere in the log same actual IP address got
replaced with same "placebo" IP address)
2) You can remove the log completely, start you profile - to make
this problem manifest itself and then e-mail me log (which will be
much shorter and will have only entries relevant to this problem)
3) When you get actual Crash, you should see corresponding "Crash
Report" file in ~/Library/Application Support/CrashReporter ( or /
Library/Application Support/CrashReporter ). Could you please e-mail
this crash report to sup...@leapingbytes.net

Andrei

[Eelco]

Hi,

Did you receive my logs and crashreporter files? I mailed them to your
account last week.

I see another issue with the menubar icon. It does not always work in
snow leopard. Sometimes it looks like it is disabled but it is still
possible to start a profile and vice versa.

br.
Eelco

On Sep 10, 2:41 pm, Andrei Tchijov <and...@leapingbytes.net> wrote:
> Hi,
>
> 1)  When you replace IP addresses, it will be nice if you do it in  
> consistent way ( so everywhere in the log same actual IP address got  
> replaced with same "placebo" IP address)
> 2)  You can remove the log completely, start you profile - to make  
> this problem manifest itself and then e-mail me log (which will be  
> much shorter and will have only entries relevant to this problem)
> 3)  When you get actual Crash, you should see corresponding "Crash  
> Report" file in ~/Library/Application Support/CrashReporter ( or /
> Library/Application Support/CrashReporter ). Could you please e-mail  

> this crash report to supp...@leapingbytes.net

[Andrei Tchijov]

Hi Eelco,
Sorry for delay. I did receive your files, but so far had very little
luck with your problem. I will announce on this list as soon as I
have any progress.

Andrei
Leaping Bytes, LLC

[andrei....@gmail.com]

Just got response from Apple. Not very informative:

"... After further investigation it has been determined that this is a
known issue, which is currently being investigated by engineering..."

I guess at this point the only thing I can do is to wait for next java
update and hope that this particular problem will be fixed. Apple
tracks this problem as bug #7165643. Due to the way Apple track
issues, no one except person who open this bug can see it (so all I
can see is that bug opened by me was marked as duplicate of this
bug). The only use for this number is to look for it in next java
update release notes, to see if this particular bug was fixed.

Sorry for inconvenience,

Andrei
Leaping Bytes, LLC