On 6/30/06, William Knop
<william.knop(a)gmail.com> wrote:
Parsing a windows inf hardly belongs anywhere but
wine.
Actually, Troy makes that point rather well in an earlier mail:
> This is not true. The existing action-on-CD-insertion programs
> provided by the
> desktop environment try to detect the contents of the CD to see
> what they
> should do, so they will be looking for the autorun.inf file.
> Additionally the
> autorun.inf file format is designed to include specifications of
> different
> commands for multiple environments, so if autorun.inf files are to be
> respected at all it makes sense that they should also be able to
> start a
> native Linux executable or shell script (discovered from an
> [autorun.linux.i386] section, for example).
>
> There is nothing in this that requires or enhances the Win32 API
> facilities
> that Wine seeks to provide. Only once the native Windows
> executable has been
> identified as the only (or best) target for autorun would Wine become
> involved, when the program in the desktop environment invoked Wine
> to run the
> executable.
Sorry, I missed this one (mailer digest mode). Hmm... You're saying
the autorun.inf format is os-independent? If so, I was unaware, and I
agree that the functionality belongs elsewhere.
Will