Since the most recent update I'm able to log on with my 32 bit SP1 vista
machine but my 64 bit SP1 machine still gives me the same crash I was getting
with the old client. Are you guys aware of this? are you working on a fix?

Thanks

Could you do the following to help us troubleshoot?

1. Start FolderShare and let it crash
2. Go to \AppData\Local\FolderShare\logs\log.log
3. Attach the last few lines of the log file

Thanks,
Christoph

"werD" wrote:

> Since the most recent update I'm able to log on with my 32 bit SP1 vista
> machine but my 64 bit SP1 machine still gives me the same crash I was getting
> with the old client. Are you guys aware of this? are you working on a fix?
>
> Thanks

Sure,
I just ran this and got the same crash. Here's a copy of the last of the log
from my system (vista x64 sp1).

Thanks in advance for any assistance, Id be glad to assist in debugging any
further.

(DETAIL): decrypted 37 of 37 bytes in buffer
00:08:09.972 serverconn.cpp:7418 (DETAIL): read NTC_TEST_LATENCY, data
length 0
00:08:09.972 fsmessage.cpp:239 (DETAIL): writing mesg of type 4
00:08:09.972 serverconn.cpp:3909 (DETAIL): got a latency test message from
server, responding
00:08:09.972 clientssl.cpp:1308 (DETAIL): copying 5 bytes into the IoBuffer
from pOutBuf (sizes: 5:2015:28)
00:08:09.972 clientssl.cpp:1347 (DETAIL): EncrytMessage succeeded, moving 37
bytes to encOutBuf, (37 bytes in buf)
00:08:09.972 connection.cpp:2152 (DETAIL): putting encOutBuf in wset
00:08:09.972 connection.cpp:2555 (DETAIL): wrote 37 encrypted bytes to socket
00:08:10.094 core.cpp:3883 (DETAIL): data available from the server! 0 bytes
in buffer already
00:08:10.094 connection.cpp:2243 (DETAIL): read 37 encrypted bytes from
PRIVATE_DATA_REMOVED on port 443, r 0, w 0, errno 0
00:08:10.094 clientssl.cpp:1221 (DETAIL): Buffers[1].BufferType =
SECBUFFER_DATA
00:08:10.094 clientssl.cpp:1232 (DETAIL): Decrypted data: 5 bytes
00:08:10.094 clientssl.cpp:1244 (DETAIL): decrypted 37 of 37 bytes in buffer
00:08:10.144 serverconn.cpp:7418 (DETAIL): read NTC_TEST_LATENCY, data
length 0
00:08:10.144 fsmessage.cpp:239 (DETAIL): writing mesg of type 4
00:08:10.144 serverconn.cpp:3909 (DETAIL): got a latency test message from
server, responding
00:08:10.144 clientssl.cpp:1308 (DETAIL): copying 5 bytes into the IoBuffer
from pOutBuf (sizes: 5:2015:28)
00:08:10.144 clientssl.cpp:1347 (DETAIL): EncrytMessage succeeded, moving 37
bytes to encOutBuf, (37 bytes in buf)
00:08:10.144 connection.cpp:2152 (DETAIL): putting encOutBuf in wset
00:08:10.144 connection.cpp:2555 (DETAIL): wrote 37 encrypted bytes to socket
00:08:10.277 core.cpp:3883 (DETAIL): data available from the server! 0 bytes
in buffer already
00:08:10.277 connection.cpp:2243 (DETAIL): read 53 encrypted bytes from
PRIVATE_DATA_REMOVED on port 443, r 0, w 0, errno 0
00:08:10.277 clientssl.cpp:1221 (DETAIL): Buffers[1].BufferType =
SECBUFFER_DATA
00:08:10.277 clientssl.cpp:1232 (DETAIL): Decrypted data: 25 bytes
00:08:10.277 clientssl.cpp:1244 (DETAIL): decrypted 53 of 53 bytes in buffer
00:08:10.327 serverconn.cpp:7418 (DETAIL): read NTC_TEST_LISTEN_PORTS, data
length 20
00:08:10.327 serverconn.cpp:6231 (DETAIL): about to call addMappings()
00:08:10.329 serverconn.cpp:6233 (DETAIL): done
00:08:10.329 serverconn.cpp:6243 (DETAIL): in handleNtcTestListenPorts, have
private IP
00:08:10.329 serverconn.cpp:6247 (DETAIL): in handleNtcTestListenPorts,
useUpnp was TRUE
00:08:10.329 upnp.cpp:293 (DETAIL): in UPNP_SEND_SEARCH, adding upnp socket
to write set
00:08:10.339 upnp.cpp:355 (DETAIL): successfully sent upnp search


