kony wrote:
On Mon, 13 Sep 2004 12:52:38 +1200, "~misfit~"
wrote:


Something is wrong there, any box that can run a PII450 will
accept at least 256MB (low-density) modules, 512MB or more
total capacity.

I'm not sure about this one. All I know is it's a strange and
uncommon board. It didn't have a SECC retainer fitted and hadn't had
one when I got it. Just the slot. From what I remember it was only
very early boards that were like this. It's a VX chipset and, until
I found the manual, wouldn't have dreamed of trying a Deschutes CPU
in it, I originally set it up with a Klamath, then found the manual
on-line so put the 450 in.

It may even support a Coppermine with the right slotket,
maybe even Tualatin same as typical BX chipset board would,
except that's probably beyond the capabilities of the
voltage regulator circuit, especially extended use at near
full load, like SETI/etc would cause.

I have a couple of Tualatin's running in Slot-T's in BX boards already.
Great combo.

ZX should support low-density 256MB modules, but stability
of *anything* on such a low-end, aged board, could be harder
to attain.

I was given this, the CPU was sitting around, IMO it's a 98 machine anyway
and 128MB is fine for 98. With these Tualatins I'm running in BX boards I'm
actually getting a little low on SDRAM anyway. Especially as a 256MB module
I had been given a while ago but hadn't tested turned out to be stuffed when
I tried it last month.

Ok, the problem. This machine runs Prime95 for 24 hours no problem.
It runs SETI CLI sweet *but*, I have the monitor set to turn off
after 10 minutes, no screen saver. If the machine has completed a
SETI WU and it's got the monitor turned off it locks up. No mouse
movement or pounding of keyboard will wake it. A hard re-set is
needed. This has happened three times and every time the first
thing the PC does when it starts is complete the last 10 seconds
of a SETI WU and then connect to get another one. It's connecting
through my LAN at the moment.

You might see if the NIC driver properties has different
settings for power management, and see if any bios settings
seem related and enable them... hard to say on an old
lower-end board like that.

I can't find anything relevant.


Maybe just leaving the monitor disconnected & off, then
never allowing OS to shut it off would suffice?

Yeah. I was thinking about giving this to a PC-less family and wanted it to
be as stable as possible.

Some boards with power management wakeup problems, benefit
from bios update.

I can't find a BIOS update for it. It doesn't have a very large
web-presence.

I got the manual from he

www.elhvb.com/mboards/ a-trend/manuals/

Atrend 6310M

You might find that other PCChips et al boards' bios would
work, providing the I/O chip and chipset are same (or
perhaps one with BX chipset would work too, unsure about
this. I do think the board was designed to accomodate
either chip, hence the missing 3rd dimm slot when ZX is
used... don't recall the other limitations of ZX vs BX at
the moment.

I take it that PCChips and Atrend are one and the same from this line of
discussion? I know little about them other than to avoid them (or so I'm
told). The one PCChips board I had ran a P200MMX at 250Mhz rock-solid for
ages. I've never had an Atrend before.

You know, it's *almost* this board:

http://www.stud.fernuni-hagen.de/q39...cpics/m726.gif

Linked from that page except mine has an Intel chipset, the third
SDRAM slot nearest the AGP slot is missing (but there is allowance
for it) and the FDD connection on mine is over by the
serial/parallel connectors (which are also oriented at 90° to the
ones on that board.

At first glance I thought that was it.

Thanks for your input Dave.

I'm pretty much out of ideas, beyond looking at power
management and trying a different NIC and/or NIC driver.

I've put a 10/base-T PCI Realtek card in it for now. I'll see how it goes
when the next SETI unit is finished. LOL, that's the difficulty with trying
to troubleshoot this, I have to wait 10 hours or so for it to complete a
SETI unit and attempt to connect (at least I think that's the trigger for
the problem) to the LAN while the monitor is off in power-saving mode to
reproduce the fault.

I'd probably just turn off monitor manually and disable all
power management except HDD spin-down, if access to the
drive can be delayed long enough... if not then perhaps a
ramdrive for storage, any file I/O happening that would
otherwise keep HDD spinning. Then again I vaguely recall
that there's some sort of diskless client potential for
SETI, if you set up boxes like that it wouldn't need the
HDD, monitor, etc.

Cheers Dave,
--
~misfit~