RE: Tagged memory (was Re: Memory Upgrade) -- MIDRANGE-L

× 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.

Subject: RE: Tagged memory (was Re: Memory Upgrade)
From: "Hall, Philip" <phall@xxxxxxxx>
Date: Fri, 28 Sep 2001 09:34:38 -0500
List-Archive: <http://archive.midrange.com/midrange-l/>
List-Help: <mailto:midrange-l-request@midrange.com?subject=help>
List-Id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-Post: <mailto:midrange-l@midrange.com>
List-Subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Dave,

> My understanding of Leif's argument is that it is possible to disable the
> code that detects that the tag is off. I have no idea whether he's right
or
> wrong.

He's right. If you locate the SLIC module that performs this (again, as
others have stated, it's all documented in Leif's book [www.iseries400.org])
make the change, the processor & disks go active for a few minutes and then
the system runs 'unprotected...'

--phil

[ Deleted uuencoded file 'winmail.dat' ]

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.