16-12-2003 02:09									#61
	Suffering from ads?

Well, it's a neat trick but it's not working for me

Very odd, but it looks like we're dealing with seperate problems...

	16-12-2003 02:13									#62
	Support Apolyton, buy Call to Power 2

quote: From the cpuinfo/cpuinf32.dll documentation: While this program works on all current Intel processors, the code is designed to not analyze processor speed if the processor is NOT an Intel processor.

What is the origin of that file can we get a file that does the job on a non intel processor properly?

-Martin

	16-12-2003 02:19									#63
	Enter the AD-FREE zone

I found something at
http://support.intel.co.jp/jp/suppo...uid/cpuinfo.htm .

At the "normal" Intel site, it is listed as not supported anymore. Maybe we should just comment out the processor speed function call, if this causes crashes at some machines. It doesn't seem to be used in the program, other than being reported in a log file or at the screen.

	16-12-2003 02:25									#64
	Remove this text

Seriously... I think this is unneccessary too.

The processor requirements are fast becoming moot, as most any machine is capable of running this, abeit slowly.

The only theroretical thing they could be looking for would be MMX capability for a software render. You can find that out in a DirectX call though, so...

Lets check it really is unused, and then turn it into a stub. Agreed?

	16-12-2003 02:28									#65
	Support Apolyton, buy Alpha Centauri

Anything that speeds up the game without side-effects (providing there are none) can't be bad...

	16-12-2003 02:28									#66
	Tired of ads?

BTW.. the regular intel site still distributes a CPUInfo package, but the dll is actually 2 years older, and unsurprisingly, doesn't work properly, either.

	16-12-2003 02:31									#67
	Inflate your Upload Space

I also have XP2000+ cpu and it reported 0MHz, and worked fine. I am on win98se by the way.

	16-12-2003 02:36									#68
	Lose 30 kilos (of popups)

Just checked it. It is never used, except for logging. I'll remove it.

	16-12-2003 20:26									#69
	Support Apolyton, buy Alpha Centauri

Well... this is almost comical. I changed the setting for where the debugger looks to operate and now the thing isn't building again... I'm sick of it.

I'm going to burn off all the data I have on here, then use Boot Magic to install a "clean", just for CTP2 and Visual Studio 6 on Win98SE partition, and a regular XP partition.

	29-12-2003 17:36									#70
	Support Apolyton, buy Civilization III: Complete

Unbelievable.

I just finished backing up and installing 98 and XP to different partitions, and setting up BootMagic, etc...

I just compiled CTP2_DBG.EXE and CTP2.EXE, using the latest code patches and the final version works just fine... and the ones I was compiling in XP never did... I'm at a loss what the issue was; everything else on the system worked perfectly... but getting it working was all that mattered.

	09-02-2004 04:34									#71
	Re: Getting really frustrated with crash Support Apolyton

quote: Originally posted by MrBaggins I did a fresh install of the code and game, and now it crashes at the point of starting a new game, just as the map is started to be displayed. I made a version with debug info, and the damn debugger crashes... :/

The crash when the map is created sounds familiar to me, occasionally the Activision's Patch 1.1 crashes on start up of a new game on my computer, the latest version didn't crashed so far. Maybe the problem are some of the memory leaks, we already fixed. So maybe you should try it again with the latest file pack.

-Martin

	09-02-2004 04:43									#72
	Tired of ads?

* MrBaggins smiles.

Well... everythings compiling and working perfectly on 98.

I may give XP a shot again for development work... but I don't need to rely on it, since it works just fine on the 98 dual boot.

	09-02-2004 04:47									#73
	Help yourself to an AD-FREE life

quote: Originally posted by MrBaggins I just compiled CTP2_DBG.EXE and CTP2.EXE, using the latest code patches and the final version works just fine... and the ones I was compiling in XP never did... I'm at a loss what the issue was; everything else on the system worked perfectly... but getting it working was all that mattered.

They don't call it eXtra Problems for nothing

	09-02-2004 21:51									#74
	Support Apolyton buy from Amazon

quote: Originally posted by MrBaggins * MrBaggins smiles. Well... everythings compiling and working perfectly on 98. I may give XP a shot again for development work... but I don't need to rely on it, since it works just fine on the 98 dual boot.

I would rather know, if it is possible to prduce now on XP a working version, because I think that you need win 98 is a seriuos factor that keeps away potiential coders.

-Martin

	10-02-2004 04:34									#75
	Seems to work just fine Support Apolyton

Seems to work just fine

Could be one of the later fixes did solve something that XP was having a problem with.

Why, however, the same files would have been producing bad code on XP but not on 98, I have NO idea.

	10-02-2004 05:15									#76
	Re: Seems to work just fine Support Apolyton or Terrorists Win

quote: Originally posted by MrBaggins Why, however, the same files would have been producing bad code on XP but not on 98, I have NO idea.

Considering the original version, I would say that this was not so good code either.

If you try to remove some of the assertions you can really search and search and won't find the sollution if you don't take a look on the memory leaks.

BTW: MrBaggens, which compiler do you use on WinXP?

-Martin

	10-02-2004 05:17									#77
	Inflate your Upload Space

Visual Studio 6 Enterprise (sp5) both times.

	12-02-2004 08:30									#78
	Remove this text

This is great news. I will be trying to compile on XP again this weekend.

Are there any steps different from the "how to compile" document when you are compiling on XP?

	12-02-2004 08:36									#79
	Support Apolyton or Terrorists Win

Nope, although I did have to force a full rebuild of ctpdb, prior to doing a full rebuild of ctp2_dbg, or I sometimes get errors in the custom compile steps, although nothing changes (tmp directory still there, etc.) The full rebuilds do solve that though.