I heard KeepTool was an app used by some government developers, so I tried installing the free trial from http://keeptool.com. Sadly, the installer complained I needed IE5 or later. The registry key trick I've been using, [Software\Microsoft\Internet Explorer] "Version"="6.0.2900.2180" didn't seem to do the trick this time.
Any suggestions on how to get past that? Thanks, Dan
-- Wine for Windows ISVs: http://kegel.com/wine/isv
On 3/10/06, Dan Kegel dank@kegel.com wrote:
I heard KeepTool was an app used by some government developers, so I tried installing the free trial from http://keeptool.com. Sadly, the installer complained I needed IE5 or later.
Filed at http://bugs.winehq.org/show_bug.cgi?id=4796 - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv
Friday, March 10, 2006, 11:53:24 PM, Dan Kegel wrote:
On 3/10/06, Dan Kegel dank@kegel.com wrote:
I heard KeepTool was an app used by some government developers, so I tried installing the free trial from http://keeptool.com. Sadly, the installer complained I needed IE5 or later.
Filed at http://bugs.winehq.org/show_bug.cgi?id=4796
- Dan
-- Wine for Windows ISVs: http://kegel.com/wine/isv
Well I guess that's the one that does need the IE installed. There are lots of programmes that relay on some functionality provided by IE. Doesn't matter if they really need it or not.
BTW is there are some particular reason that you have to cc every single bug that you file to wine-devel mailing as well? I'm sorry, but quality of those bugs are not that good really to go directly to wine-devel list. With this particular bug you could at least try to find what is that program looks at to decide if you do have IE installed or not.
Vitaliy Margolen.
On 3/10/06, Vitaliy Margolen wine-devel@kievinfo.com wrote:
BTW is there are some particular reason that you have to cc every single bug that you file to wine-devel mailing as well? I'm sorry, but quality of those bugs are not that good really to go directly to wine-devel list.
The two apps I posted about yesterday were ones that a European city needed for its transition to desktop Linux, so they seemed important enough to post about. But if others think I'm spamming the devel list, I can certainly stop.
With this particular bug you could at least try to find what is that program looks at to decide if you do have IE installed or not.
I did look at WINEDEBUG=+reg, but didn't see anything obvious. - Dan
-- Wine for Windows ISVs: http://kegel.com/wine/isv
BTW is there are some particular reason that you have to cc every single bug that you file to wine-devel mailing as well? I'm sorry, but quality of those bugs are not that good really to go directly to wine-devel list. With this particular bug you could at least try to find what is that program looks at to decide if you do have IE installed or not.
I certainly don't want wine-devel to turn into wine-users, but I think you are wrong to lump Dan's emails into that category.
Dan is a very capable developer; he may not be the most accomplished Wine hacker, but he is not without his chops. Note that many of the @ucla.edu patches that come to wine-devel are from his students.
Further, I think that Dan is triaging issues that are of fairly critical interest to Wine.
For example, IE dependence is a very hard problem for Wine; a lot of programs have that as an issue. I, for one, am grateful to Dan for running with the Windows version of Firefox, as it helps us be better ready to understand how to use Firefox to solve that problem.
Further, I happen to know that the Munich considered using Wine for their desktop migration, and they felt that Wine was 'awful'; so it is very interesting to me, personally, to explore why that might be.
Cheers,
Jeremy
Saturday, March 11, 2006, 8:27:59 AM, Jeremy White wrote:
BTW is there are some particular reason that you have to cc every single bug that you file to wine-devel mailing as well? I'm sorry, but quality of those bugs are not that good really to go directly to wine-devel list. With this particular bug you could at least try to find what is that program looks at to decide if you do have IE installed or not.
I certainly don't want wine-devel to turn into wine-users, but I think you are wrong to lump Dan's emails into that category.
Dan is a very capable developer; he may not be the most accomplished Wine hacker, but he is not without his chops. Note that many of the @ucla.edu patches that come to wine-devel are from his students.
Further, I think that Dan is triaging issues that are of fairly critical interest to Wine.
For example, IE dependence is a very hard problem for Wine; a lot of programs have that as an issue. I, for one, am grateful to Dan for running with the Windows version of Firefox, as it helps us be better ready to understand how to use Firefox to solve that problem.
Further, I happen to know that the Munich considered using Wine for their desktop migration, and they felt that Wine was 'awful'; so it is very interesting to me, personally, to explore why that might be.
Cheers,
Jeremy
Ah ok. I want to apologize then. I'm trying to get reasonable bug reports with enough information so any developer can go in and look without downloading giga-bytes of stuff to just get something like WINEDEBUG=warn+all. Also most of the bugs end up being a duplicates of already known problems.
In this particular case, I won't be surprised if all that software does is checks for one particular file somewhere in system32 directory. It's long know outstanding problem. I think if we search bugzilla we will come up with at least dozen of files that programs check for in this way.
Again, sorry for the extra noise.
Vitaliy.
On 3/11/06, Vitaliy Margolen wine-devel@kievinfo.com wrote:
Ah ok. I want to apologize then. I'm trying to get reasonable bug reports with enough information so any developer can go in and look without downloading giga-bytes of stuff to just get something like WINEDEBUG=warn+all.
Amen. I occasionally go on bug triage sprints, to help winnow out and add detail to the poor bug reports. (Heck, I even have a web page about it, http://kegel.com/wine/qa/ )
In this particular case, I won't be surprised if all that software does is checks for one particular file somewhere in system32 directory.
That's exactly right (wish I'd thought to try WINEDEBUG=+file). touch ~/.wine/drive_c/windows/system32/shdocvw.dll fixes it (thanks to Tony for the tip).
Now I just have to set up an Oracle database to test against! - Dan
It's
long know outstanding problem. I think if we search bugzilla we will come up with at least dozen of files that programs check for in this way.
Again, sorry for the extra noise.
Vitaliy.
-- Wine for Windows ISVs: http://kegel.com/wine/isv
Hi,
That's exactly right (wish I'd thought to try WINEDEBUG=+file). touch ~/.wine/drive_c/windows/system32/shdocvw.dll fixes it (thanks to Tony for the tip).
Thanks for the hint - Need for Speed Porsche Unleashed Demo needs ddraw.dll, as I found out this way ;)
I must really say I agree with you here, Jeremy. I think what Dan is doing for wine is excellent, and I for one appreciate him keeping us abreast of his efforts and the problems he encounters. The apps he's working with are really important for a lot of people, and as such they probably need our attention so we can make Wine a more viable alternative. I don't think Dan is spamming wine-devel at all; in fact I'd like to see him keep letting us know about all of these things.
Just my two cents...
James
On Sat, 2006-03-11 at 09:27 -0600, Jeremy White wrote:
BTW is there are some particular reason that you have to cc every single bug that you file to wine-devel mailing as well? I'm sorry, but quality of those bugs are not that good really to go directly to wine-devel list. With this particular bug you could at least try to find what is that program looks at to decide if you do have IE installed or not.
I certainly don't want wine-devel to turn into wine-users, but I think you are wrong to lump Dan's emails into that category.
Dan is a very capable developer; he may not be the most accomplished Wine hacker, but he is not without his chops. Note that many of the @ucla.edu patches that come to wine-devel are from his students.
Further, I think that Dan is triaging issues that are of fairly critical interest to Wine.
For example, IE dependence is a very hard problem for Wine; a lot of programs have that as an issue. I, for one, am grateful to Dan for running with the Windows version of Firefox, as it helps us be better ready to understand how to use Firefox to solve that problem.
Further, I happen to know that the Munich considered using Wine for their desktop migration, and they felt that Wine was 'awful'; so it is very interesting to me, personally, to explore why that might be.
Cheers,
Jeremy
-
Dan Kegel -
James Liggett -
Jeremy White -
Stefan Dösinger -
Vitaliy Margolen