Dual Core Optimizer

[Prostock62]

Hi guys i went ahead and installed the dual optimizer.Now checking in windows to see if its active mine reads just a bit diffrent and wondering if this is ok.

Extrem fourms has it should read out like this

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)WINDOW S

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /usepmtimer

 

Ok mine reads like this /fastdetect/noexecute=optin/usepmtimer-

The fastdetect & noexecute/ is reversed,is this ok?

[aurora]

it should be ok

[Daddyjaxx]

I don't see why not. The noexecute has absolutely nothing to do with the optimizer. That has to do with DEP. These are just commands that are run. I doubt it matters which order they are kicked off.

[Prostock62]

Thanks Guys for your replys.

[ISSA2000]

Hi guys i went ahead and installed the dual optimizer.Now checking in windows to see if its active mine reads just a bit diffrent and wondering if this is ok.

Extrem fourms has it should read out like this

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)WINDOW S

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /usepmtimer

 

Ok mine reads like this /fastdetect/noexecute=optin/usepmtimer-

The fastdetect & noexecute/ is reversed,is this ok?

 

Apparetly a software call (programming call time stamp counter=TSC) on the x2 etc causes the cpu,s to go out of internal clock sink, causing many problems.

(see cpu clock utility for a clasic example [cpuclk.exe] causes the problem in 4+ hours of running- http://www.wg7.com/ idel )

 

This program sits in memory[ amd_dc_opt.exe] (tsr) (loads at startup), any software that makes the (programming) call is redirected to a new a better way (of doing ) the same thing.

 

(Who at fault ms or amd) dont know. but ms hot fix (did not remove the problem)), it just reduced it to about 70% better. after full testing (on another post) , i found that you only need the amd patch.

 

You can put the ms hotfix on (but it will make no difference once the amd tsr patch(amd optimizer) is on.

and yes (you only need the amd cpu drivers(cool&quiet) if you are going to use this feature (via bios)

 

 

---------------------------------------------------------------------------------------------------------------------------------------

[cool& quiet] = clock the cpu down (both cpu power and internal clock+bus mhz) when the cpu is being idel (in steps)

----------------------------------------------------------------------------------------------------------------------------------------

 

basically (under clocking)..

 

i hope this helps..

P.S. ALL USERS OF X2 (DUAL CORES) SHOULD USE THE AMD FIX IS A DEFAULT INSTALL.

(I dont think they can call it a fix for MS windows-due to legal reasons- they did it because microsoft did not fix the problem and its easily fixed with a TSR programm), and amd optimizer does not improve perfomance- but it does keep it stable after a few thousand TSC calls)

 

you can load balance programs (say usin 1 cpu only (ie cpuclk.exe on cpu 1) and after 4 hours of the computer being idel the problem does not occur.)

 

This was the fix before the amd patch came out , you run bf2 on cpu 0 and cpuclock on cpu 1, and the system was stable after 4+ hours

(8 month till i new what the problem was software and not hardware/clocking...) using xp luncher

 

JUST THINK OF IS AS A MUST HAVE SERVICE PACK FOR WINDOWS...

and yes. what you are talking about in boot.ini is for the ms hotfix (see ms hotfix for dual cores)+ DEP

 

AND 1 MORE THING (IF YOU ARE HAVING STABILITY PROBLEMS IN GAMES ETC AFTER A FEW HOURS- AND YOU HAVE A DUAL CORE (X2) ETC

RUN THE AMD OPTIMIZER PATCH, THEN TRY, if it still happening , it not the TSC software problem...

 

i would have to reboot the computer every 4 hours to make the computer stably (till i found the problem.)

if i did not run the cpuclk program it would only go unstable after play a game(bf2) after 4+ hours)

so at desk top idel was ok, till i ran ahttp://www.wg7.com/rogram that does TSC calls for a the duration.

[ISSA2000]

i wonder if the intel dual core chips have the same problem.....

 

so from release to the x2 chip (+ problem) and the amd fix 8+ months of pain..

 

PEOPLE IT DOES NOT PAY TO BE ON THE CUTTING EDGE.

 

by the time you got all (or most) of the bugs out its out dated. 939?

[bozotheclown]

My god, what terrible bull crap this is.

I've had next to no problems with having a cutting edge 939 x2 cpu all this time.

The few problems I had I only noticed because there were fixes released for problems I hadn't percieved as such.

[ISSA2000]

My god, what terrible bull crap this is.

I've had next to no problems with having a cutting edge 939 x2 cpu all this time.

The few problems I had I only noticed because there were fixes released for problems I hadn't percieved as such.

 

 

nice language.....

 

bull crap?

 

well i had cutting edge gear for over 20+ years , i i dont just sit it their and do nothing with it. i max it out, and use it fully.

(ie rip 6 movies at the same time at full speed to 6 hdd on one machine& burn at 16x as well), when you do this you come accross more problems than your average setup.

 

when you have enough years doing a lot of things you pick out the problems and find ways to fix them, i run the same setup and and usually just upgrade the cpu offen..

 

This i the first time iv had sutch a problem like this, usually you just get a error message when trying to ran a software call that a cpu does not support, and it usally crashed straight away. say going from a non mmx to a mmx and trying to run a old program etc..

 

i had a asus(via) with a 3200 939 chip (app same setup+software) no problems, i change chip to a 4800 (first release in australia) and got stability problems ( TSC problem) using (4+hours of bf2) and using the cpu clock program (that iv been using fore many years on many cpus).

 

I change board to a expert + pci express video card (everything else the same) and same problem. I found the problem+solution a few months before the amd fix, which is much better.

 

 

If you want to test the problem on your cpu just download the cpu clock and run it (idel for 4+ hours (5+) and see the problem visually onscreen with that program, the cpu clock will (should stay steady at it clock speed) (for me thats 2400), after a few hours the clock starts to go up+down rapidly (from 2200-to - 2700), then you know you have the problem.

 

When i ran the ms hotfix (it was better but not removed) it went 2300- to 2500) but it should not move from the default speed of 2400.(non clocked-no cool n quiet) default settings..

 

 

You may have the problem, but unless you run certain programs for more than 4+ hours you may not see the problem.!!!!!!!!!!!!!!!!

 

(2400 clock is a 4800 chip) and the problem does it on a strip basic setup +1 burner+1hdd etc- default settings/software etc...

 

P.S A LOT OF PEOPLE ONLY REPORT THE PROBLEM (THIS PROBLEM) when they play a certain game for more than a few hours.

 

i notice straight away even if i did nothing at desktop(idel) due the fact that the cpu clock diisplay program caused the same problem as the game, but gave a visual display of the problem after 4+ hours of not restarting windows...

 

you system could be perfect stably -but due to this problem, you would think it was not, and would keep testing the hardware, when it was a software problem..

 

maybe amd has/and or will fix the problem on a hardware level (newer revision) just like when cpus have been know to have a few bugs (ie maths errors on early pentium chips, amd 64 have 2 well known problems that the bios has fixes for..)

 

sorry english is my second lang.

[Kingfisher]

Either I am really dumb( that is most likely the case) or this thread is being written in another language than english because I have no clue what this is all about.

[ISSA2000]

it was about the ms hotfix for dual core cpu, but the thread is title says "Dual Core Optimizer " which is mostlikly the amd optimizer name not the ms hotfix