×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I agree it could be the code that differentiates between p and i, and I also
concurr with the memory upgrade probably causing the error.
Remember when I said that another CE had told me that he had heard it was
caused by major configuration changes, well, this machine went out as a
TwinAx box all working, but with no memory as it was not ordered with any,
and has come back as HMC configured from the customer site, and I guess they
have added their own spare memory, so thats quite a configuration change.
When the customer tried bringing the box up they had the same errors which
is why it was sent back. I have tried putting the machine back to the exact
configuration (Same cards, memory, in the same slots, with same serial
numbers) but to no avail.
If these simple changes have caused the problem then surely it could lead to
some future headaches when us field engineers turn up on site to complete
Memory upgrades. I could understand it if it was caused by a
serial/processor change, but memory and console type, thats a but weird?
I have also heard that this problem is only linked to the latest version of
the firmware.
Martin
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
