After having cleaned a machine of extraneous software (etc.) I discovered one of my programs, CDBurnerXP Pro, would no longer run. It would hang when starting. The other odd thing was that When I started BibleDatabase it would start an installer for CDBurnerXP Pro. (Earlier that week, both had worked fine) The installer would attempt to run at least three times and would continue to loop until it was cancelled before it could rewind itself. Then Bibledatabase would start with the book of Revelation.
I stripped ALL references to CDBurnerXP from my registry and machine through some tedious regedit sessions. Now when I start Bibledatabase the problem is all but gone. I no longer have any reference I can see (everything moves too quickly) to cdburnerxp but the installer attempts to start three times before BibleDatabase comes on-screen to the search screen. Thereafter the program functions normally.
I am curious about the hook to the installer. It is the process log for the startup of BibleDatabase, recording all the called processes and their success or failure. I believe the msiexec calls that punctuate the load may be those hooks which used to attempt to install cdburnerxp Pro.

By the way: I subsequently reinstalled cdburnerxp pro and tested to see if it would work and if it would impact BibleDatabase. It worked and had no impact on BD.

The process monitoring program I used was filemon from sysinternals. There is also an utility to monitor registry activity and if I run that I will send it on as well. I have no idea how the two programs got hooked. Nothing done should have impacted them whatsoever. Hmmm.!

I'm hoping it will not be your recommendation to reinstall BD. It would involve reinstalling texts, including one you don't seem to have any more. In addition, there are no registry entries for BD. It is a Drag-N-Drop copy which has worked fine until this interesting hook.

Pleas advise. And thank you in advance for any response.

I honestly don't know. Never seen or heard of this before. I thought I heard and seen it all but this one is out of the blue for me. Sorry.

