Cesar wrote:
I see that MFC42 is missing on wine tricks.
Nope! It's installed by the vcrun6 verb: echo " vcrun6 vc6redist from VS6sp4 (mfc42, msvcp60, msvcrt)" I've been considering making it more obvious.
There's a cab available from: http://activex.microsoft.com/controls/vc/mfc42.cab
Thanks, nice to have an alternate source.
On Wed, May 7, 2008 at 12:43 PM, Dan Kegel dank@kegel.com wrote:
Cesar wrote:
I see that MFC42 is missing on wine tricks.
Nope! It's installed by the vcrun6 verb: echo " vcrun6 vc6redist from VS6sp4 (mfc42, msvcp60, msvcrt)" I've been considering making it more obvious.
There's a cab available from: http://activex.microsoft.com/controls/vc/mfc42.cab
Thanks, nice to have an alternate source.
Maybe it would be nice to have something like:
winetricks mfc42.dll
and have some sort of alias database with some dlls filenames there. It would make end users life much more easier imho.
On Wed, May 7, 2008 at 12:32 PM, Cesar Izurieta cesar@ecuarock.net wrote:
Maybe it would be nice to have something like:
winetricks mfc42.dll
and have some sort of alias database with some dlls filenames there. It would make end users life much more easier imho.
Yes, exactly. There is some question about how to present a GUI for that, the list could be quite large. So I'll probably only add aliases for a few common DLLs, at least at first.
Dan Kegel wrote:
On Wed, May 7, 2008 at 12:32 PM, Cesar Izurieta cesar@ecuarock.net wrote:
Maybe it would be nice to have something like:
winetricks mfc42.dll
and have some sort of alias database with some dlls filenames there. It would make end users life much more easier imho.
Yes, exactly. There is some question about how to present a GUI for that, the list could be quite large. So I'll probably only add aliases for a few common DLLs, at least at first.
Dan that's going way overboard. You creating another winedoors or worse winetools.
Original idea of having few dlls and registry changes in one place - was great. So no one would need to repeat those instructions over and over again. But having windows media player?! Now list of all windows dlls that some users will install just in case.
Please scale it back or split it into a separate tool.
Vitaliy.
On Wed, May 7, 2008 at 3:46 PM, Vitaliy Margolen wine-devel@kievinfo.com wrote:
Dan that's going way overboard. You creating another winedoors or worse winetools.
Original idea of having few dlls and registry changes in one place - was great. So no one would need to repeat those instructions over and over again. But having windows media player?! Now list of all windows dlls that some users will install just in case.
No, no, no. Only mfc42 and other really common ones. I promise I won't go crazy.
And it's not winedoors - it's just a shell script without any delusions of grandeur.
On 08.05.2008, at 01:23, Dan Kegel wrote:
On Wed, May 7, 2008 at 3:46 PM, Vitaliy Margolen wine-devel@kievinfo.com wrote:
Dan that's going way overboard. You creating another winedoors or worse winetools.
Original idea of having few dlls and registry changes in one place
- was
great. So no one would need to repeat those instructions over and over again. But having windows media player?! Now list of all windows dlls that some users will install just in case.
No, no, no. Only mfc42 and other really common ones. I promise I won't go crazy.
And it's not winedoors - it's just a shell script without any delusions of grandeur.
Why not having a little windows app/gui for the script, instead of having ten guis for all sorts of OS / Windowmanagers ?
Mike