This is an archive of CompuServe forum messages from 1985 to 1995, as saved in transcripts by John Foust.
Search Results (6 messages)
Don, You're exactly right, that is exactly what I need to do. Here's how I got around it without opening up an ASCII file (using the API is much easier): I need: device= device= So I compromised and did: device=, Basically I did a GetPrivateProfileString(..); for the first device keyname.…
I agree that a binary .INI would be somewhat unwieldly, however, I like the ability to make an API call to change, add (if I only could!!!), or delete an item. Beats opening, searching, reading and writing an ASCII file… MS is definately gonna have to come up with a…
Don, Thanks for the details, I'll check it out. Tom Sollas [BDI]
>> I won't tell . Thanks! My only concern is rumors I've heard about changing the SYSTEM.INI to a binary format. Would make and ASCII modification useless at that point… Tom There are 2 Replies.
#Mod .INI's w/WriteProf..
Message #3031
Thanks, Don and Dennis, Checked out the Windows Programming Reference, and discovered the functions there. Something interesting, I've noticed though, is the inability to add a "like" keyname. For instance, I need to add another "device= " line in the [386enh] section of a SYSTEM.INI. However, according to the reference,…
#Mod .INI's w/WriteProf..
Message #2499
I'd like to modify SYSTEM.INI strings with VB, and I understand that I can make API calls to do this, however, I haven't been able to find any documentation on exactly how to do this. What I'm looking to do is to modify the keyboard= and mouse= line, and also…