Re: prioris XL 5166dp memory

From: alphadoc (all.the.fun_at_the.fair)
Date: 04/28/04 

Date: Wed, 28 Apr 2004 20:16:21 +1000

I have an old HX5100DP machine that will not load win2000 directly from CD,
BUT.....
When I install NT4 first, then the upgrade to win2000 works just fine.
I have tested this with win2000 server, and win2000 beta3, and the NT4
upgrade route works each time.
My suspicion is that the win2000 installer can't ID the chipset properly,
but the upgrade through NT4 allows a generic installation, that works OK.
I also found that installing RedHat linux on the same box required that I
pass kernel parameters to allow installation, because the installer couldn't
size the memory properly.
I also remember that the PCI bus numbering was special, and PCI cards had to
be installed in an unusual order to ensure their detection at boot time in
the correct order. I think this was due to the dual serial (cascaded) PCI
busses.
I have more info on this in you want it, but only with respect to the HX
series. Please reply to the group.
Thanks.
ben_myers_spam_me_not @ charter.net (Ben Myers) wrote in message
<408a77f4.847601@news.charter.net>...
>The chipset on the Prioris XL main logic board (AKA motherboard in the rest
of
>the free world) is an old, old Intel 430NX, probably not supported properly
by
>Windows 2000. The 430NX Neptune chipset was the very first from Intel to
>support Socket 5 and Socket 7 Pentium chips.
>
>If the BIOS memory test recognized the memory, the next step is to run an
>extensive memory diagnostic test. Download MEMTEST-86 from its web site
and
>prepare a bootable Linux floppy. Boot the system from the floppy and let
it run
>through a couple of passes. The screen displayed by MEMTEST-86 shows the
amount
>of memory which the system has available, and a counter for the number of
>passes, or complete memory test cycles.
>
>If MEMTEST-86 also shows 192MB of memory, then the problem is related to
Windows
>2000.
>
>If MEMTEST-86 shows something different, RSVP with the EXACT arrangement of
>SIMMs in their sockets, i.e. capacity of each SIMM installed.
>
>If the SIMMs are all 32MB in capacity, then change the order in which they
are
>installed, and make absolutely sure that each SIMM pair consists of
indentical
>SIMMs, i.e. same manufacturer and electronics. These older motherboards
are
>extremely particular about SIMMs.
>
>I'll repeat: The memory modules MUST be fast-page mode parity 72-pin SIMMs,
70
>ns or faster. Any different SIMM does not meet DEC specs.
>
>Does this system run with full memory capacity under NT 4.0? Also, note
that
>the on-board Cirrus Logic(?) graphics chip is not supported by Windows
2000...
>Ben Myers
>
>On 24 Apr 2004 06:11:01 -0700, pmpmpm1@hotmail.com (Pascal) wrote:
>
>>Ben,
>>
>>The memory is correct recognised by the memory test from the BIOS, so
>>I suppose the combination of (old) SIMM's os correct.
>>The problem is windows 2000 won't recognize them ?
>>
>>regards,
>>
>>Pascal
>>
>>
>>> Pascal,
>>>
>>> The memory modules MUST be fast-page mode parity 72-pin SIMMs, 70 ns or
faster.
>>> EDO will not work. Neither will non-parity fast-page mode.
>>>
>>> I do not have the memory installation rules available for the XL 5166DP,
but the
>>> modules must be installed in exactly matched pairs. Or is it matched
sets of
>>> four? There are additional rules about mixing SIMMs of different
capacities...
>>> Ben Myers
>>>
>>> On 23 Apr 2004 08:30:53 -0700, pmpmpm1@hotmail.com (Pascal) wrote:
>>>
>>> >Hi,
>>> >
>>> >I've got an old Digital Prioris XL server 5166DP system. A nice system
>>> >for a home-server. I've installed win2K server on it, all running
>>> >fine. But the memory is recognized by booting, but in windows i see
>>> >only 64Mb, not the 192Mb that's installed.
>>> >
>>> >Who can help me?
>>> >
>>> >thanks
>>> >
>>> >Pascal
>

Relevant Pages

  • Re: Dell Desktop 8400 - mem slot 4 not recognized
    ... of memory configured as two half-gig DIMM in slots 1 and 2. ... The BIOS reports none present in 4. ... reseated each stick enough times to be confident it is not installer ...
    (alt.sys.pc-clone.dell)
  • Load EXE and run from memory - is it possible in C# ?
    ... I need to load some EXE file into memory and then find a ... way how to run it from the memory without saving to disk. ... The main purpose - to download a small installer from my www and then using ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: SP6 problem?
    ... > The programs are memory intensive and when deployed on the client machine ... > client, ... > So now I want to include the SP6 DLLs in the installer and I rebuild the ...
    (microsoft.public.vb.bugs)
  • Re: RAM used in a Pentium 4 1.70ghz
    ... Could this be due to the RAM being too fast for the PC 1.70ghz processor, or be realted to the BIOS speed? ... When new memory is installed, ... The memtest86+ tester, ... to your installer, ...
    (microsoft.public.windowsxp.hardware)
  • Re: BSD Installer as a replacement for sysinstall?
    ... > without having to muck around with the internals of the installer. ... There are links to a binary updater project and a sysinstall replacement ... That's not to say there's no value in just replacing ... distribution sets to upgrade. ...
    (freebsd-current)