| Subject | Re: FB 2.5 and Norton Ghost |
|---|---|
| Author | munster77054 |
| Post date | 2011-02-12T01:43:01Z |
You and I disagree with this. Why?
1. The version I'm using reboots the computer, and runs the backup in PC-DOS mode, so FB Server isn't running.
2. I've NEVER had a problem with NG with any versions of FB, other than 2.5.
3. All surface scans, index (meaning NTFS), etc are clean.
4. The drives were defragged, and free space wiped, both on the "C" drive and the destination drives, and the problem is still was there with 2.5, not 2.1.
5. As previously stated, it happened on two different computers, always in the FB folder, and only when FB 2.5 is installed, not FB 2.1.x.
If it looks like a duck, quacks like a duck, and walks like a duck, it is a duck.
Finally, a friend of mine up north also uses Norton, and FB 2.1.x (version before mine), and it was AOK. He installed FB 2.5 on his secondary machine, and the same thing happened. It isn't NG, it is FB! So three computers, all using NG, from different sources (meaning he bought his up North, and I bought mine in another state), and different computer brand names, and different OS (our computer XP Pro, his XP Home), and the same thing happens.
My friend and I are right, it is FB2.5.
1. The version I'm using reboots the computer, and runs the backup in PC-DOS mode, so FB Server isn't running.
2. I've NEVER had a problem with NG with any versions of FB, other than 2.5.
3. All surface scans, index (meaning NTFS), etc are clean.
4. The drives were defragged, and free space wiped, both on the "C" drive and the destination drives, and the problem is still was there with 2.5, not 2.1.
5. As previously stated, it happened on two different computers, always in the FB folder, and only when FB 2.5 is installed, not FB 2.1.x.
If it looks like a duck, quacks like a duck, and walks like a duck, it is a duck.
Finally, a friend of mine up north also uses Norton, and FB 2.1.x (version before mine), and it was AOK. He installed FB 2.5 on his secondary machine, and the same thing happened. It isn't NG, it is FB! So three computers, all using NG, from different sources (meaning he bought his up North, and I bought mine in another state), and different computer brand names, and different OS (our computer XP Pro, his XP Home), and the same thing happens.
My friend and I are right, it is FB2.5.
--- In firebird-support@yahoogroups.com, Cornie van Schoor <cornievs@...> wrote:
>
> I am sure you are looking at the wrong source. Reading any data in the
> way NG does, can in no way "send a shutdown/powerdown signal to
> windows", but keep in mind that your fb server maybe running and that it
> maybe updating the log file and sweeping your db's. Maybe it is not
> true anymore in the newer versions, but the one thing I learned about NG
> is that is it expect the "disk image" to be the same to when it started
> compared to while its running and completing. Having any server
> running, while doing a NG is sure way to have a bad image. There are
> cases where NG can not detect the actual changes to the partition, but
> may be aware of that there were changes, and maybe that leads to the
> "shutdown"?
>
>
> > > >
> > > > Something is wrong with FB 2.5, there is something in it, that when
> > > > Norton Ghost reads it, it sends a powerdown signal to my (and my
> > > > wife's) computer. Looks like I'm stuck on FB 2.1.x until further
> > > > notice!
> > >
> >
>