Database Search

match allmatch any Look in all areasLook in current areas Check all datesPrevious dayPrevious 3 daysPrevious weekPrevious fortnightPrevious monthPrevious 2 monthsPrevious 3 monthsPrevious half-yearPrevious year

TechHome

• Display Items in an INI file in an Itembox
• DMI Directory Management Interface Discussion
• In the Beginning - the Evolution of INI files
• IniDelete Wholesection
• IniReadPVt always Returns Default
• IniReadPvt Failing
• IniWrite and IniWritePvt commands
• IniWrite Hangs
• IniWritePvt add lines to Systemini
• Mapped INI Files
• McAfee Virus Scanner and INI files
• Read Parameters that contain Percents in INI Files
• System Ini - Writing multiple device lines to
• UDFs to Edit INI files
• Writing to the System INI file

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

WIN95 Desktop Refreshes with Every Iniwrite Problem

Keywords:   iniwrite iniwritepvt refresh    in the beginning

---

Question:

We have a wbt writing info to the win.ini via the iniwrite function. There are mutliple iniwrite calls. With each one, the desktop is being refreshed. Because this is a source of irritation for some, we're trying to eliminate this refresh. We've found using iniwritepvt and specifying win.ini seems to work. Is there any thing we should know before we implement this? There must be a reason for the two separate function calls... Thank you for your help.

Answer:

In the olden days (when you were a wee tot), there was ONLY the WIN.INI file. And thus the iniwrite function was made.

Then Lo, Microsoft said "The WIN.INI file is becoming too cluttered with the musings of various applications. Let there be other INI files private unto the applications for their own musings, and let them not clutter the WIN.INI"

And thus the IniWritePvt function was made, so that the other INI files may be modified.

And then Microsoft also said, "Lo, whenever anything makes an important change to the WIN.INI file, let them shout from the hilltops so that all applications may hear and inspect the changes and thus may then refresh their settings." Thus when you do a IniWrite, WinBatch, in your honor, shouts from the hilltops, and Explorer harkens and sees, and decides it would be best simply to refresh its desktop.

Then it came to pass that INI files fell into disfavor, and Microsoft looked upon them with great disdain. "They can only hold simple text strings", people grumbled. "We need complete scriptures, beholden to each of the myriad users", they prayed. "It makes no sense to have a multitude of different strategems for the inscribing of this data", the wise men said.

And thus, the elders huddled much, and one day proclaimed "Now we have a REGISTRY", and it can save much, and the applications can now record their musings for posterity in a new format".

---

Article ID:   W13335

Filename:   In the Beginning - the Evolution of INI files.txt

File Created: 2001:01:22:14:09:30

Last Updated: 2001:01:22:14:09:30