Text 71, 107 rader
Skriven 2006-05-12 08:40:06 av Herbert Rosenau (2:2476/493)
     Kommentar till text 65 av Sarah Nunez (1:130/604)
Ärende: Install trouble
=======================
Am 11.05.06 09:07 schrieb Sarah Nunez

 SN> 11 May 06 08:14, Herbert Rosenau wrote to Sarah Nunez:

 HR>> Since 1988 there was no need to handle with sysinst even on
 HR>> virgin drives.

 SN> The OS/2 install isn't giving me a choice.  It's coming up with
 SN> that error no matter what.

 HR>> Simple install BM, create partitons and thereafter create
 HR>> volumes from existent partitions.

 SN> That's exactly what I'm trying to do.  The Boot Manager drive is
 SN> the new drive (drive 0), with partitions already created by DFSee
 SN> (including the Boot Manager partition).  The drive I'm installing
 SN> OS/2 to (drive 1) has been in use for some time in my boys'
 SN> system and has the partition already waiting for OS/2. That
 SN> partition even had OS/2 on it at one time, but I deleted OS/2
 SN> from that partition to use the partition for other things until I
 SN> needed it for OS/2 again.  I even tried letting DFSee install
 SN> Boot Manager (whereupon Win2K also refused to install), but it
 SN> didn't make a difference to the OS/2 installer.

Ups, There can only one BM on the whole system. When you have BM on disk 2 you
must remove it from there and you must reboot to get that in effect before you
can install BM on disk 1. I have never used DFSee to partitoning. But I know
that LVM gets crazy when it should install BM on another drive as it is already
on. Be sure to use LVM mode in DFSee anything else will confuse LVM.

You are sure that the whole partitoning is done in LBA mode? You are sure that
the drives are clearly set up as master/slave? Cable select will NOT work. 

 HR>> While creating partitons there are some limits: FAT16    2 GB
 HR>> HPFS    64 GB JFS 2 TB

 SN> Another one to add to your list (for reference) is:

 SN> FAT32     32 GiB

I've given up on FAT32 years ago because crap. When I have to prepare windows I
use NTFS (same limits than HPFS/HPFS386). 


 HR>> Create all primary partitons before you tries to create logical
 HR>> drives in the only possible extended partiton on a disk.

 SN> I've forgotten now how many primary partitions can be on one
 SN> disk.  Is it one, two, or four?  And the extended partition
 SN> counts against that total, correct? I do recall that only one can
 SN> be active at any given time (without jumping through hoops that
 SN> are better left alone, of course).

A physical drive can have up to 4 partitons. One of them can be an extended
one, BM costs another one of them. My personall experience has shown that it
can be extremely problematic to have an standard partiton after an extended
one.

 HR>> Sometimes it is possible that danis506.add will not work with an
 HR>> specific IDE controller but ibm1s506.add works well.

 SN> But if DFSee/2 can see all of the drive using Dani's driver,
 SN> would that not indicate that the driver is working well with the
 SN> IDE controller?

I would say so, yes.


 SN> (As it turns out, it's a good thing I HAVEN'T been able to
 SN> install OS/2 on that partition yet!  I just remembered that I
 SN> have files on that partition that I need to move before I put
 SN> OS/2 back on there!)

OS/2 before 4.51 is really unable to get installed outside the 1024 zylinder
limit.
fdisk/LVM gets easy confused when a partiton is NOT exactly on zylinder
boundaries. That is why you should use OS/2 fdisk or OS/2/eCS LVM to make any
partitoning.

I would recommend:
- use DFSee to clean up each partitoning resulting an an clean
  disk without any partiton on it, showing the 
  whole correct space free
- boot up OS/2 4.52 or eCS 1.1 or newer
  (older versions may have a defective LVM)
  does LVM see the correct disk size?
- create partitons in following sequence
  - BM
  - primary C: (for windoes)
  - optionally primary /boot (linux; about 50MB)
    NTFS prefered
  - optionally D: extended windows data
    standard, bootable
    NTFS when possible
  - extended x: (1 - 2 GB) for eCS/os2 system
    standard, not bootable
  - extended y: (any size) JFS
    LVM, not bootable
  optionally
  - /     linux root, extended
    standard not bootable
  - /swap linux swap, extended
    standard not bootable


--- Sqed/32 1.15/development  747:
 * Origin: Sollen alle Dateien nicht geloescht werden (J/N) ? (2:2476/493)