I think this is what Andrew meant all along and this is very usefull information: > At run time, when the missiing code is invoked, it has the error > "Unable to create object PostGreSQL" [...] > GNUGK is clearly able to detect the error, and report it. The level > needs to be promoted to fatal. Now we can check if the situation is always fatal (not sure if it is) and the gatekeeper should halt, or if the error message just needs to be upgrade a few levels. Error reports that sound like "it doesn't work, so GnuGk should obviously detect and fixit" aren't quite as helpful. That's what prompted my half-funny remark. Regards, Jan -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.willamowius.de/ ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
