Newest winrash problems?
Paul.Vriens at xs4all.nl
Fri Feb 4 02:36:56 CST 2005
On Thu, 2005-02-03 at 16:21, Chris Morgan wrote:
> I'm not actually installing winsock2, just popping up a dialog during the installer mentioning that you need winsock2 if you are running on a win95 machine. What I *should* do is somehow get the nsis installer script to check for the winsock2 dlls and actually run the installer, but thats a bit more difficult than just displaying a dialog with text and a web link.
maybe you could have that one be de-selected on default? The number of
win95 running winrash seem to be outnumbered by the others.
> > I had some problems with Winrash bailing out on 2 of my win98 systems.
> > Apparently this was because a new winrash was available and it tried to
> > install that?
> > After uninstalling winrash 0009 and installing 0010 it works again. One
> > of the main differences is that winrash 0010 has an extra winsock2
> > install, could this be the cause?
I saw there's now even a 0011. The following problems where observed by
me while the automatic upgrade took place:
- for some reason the previous TAG was not used anymore. If you look at
http://test.winehq.org/data/200502031000/ you will see a load of
IDWASEMPTY's. (more than usual)
- On my WinNT4 box, the debug log file grew to 2GB!
Both of the above where solved by un-installing what was there and
installing the latest. I do think there's something wrong in the
automatic upgrade of winrash.
More information about the wine-devel