- Wine-Devel - list.winehq.org

VirtualAllocEx
by Peter Hartshorn Oct. 31, 2003

Oct. 31, 2003

Has there been any work on VirtualAllocEx for allocating memory to other processes? I would like to get this going to allow me to run mta:vc and blow away other people in gta vice city (I believe that is a noble cause). To get me started I have a question. Is there a mechanism for one wine process (thread?) to send a message to another process (thread?) and receive a response, ie a pointer? Or, can I use the wineserver as a mediator that passess messages between two wine processes? For example: app1 sends a message "allocate 1MB of virtual memory in app2" to the wineserver. The wineserver then tells app2 to "allocate 1MB of virtual memory". App2 replys to the wineserver the virtual location of the allocated memory. Wineserver replys to app1 giving the location. App1 can then use the result in WriteProcessMemory.

1 0

Using Serial Port COM1
by Orlando Feitosa Oct. 31, 2003

Oct. 31, 2003

Hello Friends, I'm trying to use an application that access the serial Port COM1 (which has a printer connected) when application tries to communicate with the port I receive the following message error "Privileged Instruction" Here is the dump... (wine 20031016 - RedHat 9.0) __________________________________________________________________________ fixme:commctrl:FlatSB_SetScrollProp stub trace:comm:GetCommState handle 0x84, ptr 0x40851bac trace:comm:GetCommState OK trace:comm:GetCommState bytesize 8 baudrate 9600 fParity 1 Parity 0 stopbits 1 trace:comm:GetCommState IXON IXOFF trace:comm:GetCommState CRTSCTS trace:comm:SetCommState handle 0x84, ptr 0x40851bac trace:comm:SetCommState bytesize 8 baudrate 9600 fParity 1 Parity 0 stopbits 1 trace:comm:SetCommState IXON IXOFF trace:comm:SetCommState CRTSCTS trace:comm:SetCommTimeouts (0x84,0x10034a40) fixme:comm:SetupComm insize 2048 outsize 1024 unimplemented stub fixme:imm:ImmGetContext (0x4005e): stub ____________________________________________________________________________ Please, someone have idea how to solve the problem ? Bests Regards, Orlando

2 1

crossover office mentioned in current "HP World"
by Dan Kegel Oct. 30, 2003

Oct. 30, 2003

HP World is HP's house rag, sent out free to everyone who buys anything from HP or attends their "HP World" show. Several times now they have used the Crossover Office that comes with SuSE Linux during a review of some product. On page 20 of the Nov 2003 issue, for instance, titled "POPping Up Terrabytes", they reviewed FIA's POPnetserver NAS 4600 model 720, and said in part "Configuration ... is about as simple as humanly possible. There is, however, one minor annoyance for a system designed to be experienced as an applince: All of the management software is designed to run on Windows, and only Windows. ... we were able to run -- albeit not completely-- POPassist on SuSE Linux Desktop with the help of CrossOver Office. The only glitch comes in actually fiding the POPnetserver. That function would not work, which left us manually inputting the new address e discovered with LiSA and My Network Places." - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

1 0

Re: Add some exports to NtDll and AdvApi32
by Alexandre Julliard Oct. 30, 2003

Oct. 30, 2003

Robert Shearman <R.J.Shearman(a)warwick.ac.uk> writes: > Changelog: > - Add some stub exports to spec files for NtDll and AdvApi As a rule, for functions that only exist in later Windows versions, it's better to add them commented out, so that apps don't try to call the stubs. We should only add a real stub if an app links against it directly. -- Alexandre Julliard julliard(a)winehq.com

1 0

Useful article on x86 disassembly skills
by Mike Hearn Oct. 30, 2003

Oct. 30, 2003

After finding that COM article, I decided to dig my way through the backissues of MSJ to see what other gems I could uncover. Here's one useful one: http://www.microsoft.com/msj/0298/hood0298.aspx It is a basic introduction to x86 assembly from a reverse engineers point of view. Most of it is basic stuff you probably know already, however there are some useful bits there - for instance, it took me some time before I figured out that "xor eax, eax" was being used to clear the register because it led to smaller code size whereas this article tells you about that and similar tricks so it's easier to read optimized code. It also gives you some useful constructs that access the TEB, for instance now I know that these fs:[00000000] things are setting up new SEH frames. A worthwhile read for times when disas is the only way forward.... thanks -mike

1 0

Re: getting started with Winelib
by Ralf Juengling Oct. 30, 2003

Oct. 30, 2003