This is a followup: Thank you BDH for attempting at least to respond. But frankly, "I honestly don't know. Never seen or heard of this before. I thought I heard and seen it all but this one is out of the blue for me. Sorry." doesn't work. This, undoubtedly, is an executable code issue and needs more than a "sorry" to address its issue. The energy the BD people have spent on "push technology" to "get to know me better" would be more impressive if that same level of proactive interest was spent on getting to the bottom of the problem.
I'd prefer he deal with this on technical issues rather than "throw mud against the wall to see what sticks" in a forum. I am clergy. I can appreciate the collateral evangelical interest which hovers around the DB but I have a non-theological question: Why does the program hook the installer and create the issue? How can I resolve it?
I have included the log file with the CPU calls at the bottom of this email for review. Here, numbered, is the analysis of the CPU calls which are taking place:
1. The BD begins after a double-click (the initial CPU call is #133) on its icon and then goes through normal CPU calls

2. I have annotated the various calls that are not the problem by creating a white space, a comment and another white space. I include the information because it may be pertinent to programmers

3. The problem appears at call #611. When CDBurnerPro was installed on the machine BD would call CDBurnerPro to install (It was already installed). I uninstalled CDBurnerPro. The call still happened. I uninstalled BD, then put BD back. It still made the MSI calls but did not mention CDBurnerPro. I subsequently reinstalled CDBurnerPro and it works fine. BD continues to call a dead-end MSI. It no longer mentions CDBurnerPro. It just flashes the installer screen and then it disappears.

4. After BD starts, it runs fine and there is no other issue until the next startup.

THE LOG FILE IS BELOW
PLEASE PASS THIS ON TO SOMEONE WHO CAN UNDERSTAND THE PROGRAMMING ISSUES ---+++I SUSPECT THIS IS A BUG +++---


Information prior to call #133 was the starting of the file-to-CPU monitoring program (filemon.exe from SysInternals)(This file is best viewed in a wide format so the numbers align on the left column):
...
133 9:55:02 PM explorer.exe:3068 SET INFORMATION C:\Documents and Settings\BCAM\ntuser.dat.LOG SUCCESS Length: 28672
134 9:55:02 PM BibleDatabase.e:2980 QUERY INFORMATION C:\Program Files\BibleDatabase\BibleDatabase.exe SUCCESS FileNameInformation
135 9:55:02 PM BibleDatabase.e:2980 QUERY INFORMATION C:\Program Files\BibleDatabase\BibleDatabase.exe SUCCESS FileNameInformation
136 9:55:02 PM BibleDatabase.e:2980 OPEN C:\WINDOWS\Prefetch\BIBLEDATABASE.EXE-35BB0AF1.pf SUCCESS Options: Open Access: Read
137 9:55:02 PM BibleDatabase.e:2980 OPEN C:\WINDOWS\Prefetch\ SUCCESS Options: Open Directory Access: 00100000
138 9:55:02 PM BibleDatabase.e:2980 QUERY INFORMATION C:\WINDOWS\Prefetch\BIBLEDATABASE.EXE-35BB0AF1.pf SUCCESS Length: 27582
139 9:55:02 PM BibleDatabase.e:2980 READ C:\WINDOWS\Prefetch\BIBLEDATABASE.EXE-35BB0AF1.pf SUCCESS Offset: 0 Length: 27582
140 9:55:02 PM BibleDatabase.e:2980 OPEN C:\Program Files\BibleDatabase SUCCESS Options: Open Directory Access: 00100020
141 9:55:02 PM BibleDatabase.e:2980 OPEN C:\Program Files\ SUCCESS Options: Open Directory Access: 00100000
142 9:55:02 PM BibleDatabase.e:2980 QUERY INFORMATION C:\Program Files\BibleDatabase\BibleDatabase.exe.Local NOT FOUND Attributes: Error

143 through 298 passes BD through the Firewall (ZoneAlarm) screening process for permission to function. BD then continues:

299 continues with BD:

326 begins verification section for WinPatrol, a resident startup controller monitor

338 BD resumes its startup:

410 At this point BD queries the Kernel and moves to the shell

432 begins csrss calls:


487 BD resumes:

517 additional csrss calls:

574 BD resumes:


611 IS WHERE THE PROBLEM BEGINS. IT CONTINUES UNTIL THE PROGRAM IS FULLY LOADED AND THEN QUITS. YOU CAN FOLLOW THE PATTERN:

611 9:55:02 PM BibleDatabase.e:2980 QUERY INFORMATION C:\WINDOWS\system32\msi.dll SUCCESS Attributes: A
612 9:55:02 PM BibleDatabase.e:2980 QUERY INFORMATION C:\WINDOWS\system32\ADVAPI32.DLL SUCCESS Attributes: A
613 9:55:02 PM BibleDatabase.e:2980 QUERY INFORMATION C:\WINDOWS\system32\SAGE.DLL NOT FOUND Attributes: Error
614 9:55:02 PM BibleDatabase.e:2980 QUERY INFORMATION C:\WINDOWS\system32\SAGE.DLL NOT FOUND Attributes: Error
615 9:55:02 PM msiexec.exe:3432 QUERY INFORMATION C:\WINDOWS\TEMP SUCCESS Attributes: D
616 9:55:02 PM msiexec.exe:3432 QUERY INFORMATION C:\WINDOWS\TEMP SUCCESS Attributes: D
617 9:55:02 PM msiexec.exe:3432 QUERY INFORMATION C:\WINDOWS\TEMP SUCCESS Attributes: D
618 9:55:02 PM msiexec.exe:3432 QUERY INFORMATION C:\WINDOWS\TEMP SUCCESS Attributes: D
619 9:55:02 PM msiexec.exe:3432 QUERY INFORMATION C:\autoexec.bat SUCCESS Attributes: A
620 9:55:02 PM msiexec.exe:3432 OPEN C:\autoexec.bat SUCCESS Options: Open Access: Read
621 9:55:02 PM msiexec.exe:3432 OPEN C:\ SUCCESS Options: Open Directory Access: 00100000
622 9:55:02 PM msiexec.exe:3432 OPEN C:\ SUCCESS Options: Open Directory Access: 00100000
623 9:55:02 PM msiexec.exe:3432 QUERY INFORMATION C:\autoexec.bat SUCCESS Length: 0
624 9:55:02 PM msiexec.exe:3432 READ C:\autoexec.bat SUCCESS Offset: 0 Length: 0
625 9:55:02 PM msiexec.exe:3432 CLOSE C:\autoexec.bat SUCCESS
626 9:55:02 PM msiexec.exe:3432 QUERY INFORMATION C:\Documents and Settings\BCAM\Local Settings\Temp SUCCESS Attributes: D
627 9:55:02 PM msiexec.exe:3432 OPEN C:\ SUCCESS Options: Open Directory Access: 00100001
628 9:55:02 PM msiexec.exe:3432 DIRECTORY C:\ SUCCESS FileBothDirectoryInformation: Documents and Settings
629 9:55:02 PM msiexec.exe:3432 CLOSE C:\ SUCCESS
630 9:55:02 PM msiexec.exe:3432 OPEN C:\Documents and Settings\BCAM\ SUCCESS Options: Open Directory Access: 00100001
631 9:55:02 PM msiexec.exe:3432 OPEN C:\Documents and Settings\ SUCCESS Options: Open Directory Access: 00100000
632 9:55:02 PM msiexec.exe:3432 DIRECTORY C:\Documents and Settings\BCAM\ SUCCESS FileBothDirectoryInformation: Local Settings
633 9:55:02 PM msiexec.exe:3432 CLOSE C:\Documents and Settings\BCAM\ SUCCESS
634 9:55:02 PM msiexec.exe:3432 QUERY INFORMATION C:\Documents and Settings\BCAM\Local Settings\Temp SUCCESS Attributes: D
635 9:55:02 PM msiexec.exe:3432 OPEN C:\ SUCCESS Options: Open Directory Access: 00100001
636 9:55:02 PM msiexec.exe:3432 DIRECTORY C:\ SUCCESS FileBothDirectoryInformation: Documents and Settings
637 9:55:02 PM msiexec.exe:3432 CLOSE C:\ SUCCESS
638 9:55:02 PM msiexec.exe:3432 OPEN C:\Documents and Settings\BCAM\ SUCCESS Options: Open Directory Access: 00100001
639 9:55:02 PM msiexec.exe:3432 OPEN C:\Documents and Settings\ SUCCESS Options: Open Directory Access: 00100000
640 9:55:02 PM msiexec.exe:3432 DIRECTORY C:\Documents and Settings\BCAM\ SUCCESS FileBothDirectoryInformation: Local Settings
641 9:55:02 PM msiexec.exe:3432 CLOSE C:\Documents and Settings\BCAM\ SUCCESS
642 9:55:02 PM msiexec.exe:3432 QUERY INFORMATION C:\WINDOWS\system32\SFC.DLL SUCCESS Attributes: A
643 9:55:02 PM msiexec.exe:3432 OPEN C:\WINDOWS\system32\SFC.DLL SUCCESS Options: Open Access: 00100020
644 9:55:02 PM msiexec.exe:3432 OPEN C:\WINDOWS\system32\ SUCCESS Options: Open Directory Access: 00100000
645 9:55:02 PM msiexec.exe:3432 OPEN C:\WINDOWS\system32\ SUCCESS Options: Open Directory Access: 00100000
646 9:55:02 PM msiexec.exe:3432 QUERY INFORMATION C:\WINDOWS\system32\SFC.DLL SUCCESS Length: 5120
647 9:55:02 PM msiexec.exe:3432 CLOSE C:\WINDOWS\system32\SFC.DLL SUCCESS
648 9:55:02 PM msiexec.exe:3432 QUERY INFORMATION C:\WINDOWS\system32\SFC.DLL SUCCESS Attributes: A
649 9:55:02 PM msiexec.exe:3432 OPEN C:\WINDOWS\system32\SFC.DLL SUCCESS Options: Open Access: 00100020
650 9:55:02 PM msiexec.exe:3432 OPEN C:\WINDOWS\system32\ SUCCESS Options: Open Directory Access: 00100000
651 9:55:02 PM msiexec.exe:3432 OPEN C:\WINDOWS\system32\ SUCCESS Options: Open Directory Access: 00100000
652 9:55:02 PM msiexec.exe:3432 CLOSE C:\WINDOWS\system32\SFC.DLL SUCCESS
653 9:55:02 PM msiexec.exe:3432 QUERY INFORMATION C:\WINDOWS\system32\sfc_os.dll SUCCESS Attributes: A
654 9:55:02 PM msiexec.exe:3432 OPEN C:\WINDOWS\system32\sfc_os.dll SUCCESS Options: Open Access: 00100020
655 9:55:02 PM msiexec.exe:3432 OPEN C:\WINDOWS\system32\ SUCCESS Options: Open Directory Access: 00100000
656 9:55:02 PM msiexec.exe:3432 OPEN C:\WINDOWS\system32\ SUCCESS Options: Open Directory Access: 00100000
657 9:55:02 PM msiexec.exe:3432 CLOSE C:\WINDOWS\system32\sfc_os.dll SUCCESS



658 9:55:02 PM explorer.exe:3068 QUERY INFORMATION C:\WINDOWS\system32\msi.dll SUCCESS Attributes: A
659 9:55:02 PM explorer.exe:3068 QUERY INFORMATION C:\Program Files\BibleDatabase\BibleDatabase.exe SUCCESS Attributes: RA


660 9:55:02 PM BibleDatabase.e:2980 QUERY INFORMATION C:\WINDOWS\system32\SAGE.DLL NOT FOUND Attributes: Error
661 9:55:02 PM BibleDatabase.e:2980 QUERY INFORMATION C:\WINDOWS\system32\SAGE.DLL NOT FOUND Attributes: Error
662 9:55:02 PM BibleDatabase.e:2980 QUERY INFORMATION C:\WINDOWS\system32\mscomctl.ocx SUCCESS Attributes: A
663 9:55:02 PM BibleDatabase.e:2980 OPEN C:\WINDOWS\system32\mscomctl.ocx SUCCESS Options: Open Access: 00100020
664 9:55:02 PM BibleDatabase.e:2980 OPEN C:\WINDOWS\system32\ SUCCESS Options: Open Directory Access: 00100000
665 9:55:02 PM BibleDatabase.e:2980 OPEN C:\WINDOWS\system32\ SUCCESS Options: Open Directory Access: 00100000
666 9:55:02 PM BibleDatabase.e:2980 QUERY INFORMATION C:\WINDOWS\system32\mscomctl.ocx SUCCESS Length: 1071088
667 9:55:02 PM BibleDatabase.e:2980 CLOSE C:\WINDOWS\system32\mscomctl.ocx SUCCESS
668 9:55:02 PM BibleDatabase.e:2980 QUERY INFORMATION C:\WINDOWS\system32\mscomctl.ocx SUCCESS Attributes: A
669 9:55:02 PM BibleDatabase.e:2980 OPEN C:\WINDOWS\system32\mscomctl.ocx SUCCESS Options: Open Access: 00100020
670 9:55:02 PM BibleDatabase.e:2980 OPEN C:\WINDOWS\system32\ SUCCESS Options: Open Directory Access: 00100000
671 9:55:02 PM BibleDatabase.e:2980 OPEN C:\WINDOWS\system32\ SUCCESS Options: Open Directory Access: 00100000
672 9:55:02 PM BibleDatabase.e:2980 CLOSE C:\WINDOWS\system32\mscomctl.ocx SUCCESS
673 9:55:02 PM BibleDatabase.e:2980 QUERY INFORMATION C:\DOCUME~1\BCAM\LOCALS~1\Temp\~DF9C88.tmp SUCCESS Length: 16384
674 9:55:02 PM BibleDatabase.e:2980 SET INFORMATION C:\DOCUME~1\BCAM\LOCALS~1\Temp\~DF9C88.tmp SUCCESS Length: 32768
675 9:55:02 PM BibleDatabase.e:2980 READ C:\DOCUME~1\BCAM\LOCALS~1\Temp\~DF9C88.tmp SUCCESS Offset: 16384 Length: 16384


676 9:55:02 PM services.exe:600 WRITE C:\WINDOWS\system32\config\AppEvent.Evt SUCCESS Offset: 33556 Length: 320
677 9:55:02 PM services.exe:600 WRITE C:\WINDOWS\system32\config\AppEvent.Evt SUCCESS Offset: 33876 Length: 40

678 BD MAKES 2ND MSI CALL AND MAKES A TOTAL OF THREE BEFORE IT FINISHES LOADING AT CPU CYCLE :

It is unfortunate you have a text character length cap on tech questions, making the posting of a complete log impossible.
In spite of my current misgivings about your tech forum, thank you in advance for any further assistance you can provide. Pleas pass this on to developers if necessary.

I am the author of the software btw, so I know exactly how it works. To be really blunt, I don't have the resources to analyze this in detail which is why I answered you the way I did.

What you need to understand is there are over 2 million copies of this software out there that work. Yours does not, so I can say with a reasonable probability of over 1 million : 1 that the problem is on your PC and not with the software.

FWIW it looks like your system is broken. SAGE.DLL is part of windows and has nothing to do with bibledatabase. Your system is reporting

C:\WINDOWS\system32\SAGE.DLL NOT FOUND Attributes: Error SAGE.DLL

Author:Microsoft Corporation

Part of:Microsoft® Windows® Task Scheduler

Thank you so much for your very rapid reply. You are, indeed, correct: it is a corruption within the Windows system and that is what I was attempting to trace down. As it continued to dog BibleDatabase and not other programs, that is the motivation to attempt to understand the hook and "unhook" it. It does not impact the newest version of BD and I will use that. Another interesting thing is that sage.dll is not present on my machine (task manager functions being handled by tskmgr.dll) but seems to be called for some unknown reason. Microsoft's msi cleaner does not show any indication there is any sort of an installer issue around BD.
Thank you for your fine work on BD. And may the help forum in the tech corner grow, not leaving the burden so heavily on your shoulders. Thanks again.