search for: size_low

Displaying 4 results from an estimated 4 matches for "size_low".

Did you mean: size_log
2007 Oct 09
1
problem mapping large files?
...s like a problem in Wine. I reran it with +server,+relay which included the following in the output: 0009:Call KERNEL32.CreateFileMappingW(00000050,00000000,00000002,00000000,8fcbf02e,00000000) ret=01028a7b 0009: create_mapping( access=000f0005, attributes=000000c0, rootdir=(nil), size_high=0, size_low=-1882460114, protect=65, file_handle=0x50, name=L"" ) 0009: create_mapping() = INVALID_PARAMETER { handle=(nil) } 0009:Ret KERNEL32.CreateFileMappingW() retval=00000000 ret=01028a7b 0009:Call KERNEL32.SetLastError(00000000) ret=01019bf6 0009:Ret KERNEL32.SetLastError() retval=00000000...
2001 Oct 23
1
wine-20011004 Problems
I'm having major problems with the 10/4 Wine release. Currently the only thing I really use Wine for is Eudora Light 3.0.5. The most stable release for me thus far has been wine-20010112, which is what I'm using right now. Most of the releases since then have had window problems with Eudora-- messages having too much blank space, strange things. So I tried 1004, and it has a new
2001 Nov 03
3
Programs under wine can't connect to the network
Hey all Have a very strange problem in slack 8, using wine 20011004. First noticed this with counterstrike, than checked with other programs that should access the net. I get this error, and programs fail: fixme:winsock:_get_sock_fd handle 304 is not a socket (GLE 6) Documentation seems to imply that if I can get on the net with linux, I should be able to use wine with it. Weirdest part is
2001 Dec 06
2
Problem report: SHRINKER.ERR, fix to DEVICE_Open/CreateFileA?
This was an error I got when running a self-installing executable, power-structure-demo.exe, available from www.write-brain.com (a demo for Power Structure). A error box appears with title SHRINKER.ERR and message: (path)\power-structure-demo.exe (3.4) (time&date) - Pager initialisation error 2 - File not found and then the program quits. Running with --debugmsg