Recommended Posts

If you are running single channel DDR400....you wont get max use because its not running the 533Mhz that it should.

If you are running Dual Channel DDR400 then it will - as it willl be able to run any CPU up to 800mhz FSB without any bottlenecks.

If you ARE using dual channel - it will downclock to dual channel DDR266 - as 266*2 = 533mhz (DDR266 was designed for the 533 bus P4)

EDIT: Make sure your mobo is compatible with the DDR400 memory. Though it should work.

Edited by absolutemaxpayne.co.uk
  Iluvatar said:
The 533mhz FSB operates with 266mhz DDR i believe. no problems with anything higher though.

My 533mhz FSB supports PC2700 or DDR333 memory...

You should find in the BIOS to set the speed of memory higher than 266 or 333... not sure that 400 is an option but I know you can set it higher.

You do not need DDR333 or DDR400 to run a P4 533Mhz bus.. It needs dual channel DDR266, thats final. Anything more than that is a bonus for overclocking. Anything less is just a bottleneck.

Only the latest Pentium 4's have a quad pumped FSB, not the 533mhz revisions.

200*4=800mhz fsb. Thats why we need DUAL channel DDR400 so that It reaches the 800mhz the chip requires.

This is how I would like to think of it:

Dual channel DDR266 was designed for the P4 533mhz.

Dual channel DDR400 was designed for the P4 800mhz.

Single channel DDR266 was designed for the older Athlon chips (Thoroughbred - 266mhz fsb)

Single channel DDR400 for the newer Athlon chips.

Single channel DDR333 is for the later Athlon Barton chips, which actually ran at 333mhz.

Note: There is no Dual channel DDR333 because no chip runs at 666Mhz FSB!

The reason why i was asking was because my MB died a couple of days ago. I do NOT have the money to buy the more exspensive stuff right now. So I need one that is cheap but works fine and that I can buy it new. So I was looking at a board with the i848P chipset. Is anyone familiar with that chipset and does it support dual channel ddr? I saw a MB on newegg.com and it seems to support it. Although, I am not sure. Can anyone tell me? Thanks for your help.

  absolutemaxpayne.co.uk said:
You do not need DDR333 or DDR400 to run a P4 533Mhz bus.. It needs dual channel DDR266, thats final. Anything more than that is a bonus for overclocking. Anything less is just a bottleneck.

Only the latest Pentium 4's have a quad pumped FSB, not the 533mhz revisions.

200*4=800mhz fsb. Thats why we need DUAL channel DDR400 so that It reaches the 800mhz the chip requires.

This is how I would like to think of it:

Dual channel DDR266 was designed for the P4 533mhz.

Dual channel DDR400 was designed for the P4 800mhz.

Single channel DDR266 was designed for the older Athlon chips (Thoroughbred - 266mhz fsb)

Single channel DDR400 for the newer Athlon chips.

Single channel DDR333 is for the later Athlon Barton chips, which actually ran at 333mhz.

Note: There is no Dual channel DDR333 because no chip runs at 666Mhz FSB!

Xeons have a bus of 667MHz.

  absolutemaxpayne.co.uk said:
You do not need DDR333 or DDR400 to run a P4 533Mhz bus.. It needs dual channel DDR266, thats final. Anything more than that is a bonus for overclocking. Anything less is just a bottleneck.

Only the latest Pentium 4's have a quad pumped FSB, not the 533mhz revisions.

200*4=800mhz fsb. Thats why we need DUAL channel DDR400 so that It reaches the 800mhz the chip requires.

This is how I would like to think of it:

Dual channel DDR266 was designed for the P4 533mhz.

Dual channel DDR400 was designed for the P4 800mhz.

Single channel DDR266 was designed for the older Athlon chips (Thoroughbred - 266mhz fsb)

Single channel DDR400 for the newer Athlon chips.

Single channel DDR333 is for the later Athlon Barton chips, which actually ran at 333mhz.

Note: There is no Dual channel DDR333 because no chip runs at 666Mhz FSB!

400mhz FSB = 100x4

533mhz FSB = 133x4

800mhz FSB = 200x4

All Pentium 4's are quad pumped FSB.

Put a 533mhz chip on a board with dual channel memory and it will take DDR333 running in dual mode

Put an 800mhz chip on a board with dual chanel memory and it will take DDR400 running in dual mode

Why is it so hard to beileve this? I have 333 memory on my 533 FSB chip and its recognized and runnning at 333...

"Note: There is no Dual channel DDR333 because no chip runs at 666Mhz FSB!"

- Put a 533 FSB chip on an 800 FSB motherboard and you will be able to run DDR333 in dual channel mode.

  PCKing said:
Why is it so hard to beileve this? I have 333 memory on my 533 FSB chip and its recognized and runnning at 333...

Yeah, I didn't say that it wouldn't work, im saying that it is not neccessary. Like I said, anything is a bonus over DDR266 because 266*2 = 533.

  Quote
- Put a 533 FSB chip on an 800 FSB motherboard and you will be able to run DDR333 in dual channel mode.

Again, it will run DC DDR333, but it still doesn't need DC DDR333. It only needs DC DDR266.

fsb = 133 MHz x 4 = 533 MHz bus

Dual channel allocates each memory stick it's own channel to operate on rather then sharing one channel. You can think of it as a 3 lane road being expanding into two 3 lane roads; the ultimate purpose being to alleviate any bandwidth limitations that might occur while using single channel. Dual channel has nothing to do with memory operating frequency. DDR266 can operate in both single channel and dual channel assuming the motherboard allows it, it does not increase to DDR333 in dual channel.

