Question on FSB, CPU ratio and VCore

Hi:
I have been reading several postings on overclocking CPU. As far I can tell, people recommended increasing the FSB freq. in the BIOS until it cannot boot any longer.
I have KT3 Ultra, Athlon XP 1800+, and DDR 333MHz.
?( How does changing the FSB freq. affects DDR freq? Is it 1:2 ratio? For example, if FSB = 133 MHz, then DDR is 266 MHz. If so, is FSB limited by DDR rated freq?
?( Does changing the FSB actually changes the clock signal feeds into the CPU?
?( Does changing the FSB only affect CPU? Does it affects the PCI bus?
?( What is CPU ratio? Is it an internal clock multiplier to the CPU?
?( How does CPU VCore affect the overclock?

http://www.msi.com.tw/program/service/forum/index.php?threadid=7501&boardid=13

Similar Messages

CPu ratio and frequency locked

Hey,
I have latest version of BIos and I can't adjust CPU frequency or ratio, there are no brackets around auto. I have Turned off OC genie, removed CMOS battery, loaded default BIOS, and all the same.
http://postimg.org/image/88o384muj/

Kt6v cpu ratio & sound problems

Hello everybody,
First of all, I apologize for my english,
I recently bought a Msi motherboard,a KT6v model (http://www.msicomputer.com/product/detail_spec/product_detail.asp?model=KT6V-LSR). My comptuer boot well, but I have two problems:
First, I can't modify the cpu ratio in the bios setting. If I do it, the four Leds of the control bracket are red and i have to do a clear CMOS (very difficult to reach the jumper :-/). It also do it if I choose the good cpu ratio and fsb (13*166)! I try with a 2400+ (15*133) and I have the same problem. These two processeurs have already been modified on an Asus a7nv8x-x(nforce2) and an Asrok Kt78xe+ (with jumper) motherboards, so I think they are not blocked. I also try to disable the "corecell" feature but it seems to be impossible in the bios. I just want to use the "high" ability of overclocking (in fact, only up the fsb and reduce the ratio) of my motherboard longly discribed in the user manual... I installed the latest via drivers.
All is working fine if the cpu ratio feature is "auto". And cpuz software says I have a 13*166 cpu ...
Second, the sound is not good. I can't use the 5.1 option (very bad rear sound and no subwoofer emulation). I try an Altec lansing 5.1 Kit and it's not working fine. I take care of the two jumpers and to install the latest drivers :-/ . It's a longtime I want to buy a sound card, perhaps it's time to do it. I'm fed up about the integrated sound cards, I want my sb Awe 64
I like Msi products and it's the first time I have problem with one of them. I hope there is a solution for the first problem, or perhaps I only misunderstood a feature?
I have another question please:
Can I switch off, during the boot of the computer, the menu for network boot option?
Thank you very much and I am sorry for my english.
MSi KT6v (latest bios)
AMD XP 3000+
ddr-sdram samsung 3200 1*512mo
Msi Rx9800 radeon 9800pro 128Mo
Enermax 300 Watt (tested with a 480watt power supply)
120 Go Western digital Pata
Msi 16x dvd-rom & Msi cdr/cdrw 52x-M
1.44Mo floppy drive
Windows 2000 rév.4

Hello all,
thanks you for your answers!
osnavi
+3,3V == 28A
+5V == 30A
+12V == 15A
-5V == 1A
-12V == 1A
+5Vsb == 2,2 A
I don't really want overclock my CPU, I want to change the fsb frequency from 166 to 200Mhz and modify the ratio from 13 to 10,5.
But I can't.
As I said before, I have already modify the cpu settings with 2 other motherboards, with the same Psu, the same cpu, and all the same components. So, I don't think the Psu is the problem, I hope these are good values because it's an expensive Enermax psu...
I will test for the sound, thank you !
Sharp
Legolas_524288
Fredrik Åsenius
I have done many tests with cpu's bios features but I have always my 'strange' problem
Thank you very much all for you answers !!

Pixel Aspect Ratio and ciphering type of footage-CS6

CS6- updated 12\18\13 V-11.03
Hi All,
A few questions about:
Pixel Aspect Ratio and ciphering type of footage. Bare with me as I touch on two different aspects of what I feel are related:
1. Setting up a Comp-
Having AE decide on the correct footage being used- Via >Import footage,.(to Folder) then drag it on, or into the 'make comp icon' where AE is supposed to do a 'best guess' for the comp settings. Be it square pix or otherwise. What are the second value in brackets ? See pic
2. Interpolation-
When using two diff footage sources- If using two different source footages in a comp. Is this where I should interplolate my footage to match the existing footage and the comp settings (If I have choosen NOT to pre-comp that secondary footage?)
3. Seperating fields-
How come footage that a camera manufacturer claims to be shooting in Progressive 30 or 24p is showing up as interlaced in my comp's CP? The manual to the cam says 30p or 24p or 60i The footage was shot at 30p (for sure)
Here is a screen grab of AE's 'best guess' of that footage, showing it with an UPPER field render; indicative of HD Interlaced footage and then in the inerpolate settings - 'kinda confirming it.
Now for the way out- Render:
4. If that is in fact Interlaced and I then want to reduce the size of that 1920 footage to 66% size... Do I need to do anything in particular at this point?
For some reason I am getting an error on my end when trying to export as an AVI and reducing size to 1280
5. Is this from the Field render of interlaced challenge?
I ended up with a couple of errors and then aborted the whole file and re-imported to start over with this error. Which happend again after a redoux
So I sent it over to Prem Pro to export those MTS Files as a movie and noted AGAIN the reference to Interlaced video. "upper and lower" Prem Pro was able to use the same MTS files and export a working movie. (so those files were not corrupt BTW) Yet Note PP's output reference to that footage again as Interlaced would be...
Thanks for any clarity on those "5" questions... NC

Thanks for the details Rick.
Thanks for the insight on #1
Ref #2, You should never change the interpretation of Pixel aspect ratio on footage unless you know for a certainty that it is wrong. For example, open Photoshop or Illustrator and create a new document that is 720 X 480 pixels and AE will always interpret the image as rectangular pixels because that is a standard rectangular pixel frame size.
Unless you specifically created the image in Photoshop with rectangular pixels it is square pixels so the interpretation must be changed to avoid distortion.
--Did you mean to write:
Unless you specifically created the image in Photoshop with SQUARE pixels using a rectangle layout? I am not trying to bust your blz here, I am trying to understand the unknown. (for me)
So it may very well be AE mis-guessing the footage and the Upper first is a mistake on AE's part and I need to test it to find out? On that note...
Ref#3, Separating fields must be done right. Some 1080P footage is interpreted as having fields. This may be incorrect and if there is a question you MUST test the footage. Test the footage by making sure that the fields are being separated
How do I make sure the fields are being seperated? Does the window as in pic two from the top of my post confirm that or is there another test?
Then I do the following:
then selecting the footage in the project panel and choosing Create Composition from Selection, then opening the Composition settings, doubling the frame rate and stepping through the footage a frame at a time. If the footage is really interlaced then each of the frames will be different. (IE: 29.94 to 59.94fps) OK
If the field order is reversed then motion will be in the right direction then reverse, then go back to the right direction. ---I did not understand? Are you referring to Upper and Lower reverse? Direction, as in fwd and back in Time line? Sorry unlclear on my end...
Oh and HFR footage? HFR? High frame rate??
One last thing, Do all cameras shoot anamorphic, or could they as AE is showing my MTS files; are Square? (1.00) Pic #1
@Dave- You -
At 1080, a lot of footage is interlaced, and evidently your camera made interlaced footage
Me- How do you know? because of the 2nd pic and upper field first indication?
You-Even if you know for a fact that it was shot 30p, the camera captures the entire frame... but it records it as two fields. They give it a fancy name: Progressive Segmented Frame.
Me- Is this typical false advertisement of the sales divison of brands like not telling you what CMOS or CCD is in a cam just slapping HD 1080p on the side of the box?
You-AE will treat it as an entire frame if you interpret it as having a field order of None.
Me- Won't that be a problem mis leading AE on an interpret?
Thanks Gents for the precise details.
Best
NC

FM-A75IA-E53 + A10-6800K cpu ratio is locked

Hi!
As Russian's MSI forum is dead I'd ask here.
New board FM-A75IA-E53 (bios 2.0) + A10-6800K + 2x4Gb 2133MHz GSkill Ares RAM
Post, Boot Win7_x64 boot is Ok. But problem comes from Sun Virtual machine player.
The virtual machine is failed to start due to virtualization is off. I have search in the bios but failed to find 'SVM enable' switch. Despite it was described in the manual. (hint: bios 2.0 'SVM enable' is absent)
The bios was updated to 2.2.
'SVM enable' switch appear with Enable/Disable options.
Win!
But!
The CPU Ratio and Turbo Ratio is locked now. The lines to set the ratio is active (highlited, not dimmed as disabled) but on action on mouse click.
Does it common error with this mobo+cpu+bios or it is my motherboard bug?
Please help.

You need to use +/- keys to change ratio settings not mouse click.

P67A-GD55: "Adjust CPU Ratio" disables "CPU Phase Control"

I'm using P67A-GD55 (BIOS ver.1.7) and i5-2500K.
I changed "Adjust CPU Ratio" and I found "CPU Phase Control" was disabled automatically.
1. Click "Green Power" and set "CPU Phase Control" to "APS Mode".
2. Click "OC" and set "Adjust CPU Ratio" to "33"
(It's a default value, but please click the number "33").
3. Click "Green Power" and check "CPU Phase Control".
It is changed to "Disabled".
Please keep "CPU Phase Control = APS Mode".

> MSI employees rarely come here and post even more rarely.
Thanks for the info.
I had another account and I reported a BIOS bug a few years ago.
MSI fixed it soon.
I remember that, so I bought the MSI mainboard.
I hope this post would help other P67A-GD55 users and the MSI developers.
Note for users:
MSI will upload the latest BIOS to the Taiwanese site first.
Taiwan - BIOS ver1.7
http://tw.msi.com/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=2226
Europe - BIOS ver1.6
http://eu.msi.com/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=2226
US - BIOS ver1.7
http://us.msi.com/mb/html/P67A-GD55_BIOS.html

Vcore and cpu ratio

Hey, i have the K7N2G and i have some problems changing the vcore and cpu ratio in bios...
my cpu is a XP 2100+, it only boots with default vcore and 1.625, and default cpu ratio... if i change the cpu ratio it doesn't boot... what's wrong? what can i do to change de vcore and cpu ratio without crashing? the max fsb that i can use is 157 (~=2050Mhz -> 157*13).
I have OCZ-EL 256Mb

Wonkanoby....I think you are incorrect (but not 100% sure). I have a 2100 Tbred B and I don't have to use the wire trick if I put it in the EPOX...ASUS..... The nforce2 should unlock the Tbred B core, am I mistaken here? I also had the same problem as the above user, but I CAN get the msi to unlock it at some lower multipliers. I'm a little confused why the asus and epox nforce2 boards unlocked my chip, but the msi will not. Any ideas?

MOVED: MSI P31 Neo and FSB/DDR ratio

This topic has been moved to Overclockers & Modding Corner.
https://forum-en.msi.com/index.php?topic=116635.0

Hello Aacko,
the P31 Neo is a budget board that is not really designed for overclocking (notice the red PCB). The P31 chipset supports DDR2-667 and DDR2-800 memory modules. With a FSB-200-MHZ-CPU installed, 1:1.66 and 1:2 are exactly the ratios you need to get your RAM to 667 MHz or 800 MHz.
Quote
Can I do something about this or should I swap P31 Neo to some P35-chipset mobo that would allow more flexible FSB/DDR ratio settings?
If you really want to overclock, you should go for a P35 Platinum or P35 Neo2-FR/FIR board.

MSI P31 Neo and FSB/DDR ratio

I purchased P31 Neo -mb and E2160 processor.
I've red that this processor could easily hit 3.0 Ghz with 333 mhz fsb. The problem is that I can't find a setting from P31 Neo's bios that would allow to unlock FSB/DDR ratio. There is only Auto, 1:1.66 and 1:2 setting for FSB/DDR ratio. When I raise the FSB the DDR speed quickly raises over 800 Mhz and the system doesn't post. 2160 Mhz is the top that i've managed to overclock E2160 because my DDR2-chips can't handle the higher FSB speeds.
Can I do something about this or should I swap P31 Neo to some P35-chipset mobo that would allow more flexible FSB/DDR ratio settings?

Hello Aacko,
the P31 Neo is a budget board that is not really designed for overclocking (notice the red PCB). The P31 chipset supports DDR2-667 and DDR2-800 memory modules. With a FSB-200-MHZ-CPU installed, 1:1.66 and 1:2 are exactly the ratios you need to get your RAM to 667 MHz or 800 MHz.
Quote
Can I do something about this or should I swap P31 Neo to some P35-chipset mobo that would allow more flexible FSB/DDR ratio settings?
If you really want to overclock, you should go for a P35 Platinum or P35 Neo2-FR/FIR board.

CPU ratio does not go higher & mem Question

Is CPU ratio the same as the mulitplier? IF so why soes mine not go higher than 10, despite reading here that people are setting theirs at 11 and 12 using the same board as mine. I'm not even sure what this does?
Right now I'm in the process of trying to overclock my machine, but getting nowhere near what some are getting here.
Mind you, I think it has a lot to do with my ram since I can not get it to post when my ram sticks are in slot 1 and 2. It only works in slot 1 and 3 with either 2 sticks of samsung or 2 sticks of infineon ram (2 sticks of 512, PC3200). Also it will not boot unless using 2T. 1T only works with one stick in slot 1.
No clue if it is the memory, although I tried 2 different types of the motherboard.
And there are so many different types of memory, I have no idea what it is I really should be getting?

Cpu Ratio/Multiplier see Extremeoverclocking Part 1: The available CPU's Each CPU in link shows the top multiplier that can be applied in the Multiplier you can run on lower values but not higher.
Read up some of the oc in this forum & check out the memory their using as a starting point.

MOVED: question regarding CPU temps and latest bios (1.8)

This topic has been moved to AMD64 nVidia Based board.
question regarding CPU temps and latest bios (1.8)

I'd believe the first bios's temps more than the second...
However what temps are given when using speed fan and/or everest? (in windows)

CPU time and ELAPSED time in tkprof question

Hi,
I have a statment that is running more than 3 HR.
I run 10046 event and found that the CPU time and the ELAPSED time is almost the same:
call count cpu elapsed disk query current rows
Parse 2 0.00 0.00 0 0 0 0
Execute 2 0.00 0.00 0 3 0 1
Fetch 97 10175.76 10094.81 11216 56387604 0 1441
total 101 10175.76 10094.82 11216 56387607 0 1442
Is that can indicate of a problem in the machine ?
The TOP activity also shows 99% cpu usage.
CPU TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
6 ? 24700 oracle 232 20 5448M 13184K run 195:34 99.18 99.00 oraclepcr
Thanks

Hi,
Thank you for your replay.
Its version 10204 on HP-UX with 24GB and 8 CPUs.
No i dont have any MERGE JOIN CARTESIAN.
The reason that i didnt upload the plan is because its too long...far too long ....
call count cpu elapsed disk query current rows
Parse 1 42.20 41.38 0 0 0 0
Execute 1 0.00 0.00 0 0 0 0
Fetch 5 444.12 447.27 1153 2486187 0 61
total 7 486.32 488.65 1153 2486187 0 61
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 65 (PSSYS)
Rows Execution Plan
0 SELECT STATEMENT MODE: ALL_ROWS
0 UNION-ALL
0 CONCATENATION
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS
0 NESTED LOOPS
0 NESTED LOOPS (OUTER)
0 HASH JOIN (OUTER)
0 HASH JOIN (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS
0 NESTED LOOPS
0 NESTED LOOPS
(OUTER)
0 NESTED LOOPS
(OUTER)
0 NESTED LOOPS
(OUTER)
0 NESTED LOOPS
(OUTER)
0 NESTED
LOOPS (OUTER)
0 FILTER
0 HASH
JOIN (OUTER)
0
TABLE ACCESS MODE: ANALYZED (BY
INDEX ROWID) OF 'PS_RD_COMPANY'
(TABLE)
0
NESTED LOOPS
0
NESTED LOOPS (OUTER)
0
NESTED LOOPS
0
NESTED LOOPS
0
HASH JOIN
0
TABLE ACCESS MODE:
ANALYZED (FULL) OF 'PS_PROD
_ITEM' (TABLE)
0
TABLE ACCESS MODE:
ANALYZED (BY INDEX ROWID)
OF 'PS_RO_LINE' (TABLE)
0
NESTED LOOPS
0
HASH JOIN
0
INDEX MOD
E: ANALYZED (FULL SCAN)
OF 'PS0RO_DEFN_HDSTAT'
(INDEX)
0
TABLE ACCES
S MODE: ANALYZED (BY
INDEX ROWID) OF 'PS_RO_H
EADER' (TABLE)
0
INDEX
MODE: ANALYZED (RANGE
SCAN) OF 'PSERO_HEADER'
(INDEX)
0
INDEX MODE:
ANALYZED (RANGE SCAN) OF
'PSARO_LINE' (INDEX (UNIQ
UE))
0
TABLE ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF
'PS_RO_BOID' (TABLE)
0
INDEX MODE: ANALYZ
ED (UNIQUE SCAN) OF 'PS_RO_
BOID' (INDEX (UNIQUE))
0
TABLE ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF
'PS_RF_INST_PROD' (TABLE)
0
INDEX MODE: ANALYZED
(RANGE SCAN) OF 'PS_RF_INST_
PROD' (INDEX (UNIQUE))
0
TABLE ACCESS MODE: ANALYZED
(BY INDEX ROWID) OF 'PS_RD_PER
SON' (TABLE)
0
INDEX MODE: ANALYZED
(UNIQUE SCAN) OF 'PS_RD_PERSO
N' (INDEX (UNIQUE))
0
INDEX MODE: ANALYZED (RANGE
SCAN) OF 'PS0RD_COMPANY' (INDEX)
0 VIEW
OF 'XLATTABLE_VW' (VIEW)
0
NESTED LOOPS
0
TABLE ACCESS MODE: ANALYZED
(FULL) OF 'PSXLATITEM' (TABLE)
0
INDEX MODE: ANALYZED (UNIQUE
SCAN) OF 'PS_PSXLATDEFN' (INDEX
(UNIQUE))
0 TABLE
ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'PS_RSF_INDUSTRY' (TABLE)
0 INDEX
MODE: ANALYZED (RANGE SCAN) OF
'PS3RSF_INDUSTRY' (INDEX)
0 TABLE
ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'NAP_CATALOG_NUM' (TABLE)
0 INDEX
MODE: ANALYZED (UNIQUE SCAN) OF
'PS_NAP_CATALOG_NUM' (INDEX (UNIQUE)
0 MAT_VIEW
ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
0 INDEX
MODE: ANALYZED (RANGE SCAN) OF
'BB_CODE_TABLE_I' (INDEX)
0 MAT_VIEW
ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
0 INDEX
MODE: ANALYZED (RANGE SCAN) OF
'BB_CODE_TABLE_I' (INDEX)
0 MAT_VIEW ACCESS
MODE: ANALYZED (BY INDEX ROWID) OF
'IP_CONNECTION_TYPES' (MAT_VIEW)
0 INDEX MODE:
ANALYZED (RANGE SCAN) OF
'IP_CONNECTION_TYPES_X1' (INDEX)
0 TABLE ACCESS
MODE: ANALYZED (BY INDEX ROWID) OF
'NAP_INTERNET' (TABLE)
0 INDEX MODE:
ANALYZED (UNIQUE SCAN) OF
'PS_NAP_INTERNET' (INDEX (UNIQUE))
0 TABLE ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF
'PS_RF_INST_PROD' (TABLE)
0 INDEX MODE:
ANALYZED (RANGE SCAN) OF
'PS_RF_INST_PROD' (INDEX (UNIQUE))
0 MAT_VIEW ACCESS
MODE: ANALYZED (BY INDEX ROWID) OF
'BB_CODE_TABLE' (MAT_VIEW)
0 INDEX MODE:
ANALYZED (RANGE SCAN) OF
'BB_CODE_TABLE_I' (INDEX)
0 TABLE ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF
'NAP_CATALOG_NUM' (TABLE)
0 INDEX MODE: ANALYZED
(UNIQUE SCAN) OF 'PS_NAP_CATALOG_NUM'
(INDEX (UNIQUE))
0 MAT_VIEW ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF 'BB_CODE_TABLE'
(MAT_VIEW)
0 INDEX MODE: ANALYZED
(RANGE SCAN) OF 'BB_CODE_TABLE_I' (INDEX)
0 MAT_VIEW ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF 'BB_CODE_TABLE'
(MAT_VIEW)
0 INDEX MODE: ANALYZED
(RANGE SCAN) OF 'BB_CODE_TABLE_I' (INDEX)
0 MAT_VIEW ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF
'IP_CONNECTION_TYPES' (MAT_VIEW)
0 INDEX MODE: ANALYZED
(RANGE SCAN) OF 'IP_CONNECTION_TYPES_X1'
(INDEX)
0 MAT_VIEW ACCESS MODE: ANALYZED
(FULL) OF 'IP_PIRSUM_CODE' (MAT_VIEW)
0 MAT_VIEW ACCESS MODE: ANALYZED
(FULL) OF 'IP_PIRSUM_CODE' (MAT_VIEW)
0 TABLE ACCESS MODE: ANALYZED (BY
INDEX ROWID) OF 'PS_BO_NAME' (TABLE)
0 INDEX MODE: ANALYZED (RANGE SCAN)
OF 'PS_BO_NAME' (INDEX (UNIQUE))
0 TABLE ACCESS MODE: ANALYZED (BY
INDEX ROWID) OF 'PS_BO_CM' (TABLE)
0 INDEX MODE: ANALYZED (RANGE SCAN)
OF 'PS_BO_CM' (INDEX (UNIQUE))
0 TABLE ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'PS_BO_CM_USE' (TABLE)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'PS_BO_CM_USE' (INDEX (UNIQUE))
0 TABLE ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'PS_CM' (TABLE)
0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF
'PS_CM' (INDEX (UNIQUE))
0 MAT_VIEW ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'BB_CODE_TABLE_I' (INDEX)
0 INDEX MODE: ANALYZED (FULL SCAN) OF
'PSHBO_NAME' (INDEX)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'PS1RD_PERSON' (INDEX)
0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
'PS_RB_WORKER' (TABLE)
0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF
'PS_RB_WORKER' (INDEX (UNIQUE))
0 INDEX MODE: ANALYZED (FULL SCAN) OF 'PSHBO_NAME'
(INDEX)
0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
'PS_RD_PERSON' (TABLE)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'PS1RD_PERSON' (INDEX)
0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
'PS_RF_GRP_MEMBER' (TABLE)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'PSARF_GRP_MEMBER' (INDEX)
0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
'PS_RF_PROVIDER_GRP' (TABLE)
0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF
'PS_RF_PROVIDER_GRP' (INDEX (UNIQUE))
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS
0 NESTED LOOPS
0 NESTED LOOPS (OUTER)
0 HASH JOIN (OUTER)
0 HASH JOIN (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS
0 NESTED LOOPS
0 NESTED LOOPS
(OUTER)
0 NESTED LOOPS
(OUTER)
0 NESTED LOOPS
(OUTER)
0 NESTED LOOPS
(OUTER)
0 NESTED
LOOPS (OUTER)
0 FILTER
0 HASH
JOIN (OUTER)
0
TABLE ACCESS MODE: ANALYZED (BY
INDEX ROWID) OF 'PS_RD_COMPANY'
(TABLE)
0
NESTED LOOPS
0
NESTED LOOPS
0
NESTED LOOPS (OUTER)
0
NESTED LOOPS
0
HASH JOIN
0
TABLE ACCESS MODE:
ANALYZED (FULL) OF 'PS_PROD
_ITEM' (TABLE)
0
TABLE ACCESS MODE:
ANALYZED (BY INDEX ROWID)
OF 'PS_RO_LINE' (TABLE)
0
NESTED LOOPS
0
HASH JOIN
0
INDEX MOD
E: ANALYZED (FULL SCAN)
OF 'PS0RO_DEFN_HDSTAT'
(INDEX)
0
TABLE ACCES
S MODE: ANALYZED (BY
INDEX ROWID) OF 'PS_RO_H
EADER' (TABLE)
0
INDEX
MODE: ANALYZED (RANGE
SCAN) OF 'PSERO_HEADER'
(INDEX)
0
INDEX MODE:
ANALYZED (RANGE SCAN) OF
'PSARO_LINE' (INDEX (UNIQ
UE))
0
TABLE ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF
'PS_RO_BOID' (TABLE)
0
INDEX MODE: ANALYZ
ED (UNIQUE SCAN) OF 'PS_RO_
BOID' (INDEX (UNIQUE))
0
TABLE ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF
'PS_RD_PERSON' (TABLE)
0
INDEX MODE: ANALYZED
(UNIQUE SCAN) OF 'PS_RD_PERS
ON' (INDEX (UNIQUE))
0
TABLE ACCESS MODE: ANALYZED
(BY INDEX ROWID) OF 'PS_RF_INS
T_PROD' (TABLE)
0
INDEX MODE: ANALYZED
(RANGE SCAN) OF 'PS_RF_INST_P
ROD' (INDEX (UNIQUE))
0
INDEX MODE: ANALYZED (RANGE
SCAN) OF 'PS0RD_COMPANY' (INDEX)
0 VIEW
OF 'XLATTABLE_VW' (VIEW)
0
NESTED LOOPS
0
TABLE ACCESS MODE: ANALYZED
(FULL) OF 'PSXLATITEM' (TABLE)
0
INDEX MODE: ANALYZED (UNIQUE
SCAN) OF 'PS_PSXLATDEFN' (INDEX
(UNIQUE))
0 TABLE
ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'PS_RSF_INDUSTRY' (TABLE)
0 INDEX
MODE: ANALYZED (RANGE SCAN) OF
'PS3RSF_INDUSTRY' (INDEX)
0 TABLE
ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'NAP_CATALOG_NUM' (TABLE)
0 INDEX
MODE: ANALYZED (UNIQUE SCAN) OF
'PS_NAP_CATALOG_NUM' (INDEX (UNIQUE)
0 MAT_VIEW
ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
0 INDEX
MODE: ANALYZED (RANGE SCAN) OF
'BB_CODE_TABLE_I' (INDEX)
0 MAT_VIEW
ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
0 INDEX
MODE: ANALYZED (RANGE SCAN) OF
'BB_CODE_TABLE_I' (INDEX)
0 MAT_VIEW ACCESS
MODE: ANALYZED (BY INDEX ROWID) OF
'IP_CONNECTION_TYPES' (MAT_VIEW)
0 INDEX MODE:
ANALYZED (RANGE SCAN) OF
'IP_CONNECTION_TYPES_X1' (INDEX)
0 TABLE ACCESS
MODE: ANALYZED (BY INDEX ROWID) OF
'NAP_INTERNET' (TABLE)
0 INDEX MODE:
ANALYZED (UNIQUE SCAN) OF
'PS_NAP_INTERNET' (INDEX (UNIQUE))
0 TABLE ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF
'PS_RF_INST_PROD' (TABLE)
0 INDEX MODE:
ANALYZED (RANGE SCAN) OF
'PS_RF_INST_PROD' (INDEX (UNIQUE))
0 MAT_VIEW ACCESS
MODE: ANALYZED (BY INDEX ROWID) OF
'BB_CODE_TABLE' (MAT_VIEW)
0 INDEX MODE:
ANALYZED (RANGE SCAN) OF
'BB_CODE_TABLE_I' (INDEX)
0 TABLE ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF
'NAP_CATALOG_NUM' (TABLE)
0 INDEX MODE: ANALYZED
(UNIQUE SCAN) OF 'PS_NAP_CATALOG_NUM'
(INDEX (UNIQUE))
0 MAT_VIEW ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF 'BB_CODE_TABLE'
(MAT_VIEW)
0 INDEX MODE: ANALYZED
(RANGE SCAN) OF 'BB_CODE_TABLE_I' (INDEX)
0 MAT_VIEW ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF 'BB_CODE_TABLE'
(MAT_VIEW)
0 INDEX MODE: ANALYZED
(RANGE SCAN) OF 'BB_CODE_TABLE_I' (INDEX)
0 MAT_VIEW ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF
'IP_CONNECTION_TYPES' (MAT_VIEW)
0 INDEX MODE: ANALYZED
(RANGE SCAN) OF 'IP_CONNECTION_TYPES_X1'
(INDEX)
0 MAT_VIEW ACCESS MODE: ANALYZED
(FULL) OF 'IP_PIRSUM_CODE' (MAT_VIEW)
0 MAT_VIEW ACCESS MODE: ANALYZED
(FULL) OF 'IP_PIRSUM_CODE' (MAT_VIEW)
0 TABLE ACCESS MODE: ANALYZED (BY
INDEX ROWID) OF 'PS_BO_NAME' (TABLE)
0 INDEX MODE: ANALYZED (RANGE SCAN)
OF 'PS_BO_NAME' (INDEX (UNIQUE))
0 TABLE ACCESS MODE: ANALYZED (BY
INDEX ROWID) OF 'PS_BO_CM' (TABLE)
0 INDEX MODE: ANALYZED (RANGE SCAN)
OF 'PS_BO_CM' (INDEX (UNIQUE))
0 TABLE ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'PS_BO_CM_USE' (TABLE)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'PS_BO_CM_USE' (INDEX (UNIQUE))
0 TABLE ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'PS_CM' (TABLE)
0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF
'PS_CM' (INDEX (UNIQUE))
0 MAT_VIEW ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'BB_CODE_TABLE_I' (INDEX)
0 INDEX MODE: ANALYZED (FULL SCAN) OF
'PSHBO_NAME' (INDEX)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'PS1RD_PERSON' (INDEX)
0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
'PS_RB_WORKER' (TABLE)
0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF
'PS_RB_WORKER' (INDEX (UNIQUE))
0 INDEX MODE: ANALYZED (FULL SCAN) OF 'PSHBO_NAME'
(INDEX)
0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
'PS_RD_PERSON' (TABLE)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'PS1RD_PERSON' (INDEX)
0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
'PS_RF_GRP_MEMBER' (TABLE)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'PSARF_GRP_MEMBER' (INDEX)
0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
'PS_RF_PROVIDER_GRP' (TABLE)
0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF
'PS_RF_PROVIDER_GRP' (INDEX (UNIQUE))
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS
0 NESTED LOOPS
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 HASH JOIN (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS
0 NESTED LOOPS
0 NESTED LOOPS (OUTER)
0 FILTER
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS
0 NESTED LOOPS (OUTER)
0 NESTED LOOPS
(OUTER)
0 NESTED LOOPS
0 NESTED LOOPS
(OUTER)
0 NESTED LOOPS
(OUTER)
0 NESTED
LOOPS (OUTER)
0 NESTED
LOOPS
0 NESTED
LOOPS (OUTER)
0
NESTED LOOPS
0
HASH JOIN
0
TABLE ACCESS MODE: ANALYZED
(FULL) OF 'PS_PROD_ITEM' (TABLE)
0
TABLE ACCESS MODE: ANALYZED
(BY INDEX ROWID) OF 'PS_RO_LINE
' (TABLE)
0
NESTED LOOPS
0
HASH JOIN
0
INDEX MODE: ANALYZED
(FULL SCAN) OF 'PS0RO_DEFN_H
DSTAT' (INDEX)
0
TABLE ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF
'PS_RO_HEADER' (TABLE)
0
INDEX MODE: ANALYZ
ED (RANGE SCAN) OF 'PSERO_H
EADER' (INDEX)
0
INDEX MODE: ANALYZED
(RANGE SCAN) OF 'PSARO_LINE'
(INDEX (UNIQUE))
0
TABLE ACCESS MODE: ANALYZED
(BY INDEX ROWID) OF 'PS_RO_BOID'
(TABLE)
0
INDEX MODE: ANALYZED (UNIQUE
SCAN) OF 'PS_RO_BOID' (INDEX
(UNIQUE))
0
TABLE ACCESS MODE: ANALYZED (BY
INDEX ROWID) OF 'PS_RD_PERSON'
(TABLE)
0
INDEX MODE: ANALYZED (UNIQUE
SCAN) OF 'PS_RD_PERSON' (INDEX
(UNIQUE))
0 TABLE
ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'PS_RF_INST_PROD' (TABLE)
0
INDEX MODE: ANALYZED (RANGE
SCAN) OF 'PS_RF_INST_PROD' (INDEX
(UNIQUE))
0 TABLE
ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'PS_BO_NAME' (TABLE)
0 INDEX
MODE: ANALYZED (RANGE SCAN) OF
'PS_BO_NAME' (INDEX (UNIQUE))
0 TABLE
ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'NAP_CATALOG_NUM' (TABLE)
0 INDEX
MODE: ANALYZED (UNIQUE SCAN) OF
'PS_NAP_CATALOG_NUM' (INDEX (UNIQUE)
0 MAT_VIEW
ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'IP_CONNECTION_TYPES'
(MAT_VIEW)
0 INDEX
MODE: ANALYZED (RANGE SCAN) OF
'IP_CONNECTION_TYPES_X1' (INDEX)
0 INDEX MODE:
ANALYZED (RANGE SCAN) OF
'PS_NAP_IP_DEBIT' (INDEX (UNIQUE))
0 SORT
(AGGREGATE)
0 INDEX
MODE: ANALYZED (RANGE SCAN) OF
'PS_NAP_IP_DEBIT' (INDEX (UNIQUE))
0 TABLE ACCESS
MODE: ANALYZED (BY INDEX ROWID) OF
'NAP_CATALOG_NUM' (TABLE)
0 INDEX MODE:
ANALYZED (UNIQUE SCAN) OF
'PS_NAP_CATALOG_NUM' (INDEX (UNIQUE))
0 MAT_VIEW ACCESS
MODE: ANALYZED (BY INDEX ROWID) OF
'IP_CONNECTION_TYPES' (MAT_VIEW)
0 INDEX MODE:
ANALYZED (RANGE SCAN) OF
'IP_CONNECTION_TYPES_X1' (INDEX)
0 TABLE ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF
'PS_RD_COMPANY' (TABLE)
0 INDEX MODE:
ANALYZED (RANGE SCAN) OF 'PS0RD_COMPANY'
(INDEX)
0 VIEW PUSHED PREDICATE
OF 'XLATTABLE_VW' (VIEW)
0 NESTED LOOPS
0 TABLE ACCESS
MODE: ANALYZED (BY INDEX ROWID) OF
'PSXLATITEM' (TABLE)
0 INDEX MODE:
ANALYZED (RANGE SCAN) OF
'PSBPSXLATITEM' (INDEX)
0 INDEX MODE:
ANALYZED (UNIQUE SCAN) OF
'PS_PSXLATDEFN' (INDEX (UNIQUE))
0 TABLE ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF
'PS_RSF_INDUSTRY' (TABLE)
0 INDEX MODE: ANALYZED
(RANGE SCAN) OF 'PS3RSF_INDUSTRY' (INDEX)
0 TABLE ACCESS MODE:
ANALYZED (BY INDEX ROWID) OF 'PS_BO_CM'
(TABLE)
0 INDEX MODE: ANALYZED
(RANGE SCAN) OF 'PS_BO_CM' (INDEX (UNIQUE))
0 TABLE ACCESS MODE: ANALYZED
(BY INDEX ROWID) OF 'PS_BO_CM_USE' (TABLE)
0 INDEX MODE: ANALYZED
(RANGE SCAN) OF 'PS_BO_CM_USE' (INDEX (UNIQUE)
0 TABLE ACCESS MODE: ANALYZED
(BY INDEX ROWID) OF 'PS_CM' (TABLE)
0 INDEX MODE: ANALYZED (UNIQUE
SCAN) OF 'PS_CM' (INDEX (UNIQUE))
0 TABLE ACCESS MODE: ANALYZED (BY
INDEX ROWID) OF 'NAP_INTERNET' (TABLE)
0 INDEX MODE: ANALYZED (UNIQUE
SCAN) OF 'PS_NAP_INTERNET' (INDEX (UNIQUE))
0 MAT_VIEW ACCESS MODE: ANALYZED (BY
INDEX ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
0 INDEX MODE: ANALYZED (RANGE SCAN)
OF 'BB_CODE_TABLE_I' (INDEX)
0 MAT_VIEW ACCESS MODE: ANALYZED (BY
INDEX ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
0 INDEX MODE: ANALYZED (RANGE SCAN)
OF 'BB_CODE_TABLE_I' (INDEX)
0 MAT_VIEW ACCESS MODE: ANALYZED (BY
INDEX ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'BB_CODE_TABLE_I' (INDEX)
0 MAT_VIEW ACCESS MODE: ANALYZED (FULL) OF
'IP_PIRSUM_CODE' (MAT_VIEW)
0 MAT_VIEW ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'BB_CODE_TABLE_I' (INDEX)
0 MAT_VIEW ACCESS MODE: ANALYZED (BY INDEX
ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'BB_CODE_TABLE_I' (INDEX)
0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID)
OF 'PS_BO_NAME' (TABLE)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'PS_BO_NAME_IDX1' (INDEX)
0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
'PS_RD_PERSON' (TABLE)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'PS1RD_PERSON' (INDEX)
0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
'PS_RF_GRP_MEMBER' (TABLE)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'PSARF_GRP_MEMBER' (INDEX)
0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
'PS_RF_PROVIDER_GRP' (TABLE)
0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF
'PS_RF_PROVIDER_GRP' (INDEX (UNIQUE))
0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
'PS_BO_NAME' (TABLE)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'PS_BO_NAME_IDX1' (INDEX)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF 'PS1RD_PERSON'
(INDEX)
0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
'PS_RB_WORKER' (TABLE)
0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF 'PS_RB_WORKER'
(INDEX (UNIQUE))

KT4V CPU ratio

Hi,
few days ago purchased MSI kt4v mainboard. I have a question about cpu ratio settings in bios.
These are the options MB offers me:
14.0
15.0
6.0
7.0
13.0
12.5/13.0
14x and 15x at the top. But when i try to set 14X133, the real setting is 4x133 !! Same with 15x (5x133). So, these 2 settings don't work! CPU is unlocked, becouse i can use all other ratios! I updated BIOS to 1.8 and it is the same! :(
Also i have a question about AGP: i have radeon 9000, but i can not choose AGP 8x in BIOS! I can only select 1x, 2x, 4x .... WHY? ?(
thanks for your answers.

i'll assume you are running your ddr333 at ddr333. if it's on auto then try setting it to spd and then making it 333. then try setting ur multiplier to 10 and fsb to 150 and then put ur fsb up in increments of 5. once it fails to post then bring it down one at a time. default clock for xp1700 is 1.466. 10x150 will put you at 1500 and should be possible. if you can make it to fsb 166 then stop and up your multiplier to 10.5. then keep upping your multiplier until it fails to post. upping your vcore might help. i'm not really all the familiar ocing xp chips though. i've heard sometimes you don't have to up the vcore.
as for the radeon. i looked for bios updates and unless you have a 3rd party radeon (ie. not made and shipped by ati) then you are probably out of luck with that. i know most nvidia's are 3rd party anyway so they all have different bios versions. best thing to do i guess would be to rma the card. i'm sure if all radeon 9000's didn't work at 8x with the kt4 there would be lot more posts like yours.

CPU ratio bug ?

Hi everybody,
I have a MSI KT3 Ultra 2, and an unlocked Tbred B 1700+ JIUCB.
When I try to boot using 14x or 15x, it posts at bogus sppeds like 667 Mhz. There is also a 12.5x/13x setting which works fine at 12.5.
So how can I set 13, 14 or 15 ?
I have the latest BIOS.
Another question, what is the PCI divider on this board? I can't seem to find a setting for this, and when I try to set 147 or higher windows would not boot. The DDR module is PC2700 and set at HCLK so it works below spec, so it does not work because of the very high PCI clock.
Thank you for any hints. Its such a shame because this CPU can easily reach 2 Ghz and I'm stuck at 1825 because of the CPU ratio problem and the FSB thing.

I think I know why it doesnt work !
I noticed that after i set the FSB to 166, the memory clock will be automatically set to HCLK+33. Its fixed and impossible to change. If I set back the FSB to 133 lets say, all memory speed modes are available again, all this in the same session.
Means that when Im trying to start at 166 the memory will be at 200 no matter what, and it can't handle that much thats why it doesnt post.

AIR, fullscreen, cpu power and a touchscreen pc: Help!

hello all
i need help on AIR in fullscreen mode, cpu power and cores.
i am a ("2 years old") self taught AS3 programmer, and i have written a specific gaming application which is intended to run on a touchscreen pc in full screen mode, as a gaming kiosk.
i am coding and debugging on my old G5 dual 2.3 PowerPC mac (screen resolution:11572x870) and i have found that some rendering operations are hard for my computer to do (frame rate drops significantly), even after doing much optimization tricks (like the excellent ones provided by Sean Christmann - http://tv.adobe.com/watch/max-2008-develop/optimizing-adobe-air-for-code-execution-memory- rendering/)
when i scale the app window down performance improves a lot (but i need it fullscreen)
as i have never learned computer programming (i am a sound designer "by day"), the terms "no graphics hardware acceleration" and "single threaded" came a bit too late for me... so although I'm not so sure flash/air/as3 was the best way to go to achieve my idea, i currently don't want to switch to another platform/languge.
i am about to purchase a touchscreen pc for this purpose. i am considering an HP touchsmart or a Sony VAIO-L for that.
my first question is: do multiple cores affect AIR performance ?
hp's best model has an Intel(R) Core(TM) 2 Duo processor T9800 [2.93GHz, 6MB L2, 1066 FSB]
and sony's best model has a 2.66GHz (Q8400S) Intel® Core® 2 Quad Processor
my second question is: is there any "wrapper" out there that will wrap my AIR app and help it by using the graphics card for accelaration?
thanx in advance,
Saar

i'm not seeing this, i ran a few demos in both gtk-demo and gtk3-demo, flipped thru a bunch of menus real fast, and the cpu usage for both was nearly indentical. those affected should probably post more info about their setup such as what graphic driver they're using and if they're on 32 or 64 bit arch, etc.
my relevant setup info:
fully updated arch-x86_64
openbox
xf86-video-nouveau 0.0.16_git20120324-1 (compiled myself from that date in order to be able to use the new SwapLimit option for reliable double buffering with vsync)

Question on FSB, CPU ratio and VCore

Similar Messages

Maybe you are looking for