Thanks Again,
DrewG

"Christoph Zelazowski [MSFT]" wrote:

> Could you do the following to help us troubleshoot?
>
> 1. Start FolderShare and let it crash
> 2. Go to \AppData\Local\FolderShare\logs\log.log
> 3. Attach the last few lines of the log file
>
> Thanks,
> Christoph
>
> "werD" wrote:
>

> > Since the most recent update I'm able to log on with my 32 bit SP1 vista
> > machine but my 64 bit SP1 machine still gives me the same crash I was getting
> > with the old client. Are you guys aware of this? are you working on a fix?
> >
> > Thanks

Christoph,

I guess someone at MSFT is keeping an eye on these discussions after all.
Any idea when the rest of the questions/comments on the discussions will get
some attention?

I am specifically wondering about when the we can expect files with
non-english/western character sets to be syncable. I have files with
Russian/Cyrilic file names that will not sync. I have seen other pasts about
Chinese characters as well. Please let us now what is going on.

"Christoph Zelazowski [MSFT]" wrote:

> Could you do the following to help us troubleshoot?
>
> 1. Start FolderShare and let it crash
> 2. Go to \AppData\Local\FolderShare\logs\log.log
> 3. Attach the last few lines of the log file
>
> Thanks,
> Christoph
>
> "werD" wrote:
>

> > Since the most recent update I'm able to log on with my 32 bit SP1 vista
> > machine but my 64 bit SP1 machine still gives me the same crash I was getting
> > with the old client. Are you guys aware of this? are you working on a fix?
> >
> > Thanks

This looks like the UPnP bug which we are currently tracking and which occurs
with some routers. I think the steps below will help you get FolderShare
working again while we are fixing the problem. Thanks for reporting the issue
and helping us make this service better.

By the way - when the client crashes, does it prompt you to send detailed
error report to MS? If so, it would definitely be helpful for us to get as
many call stacks as possible.

In the mean time, try the following:

1. Disconnect your network cable / adapter.
2. Launch FolderShare
3. Go to Settings -> Port Status
4. Uncheck “Use UPNP to automatically forward ports�
5. Reconnect your network cable / adapter
6. Restart FolderShare

Thanks,
Christoph

"werD" wrote:

