wine-devel

wine-devel@winehq.org

2 participants
84469 discussions

Re: Make QueryServiceConfigW return an empty string for empty dependencies
by James Hawkins 04 Mar '05

04 Mar '05

On Fri, 4 Mar 2005 13:54:34 +1100, Troy Rollo <wine(a)troy.rollo.name> wrote: > QueryServiceConfigW currently returns a NULL pointer for lpDependencies when > there are no dependencies. The documentation states that an empty string has > the same meaning, and at least one application (an MSIEXEC.EXE from the > Office XP CD) will SEGV if this is NULL. Using the empty string avoids this. > > ChangeLog: > Return an empty string for service dependencies when there are no > dependencies, rather than a NULL pointer, which causes some apps > to SEGV. Can you write test cases for this behaviour? -- James Hawkins

1 0

Re: Make QueryServiceConfigW return an empty string for empty dependencies
by James Hawkins 04 Mar '05

04 Mar '05

1 0

wine-user.pdf feedback 2
by Dan W. 04 Mar '05

04 Mar '05

Okay, now I found what I think is a more serious missing piece of info in wine-user.pdf. In page 20, last paragraph, it says one can start off by modifying the sample config file, which "can be found in the directory 'documentation/samples'... Problem is, I did a file search for 'documentation', and I get like 10 pages of hits I did a file search for samples, and same thing, or worse. In both cases I went through all those instances visually scanning for 'wine' or 'config' and found nothing at all. I know I ought to have the sources somewhere, because when I installed fc2, I said "install everything", and that included sources; but I have no idea where to look for the wine documentation folder. I have to give up on it for now. Far past my bedtime by now, anyways.. ;-) Cheers!

3 2

Re: MSI: Radio Buttons
by Dmitry Timoshkov 04 Mar '05

04 Mar '05

