IDAPI Directory Busy 1

[CFOLKES]

Once in awhile, one of our Pal Applications will BURP for some unknown reason and freeze up Paradox on one of our networked machines. Ctrl-Alt-Delete is the only way to get out. BUT we can't reload paradox without doing a warm boot on the machine and closing all other background connections.

If you try to reload Pdox after you CAD out, you get the "Idapi Directory Busy" error message. Is there any way to Reset Idapi without doing a warm boot of the machine? This happens on both Win Pdox 5 and 7 (Our highest version) [sig][/sig]

 

[Guest_imported]

I think I read somewhere that you can overcome this by deleting all the p*.lck, p*.net files and then fire up Paradox on a different Private directory. I'm not sure what happens in the network situation since the netDir file will still have records assigned against that user. My be worth a try, if the app can survive the directory change. (Have 2 shortcuts on the desktop). Handling of this type situation is much better in version 8.

 

[CFOLKES]

Ogriofa
Thanks for the info. We already knew about those fixes. They are used for a different circumstance. When one user does not close out an application using our programmed buttons, they leave the application open which causes other users to have a problem.

The Idapi error is quite different. It is usually caused when a long iterative function is in process, and the user tries to do something in background - (NOT necessarily on a NET WORK machine - It also happens on a Stand Alone)

I heard that there was a downloadable patch from Borland, but they no longer support Paradox, and COREL is absolutely worthless! They just want us to upgrade--- the city I work for will take forever to upgrade a system which is still working (Most of the time)

Thanks Again! [sig][/sig]

 

[footpad]

ChazJr,

The error message you're quoting is IDAPI/BDE's friendly little way of letting you know that Paradox was existed abnormally. I presume you're using Paradox 7.16 as your highest version?

The problem is being cause by limitations in 16-bit Windows. When an application crashed, any DLL's called by that application were left stranded in memory. There was no way to attach to those copies or verify that they were valid. Instead of letting you restart Paradox with a potentially blown copy of BDE in memory, Borland embedded the error message you mentioned as a reminder that you needed to restart Windows.

Now, there is a utility called SavePdox that will unload all 16-bit IDAPI/BDE DLL's from memory; if used carefully, it can help you deal with the crashes that occur. If not used carefully, it can cause major problems.

I will upload a copy of the utility to my web site in the morning; it'll be available at

http://www.techtricks.com/download/paradox/savepdox.zip.

Please give me until ~9:00 a.m. Left Coast time to get it up.

Hope this helps...

-- Lance

 

[bayBell]

Yes there is a file savepdox.exe. if you want it let me know and I will eMail it to you.
baythebell@aol.com