http://bugs.winehq.org/show_bug.cgi?id=15078
Summary: No longer possible to install Windows Script Product: Wine Version: 1.0.0 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: goeran@uddeborg.se
In wine 0.9.52 I could install Windows Script by doing "wine scripten.exe", as I describe in the AppDB for Fractal Mapper. (The suggestion exists in other AppDB entries too, like http://appdb.winehq.org/objectManager.php?sClass=version&iId=4270&iT...)
Trying to do the same in wine 1.0 no longer works. I get an error window saying "The cluster size in this system is not supported"
The console output has one line that I don't understand, but possibly could have something to do with this:
fixme:ntdll:server_ioctl_file Unsupported ioctl 24000 (device=2 access=1 func=0 method=0)
http://bugs.winehq.org/show_bug.cgi?id=15078
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal
--- Comment #1 from Vitaliy Margolen vitaliy@kievinfo.com 2008-08-30 16:12:31 --- Please try with the newest Wine version (wine-1.1.3)
http://bugs.winehq.org/show_bug.cgi?id=15078
--- Comment #2 from Göran Uddeborg goeran@uddeborg.se 2008-08-30 16:23:17 --- It's the "stable release" 1.0 that is available prebuilt for Fedora. But I'll see if I can wet up enough environment to build my own.
http://bugs.winehq.org/show_bug.cgi?id=15078
--- Comment #3 from Göran Uddeborg goeran@uddeborg.se 2008-09-01 11:01:57 --- I've built 1.1.3, and I don't get the error in that version any more. Seems to bi fixed again.
(What is the process intended behind the "stable" and "development" versions? Will there be updates in the stable branch, say 1.0.1, as in some other projects? Or is wine development more linear, so that 1.2 will be the "stable" version where this is fixed?)
http://bugs.winehq.org/show_bug.cgi?id=15078
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #4 from Vitaliy Margolen vitaliy@kievinfo.com 2008-09-01 12:48:58 --- There is already stable branch: http://source.winehq.org/git/wine.git/?a=heads
http://bugs.winehq.org/show_bug.cgi?id=15078
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Vitaliy Margolen vitaliy@kievinfo.com 2008-09-01 12:49:11 --- Fixed in wine-1.1.3
http://bugs.winehq.org/show_bug.cgi?id=15078
--- Comment #6 from Göran Uddeborg goeran@uddeborg.se 2008-09-01 13:19:47 --- :-) Ok, there is a stable branch. How is it used? :-)
I guess the question I really wanted to ask was if a bug like this, which is reported against a stable release, will get fixed in a stable branch.
But never mind, I guess I'll find out in time. And I can use the 1.1.3 I built until then.
http://bugs.winehq.org/show_bug.cgi?id=15078
--- Comment #7 from Dmitry Timoshkov dmitry@codeweavers.com 2008-09-02 03:43:06 --- If you could identify a patch that broke the application (and perhaps the one which has fixed it later) using instructions at http://wiki.winehq.org/RegressionTesting it would make it possible to consider merging the fix into the stable branch for the next release.
http://bugs.winehq.org/show_bug.cgi?id=15078
Göran Uddeborg goeran@uddeborg.se changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|No longer possible to |Not possible to install |install Windows Script |Windows Script on NFS | |filesystem
--- Comment #8 from Göran Uddeborg goeran@uddeborg.se 2008-09-06 10:03:30 --- I seem to be good at getting noise into my attempts to test Wine problems lately. What first appeared as a difference between different versions seems to be a difference between different machines. The two machines I've been using have similar configurations, but one of them mounts home directories from the other.
And it turns out that this difference is the important one, not the version difference. If WINEPREFIX is on a local ext3 filesystem it works, if WINEPREFIX is mounted via NFS it fails. This is true for all combinations I tested. In particular, 1.1.3 also fails on NFS filesystems in the way described in comment 0.
-
wine-bugs＠winehq.org