munster77054 wrote:

> You have to remember, just like viruses (I'm not saying FB is malware), all it needs to be is read into memory, and "bang" you been had.

That's not correct. I can read the most destructive code into a data area and nothing happens. Just don't execute it and make sure noone (or nothing) else executes it either.

I don't know NG, but making a disk *image* usually means blindly copying bytes, in the exact order, so you can restore the situation later if needed. Making a disk image does *not* mean executing any code found on the disk!

> It's just like this situation, there must be something in one of the FB files that is causing the problem.

That I believe. But the starting point to look for an answer is NG. You can hardly ask the FB developers "So what did you do that trips Norton Ghost?" But if you alert the NG developers, they should be able to find out *what* in the FB files triggers this behaviour.

> When it gets read, it signals the shutdown.

Again, data being *read* do nothing. Unless the process that reads them makes certain decisions based upon their content.

What's interesting is that the same problem occurs with another disk imaging program. This suggests that the cause is in a common library or system call.


Kind regards,
Paul Vinkenoog