> Sure,
> I just ran this and got the same crash. Here's a copy of the last of the log
> from my system (vista x64 sp1).
>
> Thanks in advance for any assistance, Id be glad to assist in debugging any
> further.
>
> (DETAIL): decrypted 37 of 37 bytes in buffer
> 00:08:09.972 serverconn.cpp:7418 (DETAIL): read NTC_TEST_LATENCY, data
> length 0
> 00:08:09.972 fsmessage.cpp:239 (DETAIL): writing mesg of type 4
> 00:08:09.972 serverconn.cpp:3909 (DETAIL): got a latency test message from
> server, responding
> 00:08:09.972 clientssl.cpp:1308 (DETAIL): copying 5 bytes into the IoBuffer
> from pOutBuf (sizes: 5:2015:28)
> 00:08:09.972 clientssl.cpp:1347 (DETAIL): EncrytMessage succeeded, moving 37
> bytes to encOutBuf, (37 bytes in buf)
> 00:08:09.972 connection.cpp:2152 (DETAIL): putting encOutBuf in wset
> 00:08:09.972 connection.cpp:2555 (DETAIL): wrote 37 encrypted bytes to socket
> 00:08:10.094 core.cpp:3883 (DETAIL): data available from the server! 0 bytes
> in buffer already
> 00:08:10.094 connection.cpp:2243 (DETAIL): read 37 encrypted bytes from
> PRIVATE_DATA_REMOVED on port 443, r 0, w 0, errno 0
> 00:08:10.094 clientssl.cpp:1221 (DETAIL): Buffers[1].BufferType =
> SECBUFFER_DATA
> 00:08:10.094 clientssl.cpp:1232 (DETAIL): Decrypted data: 5 bytes
> 00:08:10.094 clientssl.cpp:1244 (DETAIL): decrypted 37 of 37 bytes in buffer
> 00:08:10.144 serverconn.cpp:7418 (DETAIL): read NTC_TEST_LATENCY, data
> length 0
> 00:08:10.144 fsmessage.cpp:239 (DETAIL): writing mesg of type 4
> 00:08:10.144 serverconn.cpp:3909 (DETAIL): got a latency test message from
> server, responding
> 00:08:10.144 clientssl.cpp:1308 (DETAIL): copying 5 bytes into the IoBuffer
> from pOutBuf (sizes: 5:2015:28)
> 00:08:10.144 clientssl.cpp:1347 (DETAIL): EncrytMessage succeeded, moving 37
> bytes to encOutBuf, (37 bytes in buf)
> 00:08:10.144 connection.cpp:2152 (DETAIL): putting encOutBuf in wset
> 00:08:10.144 connection.cpp:2555 (DETAIL): wrote 37 encrypted bytes to socket
> 00:08:10.277 core.cpp:3883 (DETAIL): data available from the server! 0 bytes
> in buffer already
> 00:08:10.277 connection.cpp:2243 (DETAIL): read 53 encrypted bytes from
> PRIVATE_DATA_REMOVED on port 443, r 0, w 0, errno 0
> 00:08:10.277 clientssl.cpp:1221 (DETAIL): Buffers[1].BufferType =
> SECBUFFER_DATA
> 00:08:10.277 clientssl.cpp:1232 (DETAIL): Decrypted data: 25 bytes
> 00:08:10.277 clientssl.cpp:1244 (DETAIL): decrypted 53 of 53 bytes in buffer
> 00:08:10.327 serverconn.cpp:7418 (DETAIL): read NTC_TEST_LISTEN_PORTS, data
> length 20
> 00:08:10.327 serverconn.cpp:6231 (DETAIL): about to call addMappings()
> 00:08:10.329 serverconn.cpp:6233 (DETAIL): done
> 00:08:10.329 serverconn.cpp:6243 (DETAIL): in handleNtcTestListenPorts, have
> private IP
> 00:08:10.329 serverconn.cpp:6247 (DETAIL): in handleNtcTestListenPorts,
> useUpnp was TRUE
> 00:08:10.329 upnp.cpp:293 (DETAIL): in UPNP_SEND_SEARCH, adding upnp socket
> to write set
> 00:08:10.339 upnp.cpp:355 (DETAIL): successfully sent upnp search
>
>
> Thanks Again,
> DrewG
>
> "Christoph Zelazowski [MSFT]" wrote:
>

> > Could you do the following to help us troubleshoot?
> >
> > 1. Start FolderShare and let it crash
> > 2. Go to \AppData\Local\FolderShare\logs\log.log
> > 3. Attach the last few lines of the log file
> >
> > Thanks,
> > Christoph
> >
> > "werD" wrote:
> >

> > > Since the most recent update I'm able to log on with my 32 bit SP1 vista
> > > machine but my 64 bit SP1 machine still gives me the same crash I was getting
> > > with the old client. Are you guys aware of this? are you working on a fix?
> > >
> > > Thanks

Unfortunately FolderShare today only supports the 6 languages (EN, ES, IT,
PT, DE, FR). While we can not promise specific dates, Unicode support is
definitely high on our priority list and we are working hard on fixing the
problem.

In the mean time, if you'd like to synchronize Russian files between
multiple machines, you'll need to set the default codepage on each machine.

On Windows Vista, you can do the following:

1. Go to Regional and Language Options
2. Choose "Change the country or region"
3. Go to Administrative Tab
4. Change the "Current language for non-unicode programs" to Russian

Note: While this should enable you to synchronize files across multiple
computers, those files will not be displayed correctly when you tunnel
through the website.

Thanks,
Christoph

"Drew" wrote:

> Christoph,
>
> I guess someone at MSFT is keeping an eye on these discussions after all.
> Any idea when the rest of the questions/comments on the discussions will get
> some attention?
>
> I am specifically wondering about when the we can expect files with
> non-english/western character sets to be syncable. I have files with
> Russian/Cyrilic file names that will not sync. I have seen other pasts about
> Chinese characters as well. Please let us now what is going on.
>
> "Christoph Zelazowski [MSFT]" wrote:
>

> > Could you do the following to help us troubleshoot?
> >
> > 1. Start FolderShare and let it crash
> > 2. Go to \AppData\Local\FolderShare\logs\log.log
> > 3. Attach the last few lines of the log file
> >
> > Thanks,
> > Christoph
> >
> > "werD" wrote:
> >

> > > Since the most recent update I'm able to log on with my 32 bit SP1 vista
> > > machine but my 64 bit SP1 machine still gives me the same crash I was getting
> > > with the old client. Are you guys aware of this? are you working on a fix?
> > >
> > > Thanks