To answer the thread starter's question. PC3200 (DDR400) will work perfectly fine with a P4B, it will just run at a slower clock speed. Memory can always run at speeds less then what it was made for, it cannot be run at speeds greater then what it was meant for. The only thing I'd suggest is you use a newer motherboard that supports all the cpus for compatibility reasons. Some of the older motherboards may have trouble with newer and faster ram.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Still cars that self drive, I still would not trust them, and they should never be allowed on the road, simple as that.
    • It's better than AMD's junk, which suffers from stuttering and frame dips. It is more important than the average FPS you get.
    • Oh, another thing besides the kickass post @goretskyshared (Which I didn't know any of these optimizations, btw), there are times in which Windows may be optimizing your folder for images:    Right-click on an empty space in the folder. Click Properties. Go to the Customize tab. Under “Optimize this folder for:”, select General items from the dropdown. (Optional) Check “Also apply this template to all subfolders”. Click Apply, then OK.
    • Here's how Meta AI "leaks" your private chats, thanks in part to its terrible UX by David Uzondu Back in April, Meta launched its standalone Meta AI app, its answer to apps like ChatGPT. Powered by Llama, its own advanced AI models, the app was meant to be your conversational partner. It can write poems, help you brainstorm, generate images, and even remember details about you. The problem is, it also has a feature that unintentionally helps you "leak" your most intimate, embarrassing, and legally risky conversations onto a public feed for the world to see. This entire mess centers on a "Discover" tab baked into the app. A feature that feels more at home on Instagram or TikTok has been bizarrely grafted onto a tool some people are using as a private diary. At first glance, the feed shows what you might expect: people generating funky AI images or asking for creative writing help. But scroll for more than a minute, and you will find some deeply personal stuff. Neowin, while reviewing the app, saw people posting chats discussing their extramarital affairs and sharing private medical records. In one chat (click to expand the screenshot below), a user asks the AI, "is it bad if my vagina smells?" In another, someone seeks advice on how to handle red bumps on their inner thigh. One user, grappling with a gift for a woman in a "troubled casual dating relationship," types out his entire romantic dilemma. And here's one, where a user confesses their love for their wife who is several miles away, but admits they're developing feelings for someone else: There is also some genuinely heartbreaking stuff. An elderly, disabled dancer recounts being shooed off the dance floor at a senior community event. "I was approached by someone and was told that I couldn't be on the dance floor," they shared with the AI. Some posts even contain voice notes, so you can hear the actual stress and sadness in people's voices as they, for example, try to figure out how to bring their deceased brother, a US Army veteran, home from a foreign country. The feed is also a goldmine for anyone looking for legal or financial drama. One person asks for advice about their sister, a VP at a small company that has not paid its corporate taxes for more than a decade. They wanted to know if the sister would be liable: For this record, this is what the comments section on that one looks like: Here's another example from an accidentally public chat, where a user asked one of those "tell me everything you know about me"-style questions. Meta AI obliged, spilling out a detailed profile of the man: name, age, hometown, business aspirations, and personal goals, all pulled from past conversations: The root cause of this privacy dumpster fire is Meta's baffling user interface. At the top right of every chat, there is a "Share" button. It is not clear where you are sharing to. There is a small, easy-to-miss warning at the bottom of the screen to avoid sharing personal information, but the path to public humiliation is incredibly simple. You tap "Share," are shown a preview screen where you can edit a title, and then you tap "Post." That is it. There is no friction, especially for first-time users, no big, attention-grabbing banner that says, "Hey, this is going public for anyone using this app to see, comment on, and remix." Other platforms, like ChatGPT and Gemini, handle this responsibly. They let you share chats by generating a link you can choose to send to specific people. They do not just hurl your conversation into a public square. Also, enjoy this chat involving someone arguing with Meta AI, asking it to explain why there's so much widespread accidental sharing of personal information (click to expand): The most infuriating part is that this is a problem of Meta's own making. When anyone signs up for the app, there is no prompt. No pop-up about privacy settings, no warning that their chats could end up on a public feed. You are just dumped straight into the app, completely blind to how sharing works. The result is a whole community of users trying to clean up Meta's mess. If you’ve been paying attention, the comment sections are full of people warning others that their private thoughts are now out in the open. Some of the original posters, after being alerted, even jumped in to thank them and claimed they had no idea their chats were public. If you are one of the people who use the Meta AI app, you are probably wondering how to clean up this mess. Luckily, there is a way to claw back some privacy, though you should not have to do this in the first place. You will want to do two things: hide everything you have already shared publicly, and then stop Meta from suggesting your future chats on its other apps. Here is exactly how you do it. To make all your past public prompts private again: Select your profile on the top right to go to settings. Tap "Data and privacy." Next, tap the "Manage your Information" button Then, tap "Make all public prompts visible to only you" Finally, use "Apply to all" on the confirmation pop-up. Next, you will want to stop Meta from suggesting your prompts in its other apps. Neowin's digging uncovered this: In settings, under Data and privacy > Manage your Information, select "Suggesting prompts." Deselect "Facebook" and "Instagram." Let's just hope Meta fixes this before something more serious happens, like a government official accidentally leaking war plans (heh). Neowin has reported the problem through the Meta AI app's own "report a technical issue" feedback form, complete with a link to this article. We will update you if we hear back.
  • Recent Achievements

    • Week One Done
      elsafaacompany earned a badge
      Week One Done
    • Week One Done
      Yianis earned a badge
      Week One Done
    • Veteran
      Travesty went up a rank
      Veteran
    • One Month Later
      somar86 earned a badge
      One Month Later
    • Week One Done
      somar86 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      503
    2. 2
      ATLien_0
      257
    3. 3
      +FloatingFatMan
      185
    4. 4
      +Edouard
      177
    5. 5
      snowy owl
      128
  • Tell a friend

    Love Neowin? Tell a friend!