"Ulrich Czekalla" <ulrich.czekalla(a)utoronto.ca> wrote: > + if (control->hwnd) > + { > + WNDPROC oldproc = (WNDPROC) SetWindowLongPtrW(control->hwnd, GWLP_WNDPROC, > + (LONG)MSIRadioGroup_WndProc); Then it's better to cast to LONG_PTR instead of LONG. -- Dmitry.

1 0

Re: [ADVAPI] SetSecurityInfo
by Robert Shearman 03 Mar '05

03 Mar '05

Raphael wrote: >Hi, > > Changelog: > - simple implementation of SetSecurityInfo > >(seems to be needed by War3 frozen throne, cf >http://forums.gentoo.org/viewtopic-t-303306.html?sid=3f962c702ae58ad8902ca8…) > > I have made a few comments on the implementation below: > SRCDIR = @srcdir@ > VPATH = @srcdir@ > MODULE = advapi32.dll >-IMPORTS = kernel32 ntdll >+IMPORTS = winspool kernel32 ntdll > > Should be in DELAYIMPORTS. We don't want to slow down the loading of all applications because of this one uncommon case. >@@ -1418,6 +1422,87 @@ > { > FIXME("(%s) : stub\n", debugstr_w(lpFileName) ); > return TRUE; >+} >+ >+/****************************************************************************** >+ * SetSecurityInfo [ADVAPI32.@] >+ */ >+BOOL WINAPI SetSecurityInfo(HANDLE handle, >+ SE_OBJECT_TYPE ObjectType, >+ SECURITY_INFORMATION SecurityInfo, >+ PSID psidOwner, >+ PSID psidGroup, >+ PACL pDacl, >+ PACL pSacl) >+{ >+ SECURITY_DESCRIPTOR sd; >+ BOOL test; >+ >+ TRACE("(%p, %x, %x, %p, %p, %p, %p) : alomst stub\n", handle, ObjectType, SecurityInfo, psidOwner, psidGroup, pDacl, pSacl); > > Remove the "almost stub" part of it and just print FIXME's for the parts that aren't implemented, otherwise the next person that comes along to this function will spend hours trying to work out what isn't implemented, if they even realise this function is to blame. >+ >+ test = InitializeSecurityDescriptor(&sd, SECURITY_DESCRIPTOR_REVISION); >+ if (!test) return FALSE; >+ >+ if (SecurityInfo & DACL_SECURITY_INFORMATION) { >+ test = SetSecurityDescriptorDacl(&sd, TRUE, pDacl, TRUE); >+ } >+ if (SecurityInfo & SACL_SECURITY_INFORMATION) { >+ test = SetSecurityDescriptorSacl(&sd, TRUE, pSacl, TRUE); >+ } >+ if (SecurityInfo & GROUP_SECURITY_INFORMATION) { >+ if (NULL == psidGroup) { >+ SetLastError( ERROR_INVALID_PARAMETER ); >+ return FALSE; >+ } >+ test = SetSecurityDescriptorGroup(&sd, psidGroup, TRUE); >+ } >+ if (SecurityInfo & OWNER_SECURITY_INFORMATION) { >+ if (NULL == psidOwner) { >+ SetLastError( ERROR_INVALID_PARAMETER ); >+ return FALSE; >+ } >+ test = SetSecurityDescriptorOwner(&sd, psidOwner, TRUE); >+ } >+ >+ switch (ObjectType) { >+ case SE_KERNEL_OBJECT: >+ test = SetKernelObjectSecurity(handle, SecurityInfo, &sd); >+ break; >+ case SE_SERVICE: >+ test = SetServiceObjectSecurity(handle, SecurityInfo, &sd); >+ break; >+ case SE_REGISTRY_WOW64_32KEY: >+ case SE_REGISTRY_KEY: >+ test = RegSetKeySecurity(handle, SecurityInfo, &sd); >+ break; >+ case SE_LMSHARE: >+ /*test = NetShareSetInfo(handle, SecurityInfo, &sd); TODO: don't exit on netapi */ >+ break; >+ case SE_PRINTER: >+ { >+ PRINTER_INFO_2A pr_info; >+ memset(&pr_info, 0, sizeof(pr_info)); >+ /** maybe we should do GetPrinter before SetSecurityDesc* ? */ >+ test = GetPrinterA(handle, 2, (LPBYTE) &pr_info, 0, NULL); >+ pr_info.pSecurityDescriptor = &sd; >+ test = SetPrinterA(handle, 2, (LPBYTE) &pr_info, PRINTER_CONTROL_SET_STATUS); >+ break; >+ } >+ >+ case SE_FILE_OBJECT: >+ /*SetFileSecurity ? */ >+ case SE_WINDOW_OBJECT: > > Call SetUserObjectSecurity. >+ case SE_DS_OBJECT: >+ case SE_DS_OBJECT_ALL: >+ case SE_PROVIDER_DEFINED_OBJECT: >+ case SE_WMIGUID_OBJECT: >+ case SE_UNKNOWN_OBJECT_TYPE: >+ default: >+ WARN("unsupported ObjectType %d\n", ObjectType); > > Change this to a FIXME. >+ test = TRUE; >+ } >+ >+ return test; > > This function returns a DWORD error code, not a BOOL. > } > > /****************************************************************************** > > Rob

1 0

Re: ntdll: Add NtCreateKey tests
by Alexandre Julliard 03 Mar '05

03 Mar '05

James Hawkins <truiken(a)gmail.com> writes: > What are the steps I need to take to break registry initialisation? I > did wonder how anything in the real win32 registry could be created > though if you can't create a key directly under HKLM or HKU. If this > really does break initialisation, can we implement a different > create_key that has little restrictions and would only be used > internally, or would this just be scrapped entirely? I don't think there's any point in replicating that behavior. I doubt there's any such check on Windows either, it's most likely just a side effect of the way the registry files are "mounted" at different places in the tree. Once we have a proper implementation of RegLoadKey/RegUnloadKey we should get the same behavior automatically. -- Alexandre Julliard julliard(a)winehq.org

1 0

any way to unlink the symbolic link, not its target?
by Kuba Ober 03 Mar '05

03 Mar '05

Hi, I'm using wine to cross compile projects using vc7.1 from a software configuration tool called aegis (http://aegis.sf.net). I'm maintaining a symlinked baseline with source and derived (.obj, .exe, .pdb) files in it. A change only has copies of changed files. So, when the compiler tries to output something, it first tries to unlink the file. But that won't work as wine tries to unlink target of the symlink, instead of the symlink itself. Is there any switch somewhere to revert to deleting the symbolic links, or if not -- what source file should I look into to patch that? Thanks a lot, Kuba Ober

1 0

Re: ntdll: Add NtCreateKey tests
by Robert Shearman 03 Mar '05

03 Mar '05

James Hawkins wrote: >On 03 Mar 2005 11:02:24 +0100, Alexandre Julliard <julliard(a)winehq.org> wrote: > > >>James Hawkins <truiken(a)gmail.com> writes: >> >> >> >>>I've been discerning the behavior of RegCreateKey and NtCreateKey when >>>creating a key directly under HKLM or HKU, and this test reveals that >>>NtCreateKey does check for this case and returns a >>>STATUS_INVALID_PARAMETER. >>> >>> >>This is going to break registry initialisation. Do you really have an >>app that depends on that? >> >> >> > >What are the steps I need to take to break registry initialisation? I >did wonder how anything in the real win32 registry could be created >though if you can't create a key directly under HKLM or HKU. If this >really does break initialisation, can we implement a different >create_key that has little restrictions and would only be used >internally, or would this just be scrapped entirely? > > It looks like Windows only uses RegLoadKey to create keys under HKLM and HKU. Maybe we should do the same. Rob

2 4

Re: Wine cabinet.dll FDI Conformance Test Patch
by Dimitrie O. Paun 03 Mar '05

03 Mar '05

On Wed, Mar 02, 2005 at 03:41:21PM -0800, Rizwan Kassim wrote: Good stuff guys! Here are a few comments: +#ifndef STANDALONE +#include <wine/test.h> +#define ok2 ok +#else +/* To build outside Wine tree, compile with cl -DSTANDALONE -D_X86_ tvfs.c cabinet_fdi.c FDI.lib + These are only called if standalone are used, defining ok and START_TEST, which would normally be declared in winetree */ +#include <assert.h> +#include <stdio.h> +#define START_TEST(name) main(int argc, char **argv) +#define ok(condition, msg) \ + do { if(!(condition)) { \ + fprintf(stderr,"failed at %d, msg:" msg "\n",__LINE__); \ + exit(1); \ + } } while(0) +#define ok2(condition, msg, arg) \ + do { if(!(condition)) { \ + fprintf(stderr,"failed at %d, msg:" msg "\n",__LINE__, arg); \ + exit(1); \ + } } while(0) +#define todo_wine Please get rid of this. It is useless in the Wine tree. If you need it, just put it in a private header file, and include it there. +#ifndef DEBUG_ALLOC +FNALLOC(final_alloc) { + return malloc(cb); +} +FNFREE(final_free) { + free(pv); + return; +} +#else +FNALLOC(final_alloc) { + trace(" FNALLOC just called with %d\n",cb); + return malloc(cb); +} +FNFREE(final_free) { + trace(" FNFREE just called with %d\n",pv); + free(pv); + return; +} +#endif No need for this either. It's a test after all, there's no big deal if you have a memory leak... :) +#ifdef VERBOSE + trace(" FNFDINOTIFY real just called with %d, %d \n",fdint,pfdin); +#endif Don't do it this way. Define trace such that you can use it unconditionally. In general, try to avoid using the preprocessor in the code. + trace(" Cabinet Data : cbC %d cF %d cFi %d si %d iC %d fr %d hp %d hn %d\n", + cabinfo.cbCabinet, + cabinfo.cFolders , + cabinfo.cFiles , + cabinfo.setID, + cabinfo.iCabinet, + cabinfo.fReserve , + cabinfo.hasprev , + cabinfo.hasnext ); These should fit on 2-3 lines, no? + ok2 ( cabinfo.cbCabinet == TcbCabinet, "FDIIsCabinet,cabinfo %s data did not match! Failed!\n", cabname); + ok2 ( cabinfo.cFolders == TcFolders, "FDIIsCabinet,cabinfo %s data did not match! Failed!\n", cabname); + ok2 ( cabinfo.cFiles == TcFiles, "FDIIsCabinet,cabinfo %s data did not match! Failed!\n", cabname); + ok2 ( cabinfo.setID == TsetID, "FDIIsCabinet,cabinfo %s data did not match! Failed!\n", cabname); + ok2 ( cabinfo.iCabinet == TiCabinet, "FDIIsCabinet,cabinfo %s data did not match! Failed!\n", cabname); + ok2 ( cabinfo.fReserve == TfReserve, "FDIIsCabinet,cabinfo %s data did not match! Failed!\n", cabname); + ok2 ( cabinfo.hasprev == Thasprev, "FDIIsCabinet,cabinfo %s data did not match! Failed!\n", cabname); + ok2 ( cabinfo.hasnext == Thasnext, "FDIIsCabinet,cabinfo %s data did not match! Failed!\n", cabname); Use ok() instead of ok2(). Also, it's probably better if the message contains the values of the variables that don't match, so we know why it failed. +#ifdef TVFS_DEBUG + trace("tvfs_create called with %s, %d, %d\n", fname, buf, len); +#endif Similar to the one above, do the test inside the body of trace(), not on every use. + switch(whither) { + case SEEK_SET: { + handles[h]->pos = whence; + break; + } + case SEEK_CUR: { + handles[h]->pos += whence; + break; + } This one needs a bit of indentation, no? +int tvfs_close(int h){ + int inode = handles[h]->inode; +#ifdef TVFS_DEBUG + trace("tvfs_close called with %d\n", h); +#endif + if (!files[inode]){ + return -1; + } + free(handles[h]); + /* Currently does NOT enabled open to reuse this handle */ + return 0; + } The formatting on this is funny. It needs indenting, spaces before '{', and the opening braket for the function on a new line. +main(){ Ditto. -- Dimi.

2 1

Re: MSI trouble with ALLUSERPROFILE
by Juan Lang 03 Mar '05

03 Mar '05

> I get err with %ALLUSERPROFILE during install program: <snip> > Where I will set this env variable? (I know I can do it in shell, but > what is the right way?) Hm.. I never did get this quite right. For consistency, it should be in wine.inf. That's where USERPROFILE is: HKLM,System\CurrentControlSet\Control\Session Manager\Environment,"USERPROFILE",,"%53%" But I don't think it can go here, because setupapi (which is what interprets those funny "%53" type strings) doesn't have a magic constant for this, and there isn't a CSIDL value for it. So maybe shell32 should set it in SHELL_RegisterShellFolders? --Juan __________________________________ Celebrate Yahoo!'s 10th Birthday! Yahoo! Netrospective: 100 Moments of the Web http://birthday.yahoo.com/netrospective/

1 0

Use of STLPort with winegcc
by Boaz Harrosh 03 Mar '05

03 Mar '05

Winegcc will prepend any of the command line switches with "-I wine/include/msvcrt" if the "-no-cygwin" flag is specified. This breaks STLPort because STLPort must be first on the search path, before the regular c-runtime of the compiler. This way it can do it's tricks of what to use and what not to use from the standard c-runtime. What is the current way to solve it. I could remove the "-no-cygwin" flag and Manually add the "-I wine/include/msvcrt" and "-D__MSVCRT__". But how do I add the "-dmsvcrt" on the Winebuild command line, as it is all internal to winegcc. What would be the right way to do it? I would submit a patch, but what should I do? Just append the "-I .../msvcrt" instead of prepend, or maybe use "-isystem .../msvcrt". The docs for gcc say that "-isystem" folders will be searched before the default gcc folders but after any -I folders. Free Life Boaz

2 1

Re: MSI: Radio Buttons
by Dmitry Timoshkov 03 Mar '05

03 Mar '05

"Ulrich Czekalla" <ulrich.czekalla(a)utoronto.ca> wrote: > + if (control->hwnd) > + { > + WNDPROC oldproc = (WNDPROC) SetWindowLongW(control->hwnd, GWLP_WNDPROC, > + (LONG)MSIRadioGroup_WndProc); I'd suggest to use SetWindowLongPtrW even it's just a macro in Win32 we still need to write 64-bit clean code. -- Dmitry.

1 0

Speach rec. on Wine
by wino＠piments.com 03 Mar '05

03 Mar '05

Hi, I am trying to get Dragon Naturally Speaking to run under Wine. I have got it installed successfully from CD, now I need to get it running. I have wine-20050111 installed , a 2.6.10 kernel and a current version of IE6 since Dragon apparently needs IE installed . Some advice please. Is there any fundemental problems which make this a no-hoper, has anyone got this working so far? Any a-priori conditions or advice I should know, like what sound model to use on Linux. Where should I search for detailed info on debugging something like this? There seems to be very little detailed help for Wine which I find surprising. Maybe I have just missed it Any other advice that could save me wasting lots of time. TIA .

2 1

Re: Add all MIME types
by Mike Hearn 03 Mar '05

03 Mar '05

On Wed, 02 Mar 2005 12:56:33 +0000, Mike Hearn wrote: > Oh my god, there are a lot of these! Wouldn't it be a better long term > solution to just get the desktop environments sorted out? They should be > sharing the same MIME database now right? So why are they not all > identifying EXEs as the same MIME type? By the way, that wasn't an objection to the patch. I think it should go in. It's trivial enough and doesn't have any bad consequences except slightly less "elegance" but we can fix that one day when all the desktops are fixed :)

1 0

http://ftp.codeweavers.com/pub/crossover/office/source/office-src-4.1.0.tgz
by Grant Williamson 03 Mar '05

03 Mar '05

Hi, I am just wondering how much does the wine source located on http://ftp.codeweavers.com/pub/crossover/office/source/office-src-4.1.0.tgz differ from 20040716. I guess its codeweavers internal patched version, I see changes in there dating to January. Are there any restrictions on using this source?

3 3

Re: imagelist: style fixes
by Alexandre Julliard 03 Mar '05

03 Mar '05

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > ChangeLog > Style fixes for consistent formatting. I knew I was going to regret applying Mike's indentation patches... Folks, please let's not start an indentation police, there's no reason to "fix" anything unless a file is really so messed up that it becomes unreadable. -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: [user/tests/sysparams.c] Added more SetLastError(0)'s
by Dmitry Timoshkov 03 Mar '05

03 Mar '05

"Paul Vriens" <Paul.Vriens(a)xs4all.nl> wrote: > as discussed a few times on wine-devel, there isa need to clear the > last error before calling a SPI_{GET|SET} routine. > > It appears that not every call resets the last error to 0 on succession > and thus errors will propagate and leave us in the dark. You have to set last error to some bogus value (usually 0xdeadbeef) in order to test whether an API really has changed it. -- Dmitry.

3 2

Re: MSI: Radio Buttons
by Alexandre Julliard 03 Mar '05

03 Mar '05

Ulrich Czekalla <ulrich.czekalla(a)utoronto.ca> writes: > const static WCHAR szStatic[] = { 'S','t','a','t','i','c',0 }; > +const static WCHAR szButton[] = { 'B','U','T','T','O','N', 0 }; > + > +const static WCHAR szButtonData = { 0 }; Did you really intend to use an empty string here for the button property? That doesn't seem right; though if you really need to redefine the winproc it would be much cleaner IMO to define a proper window class. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: riched20 and test app
by Mike McCormack 03 Mar '05

03 Mar '05

Hi Krzysztof, Krzysztof Foltman wrote: > This is an attempt at starting a RichEdit 2.0 clone, plus a test app for > it (which I, for some reason, decided to call Wine WordPad). Cool. Looks like you've done alot of good work. > It lacks most essential functionality, and source formatting is not > exactly standard, but it has enough functionality to make a couple of > Wine developers convince me to release it now. Or weeks ago. Well, you wrote it, so you get to choose the formatting. I like that you've used lots of small functions, rather than monolithic 200 line globs. I like the asserts too. > The test app uses the Mike McCormack's test snippet to fill the control > with some fancy formatted text. > > Hope the patch is OK. Adding new DLL's and EXE's isn't an easy process. OK, now some suggestions: * submitting riched20 and the new wordpad program seperately would be a good idea. The bigger the patch, the longer it tends to hang round before it's committed. * instead of #ifndef __WINESRC__ ... printf ... #endif, how about using wine's debug macros TRACE, ERR, etc? Then you can just #define TRACE to printf when __WINESRC__ isn't defined * instead of XXXFK how about FIXME? * you probably should get rid of the _int3 macro in wrap.c, and replace it with DebugBreak() * ME_DumpParaStyle isn't used... maybe change it to use MESSAGE() rather than a message box. You can dump stuff by checking the condition WINE_TRACE_ON(richedit). You'll need to declare a WINE_DEFAULT_DEBUG_CHANNEL for that.. * maybe you want to add LGPL licenses on your header files? * keep the formatting in your Makefile.in the same as the other dlls. Julliard's a bit fussy about that, so he's probably going to change it anyway. Might as well save him the time. Mike

1 0

World of Warcraft - crash in game
by Alex Woods 03 Mar '05

03 Mar '05

Hi, World of Warcraft is working beautifully now apart from a crash that occurs seemingly randomly. The application is catching the crash, and giving a message like this: This application has encountered a critical error: ERROR #132 (0x85100084) Program: C:\Program Files\World of Warcraft\WoW.exe Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:557102CD EAX=00000000 EBX=55BDFCA8 ECX=00000000 EDX=55BDFBB8 ESI=5E320308 EDI=00000000 EBP=55BDFC08 ESP=55BDFB9C EIP=557102CD FLG=00010212 CS =0023 DS =002B ES =002B SS =002B FS =005B GS=0063 I know this isn't really much use on it's own. I've tried turning on +relay logging, but it's proved futile - it seems to end up freezing up my system before a crash occurs. One thing that might be useful is that the access violation always seems to be around the same small area of memory each time, eg: Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:557103CD Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:5571025D Over the course of 13 (unlucky for me ;)) crashes, these are the only 3 addresses it has given. My question is what can I do to debug this? +relay logging is probably infeasible, but I'd be happy to hack around to get it to only log certain things - I'm not sure what I'd need to log. Also, the last time it crashed, I was lucky enough to have it leave me in winedbg, which I've left open. Is there anything worth my while poking around with in there while I have the chance? I guess I'll be running memtest on my machine too, but I'd like to do what I can in winedbg first ;) Cheers. -- Alex

4 6

MSI trouble with ALLUSERPROFILE
by Vitaly Lipatov 03 Mar '05

03 Mar '05

I get err with %ALLUSERPROFILE during install program: trace:msi:MSI_FormatRecordW (L"[%ALLUSERSPROFILE]") trace:msi:deformat_string_internal Starting with L"[%ALLUSERSPROFILE]" trace:msi:find_next_outermost_key Found Key L"%ALLUSERSPROFILE" trace:msi:deformat_string_internal Current (null) .. L"%ALLUSERSPROFILE" err:msi:deformat_environment Unknown environment variable trace:msi:deformat_string_internal after everything (null) Where I will set this env variable? (I know I can do it in shell, but what is the right way?) -- Vitaly Lipatov, ALT Linux Team Russia, Saint-Petersburg, www.etersoft.ru

1 0

%Fp printf format specifier
by Uwe Bonnes 03 Mar '05

03 Mar '05

Hallo, http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore98/H… uses a "%Fp" format spezifier. Running with native msvcrt, this seems to be the same as "%p". However builtin msvcrt stumbles about the "superfluous" 'F". Does anybody know what the meaning of the "F" is? I didn't find anything on the net. And b.t.w., how do I get Google to not ignore the '%' in a search for "%Fp"? And mingw/malloc.h has the definitions of _USEDENTRY and _FREEENTRY excahnged and misses more entries... Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

6 12

Re: Use IsWindowVisible instead of GetWindowLong(GWL_STYLE) & WS_VISIBLE as a test for desktop visibility
by Ferenc Wagner 03 Mar '05

03 Mar '05

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > let's see if IsWindowVisible() better detects a not visible desktop. Ah, fine, this may put some momentum into the situation! -- Feri.

3 2

Printing in Wine (using "ttydrv" device)...
by Juergen Hammelmann 03 Mar '05

03 Mar '05

Hi All, we are developing a windows/wine app for automation of MS Word (serial printing in background to PS files with the WINEPS driver on SuSE 9.2 platform, wine-20050211). We want to run this application and Word in background as server, no graphical output should occur in this environment, we don't like to install a X11-/VNC-Server on the server: Using "ttydrv" device I found out that all graphical output is disabled and wine can run without a X11 Server / VNC Server, this is prefered: but here graphical output of printing is disabled, too! The PS files created are blank! Is there any way to configure functioning printing with "ttydrv" device? Ferenc Wagner told me, that printing and graphical output is done through GDI both, so ttydrv as GDI backend disable this all!? Is this the right explanation? Is there any way to enable this for printing again? Best Regards, Jürgen

1 0

Visual C++ 6.0 as a Winelib IDE?
by Ira Krakow 03 Mar '05

03 Mar '05

I have Visual C++ 6.0 running under Crossover Office 4.1, which of course means it's running under Wine. For one of the examples in the Wine/Winelib book, I decided to take the code produced by the VC++ Win32 "Hello World" wizard and see how to port it to Wine. Turns out, it's almost trivial. Create an empty directory, copy the *.c, *.rc, *.h, and *.ico files to it. VC++ produces tons of other files, but they're either used to maintain the Visual Studio environment, or are intermediate compilation files that aren't needed. Then run: $ winemaker . The Makefile that Winemaker generates _almost_ works. You need to delete the references to the mfc library and mfc.dll. After doing that, running make generates the .so file. Wine runs it flawlessly. I got to thinking - can I convert the code from the MFC application as easily? Seems like it's doable, because the generated code runs in VC++/Crossover Office 4.1. I tried the same steps as before, with Winemaker, but I couldn't figure out what Makefile modifications were needed. All of this got me to thinking - could Wine running Visual C++ be a viable IDE for porting? Maybe just linking VC++ with the Winelib libraries would do it. Maybe after tweaking Winemaker and publishing a HOWTO we could show that this is a viable path? It's certainly easier than for Visual Studio developers and could help attract them to Wine. Another benefit - we could use the Visual C++ sample programs as tests for Wine. The programs might exercise areas that haven't been tested thoroughly. What do you think? Ira

5 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel