Bootprocedure again

lawson_whitney at lawson_whitney at
Sat Feb 23 22:49:43 CST 2002

On Sat, 23 Feb 2002, David Elliott wrote:

> application.  Save yourself a lot of trouble trying to figure out where to
> place a hook in wine and simply write it into a completely seperate
> program.  You can then have wine actually run that program with a
> CreateProcess call or similar at whatever point.  The code to do this
> should NOT be in the wine emulators source code itself, nor do I believe
> it should be linked in with it.

Well, if it is a Winelib program, it would be linked with it, sort of,
and loaded by it, but I think that is not what you mean here, is it?
> Windows itself (win9x/me at least) actually has this code in WININIT.EXE
> which is loaded early on in the boot process.  It is not necessary or even
> desirable to have the code in the emulator itself.  It is much more
> desirable to have it be a completely seperate program.  Leave it to the

is a good neighborhood.

> distributors of Wine to implement the actual policy and only provide the
> mechanism.  This is what Alexandre has been saying, and I am saying the
> same thing.  Policy decisions do not belong in Wine, even as configuration
> options when it can be helped.  If you feel you absolutely MUST have this
> run every time a wine program is started or every time a wine program
> finishes (maybe this would be better) then write a shellscript like so:
> #!/bin/sh
> wine "$@"
> wine_movefiles
> This is so simple, why would you even waste your time trying to hack it
> into the boot code for wine?
> -Dave
Right.  I like that.


Juno offers FREE or PREMIUM Internet access for less!
Join Juno today!  For your FREE software, visit:

More information about the wine-devel mailing list