Am Mo, Jan 17, 2005 at 08:28:09 +0100 schrieb Sven Paschukat:
> The command
> wineserver -w
> waits until the wineserver ends. Maybe you can do a
> WINESERVERCOUNT=`ps -A|grep -c -h wineserver`
> if test $WINESERVERCOUNT -ge 1;then
> echo Please make sure that there are no wine
> echo apps running.
> fi
> before the wineserver command.
I already do that. Before every action WineTools waits for remaining
wineservers to exit (and tells you that with an info box). But anyway I
had myself frequent hangs if I just go very fast through Base setup... I
no there is no reason for that if Wine is not active any more, but
that's how it is.
> >Do you use wine-20041019? This version is best tested with WineTools.
> >2005-versions are not tested yet.
>
> I've tested wine 20050111 with the in our windows app integrated ie.
> There was a dead lock at the end of the installation after the reboot.
So did you use WineTools to install the IE6? It does not reboot with the
settings in the registry made by the installer. Instead it takes it's
own registry and reboots after entering this one.
> If you have same problems, try a native rpcrt4.dll and a win98 version
> for the pstores.exe.
Could you wineboot with that with the IE6's modifications to the
registry? I will make some tests with that.
> And furthermore - if it's useful for your winetools - the command
> wine ie6setup.exe /C:"ie6wzd.exe /M:0 /S:""#e"
> let the ie setup installing just minimal components.
But what for? The sense of IE6 installing is to get programs to work
that rely on it and to get many native DLLs throught this "windows
update". So the installation should be as automatic and complete as
possible.
>
> Sven
--
"Never touch a running system! Never run a touching system?
Never run a touchy system!!!"
_______________________________________________
wine-users mailing list
wine-users@xxxxxxxxxx
http://www.winehq.org/mailman/listinfo/wine-users
