Re: [OT] unhosing .rev and .livecode files
On Sun, Dec 4, 2016 at 11:28 AM, Jerry Jensenwrote: > Just one additional level of warning - if you keep Dropbox or Google Drive > online, > malware can get there too. Usually the baddies just trash your directory, but > if > they encrypt everything you have accessible online, Dropbox and Google Drive >won’t help you. Offline backup is essential, offsite is even better. Whilst your overall comment is extremely valid, that everyone should have some sort of offline back-up, the sentiment about Google Drive I think is false and probably driven by articles such as this: http://blog.teklinks.com/ask-the-engineer-why-dropbox-wont-help-if-youre-the-victim-of-cryptowall The statement that versioning is just a few hours or a couple of days at most is just wrong; certainly in the case of Google Drive, and is just a perfect example of how so many of us do not really understand the programs and services we use and the options available to us: http://fieldguide.gizmodo.com/keep-older-versions-of-your-documents-on-google-drive-f-1671188573 If Richmond had Google Drive synced to his stacks (which I appreciate he doesn't), then even at the default setting, if there was some crypto attack on his computer I would NOT discount the effort of going to your Google Drive and looking at the old versions kept - there is a little clock icon against any file that has multiple versions. Not only that, Google Drive has a menubar icon which becomes active only when it's syncing, ie I've just saved a stack. It spends most of it's time as a static Icon, so if it starts up at a random time and doesn't stop it's a clear indication to pull the ethernet, USB, Thunderbolt and FireWire cables and shut the computer down immediately - especially if I were to click on the menubar Google Drive Icon and the files it listed as being synced are ones that I haven't worked on for ages. Had to pull cables a couple of times over the years, although not for uncommanded Google Drive activity but for network traffic that didn't seem right. Cloud based sync is not THE answer, it's just one of many cheap and easy options that should be ADDED to our stash of computer prophylactics. Only if your network bandwidth is thin and/or expensive would you not avail yourself of the side benefits of free Google Drive/Dropbox. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: [OT] unhosing .rev and .livecode files
your drive was probably at some time used as a Torrent server source. Yes definitely delete all porn, don't even bother seeing if it contains illegal porn. Chances of child porn are very likely in a Torrent folder, and one has no idea where's it's from or been. In the US the son of a friend of mine was thrown in jail for 5 years by the feds and jailed as a sexual predator for what was on his hard drive. The federal prosecutor got the defendant's independent examination thrown out of court which would have proven his innocence and made it hard for him to defend himself. He's still there. On Sun, Dec 4, 2016 at 10:44 AM, Richmond Mathewson < richmondmathew...@gmail.com> wrote: > 2. So, at the cost of losing 2 more days time, I am doing a seven-fold > deletion thing offered by > Macintosh's Disk Tools as have no very great desire to find that set of > images popping up again. > -- Stephen Barncard - Sebastopol Ca. USA - mixstream.org ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: [OT] unhosing .rev and .livecode files
Thanks, one-and-all, for the kind and informative messages about backing up and so forth. I have retrieved as much as I am likely to from my zonked Linux box, and am now putting the thing back together. HOWEVER, before that: 1. Retrieved from one of my hard drives was a "rather intriguing" set of extremely foul, hard-core porn images which I most definitely did not download onto that drive. Looking through a load of old receipts I discovered that I had bought that hard-drive second-hand. 2. So, at the cost of losing 2 more days time, I am doing a seven-fold deletion thing offered by Macintosh's Disk Tools as have no very great desire to find that set of images popping up again. 3. I also noticed all sorts of advert images which, I, similarly did not download onto my hard drives; so can only conclude that whatever webpages one visits, those webpages dump their images onto your hard drive in some sort of cache that is not purged properly subsequently. 4. I have invested in a 4 TB external hard-drive as well as a further three 2 TB external hard-drives so that I cans et up some sort of rotating system as Richard Gaskin suggested. 5. I am using a 1 TB partiion on one of the 2 TB hard drives as a Time-Machine disk for my newly acquired 2006 Intel Mac. As I was completely unable to retrieve the log files from my hosed system I have no way of knowing what zonked my Linux system. What I do know is as follows: A. The computer (DELL Optiplex 754) works perfectly alright, having had it up and running doing forensic stuff on a variety of Live Disks (Xubuntu 16.04, GParted, Hiren's). B. The night before it "died" I was accessing an external disk that was freezing up the machine, and I wonder if the "culprit" was something on that disk. Richmond. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: [OT] unhosing .rev and .livecode files
I use Time Machine for hourly backups, mirror my LC stacks folder on Dropbox (so every change is also saved in the cloud), then in addition I have a peripheral hard drive at work where I back up my work stacks every time I close down for the day. I once lost over 2 weeks of notes due to a disk crash, and that taught me that it’s not a matter of *if* a disk will fail, it’s a matter of *when*. Never again. — Peter Peter M. Brigham pmb...@gmail.com > On Dec 4, 2016, at 10:54 AM, Rick Harrisonwrote: > > “Diskwarrior" is a good tool to use in addition to “Data Rescue”. > If you have to go as far as using “Disk Rescue” you have had > some major problem and may not have been doing your > backups routinely enough. > > If you already have a safe-deposit box at a bank, you may want to > consider using that as your offsite backup storage place. The idea > being that you have a couple of backup drives, one at home and > one in the bank. Every week or day depending on how much you think > you can afford to lose, visit the bank and swap the drives. Then you > aren’t trusting the internet with important backups. > > Yes it’s old school, but it works! > > Just my 2 cents for the day. ;-) > > Rick > >> On Dec 3, 2016, at 10:28 PM, Jerry Jensen wrote: >> >> Just one additional level of warning - if you keep Dropbox or Google Drive >> online, malware can get there too. Usually the baddies just trash your >> directory, but if they encrypt everything you have accessible online, >> Dropbox and Google Drive won’t help you. Offline backup is essential, >> offsite is even better. >> > > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: [OT] unhosing .rev and .livecode files
“Diskwarrior" is a good tool to use in addition to “Data Rescue”. If you have to go as far as using “Disk Rescue” you have had some major problem and may not have been doing your backups routinely enough. If you already have a safe-deposit box at a bank, you may want to consider using that as your offsite backup storage place. The idea being that you have a couple of backup drives, one at home and one in the bank. Every week or day depending on how much you think you can afford to lose, visit the bank and swap the drives. Then you aren’t trusting the internet with important backups. Yes it’s old school, but it works! Just my 2 cents for the day. ;-) Rick > On Dec 3, 2016, at 10:28 PM, Jerry Jensenwrote: > > Just one additional level of warning - if you keep Dropbox or Google Drive > online, malware can get there too. Usually the baddies just trash your > directory, but if they encrypt everything you have accessible online, Dropbox > and Google Drive won’t help you. Offline backup is essential, offsite is even > better. > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: [OT] unhosing .rev and .livecode files
Just one additional level of warning - if you keep Dropbox or Google Drive online, malware can get there too. Usually the baddies just trash your directory, but if they encrypt everything you have accessible online, Dropbox and Google Drive won’t help you. Offline backup is essential, offsite is even better. > On Dec 3, 2016, at 6:46 PM, Kay C Lanwrote: > > Hi Richmond, > > Glad to hear that you've been able to rescue most of your files. The > Data Rescue programme I use is imaginatively called 'Data Rescue' by > Prosoft. I don't think it would help in your case as I don't think the > Mac version can recover non-Mac HDs. The reason I mention it is that > it has a feature called 'FileIQ', so you drag a .livecode file onto > FileIQ, it then learns the structure of an LC file, then you can Start > Data Rescue to search all similar such files on a HD. I'm sure it > wouldn't be the only Disk Rescue programme that supported such a > feature. > > Good luck. > > PS. Every single LC stack I create, no matter how large, small, > trivial or world changing, sits in a suitably named folder within a > generic folder 'my stacks' which lives on my Google Drive. I have > plenty of back-up options (as covered by Richard) as I just can't > afford to loose a HD, but for reasons I can't explain, for LC Stacks I > feel it necessary to have quadruple redundancy back-up. Some one on > this List mentioned using Dropbox or Google Drive as a working > location for their stacks, and since following that advise I've been > most thankful. No fuss, no thought, works a treat. > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: [OT] unhosing .rev and .livecode files
Hi Richmond, Glad to hear that you've been able to rescue most of your files. The Data Rescue programme I use is imaginatively called 'Data Rescue' by Prosoft. I don't think it would help in your case as I don't think the Mac version can recover non-Mac HDs. The reason I mention it is that it has a feature called 'FileIQ', so you drag a .livecode file onto FileIQ, it then learns the structure of an LC file, then you can Start Data Rescue to search all similar such files on a HD. I'm sure it wouldn't be the only Disk Rescue programme that supported such a feature. Good luck. PS. Every single LC stack I create, no matter how large, small, trivial or world changing, sits in a suitably named folder within a generic folder 'my stacks' which lives on my Google Drive. I have plenty of back-up options (as covered by Richard) as I just can't afford to loose a HD, but for reasons I can't explain, for LC Stacks I feel it necessary to have quadruple redundancy back-up. Some one on this List mentioned using Dropbox or Google Drive as a working location for their stacks, and since following that advise I've been most thankful. No fuss, no thought, works a treat. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: [OT] unhosing .rev and .livecode files
That sounds great, but I wonder exactly how I should look for the file headers. Richmond. On 12/3/16 7:42 pm, Stephen Barncard wrote: On Sat, Dec 3, 2016 at 7:58 AM, Richmond Mathewson < richmondmathew...@gmail.com> wrote: files, and NOT .rev and .livecode files I wonder if anyone has any bright suggestions how one might go about looking for them. Look for the file header text at the beginning of every stack: like REVO7000 REVO5500 you may need to do research on the headers for the vintage stack formats. -- Stephen Barncard - Sebastopol Ca. USA - mixstream.org ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: [OT] unhosing .rev and .livecode files
On Sat, Dec 3, 2016 at 9:42 AM, Stephen Barncardwrote: > Look for the file header text at the beginning of every stack: > > like > REVO7000 > REVO5500 > There should also be a file termination character(s) -- Stephen Barncard - Sebastopol Ca. USA - mixstream.org ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: [OT] unhosing .rev and .livecode files
On Sat, Dec 3, 2016 at 7:58 AM, Richmond Mathewson < richmondmathew...@gmail.com> wrote: > files, and NOT .rev and .livecode files I wonder if anyone has any bright > suggestions how one might > go about looking for them. > Look for the file header text at the beginning of every stack: like REVO7000 REVO5500 you may need to do research on the headers for the vintage stack formats. -- Stephen Barncard - Sebastopol Ca. USA - mixstream.org ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode