http://bugs.winehq.org/show_bug.cgi?id=717
------- Additional Comments From Speeddymon(a)yahoo.com 2004-05-05 20:51 -------
Well it may be a lil while before I can help with debugging the real problem,
because as I said before I still dont have a computer, just using a public
access one. But if you know a little bit about BASH scripting, I can help you
write up a workaround..
I think that all that needs to be done is have wineshelllink check to see if
the link target exists. If it does then create the link as before, but if not,
then create the link using the dummy icon (which would be installed to
C:\Windows\System (or C:\WinNT\System32) when wine is installed)
Of course some nice but not necessary additions to this would be to have an
initscript check (upon bootup) to see if the files needed to create a proper
link exist, and if so then call wineshelllink to do so. Another thing it could
do is to remove links when someone hasnt properly uninstalled a program and the
targets _no longer_ exist (but did before). And of course if the link is
already proper then do nothing... This is of course not necessary as I said
before but would be something nice..
If anyone has any other ideas post em here and as soon as I get a computer Ill
get to writing them up..
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=717
pauling(a)starwolf.biz changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pauling(a)starwolf.biz
------- Additional Comments From pauling(a)starwolf.biz 2004-05-05 19:47 -------
See Comment 20;
I'm running wine 20040408, and this is still a problem, complete error message
reads:
Error: Unable to create a link to C:\Program Files\Starcraft\Readme.hl as
C:\WINDOWS\Start Menu\Programs\Starcraft\Starcraft Readme.lnk.
Installation Aborted
Error 0: Success
at: LinkUndo.cpp Line 165
I've tried touching the file that it's having trouble creating, to no effect,
and this has happened now reliably for 20 install cycles. Other .lnk files it
appears to be able to create without problems.
Any assistance in suggesting WINEDEBUG environment variables that might help
isolate this would be appreciated
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=2209
Summary: Cannot print from Red Hat Enterprise Linux 3
Product: Wine
Version: CVS
Platform: PC
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: medbi01(a)accpac.com
When printing from ACCPAC Advantage Series for Linux (and I expect from a test
program too) I get the error:
lpr: unable to print file: server-error-service-unavailable
This occurs just after CloseJob16 closes its fd to the printing fork.
If I modify wine to print via a temp file I get the same error, even though I
can print the temp file manually from the command line.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=2194
irshadkunda(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P4 |P1
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=2137
------- Additional Comments From vladimir(a)pobox.com 2004-04-05 18:31 -------
This is caused by exec shield being on by default. echo 0 >
/proc/sys/kernel/exec-shield and the problem goes away.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=2048
------- Additional Comments From zbyszek(a)pangea.com.pl 2004-04-05 08:17 -------
I can confirm this bug, also. I have downloaded and build version (20040408).
regards, zgibek
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1374
------- Additional Comments From lionel.ulmer(a)free.fr 2004-04-05 06:17 -------
This seems to be the 'famous' problem that is also present in the NWN toolset.
There was a mail of mine to the Wine mailing list explaining exactly the reasons
for this problem and a (hacky) fix.
I could not tell you exactly when I sent it, but it should be in the archives.
If you can't find it, I will see if I can find it in my archives.
Basically, it comes from the fact that the DC created for the OpenGL window does
not have the CLIPSIBLINGS flag set, which means that the X window associated to
this DC is the parent window with some hacks (ie X geometry translation +
passthrough). This geometry translation and passthrough is not supported by
OpenGL => the GL drawings are done in a window which is obscured by other
windows => one does not see anything.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1374
------- Additional Comments From david_costanzo(a)yahoo.com 2004-04-05 03:03 -------
I think the problem is with WGL and/or x11drv.
After hacking on wgl.c, I was able to get the camera view to draw onto the
desktop's root window. The good news is that the image looks fine, which makes
me think the gl* calls are not the problem, it's that the gl* calls are writing
to a window that is not being drawn to the screen.
I also tried calling XDrawLine on the same window on which the gl* calls are
made (you can get the Drawable in wglMakeCurrent), but I never saw my line. The
window seems to ignore all drawing commands.
Any ideas on how to trouble-shoot why drawing to a "Drawable" has no apparent
effect? Any ideas on how to determine if the Drawable in wglMakeCurrent is
really the camera window in Hammer (as opposed to some hidden window)?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=2208
Summary: Problems loading wine
Product: Wine
Version: 20040408
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-binary
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: slimreb(a)yahoo.com
I am getting an error message whenever I try to load wine. The error is:
fixme:reg:_nt_dump_lf unknown Win XP node id 0x686c: do we need to add support
for it ?
I have not been able to find out anything for this error. Please let me know
what I need to do to get this to work. Thank you.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.