Processor Question

[rcb4t2]

Hey all - this may sound weird/stupid, but I'm just noticing my system reports a "366mhz celeron" processor is installed. Is this the "300mhz" processor they refer to in the manual, or something else? I'm having some odd issues and trying to make sure I have my bios settings correctly set. Any info would be appreciated - thanks!

[Phil.c]

What are your odd issues?

Phil

[Crash]

Hey all - this may sound weird/stupid, but I'm just noticing my system reports a "366mhz celeron" processor is installed. Is this the "300mhz" processor they refer to in the manual, or something else? I'm having some odd issues and trying to make sure I have my bios settings correctly set. Any info would be appreciated - thanks!

A lot of users would replace the processor with faster units. Is this unit original to you?

Here is some info pulled from the manual for the motherboard you have in your CPU.

Chipset
• Intelâ 440BX AGPset (CB50-BX)
Intelâ 440ZX-100 AGPset (CB50-ZX)
Processor
The system board is equipped with Socket 370 for installing an Intel
CeleronTM processor that is packaged in PPGA (Plastic Pin Grid
Array). It is also equipped with a switching voltage regulator that
automatically detects 1.30V to 2.05V.
• 300A/333/366/400/433/466MHz or future 100MHz FSB
CeleronTM PPGA processor

The motherboard manual as well as the dipswitch settings are located in the database above.

What are your issues?

[synthjoe]

Maybe an inadvertent hand changed the switches, or an overclocking attempt was made. I had an overclocked PC (about the same age) that worked perfectly otherwise, but some devices on the ISA bus behaved erratically. One example was the MIDI port on the soundcard, while all other audio and OPL synth functions worked fine. Took me a month or so to accidentally figure out that it was due to overclocking - something that worked fine for more than a year (I just did not use MIDI earlier on that machine). Maybe you do have a 300 MHz CPU but DIP switches are not set adequately.

[rcb4t2]

Thanks all for the replies. This unit is not original to me.

My fader issues are described more in-depth in my "Whoa! Help needed please" thread.

I recently made myself a midi breakout cable and tried my hand at midi-mapping. Using a Logic midi channel (also tried Opus Locus LC XMU with same results) I was able to get a fader to both send and receive data to/from the DAW. Communication worked perfectly in one or the other direction, but when it was set up both ways the fader would constantly drop ~.3dbs at a time until it got to -infinity, then it would stop. I tried faders 1, 2 and 9 (to make sure it wasn't individual fader or individual fader-board related).

After many frustrations, it occurred to me that I set my BIOS settings for the 300mhz model, when I really have this phantom 366mhz processor, hence the thread.

I've heard about the 128 step vs 255 step interpolation problem, but I don't think that's related here since sending information only to the d8b worked perfectly.

I also tried mapping the pan encoders, with similar results. Although the pan values would just jump erratically, ultimately sort of getting stuck in one place on the software side (DAW), while the d8b encoder jumped around.

[rcb4t2]

(I'll open the CPU tonight if I get a chance and see what the actual processor says - overclocking/incorrectly set dipswitches sounds interesting)

[rcb4t2]

Joe (and many thanks for your continued helpful replies to my problems!) - how did your midi problems manifest? Was all back to normal when you reset the DIP switches?

[rcb4t2]

Update (sorry for the many one-liner posts!): My processor is actually a celeron 366mhz. The dip switches *were* set incorrectly - they are now set correctly. The problem with the faders not responding correctly as described above persists, unfortunately.

In other news, I programmed a midi-map and a DAW template to slowly run the faders up and down their run - it certainly looks cool! lol Hopefully it will give this board some exercise - it's been in storage for some time.

Any reason I shouldn't let this exercise routine run for a bit?

(ps: the processor is this one: http://www.cpu-world.com/CPUs/Celeron/I ... X366%20128).html)

[synthjoe]

Joe (and many thanks for your continued helpful replies to my problems!) - how did your midi problems manifest? Was all back to normal when you reset the DIP switches?

Yes, things were back to normal as soon as I reset CPU and bus speed (FSB) DIP switches. The ISA bus was running at a higher frequency as a result of overclocking, something like 10 MHz instead of the standard 8 Mhz. Most cards did not have a problem with it except the soundcard, and I might be wrong but I seem to recall that only recording (MIDI IN) had troubles, not MIDI out. Might be wrong though, has been some 10 years ago.

[Y-my-R]

Sorry for re-opening such an old thread, but I got curious after I just acquired a d8b CPU (no console), that also showed a Celeron 366 processor.

Is it maybe possible that Mackie installed those from the factory for some time, after all? (Not that it matters, since the performance will be the same... just wondering).

I searched the forum for '366', and found 3 threads (incl. this one) where people reported that this is what theirs were showing... and while I haven't yet opened the CPU I just bought, it doesn't look like it's been tinkered with. Looks almost new. And it booted right up to OS3, working normally with one of my consoles (after the typical battery warning).

The memory still only showed 32MB, so it doesn't look like someone tried to hot-rod this one.

The serial code puts it at December 2000 - much newer than what my other 2 CPUs with a 300 and 166 processor say.

Anyway... everything works fine. Just speculating if 366 MHz CPUs might be original to the d8b after all.

I'll probably open it up some time this weekend, to look for traces of modifications. But again, it looks so clean, I wouldn't have been surprised to find a warranty seal on it, that hasn't been tampered with.