Yes I spoke too soon. It played great right off the bat. Just tried it a few hours later (haven't even rebooted) and it now plays with the Benny Hill efect (BennyHill show theme music in background)Andrmgic said:I had a fresh install with my dual core from day 1, and I at first did not have any issues.. however, eventually I got the "benny hill effect" in NFS:MW demo.. then I installed Microsoft's hotfix and the problems went away. I have been unable to try HL 2 or CS:S because I have to use dial-up to connect to Steam (only broadband in my room is wireless, and all of the ports Steam and all of my other games need are blocked).
fiewtoid said:Trying to get WoW to work properly with my dual-core rig. I've done Fix #2 and Fix #3 will not work since WoW doesn't let you change the affinity. According to the OP Fix #1 just causes more issues with WoW so I didn't even try it. Any ideas?
Leright said:*sigh* this thread makes me hesitant to go with dual cores. I want to just be able to install a game and go. Might as well get a really fast single core proc, since I don't multitask too much, it is cheaper, and games and drivers that EFFECTIVELY utilize dual cores won't be released for some time now (game developers are hesitant to develop multithreaded code because it is a huge pain in the ass...). It isn't an easy task to write multithreaded code.....Carmack himself despises it.
Advil said:I think we're at the tail end of major issues. The end of this year is as far as software developers are going to be able to go before they have to at least make software compatible, even if it doesn't actually use the other core. After the holidays there are going to be a trainload of dual core systems out there, and from what I've seen, there are plenty of people willing to early adopt this technology which makes it a done deal.
Leright said:I might just go with a single core opteron 150 (2.4 ghz) for now, and then in like 1.5 years, after developers demonstrate that they are willing to suffer through the multithreaded app development process for dual core systems, I will upgrade. But right now, the multithreaded video drivers a poor dual processor support in games is not worth the extra cost, and a fast signle core solution is likely the best bet RIGHT NOW....of course, if you're big on multitasking, then dual core rules, but I am either playing a game, writing a report, working on a spreadsheet, checking email, browsing the web, or watching a DVD. I never do all of these simultaneously. Occasionally I will listen to MP3s while I write a paper, or browse the web, but nothing that will bring my single core to its knees.
for now, I am relatively confident single core is for me. I have been weighing my options for a month now, and I just need to pick something and go with it. I think I will just settle with a single core solution.
kirbyrj's boot.ini said:[boot loader]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /bootlogo /usepmtimer
kinson said:dont know how to do that ... the noobie under my name is there for a reason...
and I removed the drivers... but it still didnt work <edit: ok for some reason it worked that time.. sigh... SOOO STUPID... >
kinson said:ok I did all this stuff, cnq is running, have the cpu driver updated, have new video drivers... while playing lineage 2 tho I get a negative delta time...
any suggestions ?
question... am I suppose to leave the /usepmtimer or remove it with the m$ hotfix ??
oh and when I updated the amd driver it says 126.96.36.199 not 188.8.131.52 did anyone else get this ??
and I'm kinda getting tired of posting on here... if there is someone that can help me and guide me through these things and discuss the problems I'm still facing I'd appreciate it... just let me know
I'm thinking if the affinity launcher program didn't work, maybe there's another problem with your computer .
kinson said:I dunno man... maybe I'm doing something wrong... I mean... just the drivers, or drivers and hotfix... is there some other drivers I should try...
I'll reset my computer, set the cnq and hotfix with the /usepm... I know the game will run fine at first, its a little while in maybe an hour or so that gives me the problem...
my computer has been running since I got the hotfix and drivers to install this morning... I did the xplauncher set the affinity to core 2 and it ran fine...
maybe this is something that you can enjoy doing research on, cause honestly I'm getting sick of it and <> that close to selling it
kinson said:at the present I'd really rather not... thats alot of work ... lol and a real real time consumer...
does it make sense to have the hotfix on and the /usepmtimer set and still have a problem to where you have to set the affinity ??
kinson said:I looked at it but I'm kinda loopy on the brain processing side right now...
but if thats the case then any game that is having the super speed problem, couldnt you just set it that way to run on one core all the time ??
YARDofSTUF said:Also, to set the affinity permanently you can use "imagecfg.exe"
Google it and you'll find it for download, this link should still have it too:
Pretty handy tool for me. I went and set the affinity of my games to the 2nd and anything else I use while gaming to the 1st core. My thinking behind this is that XP will probably use the 1st core more for its services, so put all the other stuff there and use the 2nd for gaming as it should be the only thing really using that core. And if you need to set the affinity for a fix, this way its a 1 time deal, and you dont need to load another program.
Imagecfg has a problem with some directories with spaces in them, so its easiest to stick it in the folder with the *.exe file you want to change. Then use the command you need:
imagecfg -a 0x1 game.exe for core 1
imagecfg -a 0x2 game.exe for core 2
If imagecfg.exe is not in the same folder as the *.exe you want to change then you need to add the full file path to the *.exe
kinson said:ahhhh yes I read that... ok so go over this with me so I dont f*#@ something up... not extremely sure on how to set it up...
lets just say my exe is on desktop or C:\Program Files\Lineage II\system\l2.exe .. again thanks for the help...