Okay, I got it to compile by manipulating the Makefile.in (kicking some *.rc files). But the executable segfaults: [juenglin(a)alpspitze winemine]$ make sed -e 's,@bindir\@,/usr/local/bin,g' -e 's,@winelibdir\@,.,g' ./wineapploader.in >wineapploader || rm -f wineapploader LD_LIBRARY_PATH="/local/lib:$LD_LIBRARY_PATH" /local/bin/wrc -I. -I/local/include/wine/windows -o rsrc.res rsrc.rc gcc -c -I. -I/local/include/wine/windows -g -O2 -fPIC -D_REENTRANT -o dialog.o dialog.c gcc -c -I. -I/local/include/wine/windows -g -O2 -fPIC -D_REENTRANT -o main.o main.c gcc -c -I. -I/local/include/wine/windows -g -O2 -fPIC -D_REENTRANT -o winemine.exe.dbg.o winemine.exe.dbg.c LD_LIBRARY_PATH="/local/lib:$LD_LIBRARY_PATH" /local/bin/winebuild -fPIC -o winemine.exe.spec.c --exe winemine.exe -mgui rsrc.res dialog.o main.o winemine.exe.dbg.o -L/local/lib/wine -L/local/lib/wine -ladvapi32 -lcomdlg32 -lgdi32 -lkernel32 -lodbc32 -lole32 -loleaut32 -lshell32 -luser32 -lwinspool gcc -c -I. -I/local/include/wine/windows -g -O2 -fPIC -D_REENTRANT -o winemine.exe.spec.o winemine.exe.spec.c gcc -shared -Wl,-Bsymbolic -o winemine.exe.so dialog.o main.o winemine.exe.dbg.o winemine.exe.spec.o -L/local/lib -lwine -lwine_unicode -lwine_uuid -lm test -f winemine || install wineapploader winemine [juenglin(a)alpspitze winemine]$ winemine Segmentation fault Might this be a configuration problem, or is something broken in Winelib? Since I have no root account, I had to skip the invocation of /sbin/ldconfig when installing wine-20031016. So I set LD_LIBRARY_PATH to /local/lib:/local/lib/wine. Any help appreciated, Ralf On Mon, 2003-10-27 at 18:23, Ralf Juengling wrote: > On Mon, 2003-10-27 at 13:09, Alexandre Julliard wrote: > > Ralf Juengling <juenglin(a)cse.ogi.edu> writes: > > > > > So there is nothing I can do about it at the moment? > > > What is the most recent Wine version in which winemaker used to work? > > > > The previous release should work. Or try this patch: > > > > Index: tools/winemaker > > =================================================================== > > RCS file: /opt/cvs-commit/wine/tools/winemaker,v > > retrieving revision 1.65 > > diff -u -p -r1.65 winemaker > > --- tools/winemaker 5 Aug 2003 18:31:32 -0000 1.65 > > +++ tools/winemaker 27 Oct 2003 21:07:38 -0000 > > @@ -2769,14 +2769,10 @@ then > > WINE_DLL_ROOT="/lib:/lib/wine:/usr/lib:/usr/lib/wine:/usr/local/lib:/usr/local/lib/wine" > > fi > > fi > > -AC_PATH_FILE(WINE_DLL_ROOT,[libntdll.dll.so],[ > > - AC_MSG_ERROR([Could not find the Wine dlls (libntdll.dll.so)]) > > +AC_PATH_FILE(WINE_DLL_ROOT,[libntdll.def],[ > > + AC_MSG_ERROR([Could not find the Wine dlls (libntdll.def)]) > > ],[$WINE_DLL_ROOT]) > > - > > -AC_PATH_LIBRARY(WINE_DLL_ROOT,[-lntdll.dll],[$WINE_LIBRARY_PATH -lwine -lwine_unicode],[ > > - AC_MSG_ERROR([Could not link with the Wine dlls (libntdll.dll.so)]) > > -],[$WINE_DLL_ROOT]) > > -WINE_DLL_PATH="-L$WINE_DLL_ROOT/wine" > > +WINE_DLL_PATH="-L$WINE_DLL_ROOT" > > > > if test -z "$WINE_TOOL_PATH" > > then > > Thanks, together with the patch > > --- /local/downloads/wine-20031016/tools/winemaker 2003-10-27 > 18:02:41.000000000 -0800 > +++ /local/bin/winemaker 2003-10-27 18:14:22.000000000 -0800 > @@ -2635,7 +2635,7 @@ > WINE_UNICODE_ROOT="$WINE_ROOT:$WINE_ROOT/lib:$WINE_ROOT/unicode" > WINE_UUID_ROOT="$WINE_ROOT:$WINE_ROOT/lib:$WINE_ROOT/ole" > > WINE_TOOL_PATH="$WINE_ROOT:$WINE_ROOT/bin:$WINE_ROOT/tools/wrc:$WINE_ROOT/tools/winebuild" > - WINE_DLL_ROOT="$WINE_ROOT/dlls:$WINE_ROOT/lib" > + WINE_DLL_ROOT="$WINE_ROOT/dlls:$WINE_ROOT/lib:$WINE_ROOT/lib/wine" > fi > > AC_ARG_WITH(wine-includes, > > > the generated configure script does its job without errors. > Now I the following error from make: > > [juenglin(a)alpspitze winemine]$ make > sed -e 's,@bindir\@,/usr/local/bin,g' -e 's,@winelibdir\@,.,g' > ./wineapploader.in >wineapploader || rm -f wineapploader > LD_LIBRARY_PATH="/local/lib:$LD_LIBRARY_PATH" /local/bin/wrc -I. > -I/local/include/wine/windows -o En.res En.rc > En.rc:23:22: Error: parse error > make: *** [En.res] Error 1 > > > > -- Ralf Juengling <juenglin(a)cse.ogi.edu>

1 0

compiling winemine resources
by Ralf Juengling Oct. 30, 2003

Oct. 30, 2003

I was not successful with compiling the winemine application in wine-20031016. When the resource compiler is to compile one of the language dependent files, it issues a 'parse error': [juenglin(a)alpspitze winemine]$ wrc En.rc En.rc:23:22: Error: parse error Line 23 in En.rc reads LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US So it looks like wrc does not know what to do with the constant LANG_ENGLISH. Is this a bug? Any idea whats going wrong here? Ralf -- Ralf Juengling <juenglin(a)cse.ogi.edu>

2 2

Where do old rpms go
by Bill Medland Oct. 30, 2003

Oct. 30, 2003

I apologise for not concentrating; I'm sure that someone has already answered this but I can't find the answer. Do the rpms at SourceForge expire? (I see that the 20030618 for RedHat are no longer there) I just want to know since if that is the case I will have to start taking copies. On the same subject, does anyone have a consistant SuSE 8.1 rpm of the 20030618 version? (That's the last version that worked well for our InstallShield and I don't have time to try to figure out what broke) -- Bill Medland mailto:billmedland(a)mercuryspeed.com http://webhome.idirect.com/~kbmed

3 3

Re: Another symbol font fix
by Huw D M Davies Oct. 30, 2003

Oct. 30, 2003

On Wed, Oct 29, 2003 at 08:23:16PM +0100, Rein Klazes wrote: > Hi, > > There are a couple of non-MS TT fonts on my system that only display > rectangles in win98's charmap.exe. Wine recognize these to have a SYMBOL > character set but Windows (win2k) does not. So libfreetype returning a > character mapping ft_encoding_symbol is not enough, I propose testing > the 0xf000 character offset that is assumed in other parts of the code. > > Tested to work for libfreetype 2.0.9 and 2.1.5 This sounds strange. Is there any chance that you could send me the font? Failing that could you send me the output of ftdump? Huw. -- Huw Davies huw(a)codeweavers.com

2 1

Re: winetests: new addition
by Ferenc Wagner Oct. 29, 2003

Oct. 29, 2003

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > I'm still not sure how to support building with PE .exes Could you outline the problems you can see? Since it is still not in the tree, instead of patches I send comments and questions. > +#include <shellapi.h> > +#include <shellapi.h> Do we really need it twice? > + while (1) > + { > + va_start(ap, fmt); > + n = vsnprintf (p, size, fmt, ap); > + va_end(ap); > + if (n > -1 && n < size) return p; > + size = min( size*2, n+1 ); > + if(!(p = realloc (p, size))) fatal("Out of memory."); > + } MSDN has no vnsprintf() only _vsnprintf(), what is this? The size=min(...) does not make sense for me either. va_start and va_end could be moved out of the loop by using break instead of return. > +int print_version(FILE *fout) > +{ > + OSVERSIONINFOEX ver; > + > + ver.dwOSVersionInfoSize = sizeof(OSVERSIONINFOEX); > + if (!GetVersionEx ((OSVERSIONINFO *) &ver)) > + { > + ver.dwOSVersionInfoSize = sizeof(OSVERSIONINFO); > + if (!GetVersionEx ((OSVERSIONINFO *) &ver)) > + return 0; This should be made a fatal(), I think. > + } > + fprintf(fout, " dwMajorVersion=%ld\n dwMajorVersion=%ld\n" The second is dwMinorVersion. > +void deletePath( char *path ) > +{ > + SHFILEOPSTRUCT fileop; > + > + path[strlen( path ) + 1] = '\0'; We do not have space allocated for this NUL. Here we use the advanced Shell API but later not the Win32 API for opening files and such. What is our policy? > +int count_tests() This is superfluous, not used for anything particularly useful. The progress bar still did not make it... > + if((fout = fopen(test->exename, "wb"))) > + { > + fwrite(code, size, 1, fout); > + fclose(fout); > + } No error checking whatsoever... > + char line[512], *cmd; Fixed size buffers are wrong... > + if ((fp = popen( cmd, "r" ))) > + { > + while (fgets( line, sizeof(line), fp )) > + fprintf( logfp, "%s", line ); > + fclose( fp ); > + } Why not a CreateProcess with redirected stderr/stdout? > + if (!(fp = fopen( logfile, "w" ))) fatal("Could not open log file."); Why not append mode? That would also make the above redirection more secure. > + for(test = wine_tests; test->name; test++) The number of tests could be determined by sizeof instead of a special member, but I am not sure that would be worth it. > +BINDIR="../.." [...] > +for test in $TEST_EXES; do > + testname=`basename $test .exe` > + filename="$BINDIR/$test.so" I am probably too tired, but can not see how you find the test .so-s in the dlls directory... So I am back, and ready to go for finishing this project... Feri.

4 10