Settings:
L1= 256MB
L2= 10240MB
Block size= 8KB
Strategy= Read-data & Write-data
Defer-Write= 10s
Target: F:\ (NTFS, system partition)
Level2: Z:\ (1 of 3 partitions on Transcend 32GB IDE SSD)
My Windows XP32 is up to date.
Sometime, when Norton Ghost 10.0 is backing up F:\, the computer restart.
The level2 cache is killed of course.
And to be sure that all'll work fine, after the problem occurs, I've to reinstall PrimoCache from scrach.
We had the same issue with earlier versions of PrimoCache.
Best regards.
Windows XP32, PrimoCache 1.0.1 and Norton Ghost 10.0 Topic is solved
Re: Windows XP32, PrimoCache 1.0.1 and Norton Ghost 10.0
Thanks for your bug report!
I'll update this thread if we have any news.
I'll update this thread if we have any news.
Re: Windows XP32, PrimoCache 1.0.1 and Norton Ghost 10.0
Ok!
I tried to have my little brain at work this few late days.
And I found this on your FAQ page: http://www.romexsoftware.com/en-us/primo-cache/faq.html
Q: My boot partition is write protected, and I find that contents stored in level-2 storages always become invalid and useless after computer restarts.
A: PrimoCache implements a mechanism to check if cache contents stored in level-2 storages are synced with source disks. It traces and updates flags saved in Windows registry. However if boot partition is write protected, which means that these flags won't be updated, PrimoCache will think that level-2 cache contents are out of sync and reset contents.
Here is the important sentence:
It traces and updates flags saved in Windows registry.
I think that what is wrong is the use of cleaner/defagger registery tools.
I need your advice about this because I clean and defrag the registry every sunday since many years. My Windows XP32 was installed the 07/15/2007 for the last time. And before using PrimoCache I never had any problem, my PC run 24/7.
I think that I can clean the registry but have to stop to defrag...
What do you think about this?
I tried to have my little brain at work this few late days.
And I found this on your FAQ page: http://www.romexsoftware.com/en-us/primo-cache/faq.html
Q: My boot partition is write protected, and I find that contents stored in level-2 storages always become invalid and useless after computer restarts.
A: PrimoCache implements a mechanism to check if cache contents stored in level-2 storages are synced with source disks. It traces and updates flags saved in Windows registry. However if boot partition is write protected, which means that these flags won't be updated, PrimoCache will think that level-2 cache contents are out of sync and reset contents.
Here is the important sentence:
It traces and updates flags saved in Windows registry.
I think that what is wrong is the use of cleaner/defagger registery tools.
I need your advice about this because I clean and defrag the registry every sunday since many years. My Windows XP32 was installed the 07/15/2007 for the last time. And before using PrimoCache I never had any problem, my PC run 24/7.
I think that I can clean the registry but have to stop to defrag...
What do you think about this?
Re: Windows XP32, PrimoCache 1.0.1 and Norton Ghost 10.0
Oups...
My PC restarts again when Norton Ghost backups the system partition. This time, I hadn't used any Cleaner/Defragger.
I think that I'm wrong in my post above...
My PC restarts again when Norton Ghost backups the system partition. This time, I hadn't used any Cleaner/Defragger.
I think that I'm wrong in my post above...
Re: Windows XP32, PrimoCache 1.0.1 and Norton Ghost 10.0
On my PC, Norton Ghost 10.0 is scheduled to backup 2 partitions.
It backups first G:\ labeled DATAS1. Then it backups F:\ labeled SYSTEM.
The crash happend ALWAYS when backing up the SYSTEM partition. NEVER when backing up the DATAS1 partition.
It'snt a BSOD but a reset. The PC restart that's all.
This last time (02:00 AM in France, today morning) after PC restarted I've run manually the failed scheduled task. The 2 partitions backups had been done successfully.
But some other times, I've to reinstall PrimoCache from scratch to complete the failed scheduled task, if not the PC restart again when trying to backup F:\.
Regards.
It backups first G:\ labeled DATAS1. Then it backups F:\ labeled SYSTEM.
The crash happend ALWAYS when backing up the SYSTEM partition. NEVER when backing up the DATAS1 partition.
It'snt a BSOD but a reset. The PC restart that's all.
This last time (02:00 AM in France, today morning) after PC restarted I've run manually the failed scheduled task. The 2 partitions backups had been done successfully.
But some other times, I've to reinstall PrimoCache from scratch to complete the failed scheduled task, if not the PC restart again when trying to backup F:\.
Regards.
Re: Windows XP32, PrimoCache 1.0.1 and Norton Ghost 10.0
Yes, as you have tested, this issue is not related to the registry flags. We're still checking this issue. Thanks again for your information!
Re: Windows XP32, PrimoCache 1.0.1 and Norton Ghost 10.0
Ok, here we are:
07/01/2014
PrimoCache 1.0.1 - Trial (16 days left)
PrimoCache (Beta) 0.9.1 and Norton Ghost 10.0.
viewtopic.php?f=34&t=2286
norton ghost v.15 and Bsod
viewtopic.php?f=34&t=2352
Norton Ghost 14 and PrimoCache
viewtopic.php?f=34&t=2373
Windows XP32, PrimoCache 1.0.1 and Norton Ghost 10.0
viewtopic.php?f=34&t=2599
It's a pity that till now the issue about many (all?) versions of Norton Ghost isn't fixed.
The question is: "Can I really buy a non-reliable software wich otherwise works fine?"
Best regards
07/01/2014
PrimoCache 1.0.1 - Trial (16 days left)
PrimoCache (Beta) 0.9.1 and Norton Ghost 10.0.
viewtopic.php?f=34&t=2286
norton ghost v.15 and Bsod
viewtopic.php?f=34&t=2352
Norton Ghost 14 and PrimoCache
viewtopic.php?f=34&t=2373
Windows XP32, PrimoCache 1.0.1 and Norton Ghost 10.0
viewtopic.php?f=34&t=2599
It's a pity that till now the issue about many (all?) versions of Norton Ghost isn't fixed.
The question is: "Can I really buy a non-reliable software wich otherwise works fine?"
Best regards
Re: Windows XP32, PrimoCache 1.0.1 and Norton Ghost 10.0
I'm really sorry about this BSOD problem. We finally find the root cause and now fixed it in version 2.3.0.
Thank you all!
Thank you all!