Interesting. My experience is different: Early incarnations of IniReadSectionKeys did not work properly, but I have not seen problems with any ini reading commands since. There are always the issues with writing and reading in the same script because of caching and such, but I don't have a clear handle on what problems remain there. Finally, I have an unproven but strong suspicion that using Cygwin to create ini files can cause weird problems, and that this is because Cygwin leaves a file permission flag unset that Windows always sets. The symptom is that JAWS won't even see the file with some commands but will with others. This may even be at the Windows API level and not to do with JAWS at all. I've seen JAWS completely replace a .ini and a .jcf file without realizing it was there. Again though, I don't think this ever happens if Cygwin is not involved. I pretty much live in Cygwin, but most JAWS scripters probably don't. :) If you do use Cygwin, I advise `chmod +x' on all files you pass off to JAWS. On Sat, Jun 06, 2009 at 11:00:39PM +1000, Paul Magill wrote: Hi Sean, Until Jaws 6, I found they all worked perfectly, brilliantly well actually, but from version 6 I had to rewrite routines that used more than just a few INI functions in quick succession, such as in a while loop. I still use the INI functions where only a few, 2 or 3, are needed in quick succession. The problem was that they were no longer reliable, if more than a few were used immediately after each other. Sometimes 20 or 30 INI reads in quick succession would work correctly, & sometimes not. I replaced multiple INI write or INI read with JAMAL's object method of writing or reading entire text files. Not only did I regain 100% reliability, but it turned out to be faster to organise all the information I was going to write in multiple INI writes into one string, & do a single write to a text file using Jamal's text file writing method, but it was faster. * I would be most interested in how you wrote your own, if you dont mind sharing... Regards, Paul from Aust ----- Original Message ----- From: "Sean Farrow" <sean.farrow@xxxxxxxxxxxxxxxx> Hi All: I was recently using the JAWS ini functions to read and write to an ini file. I found the iniread* functions and iniFlush* functions to be problematic and ended up writing my own. I carn't remember though whether the iniread* functions cause any issues. Has anyone else had issues with these functions not working. Any advice appreciated. Sean. __________? Visit and contribute to The JAWS Script Repository http://jawsscripts.com View the list's information and change your settings at //www.freelists.org/list/jawsscripts -- Doug Lee, Senior Accessibility Programmer SSB BART Group - Accessibility-on-Demand mailto:doug.lee@xxxxxxxxxxxxxxxx http://www.ssbbartgroup.com "While they were saying among themselves it cannot be done, it was done." --Helen Keller __________ Visit and contribute to The JAWS Script Repository http://jawsscripts.com View the list's information and change your settings at //www.freelists.org/list/jawsscripts