Reply to thread

Message

<blockquote data-quote="stefanos" data-source="post: 830699" data-attributes="member: 29992">[MEDIA=youtube]sE-xdb9hTqY[/MEDIA]<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Hey Bora, I think InstallWatch 2.5 can only record up to 180,000 files for its snapshots.&nbsp; I had to give up on it back around 2012 or so, because of this.&nbsp; Maybe there is a version where this has been changed, not sure...I used to run into this running version 1.2.188360.106 on Windows XP and W7, but I haven&#039;t seen this happen in years.&nbsp; I think it&#039;s more a testament of stabler systems through the years than anything I suppose.&nbsp; Perhaps quirky PC performance of the older systems was to blame in W7.On W10, I&#039;m surprised it&#039;s happening, but there is a simple remedy if anyone is doggedly determined to run the software.&nbsp; The remedy that worked for me was to move the file C:\Fileimage.dat to a secondary drive or flash drive and then reboot to a boot time rescue environment.&nbsp; Safe Mode would probably work, can&#039;t recall if I ever tried SM.&nbsp; From there replace the file to its original location.&nbsp; Also, just rebooting and replacing the file while in Windows and then rebooting again seems to work...CPM is absolutely one of my favorite softwares through the years.&nbsp; For me for some reason it just works lol...</blockquote>

[QUOTE="stefanos, post: 830699, member: 29992"] [MEDIA=youtube]sE-xdb9hTqY[/MEDIA] :):):):) Hey Bora, I think InstallWatch 2.5 can only record up to 180,000 files for its snapshots. I had to give up on it back around 2012 or so, because of this. Maybe there is a version where this has been changed, not sure... I used to run into this running version 1.2.188360.106 on Windows XP and W7, but I haven't seen this happen in years. I think it's more a testament of stabler systems through the years than anything I suppose. Perhaps quirky PC performance of the older systems was to blame in W7. On W10, I'm surprised it's happening, but there is a simple remedy if anyone is doggedly determined to run the software. The remedy that worked for me was to move the file C:\Fileimage.dat to a secondary drive or flash drive and then reboot to a boot time rescue environment. Safe Mode would probably work, can't recall if I ever tried SM. From there replace the file to its original location. Also, just rebooting and replacing the file while in Windows and then rebooting again seems to work... CPM is absolutely one of my favorite softwares through the years. For me for some reason it just works lol... [/QUOTE]

Verification