Here's what's up. Im creating a security program for 9x.

I can't lock system.ini during a windows session because DUN looks to the file when it auto connects for a dialup session. It reads the [Password Lists] section for an existing username (to verify the existing username) and then autoconnects. If I lock system.ini then windows can't read the system.ini file and then the user has to type in the dun password everytime he/she wants to connect.





so what I doing is copying system.ini and renaming it to the .dll

problem is.. when the admin creates a new user profile (through my program the system.ini file is updated correctly in the password list section but then I copy the "new" system.ini file to replace the old .dll file the new user .pwl entry is not in the new .dll file. I think windows is still holding the original system.ini in memory. So I want to directly open the .dll file and add the entry directly.

when the user then logs off or the pc is restarted my program deletes the current system.ini file and replaces it with the .dll file (which is renamed to system.ini)


This is why I have to go directly to the .dll file.

I've been running around in circles for about 3 weeks now trying to figure this out.