only thing that has me concerned about it is that if you go to the MSI site and view the CPU compatibility for that mobo, the only toledo's listed are the 4400+ and the 4800+. the 4600+ is not listed.
there is a 4600+ manchester listed but not toledo.
so i guess that doesn't mean that it won't work - it just means that they haven't tested it.
so before i order the 4600 i just would like to hear from someone who has actually used the 4600 toledo with this mobo so that i am 100% certain before i make the purchase.
only thing that has me concerned about it is that if you go to the MSI site and view the CPU compatibility for that mobo, the only toledo's listed are the 4400+ and the 4800+. the 4600+ is not listed.
there is a 4600+ manchester listed but not toledo.
so i guess that doesn't mean that it won't work - it just means that they haven't tested it.
so before i order the 4600 i just would like to hear from someone who has actually used the 4600 toledo with this mobo so that i am 100% certain before i make the purchase.
I have a Toledo 4400+. The code name isn't the real factor, it's just the CPUID. If it will hold a 4800+ and a 4400+ it will hold a 4600+. It's the same chip with half the cache as the 4800+.
I understand your hesitance, as, like you said they only list 4400/4800 Toledo's(1MB L2) and not the 4600 (512k). Seems kind if odd, yet they say 4600 Manchester is supported. I think i'd be trying to call MSI, and hear it from the horses mouth. While i can't see why it wouldn't be supported, it would suck to find out that it doesn't. GL
wish i could call them - they don't seem to have a contact number on their site. they want you to email them and i am SURE i wont hear back on that email. i just hate to risk it. i wish i could buy from someplace that will take it back f it doesn't work.
I understand your hesitance, as, like you said they only list 4400/4800 Toledo's(1MB L2) and not the 4600 (512k). Seems kind if odd, yet they say 4600 Manchester is supported. I think i'd be trying to call MSI, and hear it from the horses mouth. While i can't see why it wouldn't be supported, it would suck to find out that it doesn't. GL
The CPU the OP has is a Toledo with half of L2 cache disabled.
I understand your hesitance, as, like you said they only list 4400/4800 Toledo's(1MB L2) and not the 4600 (512k). Seems kind if odd, yet they say 4600 Manchester is supported. I think i'd be trying to call MSI, and hear it from the horses mouth. While i can't see why it wouldn't be supported, it would suck to find out that it doesn't. GL
The CPU the OP has is a Toledo with half of L2 cache disabled. Yes..reread my post. I said that.
I understand your hesitance, as, like you said they only list 4400/4800 Toledo's(1MB L2) and not the 4600 (512k). Seems kind if odd, yet they say 4600 Manchester is supported. I think i'd be trying to call MSI, and hear it from the horses mouth. While i can't see why it wouldn't be supported, it would suck to find out that it doesn't. GL
The CPU the OP has is a Toledo with half of L2 cache disabled. Yes..reread my post. I said that.
Manchester is a native 512KB L2 design
But I am quite confident that the motherboard can support the processor
There is no such thing as a Toledo core 4600. The 4200 and 4600 are Manchester core. The difference being only trhe amount of L2 cache which on the Manchester core is 512KBx2 and on the Toledo core is 1MBx2.
The 4600 is a Manchester core only and will work fine on the Neo4 Platinum.
There is no such thing as a Toledo core 4600. The 4200 and 4600 are Manchester core. The difference being only trhe amount of L2 cache which on the Manchester core is 512KBx2 and on the Toledo core is 1MBx2.
The 4600 is a Manchester core only and will work fine on the Neo4 Platinum.
Message #8 Not all the Toledo chips are fully functional. Some of the partially functional CPUs will be marked as 512KB L2 cache ones.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.