Hallo,
for moving and deleting otherwise busy file, windows enters these
files to move in wininit.ini. At the next start of windows this file
is processed once early in the windows start up sequence. This is done
by a MZ-executable wininit.exe.
How should Wine handle that file? It is quite easy to do that task
with Window Api Calls. But then this can be done only quite late in the
Wine startup sequence. For example it could be the last task in
loader/main.c: MAIN_MainInit
This code would then however be executed at each start of a process and
not with every server start. Any idea how do do that? Perhaps some
call to the server returning true only once? Or should the server do it?
The other possibility would be to do the task of wininit.exe not with
Win Api calls but with libc calls. This would require a lot of code
duplication to read and scan the ini-file and to move or delete the
files given in dos notation.
Do we need the wininit.exe functionality as a standalong programm too?
Bye
Uwe Bonnes [EMAIL PROTECTED]
Free Software: If you contribute nothing, expect nothing
--
