--- In partman@yahoogroups.com, "Antoine Leca" <aleca@...> wrote:

>> ... when the 'puter was rebooted, Ranish (MBR) complained
>> that there were new partitions (so far so good) which it
>> would not import because they overlapped

> Are you using the "more than 4 partitions" feature? (that is, having
> "hidden partitions" which are registered inside RPM tables but not in
> the normal places (MBR and EMBR)
> If you do (and I guess you does)...

...I'm not using such "hidden hidden" parts ATM, all my partitions are
either primaries, either properly chained logical ones. But, now I
think I see the picture, RPM hidden VTOC might have 'caught' some
former (and unremembered) attempt and recorded a virtual partition.
That would explain it.

> you should compare the printout of the
> layout _before_ installing the new OS (you did print it out, right?),
> with the layout now reported by RPM.

I have printouts, not the 'before' and 'after' this incident though.

It doesn't matter much anyway, for I sorted the problem out in another
way altogether : I did the new partitioning from another, already
installed, Linux OS. After which installing the new Linux proceeded
smoothly, and this time Ranish automagically imported the new parts
and did not complain at all.

So, maybe the former problem really was caused by some incompatibility
between RPM and the PCLOS ideas of laying out partitions rather than
stale information in Ranish's own VTOC. Or both...

> If you cannot sort it out yourself, post both lists here.

It's fixed. However, in anticipation for my next mistake\\\\\
experiment, I'd take the opportunity to ask once and for all for a
*clear* explanation of the operation of [F7] in RPM 2.43 GUI : what
does it take from where to where ? UIAM [F7] is the only important
function which is not self documented, and while Muthu's how-to
mentions it more than once I don't find he explains it too
statisfactorily.

Also, what is the way to reset (zero) Ranish's VTOC again from the GUI ?

Regards

--
Czerno