S
Steven Burn
</snip>Shortly after posting, I did a lookup on MSFT. Things are as you said, but
consider there is also a problem...
http://support.microsoft.com/?id=140570
: Applications that use Wininit.ini should check for its existence in
: the Windows directory. If Wininit.ini is present, then another
: application has written to it since the system was last restarted.
: Therefore, the application should open it and add entries to the [rename]
: section. If Wininit.ini isn't present, the application should create it
: and add to the [rename] section. Doing so ensures that entries from
: other applications won't be deleted accidentally by your application.
...see that "should" everywhere? So you'll going to have all these
programmers around who don't read the shoulds, and don't ensure about not
deleting the entries of others. If you'd chosen to use this location,
then you'd have to deal with the index.dat deletion commands getting wiped
out by someone else.
I read that quite a while ago. It's one of the main things that made me
decide "to hell with that".
</snip>I agree with you entirely, am sure the runonce key is the best solution.
Btw, I like that you make it so we can explicitly check on|off the runonce,
each time. It's a relief from the glee too many programs take, in trying to
sneak things into our auto-launch areas, without asking or telling.
I wasn't originally going to, but then I realised how much I detested
programs that did that (whether they were meant to or not) and then decided
to let the user decide.
This decision was confirmed by an e-mail I received from a friend that also
suggested I have it as an option.
--
Regards
Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk
Keeping it FREE!
Disclaimer:
I know I'm probably wrong, I just like taking part ;o)