Quake One (all clients) on Windows 7

[legion]

I recently installed windows 7 from vista and every quake client crashes.

[Baker]

Even software render clients like wqpro or WinQuake?

A better question might be: what clients have you tried?

If, for instance, glpro and Qrack don't work for you maybe DirectQ would work.

If none of them work, do any 3D games work on your machine?

[lennox]

I recently installed windows 7 from vista and every quake client crashes.

Set compatibilty mode to xp sp3 and they should all work

does for me atleast.

[foq]

Interesting problem on my end—GLProquake 4 randomly stutters/fps drops. As most of you should know by now I have a hellacious computer so it's definately not hardware lag. I did put Windows 7 on my computer though, but I don't see what that would have to do with anything.

[legion]

d3dpro399, d3dpro400, glquake, and glqrack all crash with the "APPCRASH" error.
By uberspaz glpro399 and glpro400 are functional but choppy. I installed the latest drivers for my video card (geforce 9800 gtx+), tried running as administrator with all compatibilities (win95-vista sp2). Ran as a batch file with different resolutions. GLQRack and GLQuake crash immediately while the d3d builds will work until i start running around before they crash. so weird...

[MH]

DirectQ works on Windows 7 without needing any compatibility hacks or likewise. I should know, it's the OS I develop it on.

You'll probably need to update your DirectX though -see here for info on why.

A recompilation of WinQuake or GLQuake using VC++ 2008 (Express or full) should also work fine (I've gotten both to work); the primary cause of the crash seems to be outdated headers and libs from VC++ 6, which most people still use. I'd expect the same applies to any other engine that crashes (I've also seen crashes with both FitzQuake and Enhanced GLQuake, and in both cases a simple recompile with the more up to date headers and libs has fixed them).

[Baker]

Ran as a batch file with different resolutions. GLQRack and GLQuake crash immediately while the d3d builds will work until i start running around before they crash. so weird...

A recompilation of WinQuake or GLQuake using VC++ 2008 (Express or full) should also work fine (I've gotten both to work); the primary cause of the crash seems to be outdated headers and libs from VC++ 6, which most people still use. I'd expect the same applies to any other engine that crashes (I've also seen crashes with both FitzQuake and Enhanced GLQuake, and in both cases a simple recompile with the more up to date headers and libs has fixed them).

Grrrrr ....

Hey Legion, try DirectQ and if it runs I'll compile ProQuake with VC 2008 for you to see if it does solve your problem.

Thanks for the info.

[MH]

Grrrrr ....

Hey Legion, try DirectQ and if it runs I'll compile ProQuake with VC 2008 for you to see if it does solve your problem.

Thanks for the info.

Alternatively it might be the compiler, but it's definitely the case that a recompile has worked.

To be honest I'm amazed that those old headers and libs have lasted so long. They do go back as far as 1998, and with all the advances in versions of Windows that have come since the fact that they can still produce mostly valid code, at least up until recently, is a minor miracle.

You may want to do a #define of WINVER to something suitably low before any #includes, by the way, just to make certain that no code paths that are invalid on older OSs are used.

[legion]

DirectQ works fine. I just don't like how it looks. Proquake 400 seems to be working fine now since I installed the latest directx, turned off vsync, and selected the highest refresh rate available for my monitor (75 hz) as well as my monitors native resoltion (1440x900). However, my fps will drop and I will still get the "appcrash" error whenever I try to increase "pq_maxfps" above the default (72). God I hate typing on iPods. This took forever..

[MH]

From another thread:

Here's my recompile of FitzQuake 0.85 for Windows 7. The only code change I made was to remove the splash screen, as Visual C++ 2008 Express doesn't like it. This runs smoothly on my machine with no hitching or stalling or frame drops. No compatibility settings needed.

Unfortunately I'm unable to compile ProQuake from the released source (guess I'm missing some dependencies) or I'd post that too. I've been meaning to do a qRack test also, but just haven't gotten round to it yet.

[R00k]

Fortunately, I have gotten Qrack recompiled in MSVC 2008 express and runs perfectly in Windows 7 without compatibility settings AND not having to recompile any of the external libraries!
I went the long way around trying to find updated .libs only to run into more walls than hurdles.
So, i back tracked through the project properties and changed a few things and it works!

Now I'll have to fix a few stray features, maybe get x64 supported and clean up the source files for a final release.

I'm still curious about FitzQuake protocol support btw...

[lxndr]

I share your joy R00k ! I've just get quore running on x64 and there's a smile of satisfaction that sticks on my face There was a pretty damn strange buffer overflow thing that was segfaulting in PF_VarString(), had to replace

pr_string_temp - pr_strings

in pr_cmds.c by a call to a function found in ezQuake. Now it works !

[MH]

Fortunately, I have gotten Qrack recompiled in MSVC 2008 express and runs perfectly in Windows 7 without compatibility settings AND not having to recompile any of the external libraries!
I went the long way around trying to find updated .libs only to run into more walls than hurdles.
So, i back tracked through the project properties and changed a few things and it works!

Now I'll have to fix a few stray features, maybe get x64 supported and clean up the source files for a final release.

Nice one. I'd be interested if you go down the x64 route; I've made one aborted attempt so far, but right now my priorities are elsewhere, like getting the damn thing to a state where I can release it.

I'm still curious about FitzQuake protocol support btw...

Just finished it.

Easy enough to do, although the 5 other protocols I also support made it a little bit stickier on the server-side than it needed to have been. Testing on an ID1 run first, then gonna do some RemakeQuake, then some WarpSpasm, then a true network test.

[MH]

I share your joy R00k ! I've just get quore running on x64 and there's a smile of satisfaction that sticks on my face There was a pretty damn strange buffer overflow thing that was segfaulting in PF_VarString(), had to replace

pr_string_temp - pr_strings code

in pr_cmds.c by a call to a function found in ezQuake. Now it works !

PF_VarString rings a few bells with me too. Also had a weird buffer overflow/segfault as a result of Microsofts new multithreaded CRT, and had to do a workaround. Something like this worked for me:

char *PF_VarString (int first)
{
	int i;
	static char out[4096];
	int len = 0;

	out[0] = 0;

	for (i = first; i < pr_argc; i++)
	{
		char *append = G_STRING ((OFS_PARM0 + i * 3));

		// prevent buffer overflow in this function
		len += strlen (append);

		if (len > 4090) break;

		strcat (out, append);
	}

	return out;
}

[lxndr]

the strlen segfaults on linux

Apparently it happens when there's several calls to the sprint function within QC.