10-02-2007 02:51 PM
10-03-2007 10:44 AM
10-04-2007 02:28 PM
07-10-2013 06:24 PM
I have experienced the Runtime 216 Error (at 000022EA) when attempting to use DIAdem 6.02 under Windows 2000 SP4 as well as XP. This is not an issue of the application's lack of certification for use with XP. The response from Otmar D. Foehner, suggesting an upgrade as a way of dealing with a problem, reveals a lack of professionalism and substance. Even if money were not an issue, this response fails to acknowledge the potential necessity to use older software in specific circumstances. In addition, Windows XP was well underway some time before1998: it was not, as the author claims, beyond the "dreams" of Microsoft's programmers. Microsoft released the first SDK (a set of tools to provide programmers what they need to develop new software for an OS) for Windows XP in January, 2000: DIAdem 6.02 was released in July of that year. Perhaps a Business Manager should take some care when addressing technical issues to ensure such content is accurate and conveys an appropriate attitude, as this response communicates a sentiment akin to "we have no interest in helping you solve problems or address issues, just submit us a PO for $8,000 and leave us alone..."
I have a set of autosequences -- written in 1998 -- that analyze and report rarely acquired data types for an application report that is both computationally complex and uses an involved set of logic controls (>12,000 lines of code). I was promised that these autosequences would operate "just fine" when upgrading from Version 6.02 to 7 (when NI took over). Despite the promises, each of these autosequences crashed -- despite considerable work to "bring them up to date." We now use version 8 and 11 (depending on the lab) for 98% of our work. However, I'm still struggling with this Runtime error when I need to use Version 6 for my specialized autosequences.
Regards,
JMM
07-11-2013 02:46 PM
Hi JMM,
We really ought to be able to get your DIAdem 6 code to work with DIAdem 8.1 without too much trouble. I have run DIAdem 8.1 on Windows 7 64bit with no trouble, so that would be > 10 years of forward compatibility. I haven't tested yet with Windows 8. DIAdem 8.1 is in general a superset of DIAdem 6.
Obviously the error message DIAdem is throwing in these cases is not helpful, so there's very little for us to go on to start tracking down the problem. Have you tried running the DIAdem 6 code on DIAdem 8.1? I'm guessing you have, so what sort of errors did you get? Is there anything from the DIAdem 6 code or any data set you can send to us to try to reproduce the error you're having? DIAdem 9.0 was a BIG departure from DIAdem 8.1, so that will be a bigger compatibility bump to cross than from DIAdem 6 to DIAdem 7 or DIAdem 7 to DIAdem 8. If you feel uncomfortable posting to this discussion forum, you can email me directly at brad.turpin@ni.com
Regards,
Brad Turpin
DIAdem Product Support Engineer
National Instruments