Christoph,
Thanks for your continued assistance. I'm no longer getting the option to
send any reports on this to microsoft, only to close or debug.

Unfortunately, If I unplug the adapter and launch foldershare, When I view
the settings --> Port Status. The option “Use UPNP to automatically forward
ports� is greyed out(disabled?). Is there a way i can do this through
configuration files? or any other steps that might fix this?

Thanks again,
Drew

"Christoph Zelazowski [MSFT]" wrote:

> This looks like the UPnP bug which we are currently tracking and which occurs
> with some routers. I think the steps below will help you get FolderShare
> working again while we are fixing the problem. Thanks for reporting the issue
> and helping us make this service better.
>
> By the way - when the client crashes, does it prompt you to send detailed
> error report to MS? If so, it would definitely be helpful for us to get as
> many call stacks as possible.
>
> In the mean time, try the following:
>
> 1. Disconnect your network cable / adapter.
> 2. Launch FolderShare
> 3. Go to Settings -> Port Status
> 4. Uncheck “Use UPNP to automatically forward ports�
> 5. Reconnect your network cable / adapter
> 6. Restart FolderShare
>
> Thanks,
> Christoph
>
> "werD" wrote:
>

> > Sure,
> > I just ran this and got the same crash. Here's a copy of the last of the log
> > from my system (vista x64 sp1).
> >
> > Thanks in advance for any assistance, Id be glad to assist in debugging any
> > further.
> >
> > (DETAIL): decrypted 37 of 37 bytes in buffer
> > 00:08:09.972 serverconn.cpp:7418 (DETAIL): read NTC_TEST_LATENCY, data
> > length 0
> > 00:08:09.972 fsmessage.cpp:239 (DETAIL): writing mesg of type 4
> > 00:08:09.972 serverconn.cpp:3909 (DETAIL): got a latency test message from
> > server, responding
> > 00:08:09.972 clientssl.cpp:1308 (DETAIL): copying 5 bytes into the IoBuffer
> > from pOutBuf (sizes: 5:2015:28)
> > 00:08:09.972 clientssl.cpp:1347 (DETAIL): EncrytMessage succeeded, moving 37
> > bytes to encOutBuf, (37 bytes in buf)
> > 00:08:09.972 connection.cpp:2152 (DETAIL): putting encOutBuf in wset
> > 00:08:09.972 connection.cpp:2555 (DETAIL): wrote 37 encrypted bytes to socket
> > 00:08:10.094 core.cpp:3883 (DETAIL): data available from the server! 0 bytes
> > in buffer already
> > 00:08:10.094 connection.cpp:2243 (DETAIL): read 37 encrypted bytes from
> > PRIVATE_DATA_REMOVED on port 443, r 0, w 0, errno 0
> > 00:08:10.094 clientssl.cpp:1221 (DETAIL): Buffers[1].BufferType =
> > SECBUFFER_DATA
> > 00:08:10.094 clientssl.cpp:1232 (DETAIL): Decrypted data: 5 bytes
> > 00:08:10.094 clientssl.cpp:1244 (DETAIL): decrypted 37 of 37 bytes in buffer
> > 00:08:10.144 serverconn.cpp:7418 (DETAIL): read NTC_TEST_LATENCY, data
> > length 0
> > 00:08:10.144 fsmessage.cpp:239 (DETAIL): writing mesg of type 4
> > 00:08:10.144 serverconn.cpp:3909 (DETAIL): got a latency test message from
> > server, responding
> > 00:08:10.144 clientssl.cpp:1308 (DETAIL): copying 5 bytes into the IoBuffer
> > from pOutBuf (sizes: 5:2015:28)
> > 00:08:10.144 clientssl.cpp:1347 (DETAIL): EncrytMessage succeeded, moving 37
> > bytes to encOutBuf, (37 bytes in buf)
> > 00:08:10.144 connection.cpp:2152 (DETAIL): putting encOutBuf in wset
> > 00:08:10.144 connection.cpp:2555 (DETAIL): wrote 37 encrypted bytes to socket
> > 00:08:10.277 core.cpp:3883 (DETAIL): data available from the server! 0 bytes
> > in buffer already
> > 00:08:10.277 connection.cpp:2243 (DETAIL): read 53 encrypted bytes from
> > PRIVATE_DATA_REMOVED on port 443, r 0, w 0, errno 0
> > 00:08:10.277 clientssl.cpp:1221 (DETAIL): Buffers[1].BufferType =
> > SECBUFFER_DATA
> > 00:08:10.277 clientssl.cpp:1232 (DETAIL): Decrypted data: 25 bytes
> > 00:08:10.277 clientssl.cpp:1244 (DETAIL): decrypted 53 of 53 bytes in buffer
> > 00:08:10.327 serverconn.cpp:7418 (DETAIL): read NTC_TEST_LISTEN_PORTS, data
> > length 20
> > 00:08:10.327 serverconn.cpp:6231 (DETAIL): about to call addMappings()
> > 00:08:10.329 serverconn.cpp:6233 (DETAIL): done
> > 00:08:10.329 serverconn.cpp:6243 (DETAIL): in handleNtcTestListenPorts, have
> > private IP
> > 00:08:10.329 serverconn.cpp:6247 (DETAIL): in handleNtcTestListenPorts,
> > useUpnp was TRUE
> > 00:08:10.329 upnp.cpp:293 (DETAIL): in UPNP_SEND_SEARCH, adding upnp socket
> > to write set
> > 00:08:10.339 upnp.cpp:355 (DETAIL): successfully sent upnp search
> >
> >
> > Thanks Again,
> > DrewG
> >
> > "Christoph Zelazowski [MSFT]" wrote:
> >

