Hi Jonathan!

Thus quoth Jonathan de Boyne Pollard to Will Honea:

 JdBP> I suspect that we might be begging Daniela to modify Build_Next_VolCB() 
and
 JdBP> Process_Partition() in OS2DASD.DMD .  (-:  

 JdBP> By the looks of it (i.e. from reading the source), Process_Partition()
takes the first
 JdBP> recognisable partition in the MBR that it finds, and Build_Next_VolCB() 
only calls it once
 JdBP> per MBR.  

 JdBP> The modification should be relatively simple.  One simply needs to take 
the
 JdBP> for(i=0;i<4;++i) loop out of Process_Partition() and move it into both
Build_Next_VolCB()
 JdBP> and BPBFromScratch(), modifying it along the way so that it doesn't
exit prematurely any
 JdBP> more by removing the `found' logic, and make Process_Partition() take
the current loop
 JdBP> index as an extra parameter instead.

 JdBP> Daniela ?

What's wrong with the current logic? And - assuming you have both the tools
and the sources available - why don't you just go ahead and try it yourself?

Thinking about improving OS2DASD I'd rather like to support type 0F extended
partitions to remove the hassles of the MICROS~1 idiosyncrasies. And, instead
of changing the sources, finding a patch to do that is better IMHO because it
most likely will work with future fixpacks as well. This is why I created a
patch tool to overcome the over-64MB memory detection defect with new BIOSes
instead of compiling a private version of OS2LDR: the patch works from old
Warp3 fixpack levels up to Warp Server for e-Business regardless of the
multitude of OS2LDR versions they use.

bye, Dani

--- Sqed/32 1.14/r01354