On Tue, 28 Mar 2000 Andries.Brouwer@cwi.nl wrote:
> > Andries.........I have your answer to JUMPON.EXE.
>
> That is good.
> What is the answer?
>
> The question was: What precisely does JUMPON.EXE do?
Sorry......brain reaction......
Yes, goes in and sets/truncates the total drive capactity at the 32GB
limit, and the NVRAM is set with VV == 0 to hold the settings regardless
of power cycle or whatever.
The setting of VV == 1 will allow it to revert to the "previous" capacity
issued before the most recent SET_MAX_ADDRESS.
Original was 40GB
Call SET_MAX_ADDRESS to set/get 32GB VV == 0
while (!VV)
power cycles always returns 32GB
Later :: Set VV == 1
power cycles always returns 40GB
It does seem possibble to call any capacity "TWICE" the is key, and then
call it a "THIRD" time with a different value and set VV == 0 and then
later set VV == 1 and you are stuck........
40GB
SET_MAX_ADDRESS >> 35GB VV == 0
SET_MAX_ADDRESS >> 35GB VV == 0
SET_MAX_ADDRESS >> 32GB VV == 0
VV == 1 >> SET_MAX_ADDRESS == 35GB
I am asking both Quantum and Maxtor to clarify the possible case, above...
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Mar 31 2000 - 21:00:21 EST