At 11:24 AM 2/29/00 -0500, you wrote: >Another way to insure backups of revisions is to get an HP CD Burner and >use their Simpltrax software that comes with it. It will backup changed >files in any directories you specify and all old revisions are also >available on the CD. This gives full revision history and you never >overwrite the older revisions. It works well for me and doesn't waste space >if nothing is changed. Fairly cheap insurance. > > If you have an extra box and you're Linux savvy you should consider setting up CVS. It allows revision control and history, along with diff based merges of files that multiple people are editing all over the network. There is a java extension to it that allows it to work on about any platform. With cygnus stuff you may even be able to set up CVS ona windows box but I've never tried it. HTH > >At 01:17 PM 11/18/99 -0800, you wrote: >>Wagner Lipnharski wrote: >>> >>> I already have lots of troubles to keep track of what version is the >>> last one, with so many protection copies, backups, moving disks from one >>> computer to another and so on. I am *not* that organized. It was the >>> version I changed code in the office, or at the lab?, or the one I did >>> at my home last night? I changed it last night? or it was something >>> else?... arggg, too old! brain is starting to fail. >>> >>> Wagner. >> >>How I handle source backups, in a Batch file; I run this once per >>BOOTUP, usually - yeah, eats space - but it means I have CURRENT >>backups, always. I do the same with other critical files. Inline'd >>some called subroutines. Yeah, no comments, so shoot me (And I >>usually put each project's name in place of the "Backup" part of the zip >>files below, this is "genericized" somewhat.) Keep meaning to write a >>Pascal or C program to handle doing this with more "uniqueness" (i.e. >>don't end up with 7 copies of the same version), but haven't. >> >>> if not exist c:\Source\Backups\nul md c:\Source\Backups >>> c: >>> cd c:\Source >>> c:\utils\pkzip -f -ex -o _backup >>> cd c:\Source\Backups >>> del Backup_9.zip >>> ren Backup_8.zip Backup_9.zip >>> ren Backup_7.zip Backup_8.zip >>> ren Backup_6.zip Backup_7.zip >>> ren Backup_5.zip Backup_6.zip >>> ren Backup_4.zip Backup_5.zip >>> ren Backup_3.zip Backup_4.zip >>> ren Backup_2.zip Backup_3.zip >>> ren Backup_1.zip Backup_2.zip >>> ren Backup_0.zip Backup_1.zip >>> ren _Backup_.zip Backup_0.zip >>> copy c:\Source\_Backup.Zip _Backup_.Zip >>> cd \ >> >>Another rule I've learned is, "There CAN BE only ONE master copy of >>source code." So - my master copy gets put on a laptop while in work, >>and STAYS on there, all other copies are slave copies, if I'm likely to >>work on it anywhere but at the development machine. PC110's are GREAT >>for this, work well for text editing for me >> >> Mark >> >>-- >>I do small package shipping for small businesses, world-wide. >> >> >Larry G. Nelson Sr. >mailto:L.Nelson@ieee.org >http://www.ultranet.com/~nr Erik Reikes Senior Software Engineer Xsilogy, Inc. ereikes@xsilogy.com ph : (858) 535-5113 fax : (858) 535-5163 cell : (858) 663-1206