11-28-2006 04:03 AM
11-28-2006 08:27 AM
Hi Jeff,
I have heard of a very similar problem reported by a different customer using DIAdem 10.0. In that case DIAdem terminated abruptly while it was using its internal virtual memory management (HDF files) to exceed the 2 GB of addressable memory that a 32 OS is willing to give it. This resulted in those files being left orphaned the next time DIAdem was started. DIAdem 10.1 has been edited to check for these files at startup and delete them. My guess is that DIAdem 10.1 would automatically do what you are now manually doing with your start script. Until you upgrade to 10.1, though, it sounds like you have the correct workaround in place.
Regards,
Brad Turpin
DIAdem Product Support Engineer
National Instruments