If present, MaxPartnerStorage specifies a new value for the size of the portion of third-party nonvolatile
storage that is reserved for partner applications. This size is specified as a number of bytes.
The remaining portion of third-party non-volatile storage is used for non-partner applications. The total
size of non-volatile storage is an implementation-dependent quantity, but shall not be less than 96
kilobytes. The size must be a multiple of 4kBytes.
If present, MaxNonPartnerTotalAllocationSize specifies the maximum total number of bytes
that can be allocated by any application that is not in the Factory Partner Allocation Control List. The
size must be a multiple of 4kBytes. In AMT Release 4.0 and later releases this parameter changed
from uint16 to uint32.
The result of this function is subject to the current allocated space. If the non-partner currently
allocated space is larger than the portion which is left after MaxPartnerStorage is increased, then
the function will fail. (The IT would have to first remove the non-partner application(s) and reduce the
non-partner allocated space).
If the MaxNonPartnerTotalAllocationSize is smaller than the size currently used by a nonpartner
application, then the function will fail. Similarly, if one of the new values contradicts the current
actual allocation (e.g. a non-partner application has allocated more space than defined in the new
How much memory is available in the 3rd Party Data Store?
Intel AMT 1.0 systems have 96k of NVRAM. All computers with Intel AMT 2.0 and beyond have 192k of NVRAM. This said, vendors can probably change this and it's generally accepted that any single application should not use more than 48k of it so that several applications can share this space.
You could also try to use some type of compression when placing data into the 3rd Party Data Store (3PDS) so that this space can be most efficiently.
I hope this helps..