"kony" weaseled out:
The "serious flaw" is that Crucial's OEM search parrots what the
OEM specified at the time of manufacture - which in my system's
case was 8 years ago when the largest DIMM size was 128MB.
The serious flaw is that they're not keeping track of which
board was in which system and no basing the recommendation
upon that. A database for system X should include that it
uses board Y, returning the same search results as if you'd
searched for board Y in the first place.
But when Crucial does a System Scan search, it parrots what the
manufacturer of the motherboard said at the time that the manufacturer
published its test results - which in the case of Intel's SE440BX was
3.5 years ago when the largest available DIMM size was 256MB.
Your timeline is a bit off, 3.5 years ago the largest DIMM
was larger than 256MB. We'd mentioned this, that it's not a
matter of what was available, that it's the actual limit.
Remember that while this may be the first time you're trying
to do this, 440BX boards were common as dirt a few years
ago. Once motherboards began supporting higher density
memory (for example i815 or Via 694 chipsets), 512MB modules
became fairly common.
Roughly speaking, we can get a timeline from an Anandtech
Apollo Pro (Via 694) Motherboard Roundup in Feb. '00, and
I'm sure I was buying them (512MB per) in '01 as I still
have receipts for systems originally equipped with 512MB
modules.
In other words, Crucial will only use published specs, not engineering
knowledge or practical experience in advising customers.
If you mean published specs in the strictest terms, yes.
Quite a few systems did use the SE440BX though, that too was
a "spec" that would've been applicable in their database and
could've yielded better search results.
That's the reason for my posting - to find someone with the engineering
knowledge or the practical experience to say if 512MB modules would
work today (at least while keeping the total RAM size to 1GB or less).
It's too bad that neither Crucial nor Intel would venture a guess, but
that seems to be the nature of corporate liability nowadays.
It is not supported in the real, "won't work" sense, not in
the "we didn't bother to try or mention it", sense like it
was with 256MB in some instances. While it is sometimes
true that modules simply weren't available at the time, that
is not the situation in this case with 512MB and above.
You can Google search for others who have tried it and
failed if you like.