Re: wined3d: Implement vertex fog with pixel shaders
Did you check if the clamping is required?
Benchmark quandary
Hello All, I have some benchmarks posted here: http://wiki.winehq.org/BenchMark-0.9.5 as well as here: http://wiki.winehq.org/BenchMark-0.9.6 And I have all the Graphics test in PCMark 04 running, but the app is crashing between test, but if I run them one at a time they will complete.. The quandary is would posting the test results from each test while not run as a whole but separately be of use? and would this be unfair when comparing the results against XP??? -- Tom Wickline Respectable computing - Linux/FOSS
Re: Another GSoC idea
On Friday 16 March 2007 02:49, Remco wrote: > I was thinking of a combined project between Ogre (graphics engine) and > Wine. Ogre works on Windows and Linux. It has an OpenGL and DirectX > backend. Maybe a student could try to get the DirectX-backend working in > Linux with Wine. I haven't tried yet, but this should be rather straightforward. You'd need to recompile all the depenencies and Ogre from source in wine, though, that's quite a hassle. I use Ogre in another project I'm in, I build Ogre rpm packages, I know what I'm talking about there. The Win32 dep package is for MSVC++ 2005 SP1, which didn't work in Wine, I think. > This would result in a lot of patches for Wine, and the first native Linux > DirectX app of this size that I know of. Wouldn't that be cool? I don't actually see the difference between running Ogre apps and other DirectX apps. Or am I getting you wrong and you're suggesting to make the DirectX backend work as a winelib app on native Linux without Wine? Cheers, Kai -- Kai Blin, WorldForge developerhttp://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin/ -- Will code for cotton. pgpCBRhxpaPzQ.pgp Description: PGP signature
Re: Want to be a Wine mentor for Google Summer of Code 2007?
On Thursday 15 March 2007 20:09, Matt Finnicum wrote: > They had Wine listed last night when they first started posting the > projects (the list was only five projects long), but then they removed > the whole list for a while so they could finish preparing it. So I'm > assuming we'll be added from that as well. Yeah, someone on IRC told me about this (that we were on the list last night) after I posted. Oh well, the deadline is the 24th, so if Wine is on the list in three or four days, that's still fine. :) Cheers, Kai -- Kai Blin, WorldForge developerhttp://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin/ -- Will code for cotton. pgpVvzEvOAID3.pgp Description: PGP signature
Another GSoC idea
I was thinking of a combined project between Ogre (graphics engine) and Wine. Ogre works on Windows and Linux. It has an OpenGL and DirectX backend. Maybe a student could try to get the DirectX-backend working in Linux with Wine. This would result in a lot of patches for Wine, and the first native Linux DirectX app of this size that I know of. Wouldn't that be cool? Remco Need Mail bonding? Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users. http://answers.yahoo.com/dir/?link=list&sid=396546091
Re: FDI: Constify some variables
On 3/15/07, Andrew Talbot <[EMAIL PROTECTED]> wrote: James Hawkins wrote: > Are you checking with the SDK to make sure these changes are legit? > This isn't how the Windows SDK fdi.h has these defined. > I ascertained that the function-pointer parameters of FDICreate() should have the same signatures as the corresponding low-level file functions (e.g., pfnopen should point to a function that takes and returns identical parameters to _open(), pfnwrite to _write(). Its pfnopen, is of type PFNOPEN and its pfnwrite of type PFNWRITE, so I constified those types to match the signatures of _open() and _write(), respectively, and altered the functions that were affected. That's not how it works. PFNOPEN, et al., has a specific definition that is similar to, but not the same as, the corresponding low-level file IO function. If you make a change to a public header, you need to check the same header in the SDK and make sure that the change is warranted. As it stands, this is wrong. -- James Hawkins
Status of Wine & Mac OS X
Dear Wine deevlopers. I was looking thorugh the mailing list archives about the status of wine working in Intel-Macs. I'd like to start helping the wine project making some effort in Macintel computer, and i like to reach some 3D approach that works in Mac. Waiting your comments Best Regards Rafa Campos (aka methril).
Re: FDI: Constify some variables
James Hawkins wrote: > Are you checking with the SDK to make sure these changes are legit? > This isn't how the Windows SDK fdi.h has these defined. > I ascertained that the function-pointer parameters of FDICreate() should have the same signatures as the corresponding low-level file functions (e.g., pfnopen should point to a function that takes and returns identical parameters to _open(), pfnwrite to _write(). Its pfnopen, is of type PFNOPEN and its pfnwrite of type PFNWRITE, so I constified those types to match the signatures of _open() and _write(), respectively, and altered the functions that were affected. -- Andy.
Re: Need help with SymInitializeW
Kapila De Silva a écrit : Hi guys, I put some more debug in the process_find_by_handle function of dbghelp.c, and what Im seeing is the second time we call SymInitializeW, we appear to create a new process structure, so following calls to process_find_by_handle returns the new one, and not the old one. In the trace below, the first call to process_find_by_handle returns a process structure stored at 0x16c600, but the next calls locate two process structures (one at 0x16c600 and one at 0xf5ee680). Could this be an issue? Both seem to have the same process handle of 0x. Maybe when allocating a new process structure we should check if one already exists with the same handle? Again, I said I'll send a patch for the syminitialize issue being called twice (but I need to figure out the semantics for the SymCleanup, which seem to be ackward...), but that's unlikely the cause of the later crash, so you don't need to spend too much time on the dbghelp issue (if you really want to be sure, in SymInitialize return TRUE if we've found an existing process with the same handle) A+ -- Eric Pouech "The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams)
Re: FDI: Constify some variables
On 3/15/07, Andrew Talbot <[EMAIL PROTECTED]> wrote:
Changelog:
FDI: Constify some variables.
diff -urN a/dlls/cabinet/cabinet_main.c b/dlls/cabinet/cabinet_main.c
--- a/dlls/cabinet/cabinet_main.c 2007-03-15 17:31:18.0 +
+++ b/dlls/cabinet/cabinet_main.c 2007-03-15 20:16:45.0 +
@@ -86,7 +86,7 @@
HeapFree(GetProcessHeap(), 0, memory);
}
-static INT_PTR fdi_open(char *pszFile, int oflag, int pmode)
+static INT_PTR fdi_open(const char *pszFile, int oflag, int pmode)
{
HANDLE handle;
DWORD dwAccess = 0;
@@ -131,7 +131,7 @@
return 0;
}
-static UINT fdi_write(INT_PTR hf, void *pv, UINT cb)
+static UINT fdi_write(INT_PTR hf, const void *pv, UINT cb)
{
HANDLE handle = (HANDLE) hf;
DWORD dwWritten;
diff -urN a/dlls/msi/files.c b/dlls/msi/files.c
--- a/dlls/msi/files.c 2007-02-26 17:43:07.0 +
+++ b/dlls/msi/files.c 2007-03-15 20:56:44.0 +
@@ -161,7 +161,7 @@
msi_free(pv);
}
-static INT_PTR cabinet_open(char *pszFile, int oflag, int pmode)
+static INT_PTR cabinet_open(const char *pszFile, int oflag, int pmode)
{
HANDLE handle;
DWORD dwAccess = 0;
@@ -202,7 +202,7 @@
return 0;
}
-static UINT cabinet_write(INT_PTR hf, void *pv, UINT cb)
+static UINT cabinet_write(INT_PTR hf, const void *pv, UINT cb)
{
HANDLE handle = (HANDLE) hf;
DWORD dwWritten;
diff -urN a/dlls/setupapi/setupcab.c b/dlls/setupapi/setupcab.c
--- a/dlls/setupapi/setupcab.c 2006-11-10 17:26:30.0 +
+++ b/dlls/setupapi/setupcab.c 2007-03-15 20:45:39.0 +
@@ -113,7 +113,7 @@
HeapFree(GetProcessHeap(), 0, pv);
}
-static INT_PTR sc_cb_open(char *pszFile, int oflag, int pmode)
+static INT_PTR sc_cb_open(const char *pszFile, int oflag, int pmode)
{
DWORD creation = 0, sharing = 0;
int ioflag = 0;
@@ -204,7 +204,7 @@
return num_read;
}
-static UINT sc_cb_write(INT_PTR hf, void *pv, UINT cb)
+static UINT sc_cb_write(INT_PTR hf, const void *pv, UINT cb)
{
DWORD num_written;
/* BOOL rv; */
diff -urN a/include/fdi.h b/include/fdi.h
--- a/include/fdi.h 2006-05-23 13:49:04.0 +0100
+++ b/include/fdi.h 2007-03-15 19:53:38.0 +
@@ -205,14 +205,14 @@
typedef void (__cdecl *PFNFREE)(void *pv);
#define FNFREE(fn) void __cdecl fn(void *pv)
-typedef INT_PTR (__cdecl *PFNOPEN) (char *pszFile, int oflag, int pmode);
-#define FNOPEN(fn) INT_PTR __cdecl fn(char *pszFile, int oflag, int pmode)
+typedef INT_PTR (__cdecl *PFNOPEN) (const char *pszFile, int oflag, int pmode);
+#define FNOPEN(fn) INT_PTR __cdecl fn(const char *pszFile, int oflag, int
pmode)
typedef UINT (__cdecl *PFNREAD) (INT_PTR hf, void *pv, UINT cb);
#define FNREAD(fn) UINT __cdecl fn(INT_PTR hf, void *pv, UINT cb)
-typedef UINT (__cdecl *PFNWRITE)(INT_PTR hf, void *pv, UINT cb);
-#define FNWRITE(fn) UINT __cdecl fn(INT_PTR hf, void *pv, UINT cb)
+typedef UINT (__cdecl *PFNWRITE)(INT_PTR hf, const void *pv, UINT cb);
+#define FNWRITE(fn) UINT __cdecl fn(INT_PTR hf, const void *pv, UINT cb)
typedef int (__cdecl *PFNCLOSE)(INT_PTR hf);
#define FNCLOSE(fn) int __cdecl fn(INT_PTR hf)
Are you checking with the SDK to make sure these changes are legit?
This isn't how the Windows SDK fdi.h has these defined.
--
James Hawkins
Re: Makefiles: Be less verbose when performing make rules by only printing the command being executed and the source and/or target file.
Robert Shearman <[EMAIL PROTECTED]> writes: > I don't see how. It doesn't change the portability with other versions > of make, and although I'm not an expert on shell programmings, I don't > think I used an non-portable constructs there. The MAKEFLAGS hack is certainly non portable, and won't behave right on other makes. Using a shell script will also cause trouble on Windows. The extra shell evaluation will also require some extra quoting, that may be tricky to get right. It's really a lot of trouble... -- Alexandre Julliard [EMAIL PROTECTED]
Re: Makefiles: Be less verbose when performing make rules by only printing the command being executed and the source and/or target file.
Alexandre Julliard wrote: I've been thinking about this some more, and I don't think I'll put it in. It's going to cause a lot of trouble and portability headaches, for only a minor cosmetic gain. I don't see how. It doesn't change the portability with other versions of make, and although I'm not an expert on shell programmings, I don't think I used an non-portable constructs there. -- Rob Shearman
Re: Want to be a Wine mentor for Google Summer of Code 2007?
They had Wine listed last night when they first started posting the projects (the list was only five projects long), but then they removed the whole list for a while so they could finish preparing it. So I'm assuming we'll be added from that as well. --Matt On 3/15/07, James Hawkins <[EMAIL PROTECTED]> wrote: On 3/15/07, Maarten Lankhorst <[EMAIL PROTECTED]> wrote: > Kai Blin schreef: > > On Tuesday 13 March 2007 08:29, Dan Kegel wrote: > > > >> I'm looking for active Wine developers to act > >> as mentors for Google Summer of Code 2007. > >> If you're interested, please let me know quickly; > >> the list has to be finalized in the next half-day > >> or so. (Sorry for the late notice; I wasn't paying > >> attention, and the deadline snuck up on me...) > >> > > Looks like we were too late then? We're not on the list of mentoring projects > > this year, it seems. > > > > Cheers, > > Kai > Seems that way, looks like we indeed missed them, is it still possible > to participate for soc 2007 with wine, or do we have to wait till next year? > Read Dan's earlier post: > I'm fine this year, but considering how I missed the deadline (we were saved by LH's kindness), I'm assuming we'll be added. Correct me if I'm wrong, Dan. -- James Hawkins
Re: Want to be a Wine mentor for Google Summer of Code 2007?
On 3/15/07, Maarten Lankhorst <[EMAIL PROTECTED]> wrote: Kai Blin schreef: > On Tuesday 13 March 2007 08:29, Dan Kegel wrote: > >> I'm looking for active Wine developers to act >> as mentors for Google Summer of Code 2007. >> If you're interested, please let me know quickly; >> the list has to be finalized in the next half-day >> or so. (Sorry for the late notice; I wasn't paying >> attention, and the deadline snuck up on me...) >> > Looks like we were too late then? We're not on the list of mentoring projects > this year, it seems. > > Cheers, > Kai Seems that way, looks like we indeed missed them, is it still possible to participate for soc 2007 with wine, or do we have to wait till next year? Read Dan's earlier post: I'm fine this year, but considering how I missed the deadline (we were saved by LH's kindness), I'm assuming we'll be added. Correct me if I'm wrong, Dan. -- James Hawkins
Re: Link creation not working _properly_ under 2.6 kernel?
On 3/15/07, Lei Zhang <[EMAIL PROTECTED]> wrote: It looks like the icon bug has already been reported: http://bugs.winehq.org/show_bug.cgi?id=7084 On my machine, wine puts WinRar.desktop in ~/.local/shared/applications/wine/Programs/WinRar, which then appears in my KDE menu. Are you saying the .desktop files went into ~/.wine/drive_c/Program Files/WinRar instead? Yes, except that my Drive C is mapped to /mnt/d but that shouldnt make any difference. Note that this happens with the 2.6.20.2 kernel from kernel.org, which the 2.6 kernel is now required in order to run wine on Slackware 11.. Now that I think about it, I cant get wine to run on the Slack 11 2.4 kernel because of missing kernel support for something, so I had to get the 2.6 kernel from kernel.org.. When I originally installed this box, the current 2.6 was 2.6.20.1 and wine installed WinRAR to the menu and the desktop properly. Then I broke my install and had to to a clean reinstall of Slack, and so when I went back to kernel.org, the kernel was 2.6.20.2, so I downloaded it and compiled and installed.. After that I installed wine, and the menu shortcuts were put in the wrong folder. Perhaps I either missed a config option in the kernel that is affecting this, or something that was changed in 2.6 actually breaks wine's menu creation? Like I said, the wine version didn't change between the reinstalls because I can't use git -- Thanks Tom Check out this new 3D Instant Messenger called IMVU. It's the best I have seen yet! http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email
Re: Want to be a Wine mentor for Google Summer of Code 2007?
Kai Blin schreef: > On Tuesday 13 March 2007 08:29, Dan Kegel wrote: > >> I'm looking for active Wine developers to act >> as mentors for Google Summer of Code 2007. >> If you're interested, please let me know quickly; >> the list has to be finalized in the next half-day >> or so. (Sorry for the late notice; I wasn't paying >> attention, and the deadline snuck up on me...) >> > Looks like we were too late then? We're not on the list of mentoring projects > this year, it seems. > > Cheers, > Kai Seems that way, looks like we indeed missed them, is it still possible to participate for soc 2007 with wine, or do we have to wait till next year? Maarten
Re: Bug with creating an attachment
Should be fixed now. On Thu, 2007-03-15 at 10:52 -0500, Tom Spear wrote: > I am getting an error trying to create an attachment in bugzilla. If > I paste it my email will come thru as html, but if I attach, it will > be a picture attachment, neither of which are allowed.. > > Ill just type the error: > > Internal Error > > Bugzilla has suffered an internal error. Please save this page and > send it to [EMAIL PROTECTED] with the details of what you were > doing at the time this message appeared.
Defining COM interfaces without IDL
Hi. The PSDK headers sometimes use IDL to define an interface, sometimes it's done by hand (or rather using macros). I don't know if there is any reason for that (someone in the channel said it's just sloppiness by MS) - so, are there any resulting differences regarding source compatibility or can we just use IDL even if MS didn't? Felix
Re: Link creation not working _properly_ under 2.6 kernel?
On 3/15/07, Tom Spear <[EMAIL PROTECTED]> wrote: On 3/15/07, Lei Zhang <[EMAIL PROTECTED]> wrote: > On 3/15/07, Tom Spear <[EMAIL PROTECTED]> wrote: > > On 3/15/07, Tom Spear <[EMAIL PROTECTED]> wrote: > > > Hi all, I just got Slackware 11, and have a couple issues with link > > creation. I cant say that this worked with 10.2 either though, as I havent > > had a Linux machine in about a year, since the motherboard died on my last > > one.. > > > > > > The first issue is that regardless of which kernel I use, the Desktop link > > doesn't have the WinRAR icon, just the default blank paper KDE icon, and the > > menu entries have no icons at all. > > > > > > Second, with 2.4 the icon is created and put on my desktop, but with 2.6 > > it is created and put where I have Drive C pointed to in winecfg. > > > > > > Third, with 2.4 the menu entries are put in the menu under the wine > > folder, but with 2.6 they are put under the installdir of the app. > > > > > > I am using 0.9.32, as I cannot download the git version due to the > > corporate firewall, and transparent web proxy.. > > > > > > If needed I can create a bug for this issue, and as soon as I get a free > > minute I will reinstall and get the debug messages. > > > > > > > Update: seems that the relocation of the icon to the desktop is working, I > > just needed to use winecfg to point to the location of the Desktop, however > > after removing WinRAR, and the WinRAR shortcut directory from the root of > > the "C Drive" and reinstalling, the menu entries folder is still located in > > /d/Program\ Files/WinRAR > > > > Tom > > > > I'm using Slackware 11 here and Winrar put the desktop icon in the > correct location, that is, ~/Desktop. It sounds like you had some > configuration problems? Can you start with a fresh .wine directory and > try again? > > If you are confident this is not due to a configuration issue, please > file a bug. Also, this discussion is probably more appropriate for the > wine-users mailing list. > > - Lei > My update says that the icon is on the desktop. However the other issues still remain (the icon not being a WinRAR icon, and the menu not being put in my KDE menu, but instead under C:\\Program\ Files\\WinRAR This is a fresh .wine directory, as this is a fresh install of Slackware 11, not an upgrade, so I know it isn't a config issue. This is definitely a bug.. wineshelllink is failing to fork and exec, or so I gathered from a message right before the installer quit that said something to that effect. I will attach the full output in just a sec. -- Thanks Tom It looks like the icon bug has already been reported: http://bugs.winehq.org/show_bug.cgi?id=7084 On my machine, wine puts WinRar.desktop in ~/.local/shared/applications/wine/Programs/WinRar, which then appears in my KDE menu. Are you saying the .desktop files went into ~/.wine/drive_c/Program Files/WinRar instead?
Re: Link creation not working _properly_ under 2.6 kernel?
My update says that the icon is on the desktop. However the other issues still remain (the icon not being a WinRAR icon, and the menu not being put in my KDE menu, but instead under C:\\Program\ Files\\WinRAR This is a fresh .wine directory, as this is a fresh install of Slackware 11, not an upgrade, so I know it isn't a config issue. This is definitely a bug.. wineshelllink is failing to fork and exec, or so I gathered from a message right before the installer quit that said something to that effect. I will attach the full output in just a sec. Here is the output, attached for your viewing pleasure. It is not a full trace, just the output from running wine wrar362.exe with no WINEDEBUG= parameters.. Looks like something is broken either in the shell linker itself or in the menu builder, not sure which yet. trace Description: Binary data
Re: Link creation not working _properly_ under 2.6 kernel?
On 3/15/07, Lei Zhang <[EMAIL PROTECTED]> wrote: On 3/15/07, Tom Spear <[EMAIL PROTECTED]> wrote: > On 3/15/07, Tom Spear <[EMAIL PROTECTED]> wrote: > > Hi all, I just got Slackware 11, and have a couple issues with link > creation. I cant say that this worked with 10.2 either though, as I havent > had a Linux machine in about a year, since the motherboard died on my last > one.. > > > > The first issue is that regardless of which kernel I use, the Desktop link > doesn't have the WinRAR icon, just the default blank paper KDE icon, and the > menu entries have no icons at all. > > > > Second, with 2.4 the icon is created and put on my desktop, but with 2.6 > it is created and put where I have Drive C pointed to in winecfg. > > > > Third, with 2.4 the menu entries are put in the menu under the wine > folder, but with 2.6 they are put under the installdir of the app. > > > > I am using 0.9.32, as I cannot download the git version due to the > corporate firewall, and transparent web proxy.. > > > > If needed I can create a bug for this issue, and as soon as I get a free > minute I will reinstall and get the debug messages. > > > > Update: seems that the relocation of the icon to the desktop is working, I > just needed to use winecfg to point to the location of the Desktop, however > after removing WinRAR, and the WinRAR shortcut directory from the root of > the "C Drive" and reinstalling, the menu entries folder is still located in > /d/Program\ Files/WinRAR > > Tom > I'm using Slackware 11 here and Winrar put the desktop icon in the correct location, that is, ~/Desktop. It sounds like you had some configuration problems? Can you start with a fresh .wine directory and try again? If you are confident this is not due to a configuration issue, please file a bug. Also, this discussion is probably more appropriate for the wine-users mailing list. - Lei My update says that the icon is on the desktop. However the other issues still remain (the icon not being a WinRAR icon, and the menu not being put in my KDE menu, but instead under C:\\Program\ Files\\WinRAR This is a fresh .wine directory, as this is a fresh install of Slackware 11, not an upgrade, so I know it isn't a config issue. This is definitely a bug.. wineshelllink is failing to fork and exec, or so I gathered from a message right before the installer quit that said something to that effect. I will attach the full output in just a sec. -- Thanks Tom Check out this new 3D Instant Messenger called IMVU. It's the best I have seen yet! http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email
Re: Bug with creating an attachment
Yep, Bugzilla is broken in several places right now... including the ability to add new bugs. :-( On 3/15/07, Tom Spear <[EMAIL PROTECTED]> wrote: Another bug, this time with posting a comment.. undef error - Can't find param named product at /usr/share/perl/5.8/CGI/Carp.pm line 314. On 3/15/07, Tom Spear <[EMAIL PROTECTED]> wrote: > I am getting an error trying to create an attachment in bugzilla. If I paste it my email will come thru as html, but if I attach, it will be a picture attachment, neither of which are allowed.. > > Ill just type the error: > > Internal Error > > Bugzilla has suffered an internal error. Please save this page and send it to [EMAIL PROTECTED] with the details of what you were doing at the time this message appeared. > > -- > Thanks > > Tom > > Check out this new 3D Instant Messenger called IMVU. It's the best I have seen yet! > > > > http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email -- Thanks Tom Check out this new 3D Instant Messenger called IMVU. It's the best I have seen yet! http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email
Re: Link creation not working _properly_ under 2.6 kernel?
On 3/15/07, Tom Spear <[EMAIL PROTECTED]> wrote: On 3/15/07, Tom Spear <[EMAIL PROTECTED]> wrote: > Hi all, I just got Slackware 11, and have a couple issues with link creation. I cant say that this worked with 10.2 either though, as I havent had a Linux machine in about a year, since the motherboard died on my last one.. > > The first issue is that regardless of which kernel I use, the Desktop link doesn't have the WinRAR icon, just the default blank paper KDE icon, and the menu entries have no icons at all. > > Second, with 2.4 the icon is created and put on my desktop, but with 2.6 it is created and put where I have Drive C pointed to in winecfg. > > Third, with 2.4 the menu entries are put in the menu under the wine folder, but with 2.6 they are put under the installdir of the app. > > I am using 0.9.32, as I cannot download the git version due to the corporate firewall, and transparent web proxy.. > > If needed I can create a bug for this issue, and as soon as I get a free minute I will reinstall and get the debug messages. > Update: seems that the relocation of the icon to the desktop is working, I just needed to use winecfg to point to the location of the Desktop, however after removing WinRAR, and the WinRAR shortcut directory from the root of the "C Drive" and reinstalling, the menu entries folder is still located in /d/Program\ Files/WinRAR Tom I'm using Slackware 11 here and Winrar put the desktop icon in the correct location, that is, ~/Desktop. It sounds like you had some configuration problems? Can you start with a fresh .wine directory and try again? If you are confident this is not due to a configuration issue, please file a bug. Also, this discussion is probably more appropriate for the wine-users mailing list. - Lei
Re: Bug with creating an attachment
Another bug, this time with posting a comment.. undef error - Can't find param named product at /usr/share/perl/5.8/CGI/Carp.pm line 314. On 3/15/07, Tom Spear <[EMAIL PROTECTED]> wrote: I am getting an error trying to create an attachment in bugzilla. If I paste it my email will come thru as html, but if I attach, it will be a picture attachment, neither of which are allowed.. Ill just type the error: Internal Error Bugzilla has suffered an internal error. Please save this page and send it to [EMAIL PROTECTED] with the details of what you were doing at the time this message appeared. -- Thanks Tom Check out this new 3D Instant Messenger called IMVU. It's the best I have seen yet! http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email -- Thanks Tom Check out this new 3D Instant Messenger called IMVU. It's the best I have seen yet! http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email
Bug with creating an attachment (take 2)
I am getting an error trying to create an attachment in bugzilla. If I paste it my email will come thru as html, but if I attach, it will be a picture attachment, neither of which are allowed.. Ill just type the error: Internal Error Bugzilla has suffered an internal error. Please save this page and send it to [EMAIL PROTECTED] with the details of what you were doing at the time this message appeared. URL: http://bugs.winehq.org/attachment.cgi undef error - Can't find param named product at Bugzilla/Config.pm line 124. -- Thanks Tom Check out this new 3D Instant Messenger called IMVU. It's the best I have seen yet! http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email
Bug with creating an attachment
I am getting an error trying to create an attachment in bugzilla. If I paste it my email will come thru as html, but if I attach, it will be a picture attachment, neither of which are allowed.. Ill just type the error: Internal Error Bugzilla has suffered an internal error. Please save this page and send it to [EMAIL PROTECTED] with the details of what you were doing at the time this message appeared. -- Thanks Tom Check out this new 3D Instant Messenger called IMVU. It's the best I have seen yet! http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email
Re: Want to be a Wine mentor for Google Summer of Code 2007?
On Tuesday 13 March 2007 08:29, Dan Kegel wrote: > I'm looking for active Wine developers to act > as mentors for Google Summer of Code 2007. > If you're interested, please let me know quickly; > the list has to be finalized in the next half-day > or so. (Sorry for the late notice; I wasn't paying > attention, and the deadline snuck up on me...) Looks like we were too late then? We're not on the list of mentoring projects this year, it seems. Cheers, Kai -- Kai Blin, WorldForge developerhttp://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin/ -- Will code for cotton. pgp8sqbS1s9FU.pgp Description: PGP signature
Re: Link creation not working _properly_ under 2.6 kernel?
On 3/15/07, Tom Spear <[EMAIL PROTECTED]> wrote: Hi all, I just got Slackware 11, and have a couple issues with link creation. I cant say that this worked with 10.2 either though, as I havent had a Linux machine in about a year, since the motherboard died on my last one.. The first issue is that regardless of which kernel I use, the Desktop link doesn't have the WinRAR icon, just the default blank paper KDE icon, and the menu entries have no icons at all. Second, with 2.4 the icon is created and put on my desktop, but with 2.6it is created and put where I have Drive C pointed to in winecfg. Third, with 2.4 the menu entries are put in the menu under the wine folder, but with 2.6 they are put under the installdir of the app. I am using 0.9.32, as I cannot download the git version due to the corporate firewall, and transparent web proxy.. If needed I can create a bug for this issue, and as soon as I get a free minute I will reinstall and get the debug messages. Update: seems that the relocation of the icon to the desktop is working, I just needed to use winecfg to point to the location of the Desktop, however after removing WinRAR, and the WinRAR shortcut directory from the root of the "C Drive" and reinstalling, the menu entries folder is still located in /d/Program\ Files/WinRAR Tom
Link creation not working _properly_ under 2.6 kernel?
Hi all, I just got Slackware 11, and have a couple issues with link creation. I cant say that this worked with 10.2 either though, as I havent had a Linux machine in about a year, since the motherboard died on my last one.. The first issue is that regardless of which kernel I use, the Desktop link doesn't have the WinRAR icon, just the default blank paper KDE icon, and the menu entries have no icons at all. Second, with 2.4 the icon is created and put on my desktop, but with 2.6 it is created and put where I have Drive C pointed to in winecfg. Third, with 2.4 the menu entries are put in the menu under the wine folder, but with 2.6 they are put under the installdir of the app. I am using 0.9.32, as I cannot download the git version due to the corporate firewall, and transparent web proxy.. If needed I can create a bug for this issue, and as soon as I get a free minute I will reinstall and get the debug messages. -- Thanks Tom Check out this new 3D Instant Messenger called IMVU. It's the best I have seen yet! http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email
Re: Romanian Wine translation
On Thu, March 15, 2007 05:12, Michael Stefaniuc wrote: > Hi, > > MikoÅaj Zalewski wrote: >> I've seen you have started the Romanian translation of wine. Could you >> look on the page http://wiki.winehq.org/SublangNeutral and mark if >> Romanian should use SUBLANG_NEUTRAL or sublang codes? > I would have done that myself long ago but I do not know that. I'll use > LANG_NEUTRAL as long as somebody more knowledgeable dosn't change it. I'd say this is the correct thing to do. There are Moldavian, etc for SUBLANG, but we should use the "standard" (Academy sanctioned) version, which would qualify to NEUTRAL IMO. -- Dimi Paun <[EMAIL PROTECTED]> Lattica, Inc.
Re: user32: Restore erroneously removed chunk of code
Dmitry Timoshkov <[EMAIL PROTECTED]> writes: > one of my recent MDI patches has caused a regression in one of applications > I'm working on. This patch should fix it by restoring apparently erroneously > removed chunk of code. > > Changelog: > user32: Restore erroneously removed chunk of code. This breaks the tests: ../../../tools/runtest -q -P wine -M user32.dll -T ../../.. -p user32_test.exe.so msg.c && touch msg.ok msg.c:2836: Test failed: ShowWindow(SW_RESTORE):invisible MDI child: the msg sequence is not complete: expected 0046 - actual msg.c:2866: Test failed: ShowWindow(SW_RESTORE):maximized MDI child: the msg sequence is not complete: expected 0046 - actual -- Alexandre Julliard [EMAIL PROTECTED]
Re: Delayed debug patch
On Thu, Mar 15, 2007 at 11:08:49AM +, Kapila De Silva wrote: > Can someone tell me how to apply this to my git copy of wine please? > This would help a lot with my debugging... I have that in a slightly modified form in my hacks git repository, please read the Changelog for that patch to see how it works. git fetch git://repo.or.cz/wine/hacks.git master:hacks git checkout hacks Or you can just pick the specific patch from that branch. See http://repo.or.cz/w/wine/hacks.git for the git webinterface to that repository. Jan
Re: Makefiles: Be less verbose when performing make rules by only printing the command being executed and the source and/or target file.
Robert Shearman <[EMAIL PROTECTED]> writes: > I've also modified tools/makerule to respect the "-s" flag passed into make. > > Alexandre suggested on IRC that I always print the destination file, > but I want to make sure that the technical details of this patch are > acceptable before making tweaks to the printed commands. I've been thinking about this some more, and I don't think I'll put it in. It's going to cause a lot of trouble and portability headaches, for only a minor cosmetic gain. This thing really belongs in make itself; it shouldn't be hard to patch GNU make to have a mode where it only displays the command name and target instead of the whole command line. Then it would work for all projects, and wouldn't require adding complexity to the makefiles. -- Alexandre Julliard [EMAIL PROTECTED]
Delayed debug patch
Can someone tell me how to apply this to my git copy of wine please? This would help a lot with my debugging... Thanks Kapila
Re: Romanian Wine translation
Hi, Mikołaj Zalewski wrote: > I've seen you have started the Romanian translation of wine. Could you > look on the page http://wiki.winehq.org/SublangNeutral and mark if > Romanian should use SUBLANG_NEUTRAL or sublang codes? I would have done that myself long ago but I do not know that. I'll use LANG_NEUTRAL as long as somebody more knowledgeable dosn't change it. bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 Sr. Network EngineerFax.: +49-711-96437-111 Red Hat GmbHEmail: [EMAIL PROTECTED] Hauptstaetterstr. 58http://www.redhat.de/ D-70178 Stuttgart
Re: Need help with SymInitializeW
Hi guys, I put some more debug in the process_find_by_handle function of dbghelp.c, and what Im seeing is the second time we call SymInitializeW, we appear to create a new process structure, so following calls to process_find_by_handle returns the new one, and not the old one. In the trace below, the first call to process_find_by_handle returns a process structure stored at 0x16c600, but the next calls locate two process structures (one at 0x16c600 and one at 0xf5ee680). Could this be an issue? Both seem to have the same process handle of 0x. Maybe when allocating a new process structure we should check if one already exists with the same handle? Thanks Kapila. fixme:dbghelp:SymInitialize Calling SymInitializeW 0x fixme:dbghelp:SymInitializeW (0x (null) 1) fixme:dbghelp:process_find_by_handle Searching for process 0x compared to 0x (0x16c600) fixme:dbghelp:process_find_by_handle Returning process handle 0x16c600 and 0x fixme:dbghelp:SymInitializeW what to do ?? fixme:dbghelp:SymInitializeW Not User search path fixme:dbghelp:SymInitializeW check live target fixme:dbghelp:SymInitializeW Invade Process fixme:dbghelp:process_find_by_handle Searching for process 0x compared to 0x (0xf5ee680) fixme:dbghelp:process_find_by_handle Searching for process 0x compared to 0x (0x16c600) fixme:dbghelp:process_find_by_handle Returning process handle 0xf5ee680 and 0x On Wed, 2007-03-14 at 20:53 +0100, Eric Pouech wrote: > Paul Vriens a écrit : > > Eric Pouech wrote: > >> Kapila De Silva a écrit : > >>> Hi All, > >>> > >>> Im trying to debug a crash in Everquest 2, (bug 7705) and am hoping > >>> someone here can help. > >>> > >> I'll send a fix later on for the FIXME, but it's unlikely this is > >> what's causing the crash > >> So, you have to understand where the 0x as an address comes > >> from. sometimes, +relay helps figuring that out, but YMMV > >> > >> A+ > >> > > Hi, > > > > just wanted to report that Process Explorer also calls it with > > 0x when viewing the 'System Information': > > > > trace:dbghelp:SymInitializeW (0x (null) 0) > > trace:dbghelp:elf_load_file Processing elf file 'L"wine-kthread"' at > > > > trace:dbghelp:elf_load_file Processing elf file > > 'L"/usr/lib/qt-3.3/bin/wine-kthread"' at > > trace:dbghelp:elf_load_file Processing elf file > > 'L"/usr/kerberos/bin/wine-kthread"' at > > trace:dbghelp:elf_load_file Processing elf file > > 'L"/usr/local/bin/wine-kthread"' at > > > > Could 0x mean something like system-wide? > > > > Cheers, > > > > Paul. > > > > > in that cas 0x is the default handle to the current process, and > is never derefenced... > include/winbase.h:#define GetCurrentProcess() ((HANDLE)0x) > A+ >
