See Getting Started for basic orientation and tasks. CaTS provides Pilot (LMS) training and support for all Wright State teaching faculty, staff, and graduate assistants. If you have a problem with your username or password, contact the CaTS Help Desk at 93. Now, apparently, everything is back in order. To log in, use your 'w' ID number and the corresponding password. Once the synchronization was complete, I turned the file protection back on: ESETs detected and cleaned two infected files, now fully identified by name and volume / folder. That is, previously it would stall because of the detection of the trojan after the cleaning process, it would restart syncing, only to get the infected chunk back in the.

Upon the advice of the Dropbox support person, I turned off the real-time file protection and allowed Dropbox to complete its synchronization. One such (incomplete) chunk showed up during the attempted syncing process with a machine-labelled partial file - enough for ESETs to identify the suspect element as a trojan - but gave me no further information as to the actual element () that was triggering the identification and cleaning, much less the filename / path of where it was found. The reason this wasn't immediately obvious: when Dropbox syncs files, as you may well know, it does them in chunks, deposited in the. This was a start part for Internet Explorer that at that time (2012-2014) was connected with a malware. Two of these files, I eventually learned, included '.'. When doing some updating the relative a couple of years ago, I made back up files from an old PC. It turns out that Dropbox was attempting to synchronize a couple of files from a German relative. In the meantime, I've discovered - thanks to help from Dropbox support - what the problem was.

Dropbox logs