and you repliedthe install.log file becomes massive and makes my O2 orbit grind to a halt. I presume it's because I don't have BirdieSync installed on my work pc where it is connected most of the day. These are the messages contained in the log (which got up to 11mb before I ran out of space) :
Local 2010-01-21 14:34:42::423 Mobile device cradled
Local 2010-01-21 14:34:43::557 Mobile device connected to the desktop
Local 2010-01-21 14:34:45::480 ERROR: Cannot read socket data. Error = 10054 (GetLastError = 10054)
Local 2010-01-21 14:34:45::662 ERROR: Impossible to read connection data (GetLastError = 10054)
Local 2010-01-21 14:34:46::043 ERROR: Cannot read connection data (result = 0x0) (GetLastError = 10054)
Local 2010-01-21 14:34:47::701 Mobile device cradled
Local 2010-01-21 14:34:47::829 Mobile device connected to the desktop
Local 2010-01-21 14:34:49::707 ERROR: Cannot read socket data. Error = 10054 (GetLastError = 10054)
Local 2010-01-21 14:34:49::889 ERROR: Impossible to read connection data (GetLastError = 10054)
Local 2010-01-21 14:34:49::069 ERROR: Cannot read connection data (result = 0x0) (GetLastError = 10054)
Local 2010-01-21 14:34:49::259 Mobile device cradled
and so on.
Any chance you could limit the size of the log file?
.I suppose you meant BirdieSync.log instead of install.log. I understand your problem and your analysis seems correct. I'll see what it's possible to do about it
Has there been any progress made. My device ran out of space again today and it means I have to keep uninstalling birdiesync.
Thanks.