I ran into a interesting situation, that leads me to believe there is something strange in FB 2.5. Let me explain. For years and years, I've used Norton Ghost to back up my computer. During the build process, I ghost my computer at strategic locations as follows:

(01) COMODO5-BASIC-W2K-(NO-LAN-DVRS)-(NO-DST).GHO
(2a) COMODO5-POST-ACT-NO-DVRS-(NO-DST).GHO
(2b) COMODO5-VIDEO-WIRELESS-DVRS-ONLY-(NO-DST).GHO
(2c) COMODO5-DRIVERS-WIRELESS-(NO-DST).GHO
(03) COMODO5-SP3-(NO-DST).GHO
(04) COMODO5-SP3-COMODO5-AVAST5-VNC-(NO-DST).GHO
(05) COMODO5-SP3-TEXTPAD-ZIP-PDF-PTRS-(NO-DST).GHO
(06) COMODO5-SP3-WIN-UPD-(NO-DST).GHO
(07) COMODO5-SP3-WIN-UPD-SETTINGS-CHGD-(NO-DST).GHO
(08) COMODO5-SP3-OFC-(2007)-PRO-OFC-UPD-(NO-DST).GHO
(09) COMODO5-SP3-APPS-AVS-PSE-NO-BDS4(JCL3)-MYSQL-(NO-DST).GHO
(10) COMODO5-SP3-BDS4(JCL3)-MYSQL-(NO-DST).GHO
(11) COMODO5-SP3-BDS4(JCL3)-FF3-RF-PSE-AVS-MYSQL-(NO-DST)-FF3.GHO

I do this, so, if I have to, I can fall back to point "X", and not have to redo everything. For instance, if I'm going to install new software, and I want it in the "base configuration", I then restore (09), put the new software in, then do (10) and (11) again.

Well, I decided to install FB 2.5, I restored my system to (09), uninstalled FB 2.1.x, installed FB 2.5.X, and tried to ghost it. At around 50-60%, my system powered down. Thought this was weird, so I tried it again, but directed the ghost image to another HDD. It failed again. I ran CHKDSK on all drives, they were clean, I then on my one external HDD, I removed files, and got the free space up to 250GB. I compressed (defragged) the drive, and then tried FB 2.5 again, still failed.

I then restored the system to the 2.1.x version of (09), and ghosted, and it worked perfectly. Since between each ghost (of 2.5.x), I purged the "bad" ghost image, used a program that cleared the free space, I knew that the same part of the disks would be used (it was 4 parts, with 3 parts being 2GB in side), since Windows writes from first empty space to the end.

This tells me that there is something weird in FB 2.5.x, because my system wouldn't power down when I did ghosted 2.1.x, but it did on 2.5.x, AND each time I was watching the ghost progression, all I can say for sure, is that it was in the Firebird program files folder.

It can't just be a coincidence that it happens always in the FB folder, when I'm ghosting the drive with FB 2.5, and only happens with FB 2.5 and not FB 2.1.x. It also happends at the same spot regardless of where I direct the ghost output.

This is the first time this type of thing has happened over the years, and it is always on FB 2.5, not FB 2.1.x, the chkdsks come up clean, so EVERYTHING, I REPEAT EVERYTHING says it's FB 2.5 causing the issue.

It should also be noted, that my "C" drive has been defragged also, and by using the "find file" ability, I have been able to determine that each time the ghost failed, the files were in different locations on my HDD, and couple that with the success of 2.1.X FB ghosting, proves, which I also checked with the find file ability (what shows the exact location on the HDD), there is no way that is is a bad HDD.

Finally, it should be noted, that this happened on my LAPTOP and my WIFE'S laptop, and it was consistant between both computers. It happened in the FB directory, and the ghost image was being save to different HDD (including an external), and it kept blowing up.

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!