> > > Could you do the following to help us troubleshoot?
> > >
> > > 1. Start FolderShare and let it crash
> > > 2. Go to \AppData\Local\FolderShare\logs\log.log
> > > 3. Attach the last few lines of the log file
> > >
> > > Thanks,
> > > Christoph
> > >
> > > "werD" wrote:
> > >
> > > > Since the most recent update I'm able to log on with my 32 bit SP1 vista
> > > > machine but my 64 bit SP1 machine still gives me the same crash I was getting
> > > > with the old client. Are you guys aware of this? are you working on a fix?
> > > >
> > > > Thanks

Ok,
I went to AppData\Local\FolderShare\settings\Global.ini and changed useUpnp
to false and Foldershare connected up and is syncing.

Thanks immensely for your help. If there's anything I can do to troubleshoot
the issue further let me know. I have a pretty elaborate switch to router to
router setup(all netgear) that might make for a good testbed/

Thanks Again,
DrewG


"Christoph Zelazowski [MSFT]" wrote:

> This looks like the UPnP bug which we are currently tracking and which occurs
> with some routers. I think the steps below will help you get FolderShare
> working again while we are fixing the problem. Thanks for reporting the issue
> and helping us make this service better.
>
> By the way - when the client crashes, does it prompt you to send detailed
> error report to MS? If so, it would definitely be helpful for us to get as
> many call stacks as possible.
>
> In the mean time, try the following:
>
> 1. Disconnect your network cable / adapter.
> 2. Launch FolderShare
> 3. Go to Settings -> Port Status
> 4. Uncheck “Use UPNP to automatically forward ports�
> 5. Reconnect your network cable / adapter
> 6. Restart FolderShare
>
> Thanks,
> Christoph
>
> "werD" wrote:
>

