[SOLVED] vista & truecrypt

[smrtak]

Hi,
i play long time tremulous on Vista 32bit with 'no problem', but now i transfer whole disc to true crypt encryption. All work fine but tremulous not start (application error), console output is normal.

i try new GF driver, but no effect, any ideas?

thx

[smrtak]

i try build debug version in VS and i found problem in
file: vm_x86.c
function: int   VM_CallCompiled( vm_t *vm, int *args )
line 1178:      mov      programStack, esi


maybe call problem with encrypted files?

[gimhael]

Is there a compiler error or a runtime error ?

The VM_CallCompiled function is called when the client wants to run a piece of code in one of the JIT-ed QVM files, so it might trigger some Antivirus stuff, but it's not using any files at all.

[smrtak]

Is there a compiler error or a runtime error ?

The VM_CallCompiled function is called when the client wants to run a piece of code in one of the JIT-ed QVM files, so it might trigger some Antivirus stuff, but it's not using any files at all.

runtime error,
i find now this compiled version work fine:
http://releases.mercenariesguild.net/client/.

[kevlarman]

Is there a compiler error or a runtime error ?

The VM_CallCompiled function is called when the client wants to run a piece of code in one of the JIT-ed QVM files, so it might trigger some Antivirus stuff, but it's not using any files at all.

runtime error,
i find now this compiled version work fine:
http://releases.mercenariesguild.net/client/.

tremulous 1.1 will set off DEP, need to either disable it for tremulous or (as you did) get a new client that properly marks the memory with the compiled qvm executable after it compiles it.

[smrtak]

tremulous 1.1 will set off DEP, need to either disable it for tremulous or (as you did) get a new client that properly marks the memory with the compiled qvm executable after it compiles it.

ah thx for info, i dont know what is DEP, i recovery MBR (removing GRUB) then DEP turn always on. Now is all ok.

[gimhael]

Its the Data Execution Prevention, this is an Antivirus/trojan feature of Windows. I have no idea how your MBR or your encrypted parition can influence this except if you boot into a different Windows installation.