Athlon X2 and Lineage 2

[compnurd9]

Has anyone had complete success getting there X2 to work with L2. I have tried run first and setting the affinity but both crash the game with a blue screen. This is heartbreaking because i play this game all the time and need to fix this

 

[compnurd9]

wow i cant believe no one so far i am starting to regret this CPU purchase

 

[rise]

sorry i don't play the game but have you installed the x2 drivers?

 

[compnurd9]

oh yea been through all of that.

 

[rise]

i figured as much when you said you set affinity but thought i'd make sure

thats really odd, i've had no problem with anything but serious sam2 demo which is fixed by setting affinity.

 

[compnurd9]

yeh it is actually it is the only game left that i can not get to work

 

[Ronin]

Use the flag /usepmtimer in the boot.ini. That should fix the problem.

 

[compnurd9]

that flag is already there as it was added by the amd drivers

 

[Ronin]

Eh? Show me your boot.ini, please.

 

[LifeStealer]

Are you using 32bit or 64bit xp?

 

[compnurd9]

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /usepmtimer


32 bit if someone maybe could

the error occurs after i click start from the first screen but before the log in screen. i get a negative delta timer. you can download the game for free

http://www.lineage2.com/pds/game_dw.html

maybe someone with a X2 can try it as well but there is a thread going on the l2 forums with this issue and no resoulution yet

 

[compnurd9]

what is everyones new x2 driver date mine is 10/24/04

 

[compnurd9]

i may have to sell this chip and either get a single core or a intel dual core if i cant fix this

 

[McGeyser]

This game is that great, that you would have every other game work but this L2 game, and that makes want to get rid of the processor?? I'll try this demo later, but are you sure it is the CPU and not the games problem? You don't think the makers of L2 will fix this, that they hate X2 and will never allow their game to play on it? Did you write to them and ask their support team?

 

[compnurd9]

yes i wrote to them and they are trying to fix the issue but they believe it is something with the way the dual core balances its load(which i have seen is a issue with this chip regardless) this is the only game i play right now and it is not worth the cpu if i cant play it.

 

[McGeyser]

The load balance is a function of your OS, maybe you should ask M$ why load balancing is causing errors in this one and only game that has this problem. I will d/l and run this game tonight and post back.

 

[compnurd9]

if you really wanna laugh i removed the pmtimer line from the boot loader and went back to the windows cpu drivers and so far it is working. i will keep messing and see how it goes

 

[compnurd9]

Also i would ask MS but the Intel Dual Core does not have this problem so it is AMD related

 

[evilharp]

Originally posted by: compnurd9
Also i would ask MS but the Intel Dual Core does not have this problem so it is AMD related

Uh, no. Intel doesn't have this problem because their driver support is better (at the moment) and they went through all this crap with Hyperthreading already (example: http://support.microsoft.com/?id=835730 note the /pmtimer flag as well). Programs since Hyperthreading are written to use it or disable it (i.e. run on 1 processor) when Intel processors are used.

Try using Rope/WinXPLauncher/Runfirst or other affinity programs first. These programs resolve most (if not all) issues with games.

Search the forum for fixes, as this "X2 problem" has been discussed like mad lately.

 

[Ronin]

Uh, no, Intel doesn't have this problem because they don't scare cache between CPUs, where AMD does (although you'll find that nowhere in the documentation).

Thanks for providing misinformation, though.

 

[thescreensavers]

Originally posted by: compnurd9
what is everyones new x2 driver date mine is 10/24/04

mine is 10/26/04

 

[Markfw]

Originally posted by: evilharp

Originally posted by: compnurd9
Also i would ask MS but the Intel Dual Core does not have this problem so it is AMD related

Uh, no. Intel doesn't have this problem because their driver support is better (at the moment) and they went through all this crap with Hyperthreading already (example: http://support.microsoft.com/?id=835730 note the /pmtimer flag as well). Programs since Hyperthreading are written to use it or disable it (i.e. run on 1 processor) when Intel processors are used.

Try using Rope/WinXPLauncher/Runfirst or other affinity programs first. These programs resolve most (if not all) issues with games.

Search the forum for fixes, as this "X2 problem" has been discussed like mad lately.

Did you read his reply ? The X2 drivers FIXED the problem ! He didn't even need that pmtimer flag, in fact it messed it up !

 

[Furen]

Arg... lineage... so very time consuming. That's why I ended up quitting it (I just couldnt handle the grind after Lvl67 in C3... hell even before that). Gameguard is horrible, too...

 

[evilharp]

Originally posted by: Ronin
Uh, no, Intel doesn't have this problem because they don't scare cache between CPUs, where AMD does (although you'll find that nowhere in the documentation).

Thanks for providing misinformation, though.

Really? Well your post is the first I have read that implies that a "shared" cache is the root cause of issues with games. Can you refer me to a site that explains this in detail, I am curious to learn more.

As for "misinformation", I am afraid that I don't totally follow your meaning. Intel did have a problem with Hyperthreading, and does have better driver support courtesy of a larger install base and "Intel" compilers being the norm. Working as a Systems Analyst, I had nothing but trouble with certain in-house applications when HT systems first arrived. We used /pmtimer to resolve these problems until new drivers arrived.

Originally posted by: Markfw900
Did you read his reply ? The X2 drivers FIXED the problem ! He didn't even need that pmtimer flag, in fact it messed it up !

Yes, I read his reply. However, the /pmtimer flag has resolved numerous problems for other games, so I wouldn't say that the "problem is fixed". Considering that the X2 drivers add the /pmtimer flag to the boot.ini, the drivers didn't completely fix the problem either. Also, if you read my post you'll notice I try to explain why Intel DC chips are not having these problems. Ronin was kind enough to add some more information that I was unaware of.

All I tried to do was add some input, and suggest some fixes that have worked for other X2 owners (including myself).

 

[Ronin]

Originally posted by: evilharp

Originally posted by: Ronin
Uh, no, Intel doesn't have this problem because they don't scare cache between CPUs, where AMD does (although you'll find that nowhere in the documentation).

Thanks for providing misinformation, though.

Really? Well your post is the first I have read that implies that a "shared" cache is the root cause of issues with games. Can you refer me to a site that explains this in detail, I am curious to learn more.

As for "misinformation", I am afraid that I don't totally follow your meaning. Intel did have a problem with Hyperthreading, and does have better driver support courtesy of a larger install base and "Intel" compilers being the norm. Working as a Systems Analyst, I had nothing but trouble with certain in-house applications when HT systems first arrived. We used /pmtimer to resolve these problems until new drivers arrived.

Originally posted by: Markfw900
Did you read his reply ? The X2 drivers FIXED the problem ! He didn't even need that pmtimer flag, in fact it messed it up !

Yes, I read his reply. However, the /pmtimer flag has resolved numerous problems for other games, so I wouldn't say that the "problem is fixed". Considering that the X2 drivers add the /pmtimer flag to the boot.ini, the drivers didn't completely fix the problem either. Also, if you read my post you'll notice I try to explain why Intel DC chips are not having these problems. Ronin was kind enough to add some more information that I was unaware of.

All I tried to do was add some input, and suggest some fixes that have worked for other X2 owners (including myself).

This information is based on extensive internal research at my office, in an attempt to figure out what was causing the problem, so I'm afraid I can't provide you a link.