Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #7324 > unrolled thread

Repository Probably Destroyed and BuildRepo.exe

Started byGlenn Keeler <glennkeeler@shaw.ca>
First post2014-10-16 14:56 -0700
Last post2014-10-17 19:41 -0700
Articles 6 — 3 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Repository Probably Destroyed and BuildRepo.exe Glenn Keeler <glennkeeler@shaw.ca> - 2014-10-16 14:56 -0700
    Re: Repository Probably Destroyed and BuildRepo.exe Glenn Keeler <glennkeeler@shaw.ca> - 2014-10-16 19:52 -0700
      Re: Repository Probably Destroyed and BuildRepo.exe Steve E <steven_emmett@yahoo.co.uk> - 2014-10-16 23:21 -0700
        Re: Repository Probably Destroyed and BuildRepo.exe Glenn Keeler <glennkeeler@shaw.ca> - 2014-10-17 19:44 -0700
    Re: Repository Probably Destroyed and BuildRepo.exe D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2014-10-17 12:07 +0200
      Re: Repository Probably Destroyed and BuildRepo.exe Glenn Keeler <glennkeeler@shaw.ca> - 2014-10-17 19:41 -0700

#7324 — Repository Probably Destroyed and BuildRepo.exe

FromGlenn Keeler <glennkeeler@shaw.ca>
Date2014-10-16 14:56 -0700
SubjectRepository Probably Destroyed and BuildRepo.exe
Message-ID<6bb3033a-f5f0-4a5a-9a11-c19643eb82bc@googlegroups.com>
Just today I have started getting "Repository Probably Destroyed" messages, although the repository happily opens after that. The messages also repeat when I switch projects or when VOPP is exporting my projects on shutdown.

I created a new project into which to import one set of my programs but the message continues to appear.

I have read some of the prior reports where the advice was "make a new repository"... but I don't know how to do that. I have found the file BuildRepo.exe in the bin folder for VO 2.8. 

Does anyone have information for me on how to use this utility to create a new repository?

Thanks

[toc] | [next] | [standalone]


#7325

FromGlenn Keeler <glennkeeler@shaw.ca>
Date2014-10-16 19:52 -0700
Message-ID<f42e0cc7-6227-444b-a970-300e8305dcfb@googlegroups.com>
In reply to#7324
To add a little to this, I have noted that in my system folder there is a SYSTEM_L.IDX file that is dated today for when this issue arose. It is also quite small, 64 bytes.

In a backup from relatively recently, this file is dated 09/30/2009 and is 67,576 bytes.

Before I do something foolish, does anyone have advice as to the effect of restoring this file from my most recent backup?

[toc] | [prev] | [next] | [standalone]


#7327

FromSteve E <steven_emmett@yahoo.co.uk>
Date2014-10-16 23:21 -0700
Message-ID<6ae84d39-8ecf-4c0e-826b-4ccd79baae26@googlegroups.com>
In reply to#7325
Hi Glenn, the file in question is the index for the system library and you will find a copy of this in each project that you have. The one on my machine is 67,576 bytes but a slightly different date to yours because of the point release of VO, the modified date on mine is 25th July 2007 @ 03:03:22. I'm on 2.8 SP2a (2832), I suspect you are on a slightly later patch.

Anyway, in the cavo28\Unsupported\RepoBuilder folder there is a document that describes the build process. This is not something I personally have done but I'm sure some others will have. 

My advise would be to secure the current SYSTEM_L.IDX file and then just restore the one from your backup if that's the only one that is different. If there are more files that are different, then save to folder and restore the full folder from a back-up. I believe that the contents of this folder only change when you install a patch or never version of VO.

[toc] | [prev] | [next] | [standalone]


#7334

FromGlenn Keeler <glennkeeler@shaw.ca>
Date2014-10-17 19:44 -0700
Message-ID<d085943d-8c71-47ca-a0c4-b67abfd34708@googlegroups.com>
In reply to#7327
On Friday, October 17, 2014 12:21:22 AM UTC-6, Steve E wrote:

> My advise would be to secure the current SYSTEM_L.IDX file and then just 
> restore the one from your backup if that's the only one that is different. 

Thanks Steve. I did successfully restore that file and life has returned to normal. It makes me thankful for my regular backups!

[toc] | [prev] | [next] | [standalone]


#7329

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2014-10-17 12:07 +0200
Message-ID<diq14a5v8qpua3urb8d2ujbrr5td9nrvlk@4ax.com>
In reply to#7324
On Thu, 16 Oct 2014 14:56:31 -0700 (PDT), Glenn Keeler
<glennkeeler@shaw.ca> wrote:

Hello Glenn,
>
>I created a new project into which to import one set of my programs but the message continues to appear.
>I have read some of the prior reports where the advice was "make a new repository"... 
>but I don't know how to do that. I have found the file BuildRepo.exe in the bin folder for VO 2.8. 


This is strange. You make a new repo by creating a new project. Do you
still get the error when you open this new (empty apart from system
files) rep/project? In that case you probably have to reinstall Cavo.
If you have cavo on a second system e.g. a laptop, you can create a
project with the same name + path as your faulty project, rename the
directory and copy the directory from your falty cavo in its place. 

If it looks good there, the problem is definitely somewhere in your
c:\cavoxx dir and not the project itself.

Remember that once you installed everything you can copy 1:1. If I
want cavo on a laptop or something when I travel, I only need to
install Cavo once without updates and settings and I get exactly the
same Cavo + projects as in my main project after I copy all files. I
usually only copy the relevant project directories.

Dick

[toc] | [prev] | [next] | [standalone]


#7333

FromGlenn Keeler <glennkeeler@shaw.ca>
Date2014-10-17 19:41 -0700
Message-ID<18c43cb3-e9cf-4f72-babe-07ab19bce539@googlegroups.com>
In reply to#7329
On Friday, October 17, 2014 4:07:25 AM UTC-6, D. J. W. van Kooten wrote:

> This is strange. You make a new repo by creating a new project. Do you
> still get the error when you open this new (empty apart from system
> files) rep/project? In that case you probably have to reinstall Cavo.
> 
> If you have cavo on a second system e.g. a laptop, you can create a
> project with the same name + path as your faulty project, rename the
> directory and copy the directory from your falty cavo in its place. 

Thanks for your response, Dick. Creating a new project did not fix this issue, which is why I went looking for a damaged or altered file. When I restored SYSTEM_L.IDX from a recent backup (which returned it to the 2009 date and much larger size) the notices about a destroyed repo stopped and I am happily picking up from where I left off. And deeply appreciative that I do not have to reinstall VO!

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web