> > Sure,
> > I just ran this and got the same crash. Here's a copy of the last of the log
> > from my system (vista x64 sp1).
> >
> > Thanks in advance for any assistance, Id be glad to assist in debugging any
> > further.
> >
> > (DETAIL): decrypted 37 of 37 bytes in buffer
> > 00:08:09.972 serverconn.cpp:7418 (DETAIL): read NTC_TEST_LATENCY, data
> > length 0
> > 00:08:09.972 fsmessage.cpp:239 (DETAIL): writing mesg of type 4
> > 00:08:09.972 serverconn.cpp:3909 (DETAIL): got a latency test message from
> > server, responding
> > 00:08:09.972 clientssl.cpp:1308 (DETAIL): copying 5 bytes into the IoBuffer
> > from pOutBuf (sizes: 5:2015:28)
> > 00:08:09.972 clientssl.cpp:1347 (DETAIL): EncrytMessage succeeded, moving 37
> > bytes to encOutBuf, (37 bytes in buf)
> > 00:08:09.972 connection.cpp:2152 (DETAIL): putting encOutBuf in wset
> > 00:08:09.972 connection.cpp:2555 (DETAIL): wrote 37 encrypted bytes to socket
> > 00:08:10.094 core.cpp:3883 (DETAIL): data available from the server! 0 bytes
> > in buffer already
> > 00:08:10.094 connection.cpp:2243 (DETAIL): read 37 encrypted bytes from
> > PRIVATE_DATA_REMOVED on port 443, r 0, w 0, errno 0
> > 00:08:10.094 clientssl.cpp:1221 (DETAIL): Buffers[1].BufferType =
> > SECBUFFER_DATA
> > 00:08:10.094 clientssl.cpp:1232 (DETAIL): Decrypted data: 5 bytes
> > 00:08:10.094 clientssl.cpp:1244 (DETAIL): decrypted 37 of 37 bytes in buffer
> > 00:08:10.144 serverconn.cpp:7418 (DETAIL): read NTC_TEST_LATENCY, data
> > length 0
> > 00:08:10.144 fsmessage.cpp:239 (DETAIL): writing mesg of type 4
> > 00:08:10.144 serverconn.cpp:3909 (DETAIL): got a latency test message from
> > server, responding
> > 00:08:10.144 clientssl.cpp:1308 (DETAIL): copying 5 bytes into the IoBuffer
> > from pOutBuf (sizes: 5:2015:28)
> > 00:08:10.144 clientssl.cpp:1347 (DETAIL): EncrytMessage succeeded, moving 37
> > bytes to encOutBuf, (37 bytes in buf)
> > 00:08:10.144 connection.cpp:2152 (DETAIL): putting encOutBuf in wset
> > 00:08:10.144 connection.cpp:2555 (DETAIL): wrote 37 encrypted bytes to socket
> > 00:08:10.277 core.cpp:3883 (DETAIL): data available from the server! 0 bytes
> > in buffer already
> > 00:08:10.277 connection.cpp:2243 (DETAIL): read 53 encrypted bytes from
> > PRIVATE_DATA_REMOVED on port 443, r 0, w 0, errno 0
> > 00:08:10.277 clientssl.cpp:1221 (DETAIL): Buffers[1].BufferType =
> > SECBUFFER_DATA
> > 00:08:10.277 clientssl.cpp:1232 (DETAIL): Decrypted data: 25 bytes
> > 00:08:10.277 clientssl.cpp:1244 (DETAIL): decrypted 53 of 53 bytes in buffer
> > 00:08:10.327 serverconn.cpp:7418 (DETAIL): read NTC_TEST_LISTEN_PORTS, data
> > length 20
> > 00:08:10.327 serverconn.cpp:6231 (DETAIL): about to call addMappings()
> > 00:08:10.329 serverconn.cpp:6233 (DETAIL): done
> > 00:08:10.329 serverconn.cpp:6243 (DETAIL): in handleNtcTestListenPorts, have
> > private IP
> > 00:08:10.329 serverconn.cpp:6247 (DETAIL): in handleNtcTestListenPorts,
> > useUpnp was TRUE
> > 00:08:10.329 upnp.cpp:293 (DETAIL): in UPNP_SEND_SEARCH, adding upnp socket
> > to write set
> > 00:08:10.339 upnp.cpp:355 (DETAIL): successfully sent upnp search
> >
> >
> > Thanks Again,
> > DrewG
> >
> > "Christoph Zelazowski [MSFT]" wrote:
> >

> > > Could you do the following to help us troubleshoot?
> > >
> > > 1. Start FolderShare and let it crash
> > > 2. Go to \AppData\Local\FolderShare\logs\log.log
> > > 3. Attach the last few lines of the log file
> > >
> > > Thanks,
> > > Christoph
> > >
> > > "werD" wrote:
> > >
> > > > Since the most recent update I'm able to log on with my 32 bit SP1 vista
> > > > machine but my 64 bit SP1 machine still gives me the same crash I was getting
> > > > with the old client. Are you guys aware of this? are you working on a fix?
> > > >
> > > > Thanks

Thanks for the info.

I am primariliy and English user but I have some files in Russian (I am
learning the language now). Won't changing the code page for the computer
mess a lot of other things up?

Also, I don't remember seeing the supported list of languages anywhere.
Where would I have found that?

Please do support Unicode ASAP.

The system codepage will only affect other non-unicode applications. If you
don't have any, you should be fine.

As to supported list of languages - you are right - it isn't obvious from
our download page.

Thanks,
Christoph

"Drew" wrote:

> Thanks for the info.
>
> I am primariliy and English user but I have some files in Russian (I am
> learning the language now). Won't changing the code page for the computer
> mess a lot of other things up?
>
> Also, I don't remember seeing the supported list of languages anywhere.
> Where would I have found that?
>
> Please do support Unicode ASAP.