Quake2

[Stephen Howe]

System: Windows XP Professional with SP2 applied

I cannot get Quake 2 to work reliably on Windows XP.
The main problem is that every time I quit Quake 2 and go back in and try
and load a saved game, I get message "function pointers have moved".

This is with version 3.20 of Quake 2

A few points:

I have _NOT_ installed any of the mission packs
I have _NOT_ upgraded versions of Quake2 expecting saved games of earlier
version to load.

I am going to try reinstalling as I installed it before SP2 but I don't have
much hope that this will cure it. I am not using any XP "compatibility mode"
options.

Any suggestions to fixing this game so that saved positions are usable?

Thanks

Stephen Howe

 

[Stephen Howe]

System: Windows XP Professional with SP2 applied

I cannot get Quake 2 to work reliably on Windows XP.
The main problem is that every time I quit Quake 2 and go back in and try
and load a saved game, I get message "function pointers have moved".

Note also that this does not happen with Windows 2000,98,95 etc, just XP.

Stephen Howe

 

[Neil Dela Osa]

This thread mentions deleting the backup folder and config files for Quake
II or using an anti-cheat utility.

http://www.ntcompatible.com/thread22781-1.html


According to this thread it sounds like an application error. It mentions
recompiling code to use fixed base address pointers.

http://www.forumplanet.com/planetquake/topic.asp?fid=1491&tid=1320347&p=1


File planet mentions some launchers for the above problem. Check out the
"Load Level" Patches. I'm even finding source code samples.

http://www.fileplanet.com/section.aspx?s=33219&v=0

 

[Stephen Howe]

This thread mentions deleting the backup folder and config files for Quake

II or using an anti-cheat utility.

http://www.ntcompatible.com/thread22781-1.html

Nope, no good

According to this thread it sounds like an application error. It mentions
recompiling code to use fixed base address pointers.

http://www.forumplanet.com/planetquake/topic.asp?fid=1491&tid=1320347&p=1

But I am running the original game. I don't have the source to compile.

The right thing to do is rebase the DLLs so that the base address is
something relatively unique in address terms. Some high address in the user
range springs to mind.

But right now I have settled to editing gamex86.dll.

Changing the byte at offset skips the test ReadLevel test

baseq2\gamex86.dll: 11E3F 74->EB
xatrix\gamex86.dll: 1346A 74->EB
rogue\gamex86.dll: 1DABD 74->EB

And that solves it

Stephen Howe

 

[Neil Dela Osa]

Good job.

Nope, no good


But I am running the original game. I don't have the source to compile.

The right thing to do is rebase the DLLs so that the base address is
something relatively unique in address terms. Some high address in the
user
range springs to mind.

But right now I have settled to editing gamex86.dll.

Changing the byte at offset skips the test ReadLevel test

baseq2\gamex86.dll: 11E3F 74->EB
xatrix\gamex86.dll: 1346A 74->EB
rogue\gamex86.dll: 1DABD 74->EB

And that solves it

Stephen Howe