04-13-2007 03:46 PM
04-14-2007 12:39 PM
Ini_WriteToFile function uses a couple of functions that can generate this error. The error returned is the originalone generated by these functions except for a call to fflush whose possible errors are remapped from the original value of errno variable.
In any case, since this tool is distributed at source code level you can examine this function in detail and check for possible causes. Maybe the best way to do this is to load the instrument in the Instrument menu instead of the library menu, then execute Edit >> Attach and edit source function in the same menu and then put some conditional breakpoints trapping error < 0 condition in the disk-access functions included in Ini_WrtiteToFile function.
04-16-2007 08:58 AM
Hello Roberto,
thanks for your reply. Unfortunately this problem happens not here on my system but at a customer who uses the compiled application. I was just wondering that "Input/Output Error" was listed as "Among the more commonly encountered errors are:" in the description of the Ini_WriteToFile function
All other erros in that list have a clear understandable meaning, whereas "Input/Output error" seems a bit undefined...
Among the more commonly encountered errors are:
Out of memory! | |
Too many files are open. | |
Input/Output error. | |
File not found. | |
File access permission denied. | |
Disk is full. | |
File already open. | |
Badly formed pathname. | |
Could not generate an unused temporary file name in the same directory as the output file. | |
Could not create a temporary file in the same directory as the output file. |
So if it is a commonly encountered error for this function, there should be a defined meaning behind it as it is for all other erros in that list.
Best Regards,
Greg
04-19-2007 07:21 AM
Any statement from NI to this problem?
Thanks,
Greg
04-19-2007 10:53 AM
04-19-2007 11:11 AM
04-19-2007 12:03 PM
04-20-2007 01:23 AM