http://bugs.winehq.org/show_bug.cgi?id=9313
Summary: InstallShield Wizard exits because requires newer system Product: Wine Version: 0.9.24. Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-binary AssignedTo: wine-bugs@winehq.org ReportedBy: wine@skewray.com
Created an attachment (id=7581) --> (http://bugs.winehq.org/attachment.cgi?id=7581) Output from wine
I am trying to install a program called FRED, an optical engineering program from Photon Engineering, www.photonengr.com. Aquiring the .exe demo install requires signing up, so I will send the .exe to anyone who asks me.
The InstallShield Wizard exits after the message:
This application requires a newer version of Windows. Please upgrade your operating system.
I used winecfg to set the OS version to everything from 95 up to XP. Made no difference.
http://bugs.winehq.org/show_bug.cgi?id=9313
Skewray wine@skewray.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #1 from Skewray wine@skewray.com 2007-08-13 22:44:18 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=9313
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID
--- Comment #2 from Vitaliy Margolen vitaliy@kievinfo.com 2007-08-13 22:45:40 --- How about using latest Wine version?
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #3 from Skewray wine@skewray.com 2007-08-14 00:08:20 --- Because the version I have is the most recent one that comes with my distribution. Are all the responses to bug reports this rude?
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #4 from L. Rahyen mail@science.su 2007-08-14 00:59:58 --- Why do you think Vitaliy's answer is rude? He is right. No one cannot help you if you are using ancient WINE version! Even if bug you are talking about still exists and someone will made a fix you will never be able to use that fix anyway if you don't want to upgrade WINE so why to bother in a first place? If you are interested in any kind of fixes for any WINE bugs then first thing you should do is to upgrade to newest version - you find THOUSANDS of fixes after upgrade because your version is almost 1 year old! Only then if problem still persist you can and should report bug.
In other words you must upgrade at least to 0.9.43 or to current git (this is even better). If up-to-date package for your distro doesn't exist you always can compile WINE yourself. Even if you know nothing about programming this is very simple. You can download source code here: http://prdownloads.sourceforge.net/wine/wine-0.9.43.tar.bz2
Test it with current WINE and reopen this bug if appropriate. But there is very high chances that it is already fixed long time ago.
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #5 from Skewray wine@skewray.com 2007-08-15 12:25:16 --- Wine has a bug system that allows users to add bugs for older versions. What is not rude about allowing people to enter bug reports and them catigating them for doing so? If Wine wishes to have a civilized bug reporting system, then new bugs should only be allowed to be entered for versions of Wine which are considered current.
http://bugs.winehq.org/show_bug.cgi?id=9313
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Vitaliy Margolen vitaliy@kievinfo.com 2007-08-15 12:50:07 --- Closing invalid. User refuses to upgrade to the recent Wine version.
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #7 from Skewray wine@skewray.com 2007-08-16 10:05:38 --- I installed 0.9.43. The bug is still there.
http://bugs.winehq.org/show_bug.cgi?id=9313
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |thestig@google.com
--- Comment #8 from Lei Zhang thestig@google.com 2007-08-16 10:10:39 --- did you start with a clean .wine directory after upgrading wine to 0.9.43?
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #9 from Skewray wine@skewray.com 2007-08-16 10:24:37 --- I did. I removed .wine completely, and ran winecfg. No change.
http://bugs.winehq.org/show_bug.cgi?id=9313
Louis Lenders xerox_xerox2000@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox_xerox2000@yahoo.co.uk
--- Comment #10 from Louis Lenders xerox_xerox2000@yahoo.co.uk 2007-08-16 10:29:48 --- Could you run the application like:
WINEDEBUG=+tid,+seh,+relay wine program_name.exe &> /tmp/relay.log && grep -A 20 -B 300 "requires" /tmp/relay.log > /tmp/relay.txt
and attach compressed (bzip2) /tmp/relay.txt file
http://bugs.winehq.org/show_bug.cgi?id=9313
Louis Lenders xerox_xerox2000@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|INVALID |
--- Comment #11 from Louis Lenders xerox_xerox2000@yahoo.co.uk 2007-08-16 10:31:20 --- (Reopened. User upgraded to wine-0.9.43)
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #12 from Louis Lenders xerox_xerox2000@yahoo.co.uk 2007-08-16 10:39:24 ---
WINEDEBUG=+tid,+seh,+relay wine program_name.exe &> /tmp/relay.log && grep -A 20 -B 300 "requires" /tmp/relay.log > /tmp/relay.txt
Sorry, think need more lines then 300. Just run by WINEDEBUG=+tid,+seh,+relay wine program_name.exe &>/tmp/relay.log and attach that whole compressed file here
http://bugs.winehq.org/show_bug.cgi?id=9313
Jesse Allen the3dfxdude@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |http://www.photonengr.com/so | |ftware.html Component|wine-binary |wine-misc
--- Comment #13 from Jesse Allen the3dfxdude@gmail.com 2007-08-16 10:53:21 --- The sys reqs on the programs page says, "Windows XP with Media". Do they mean Media Center?
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #14 from Skewray wine@skewray.com 2007-08-16 11:01:29 --- I don't understand what I do with this bit of command line code. Obviously I don't cut-and-paste into csh. I've been trying to run this installer by using "wine prog.exe".
I am leaving town in half an hour. I am not get back to this until next week.
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #15 from Skewray wine@skewray.com 2007-08-16 11:14:13 --- I figured it out -- use bash. The file is huge. I put the original executable at http://www.skewray.com/FRED_6.40.0_demo_setup.exe and I am transfering the relay.log file to http://www.skewray.com/relay.log right now, but it won't finish before I leave.
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #16 from Louis Lenders xerox_xerox2000@yahoo.co.uk 2007-08-16 11:46:19 --- The installer works just fine for me. Mystery.... I'll have a look at the relay.log too
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #17 from Jesse Allen the3dfxdude@gmail.com 2007-08-16 11:49:22 --- (In reply to comment #16)
The installer works just fine for me. Mystery.... I'll have a look at the relay.log too
Default settings? Then it probably isn't the windows version per se. It's probably querying something hardware specific?
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #18 from Austin English austinenglish@gmail.com 2007-08-16 13:33:49 --- Works fine for me in wine 0.9.43, ubuntu feisty. Didn't touch winecfg, so all settings were defaults. Hardware wise, this was on a Virtualbox VM. I'll try to run tonight on some other hardware, to see if that makes a difference.
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #19 from Austin English austinenglish@gmail.com 2007-08-18 12:59:50 --- Same result in wine 0.9.43/kubuntu gusty, nvidia 5200, amd 64 3500+. Can anyone other than reporter reproduce this bug?
Skewray, can you do 'lspci -v' and attach?
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #20 from Skewray wine@skewray.com 2007-08-21 00:24:56 --- I compressed relay.log and put it on the web at http://www.skewray.com/relay.log.gz .
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #21 from Skewray wine@skewray.com 2007-08-21 19:44:42 --- Created an attachment (id=7728) --> (http://bugs.winehq.org/attachment.cgi?id=7728) results of lspci -v
http://bugs.winehq.org/show_bug.cgi?id=9313
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|thestig@google.com |
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #22 from Austin English austinenglish@gmail.com 2007-08-22 15:13:22 --- Created an attachment (id=7737) --> (http://bugs.winehq.org/attachment.cgi?id=7737) lspci -v
Another successful install. Attaching lspci -v of this machine for reference.
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #23 from Skewray wine@skewray.com 2007-08-22 18:40:54 --- I just tried this on a completely different machine, running Ubuntu rather than SuSE. Exactly the same thing happened.
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #24 from Skewray wine@skewray.com 2007-08-24 00:15:27 --- I ran the FRED installer on another computer (Ubuntu 6.10, completely different hardware) and put the the relay.log file under http://www.skewray.com/relay2.log.gz . I get the same error. I assume, since no one else sees this error, that I am cursed.
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #25 from Skewray wine@skewray.com 2007-09-02 16:18:21 --- I just tried this again under wine-0.9.44. The problem persists. The only difference is that all the windows are now pop-unders rather than pop-ups.
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #26 from Vitaliy Margolen vitaliy@kievinfo.com 2007-09-02 17:19:03 --- Are you removing ~/.wine directory when you testing each new version? Also before compiling Wine have you installed all dependencies? Check with ./configure --verbose.
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #27 from Skewray wine@skewray.com 2007-09-02 18:36:00 --- I did the following:
1) installed wine from SuSE 10.2 rpm repository given on winehq.org. 2) removed ~/.wine 3) ran winecfg and changed location of C: 4) installed IE6 using wine (The FRED installer asks for that first) 5) ran wineboot (the IE6 installer says to reboot) 6) attempted to install FRED using wine
Since I am using a distribution rpm, I assume that the various dependencies are satisfied. Am I wrong?
http://bugs.winehq.org/show_bug.cgi?id=9313
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID
--- Comment #28 from Vitaliy Margolen vitaliy@kievinfo.com 2007-09-02 18:44:29 --- (In reply to comment #27)
I did the following:
- ran winecfg and changed location of C:
Why did you do this? DO NOT change default location of C: drive!
- installed IE6 using wine (The FRED installer asks for that first)
DO NOT INSTALL IE! Use 'winetricks fakeie6' : http://wiki.winehq.org/winetricks
- ran wineboot (the IE6 installer says to reboot)
- attempted to install FRED using wine
INVALID.
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #29 from Skewray wine@skewray.com 2007-09-03 09:31:10 --- So how do I use wine at all? My C: drive isn't in ~/.wine/drive_c. Am I supposed to use a softlink? If so, why does winecfg allow the C: drive to be changed? Why isn't all this documented in the wine install directions?
I did what appeared to me to be a perfectly reasonable set of steps, and I got a bizarre result. That means that something is wrong with wine that needs to be fixed. Wine installation should not be an expert system that requires common users to read every obscure bit of documentation on the web, such as some page called "winetricks".
http://bugs.winehq.org/show_bug.cgi?id=9313
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #30 from Vitaliy Margolen vitaliy@kievinfo.com 2007-09-03 10:35:42 --- It seems you don't understand that when reassigning drive C: you also _HAVE TO_ copy all of the content of the old C: drive (or better yet, move it into the new place).
Closing. confirmed invalid.
http://bugs.winehq.org/show_bug.cgi?id=9313
--- Comment #31 from Jesse Allen the3dfxdude@gmail.com 2007-09-03 21:15:50 --- (In reply to comment #29)
So how do I use wine at all? My C: drive isn't in ~/.wine/drive_c. Am I supposed to use a softlink? If so, why does winecfg allow the C: drive to be changed? Why isn't all this documented in the wine install directions?
I did what appeared to me to be a perfectly reasonable set of steps, and I got a bizarre result. That means that something is wrong with wine that needs to be fixed. Wine installation should not be an expert system that requires common users to read every obscure bit of documentation on the web, such as some page called "winetricks".
Maybe. There is a reason why windows does not allow switching the drive letter for the currently running windows install. However, wine is definitely more lenient as you actually can do it if done right. This bug as filed is invalid from a broken config.
Most people do not need to switch drive C so this is kind of an obscure thing to deal with.
-
wine-bugs＠winehq.org