Hello (and thanks Jan)
   I think I have pretty well eliminated "other systems" as a
problem if I understand you correctly.  I retried the install and
eliminated anything I can think of thusly
   1) removed all other drives but for floppy and cdrom
   2) removed airboot
   3) created a 4mb unformatted space and a 4G primary space which does not
cross 1024th (it's an older 4G drive and shows only 523 cylinders total)
even though this is not the drive I wish to ultimately use.  I'll ghost
from it if necessary but at least thought it a good start to discover
what's wrong
   4) even moved it all to an older P3 system just to eliminate any
possible AMD64 w/ nvidia chipset probs (not that I've had any running the
previously ghosted system - just installing) 
   
   So now I am once again pulling out my hair because I still get the same
problem.  The install gets thru phase one to where one first boots from
hard drive and immediately stops right after the little white OS2 logo with
the same "startup file system is oncorrect" message.  Now I am
wracking my brain trying to recall the deeper impot of "set
instalable" vs/ "set startable" vs/ "set bootable"
(or the effect therof caused by "adding to boot mgr menu") since
I can only believe it must have something to do with that.  The hard drive
is in great shape.  The cdrom drive is brand new and works fine both
reading and writing on other systems.  The floppies are new and clean and
appear to function normally with the only unusual mod of renaming
"Vcu.exe" which doesn't seem to affect any of the visible
processes.  I am still using Danis506, renamed "ibm1s506.add",
newer "os2ldr", "ibmatapi.flt",
"ibmdasd.dmd", "ibmidecd.dmd", and
"os2cdrom.dmd" even though the hdd is only 4G since I want to
ulti

mately use the process w/ diskettes for a 10G or larger drive.  On the
AMD64 system there will also be a first hdd of other systems on a 160G
drive.

  Do you all agree this is a problem with LVM setting the proper
"installable" vs "startable" mess?  What can I do to
overcome this crazy roadblock?

sincerely 
getting desperate
Jimmy


> Hmmm, I can get that one as well, if I install two systems and set the
> other to C: and/or ignore/forget to hide the other system properly in
> OS/2-eCS (Option is there in LVM).
> 
> The problem is that the system read the boot info just as you state,
> but when it tries to load the system after that,  it can't load as it
> incorrectly read from drive C: on the other system, even though drive
> C: in OS/2 and eCS has been set during install. I can't explain why,
> but hiding the other systems boot drive may help you solve the problem
> (Provided that is the problem solution for you). Look in documentation
> for it if you can for more in depth info.
> 


------------------------ Yahoo! Groups Sponsor --------------------~--> 
Get fast access to your favorite Yahoo! Groups. Make Yahoo! your home page
http://us.click.yahoo.com/dpRU5A/wUILAA/yQLSAA/9rHolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

 To visit your group on the web, go to:
    http://groups.yahoo.com/group/os2hardware/

 To unsubscribe from this group, send an email to:
    os2hardware-unsubscribe{at}yahoogroups.com

 Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



---