search for: ra2

RA2:YR is a 2D game - I think it probably uses DirectDraw. It runs slower with 0.9.16 and now the in game cursor flickers. Besides minor audio problems it ran fine in 0.9.15. I tried setting HKEY_CURRENT_USER\Software\Wine\Direct3D\DirectDrawRenderer to "gdi". It made no difference. Is that...

...lled and I'm not normally in a mood to recompile my kernel, and the Windows users that I want to play against do want to install IPX, I downloaded a patched wsock32.dll from http://www.understorm.net/ . According to the site, it lets the games multiplayer run over UDP. Without the patched DLL, RA2 does not enter the LAN screen, while with the patch it actually enters it. I cannot see games though. Now the question: When setting the override for wsock32 in WineCfg, Wine warns that Bad Things(TM) may happen. What happens if I override wsock32? Is it where Wine interface with the native networ...

nicolo.p wrote: > Thanks to Gert van den Berg, I found out using WINEDEBUG=+loaddll that the overwriting rule for native has to be put not for Ra2.exe (which I play with), but for game.exe; in this way I get > > Code: > trace:loaddll:load_native_dll Loaded L"C:\\Westwood\\RA2\\WSOCK32.dll" at 0x10000000: native > > instead of > > Code: > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\...

I've just tried to launch RA2 using wine, with great success: it ran perfectly and fast at the first try. However, the mouse is screwing around. If I run as root, everything works fine, but the mouse pointer is invisible. I can move it around and control the game blindly, but that isn't really fun. If I run as a user, the m...

...help in playing LAN games with Red alert 2. some data: I'm using wine 1.2.1 on Ubuntu 10.04, with kernel 2.6.32-27-generic the game is Red alert 2, with patch 1.006. What I would like to do is playing LAN games, using the UDP patch given at understorm at http://www.understorm.net/downloads/ts_ra2_lanpatch_1_00.zip What I made is copy the wsock32.dll file in the same directory where the Ra2.exe file is (the name of the executable file I play with), but it doesn't seem to work (it should, since I know for sure the patch runs on Windows, and I've heard about other people, in other post...

...@@ __cast6_enc_blk8: movq %rdi, CTX; - vmovdqa .Lbswap_mask, RKM; - vmovd .Lfirst_mask, R1ST; - vmovd .L32_mask, R32; + vmovdqa .Lbswap_mask(%rip), RKM; + vmovd .Lfirst_mask(%rip), R1ST; + vmovd .L32_mask(%rip), R32; inpack_blocks(RA1, RB1, RC1, RD1, RTMP, RX, RKRF, RKM); inpack_blocks(RA2, RB2, RC2, RD2, RTMP, RX, RKRF, RKM); @@ -301,7 +305,7 @@ __cast6_enc_blk8: popq %rbx; popq %r15; - vmovdqa .Lbswap_mask, RKM; + vmovdqa .Lbswap_mask(%rip), RKM; outunpack_blocks(RA1, RB1, RC1, RD1, RTMP, RX, RKRF, RKM); outunpack_blocks(RA2, RB2, RC2, RD2, RTMP, RX, RKRF, RKM); @@ -323...

Changes: - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce

Changes: - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce

These patches make the changes necessary to build the kernel as Position Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below the top 2G of the virtual address space. It allows to optionally extend the KASLR randomization range from 1G to 3G. Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler changes, PIE support and KASLR in general. Thanks to

These patches make the changes necessary to build the kernel as Position Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below the top 2G of the virtual address space. It allows to optionally extend the KASLR randomization range from 1G to 3G. Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler changes, PIE support and KASLR in general. Thanks to

Changes: - patch v3: - Update on message to describe longer term PIE goal. - Minor change on ftrace if condition. - Changed code using xchgq. - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace

Changes: - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce dynamic relocation space on mapped memory. It also simplifies the relocation process. - Move the start the module section next to the kernel. Remove the need for -mcmodel=large on modules. Extends

Changes: - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce dynamic relocation space on mapped memory. It also simplifies the relocation process. - Move the start the module section next to the kernel. Remove the need for -mcmodel=large on modules. Extends

...hIX}X{g(aGwlm`_P}()xTahQ*ZRyu20xG)!9oJp`2N{=7$$qN3 zV4hx&*RSo?1K_L|8KNDHWL!rOg{2$*P_^r(FM4 at ta#mO at f(k4ETR*W`AsOk~bmiH5 z$IP|^3Z*+}ykqe{+&J};rlFJ?XXZ7vlV;KBxMDM<-b$K=s_^K9EZr=NuXX;<b6x~g zrpE%dSPM^*VfPuaR_lu=r3Q at CuD-(1J%+7&o*Ja7+_>zVblWRl76X9svPHYila0`Q zi%)=oy=0P4Cmq17|JRa2*8&ecCx_R{sP0C#nfb__G at M<RnMy2AMv^4Zw?s0TM^%b9 z$;N)sF&G(6+1`QZD*_pzZaCwkz_5AQFe4^86ERlK-a9M+(T{<+s<ED-BQLd^Tb_8; z8ee8zUKzZbZev+C<5;^m>D6{8?@5Slz|wm)yQFhVE+P<p<o{PT=Zg!?LH(Oba=SL` zkdIr%PEMJ$+|inpBm;rfxUm(}oM1gf*<}twR*)nr1TZ?70_%7CM%Keb+j9mP%dga( z6IE1ZUYdyNeL93~w#...