Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: When starting computer, multiple DIAdem attempted startups (5 copies try to start) and errors.
33 views
Skip to first unread message
Twigeater
Mar 26, 2008, 4:40:08 PM3/26/08
to
Hello David!
You can try the free SysInternals (now Microsoft) too AutoRuns to determine wich programs are started in the boot sequence. You can download this verry good tool here: <a href="http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx" target="_blank">http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx</a>
Hope this helps
Matthias
You can try the free SysInternals (now Microsoft) too AutoRuns to determine wich programs are started in the boot sequence. You can download this verry good tool here: <a href="http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx" target="_blank">http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx</a>
Hope this helps
Matthias
Brad Turpin
Mar 27, 2008, 9:40:12 AM3/27/08
to
Hi David,
DIAdem does not by default start at boot up, and certainly it does not by default launch 5 times when it is started. It sounds to me like you or someone else has configured that computer to run DIAdem at boot time. The fact that DIAdem is throwing an error when starting and complaining that the DataFinder can't be started is something I've seen before, but always when DIAdem has been intentionally started.
Have you looked into the "Start Menu\Programs\Startup" directory to see if DIAdem.exe is there? It is also possible to configure services and applications to start at boot time in various Windows configuration dialogs, but I'm no expert there.
Do you see this behavior on any other computers?Brad TurpinDIAdem Product Support EngineerNational Instruments
DIAdem does not by default start at boot up, and certainly it does not by default launch 5 times when it is started. It sounds to me like you or someone else has configured that computer to run DIAdem at boot time. The fact that DIAdem is throwing an error when starting and complaining that the DataFinder can't be started is something I've seen before, but always when DIAdem has been intentionally started.
Have you looked into the "Start Menu\Programs\Startup" directory to see if DIAdem.exe is there? It is also possible to configure services and applications to start at boot time in various Windows configuration dialogs, but I'm no expert there.
Do you see this behavior on any other computers?Brad TurpinDIAdem Product Support EngineerNational Instruments
DavidF
Mar 27, 2008, 10:10:11 AM3/27/08
to
Helllo Brad (and Matthias),
I have been using the tool Matthias recommended and it is indeed a very useful program. It looks like I can stop it from doing the autostart. However, I did not intentionally cause DIAdem to autostart and do not know how this happened. (I must have done it since no one else messes with my laptop.)
A bit of historical info. I originally used a demo disk of ver 10.0 and then used the activation code after purchasing. I started having trouble with auto start and decided to upgrade to version 10.2 hoping ver 10.0 would be deleted and all troubles would be gone. No such luck. I now have both versions and need to remove ver 10.0. However, the control panel and 'add or remove programs' only finds one Nat Inst program (and it doesn't identify version).
Manually starting ver 10.0, generates an error message: "cannot open data store "MydataFinder"
Manually starting ver 10.2 generates an error message: ""data finder cannot start due to an internal error (100) invalid config etc."
In spite of error messages, the programs seem to generally work fine. I am in the process of using the program recommended by Matthias to eliminate startup issues. I am also considering uninstalling and re-installing but am uncertain of which version will be uninstalled since only one program is identified.
After I send this, I'm going to do a restart and see if problem with multiple restarts has been eliminated.
Thanks for all your help.
David F
I have been using the tool Matthias recommended and it is indeed a very useful program. It looks like I can stop it from doing the autostart. However, I did not intentionally cause DIAdem to autostart and do not know how this happened. (I must have done it since no one else messes with my laptop.)
A bit of historical info. I originally used a demo disk of ver 10.0 and then used the activation code after purchasing. I started having trouble with auto start and decided to upgrade to version 10.2 hoping ver 10.0 would be deleted and all troubles would be gone. No such luck. I now have both versions and need to remove ver 10.0. However, the control panel and 'add or remove programs' only finds one Nat Inst program (and it doesn't identify version).
Manually starting ver 10.0, generates an error message: "cannot open data store "MydataFinder"
Manually starting ver 10.2 generates an error message: ""data finder cannot start due to an internal error (100) invalid config etc."
In spite of error messages, the programs seem to generally work fine. I am in the process of using the program recommended by Matthias to eliminate startup issues. I am also considering uninstalling and re-installing but am uncertain of which version will be uninstalled since only one program is identified.
After I send this, I'm going to do a restart and see if problem with multiple restarts has been eliminated.
Thanks for all your help.
David F
DavidF
Mar 28, 2008, 8:40:11 AM3/28/08
to
Brad / Matthias,
Just wanted to say thanks for your help. In the midst of everything else going on as well as getting help from both of you, Russ Greenwood happened to be in the building and stopped by. We uninstalled version 10.0 and now everything seems to work just fine. He also helped me with some DIAdem script 'opportunities' and now all is well. Brad - he spoke very highly of you since he used to sit nearby and observe your helpfullness with DIAdem issues. Matthias - the program from Sysinternals is very useful. It will come in handy in the future.
Thanks again to both of you.
David F
Just wanted to say thanks for your help. In the midst of everything else going on as well as getting help from both of you, Russ Greenwood happened to be in the building and stopped by. We uninstalled version 10.0 and now everything seems to work just fine. He also helped me with some DIAdem script 'opportunities' and now all is well. Brad - he spoke very highly of you since he used to sit nearby and observe your helpfullness with DIAdem issues. Matthias - the program from Sysinternals is very useful. It will come in handy in the future.
Thanks again to both of you.
David F
jbrandim
Aug 5, 2008, 10:10:11 AM8/5/08
to
We've had the same issue crop up on a PC running 10.0.
On login, 5 or more copies of Diadem launch. This particular machine had 9.1 and 10.0 both installed. Normally, they get along fine.
I'll try removing 10.0 and installing 10.2 to see what happens.
On login, 5 or more copies of Diadem launch. This particular machine had 9.1 and 10.0 both installed. Normally, they get along fine.
I'll try removing 10.0 and installing 10.2 to see what happens.
Dr. Doiron
Aug 6, 2008, 3:10:13 PM8/6/08
to
Hello Jbrandim,
Did you try using the program Matthias recommended earlier in this thread?
Let me know how the uninstall/10.2 install goes.
Did you try using the program Matthias recommended earlier in this thread?
Let me know how the uninstall/10.2 install goes.
jbrandim
Aug 11, 2008, 12:40:11 PM8/11/08
to
Yes, we tried using the sysinternals "Autoruns" program. We didn't see any references to Diadem in the Autoruns output.
Yes, we rebooted during the install.
I have uninstalled Diadem 10.0, and installed 10.2. The problem presists.
Yes, we rebooted during the install.
I have uninstalled Diadem 10.0, and installed 10.2. The problem presists.
Brad Turpin
Aug 12, 2008, 5:10:11 PM8/12/08
to
Hi Jeff,
I ran your scenario by R&D, and they wondered if perhaps there were multiple "Run-Once" registry entries under the DIAdem registry key group. This would result from multiple incomplete installation attempts.
I ran your scenario by R&D, and they wondered if perhaps there were multiple "Run-Once" registry entries under the DIAdem registry key group. This would result from multiple incomplete installation attempts.
0 new messages