InCD and Retrospect, are they not playing nice together?
Posted: Wed Oct 15, 2003 7:06 amWith Win 2000 SP 4, Retrospect 6.5 and InCD 3.5.24.0, I appear to be seeing the following behavior:
1. I periodically save the Retrospect catalog files to CD-RW, along with the config65.dat file.
2. After copyimg the files to the CD-RW and removing the CD-RW media, I am finding that if I run Retrospect without rebooting the system, a BSOD occurs not too long after I start running a Retrospect job. This has occurred the last 3 times I copied the files to the CD-RW. Note that Retrospect does not have to be run right away fpr the problem to occur.
My theory is that InCD is somehow preventing Retrospect from modifying the Retrospect catalog files because the BSOD seems to occur at a point at which I would expect that Retrospect is trying to update the catalog.
If I reboot the system, no such problem.
I cannot try this with InCD 4 because InCD 4 still has the Word bug, so I'm stuck with InCD 3.
1. I periodically save the Retrospect catalog files to CD-RW, along with the config65.dat file.
2. After copyimg the files to the CD-RW and removing the CD-RW media, I am finding that if I run Retrospect without rebooting the system, a BSOD occurs not too long after I start running a Retrospect job. This has occurred the last 3 times I copied the files to the CD-RW. Note that Retrospect does not have to be run right away fpr the problem to occur.
My theory is that InCD is somehow preventing Retrospect from modifying the Retrospect catalog files because the BSOD seems to occur at a point at which I would expect that Retrospect is trying to update the catalog.
If I reboot the system, no such problem.
I cannot try this with InCD 4 because InCD 4 still has the Word bug, so I'm stuck with InCD 3.