• Content Count

  • Joined

  • Last visited

About simondarren

  • Rank
  1. @RomanZ Thanks, I'm going to stop that syncing until this release comes out. Maybe this will fix all my issues. Appreciate your work!
  2. As you know, my case, only one side ever changes any files. I'm really just using this for an offsite backup. AND. Something just hit us again over night. The orig setup that I created this post on. I had stopped syncing those two. I replaced the computer on the A side. I recreated the sync pair, this time as I said I would I setup a READ ONLY KEY on the B side. I fired that off 2 nights back. Well last night. BAM, excel file they use every day, is suddenly...Empty. Blank. I go looking's the weird part. A perfectly good copy of the file is in Sync Archive on the "A" sid
  3. I have the logs turned on this end, teh B side. I'll have to ck the A side, we've not had much issue there before, this is not the same A side as the orig post. I disconnected that as I replaced that machine and have not re-synced yet. Office 2010, Windows7 Pro. Thanks for cking into it, my plate is really full ATM, I'll do my best to get those logs ASAP.
  4. I just got hit again on this. Again, excel files. The !SYNC file remains on the end that saved it. The actual excel file is GONE from that side. The B side has a badly damaged version of the excel file. I can open it but excel spits out all kinds of errors, about white space expected and others errors. I just checked both ends, both on the most recent version of BTS. The only thing that is unique is this client has decided to put . in the file name area so these excel files are like 8.1.14.xls and such. And for the most part, we're OK but just randomly now, its just imploded and the file
  5. yes, it asked if I wanted to submit it. I said yes. I know where the WER reports are, is there another file you need? let me know the path and where to send it.
  6. @mariano, yes mine were ALL XLS files as well and I'm pretty sure other file types were modified during the down time and yet, they were not reverted like the XLS files were. least not reported to me. @weegee, YIPES! Sorry to hear even with readonly enabled. That was my backup plan. I would have tried some FileSystem undelete tools myself on this one. Update on me: BTSYNC crashed again. I've not restarted it. Backing up on both ends first. Will restart and get back if we have another incident.
  7. JimmyTheSaint - Sorry, I thought I replied to you but thank you for your very insightful response. Most of my post here is about feedback. In case a bug has crept in. Since its all worked very flawlessly up until now. If perhaps someone had an idea what to do if I saw this error dialog show up again, that would be welcome, otherwise I think I'll just recreate my folders 'read only' and my problem goes away. But I thought I'd contribute my experience in hopes of some helpful feedback for product development. I appreciate your insights! -=darren
  8. They were not changed on "B". No one has access to it but myself. I didn't touch that computer from Monday until maybe Thursday morning when I saw the error. And what was over written by older files, were daily log spreadsheets and items that staff uses on "A" daily. So random and spread out, its not likely I would have even know to open each of those on this end. And I wasn't sure if this was clear but it was EVERY file they changed on the "A" side after Monday. I thought about maybe a random disc error on the "B" side could have maybe triggered one file to change and cause somethi
  9. Let me first say I've been using BT from the start and on a lot of devices for a number of reasons and have yet to encounter many issues (aside from some stray !sync that linger, only around EXCEL files for some odd reason, those just randomly will not go away). Now to my current and FIRST real issue. Two machines. Both running BTS 1.3.94. Windows 7. 32bit. Machine "B" went offline for about a week. I fired it back up. When I noticed it was off (this is the only thing this machine does), not part of the issue. BTsync launched fine. This is a Monday. Machine "A" was always on and cont