The downloadable trial version of the VB application "Church Windows" installs fine... IF you first create a registry key to make it think IE6 is installed install the VB6 runtime install MFC40.DLL install MFC42.dll The latter three problems really aren't Wine's fault; the app leaves them out because most windows systems have them these days (really?). But the IE registry key is something Wine should maybe set by default. (See http://bugs.winehq.org/show_bug.cgi?id=3453) I even wrote a script to automate the download and install of all the prerequisites and the app itself; it's at http://kegel.com/wine/cw.sh.txt
Sadly, the app doesn't work too well once installed, but that's another story ( http://bugs.winehq.org/show_bug.cgi?id=3624 )
On Thu, 20 Oct 2005 07:37:19 +0200, Dan Kegel daniel.r.kegel@gmail.com wrote:
The latter three problems really aren't Wine's fault; the app leaves them out because most windows systems have them these days (really?).
That might just be why it was checking for the presence of IE6. A pretty clumbsy way of ensuring certain base files are there.
But the IE registry key is something Wine should maybe set by default.
Nonsense, then every prog would be misled as to what is present on the system.
It would be better is programs checked for what they really need rather than forcing users to install IE crap they dont want for a couple of dlls but that is pretty typical of a lot of what is produced under windows, and it sounds like this is not very good software either.
Hi,
On Thu, Oct 20, 2005 at 08:33:47AM +0200, wino@piments.com wrote:
On Thu, 20 Oct 2005 07:37:19 +0200, Dan Kegel daniel.r.kegel@gmail.com wrote:
But the IE registry key is something Wine should maybe set by default.
Nonsense, then every prog would be misled as to what is present on the system.
At first I thought that Wine should have set it by default (just as mentioned in a recent wine-devel mail), but you're right, I'd say we should only set it once Wine is able to cover a significant amount of IE functionality (i.e. we do have a usefully working browser). Which might just as well be never... The risk of programs failing due to discovering our IE version key and then unsuccessfully and *silently* trying to use our horribly incomplete IE functionality is a lot worse than not having the IE key and thus programs usually telling the user that IE is not available and that he should install it.
Andreas Mohr
On Thu, 2005-10-20 at 08:52 +0200, Andreas Mohr wrote:
On Thu, Oct 20, 2005 at 08:33:47AM +0200, wino@piments.com wrote:
On Thu, 20 Oct 2005 07:37:19 +0200, Dan Kegel
wrote:
But the IE registry key is something Wine should maybe set by default.
Nonsense, then every prog would be misled as to what is present on
the
system.
At first I thought that Wine should have set it by default (just as
mentioned
in a recent wine-devel mail), but you're right, I'd say we should only
set it
once Wine is able to cover a significant amount of IE functionality
(i.e.
we do have a usefully working browser). Which might just as well be
never...
The risk of programs failing due to discovering our IE version key and
then
unsuccessfully and *silently* trying to use our horribly incomplete IE functionality is a lot worse than not having the IE key and thus
programs
usually telling the user that IE is not available and that he should
install
it.
What about a checkbox in winecfg? "Fool programs to think IE6 is installed" or something. Possibly with a dropdown box for versions.
winecfg should of course then be able to check that there is no IE installed. Or maybe a version override would be beneficial anyways..?
In any case. A program I have here will not install without IE6, and works perfectly well (except auto update) when just setting the registry setting. Saves me a lot of grief.
-HK
On Thu, 20 Oct 2005 12:09:57 +0200, Hans Kristian Rosbach hk@isphuset.no wrote:
In any case. A program I have here will not install without IE6, and works perfectly well (except auto update) when just setting the registry setting. Saves me a lot of grief. -HK
That's fine , you set it and you know why and so you dont need to debug why the update is broken.
I have a prog that does need IE6 and frigging it wont work, I've spent a lot of time trying.
Le jeudi 20 octobre 2005 à 13:05 +0200, wino@piments.com a écrit :
On Thu, 20 Oct 2005 12:09:57 +0200, Hans Kristian Rosbach hk@isphuset.no wrote:
In any case. A program I have here will not install without IE6, and works perfectly well (except auto update) when just setting the registry setting. Saves me a lot of grief. -HK
That's fine , you set it and you know why and so you dont need to debug why the update is broken.
I have a prog that does need IE6 and frigging it wont work, I've spent a lot of time trying.
Do you have an example where setting the key made it worst than before ?
On 10/20/05, Hans Kristian Rosbach hk@isphuset.no wrote:
What about a checkbox in winecfg? "Fool programs to think IE6 is installed" or something. Possibly with a dropdown box for versions.
Yeah! That would fit real nice right below the one that lets you pick the Windows version. I've entered your idea in as an enhancement request in Bugzilla, http://bugs.winehq.org/show_bug.cgi?id=3627 - Dan
-
Andreas Mohr -
Dan Kegel -
Hans Kristian Rosbach -
Jonathan Ernst -
wino＠piments.com