8 Oct
2015
8 Oct
'15
4:37 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
Cross-post for those not on the users list:
http://trinity-users.pearsoncomputing.net/?0::9262
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlYWm+IACgkQLaxZSoRZrGFevQDfezNCUJkDXxoodL5RUbvI1I6W
V06dyNZAyNxYOgDeP7Zvvd3Zg6HSAtEF+BOIhxD8n3KceEyLnmCjyA==
=CVSR
-----END PGP SIGNATURE-----
9 Oct
9 Oct
6:25 p.m.
New subject: [trinity-devel] Master server status
Date: Thu, 8 Oct 2015 11:37:54 -0500
From: kb9vqf(a)pearsoncomputing.net
To: trinity-devel(a)lists.pearsoncomputing.net
Subject: [trinity-devel] Master server status
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
Cross-post for those not on the users list:
http://trinity-users.pearsoncomputing.net/?0::9262
Tim
Hi,
I hope replacing the CPU will improve the system stability.
If a computer fails a memtest86+, it can be anything in the path between the ram, chipset
and cpu. I've seen recently a similar case where the ram has been changed in an IBM
Xeon server, but is still failed memtest86+. The only solution has been to do a P2V on a
new HP all-in-one PC. Its intel i3 is far more powerful, even in a vm, than the original
Pentium 4 era Xeon.
Alexandre
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlYWm+IACgkQLaxZSoRZrGFevQDfezNCUJkDXxoodL5RUbvI1I6W
V06dyNZAyNxYOgDeP7Zvvd3Zg6HSAtEF+BOIhxD8n3KceEyLnmCjyA==
=CVSR
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
3362
days inactive
3363
days old
1 comments
2 participants
participants (2)
-
Alexandre -
Timothy Pearson