Hi, I am attempting to migrate a modest project from VSS to SVN.
- Our VSS database DATA folder is approximately 40GB in size. - I am using DESTROY to strip away all but the target project (overnight), - then ANALYZE (at least 20 hours) - and vss2svn.pl to convert. However, vss2svn.pl terminates with one of 2 errors: 1. file corrupted, cannot continue or 2. memory error: "The instruction at "0x28085bc1" referenced memory at "0x000000004". The memory could not be "written"." (This last error occurs during "STARTING CACHE FOR PhysicalAction") Can you help me understand what's going on here and what I might do? Also, can you explain why VSS has so many corruptions (reams and reams from ANALYZE) and yet never corrupts the source? Our developers have never reported any source corruption. David
_______________________________________________ vss2svn-users mailing list Project homepage: http://www.pumacode.org/projects/vss2svn/ Subscribe/Unsubscribe/Admin: http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org Mailing list web interface (with searchable archives): http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
