🚀 go-pugleaf

guz~zle@hubble.dialix.com.au writes:

>I'm trying to install Warp Connect on my second hard disk, and the
>installation goes OK until Advanced plonks me into fdisk.

Unless you have BootManager installed on the first disk, you cannot
install on anything other than a primary partition on the first
disk.

In <892995718.938508@hubble.dialix.com.au>, guz~zle@hubble.dialix.com.au writes:
]I'm trying to install Warp Connect on my second hard disk, and the
]installation goes OK until Advanced plonks me into fdisk.

]Here's my partition table:

] Disk 1 2
]�����������������������������������������������������������������������������
] Partition Information
] Name          Status               Access           FS Type
]MBytes
]�����������������������������������������������������������������������������
]               None                : Primary         FreeSpace           1
]               None               D: Primary         FAT               100
]               None               G: Logical         HPFS              200
]               None                : Logical         FreeSpace         201
]               None               H: Logical         HPFS                9
]               None                : Pri/Log         FreeSpace           1

]The drive I want to install on is D:, but when I select it and press
]enter, all the options except Delete Partition are not actioned! If I
]delete the partition, or try on the other free space areas, there are no
]actionable items at all!

]I'm seeking opinions and ideas here. As I see it, my partion table is
]flaky, and I can:
]1) buy a flash disk repair tool and X my fingers
]2) try a better fdisk (from Warp 4? Linux?)
]3) switch the drive to the first, and see if that makes a difference
]4) give up, install Connect on the first drive, formatting over my Warp 3

]All of these have problems, so I'm...
]5) posting to the net!

I've never tried to install to a primary partition on the second drive: 
    I've had no problem at all with installing to logical drives.

You DO need to have bootmanager installed on the first.

Instead of a screen print, run
fdisk /query
which prints all the info for all partitions: like this-

[C:\]fdisk /query


Drive Name  Partition Vtype FStype Status   Start     Size

    1 0000003f     :    1    0a      2          0        3
    1 NT           :    1    17      1          3      401
    1 Connect     C:    1    07      1        405      401
    1 Warp 4      D:    2    07      1        807      401
    1 Utility     E:    2    07      1       1208       51
    1 Debug       F:    2    07      1       1260       51
    1 0028f9bf    G:    2    07      0       1311      901
    1 0045273f     :    2    83      0       2212      862
    2 Linux2       :    2    83      1          0      100
    2 0003237f     :    2    83      0        100      400
    2 000fa4af    H:    2    07      0        500      400
    2 001c25df     :    2    08      0        900     1113
                                             **BIOS: 504MB
    3 00000020    I:    1    07      2          0      217

[C:\]

FDISK seems to be wary of what options it allows on drives the BIOS can't 
    handle: basically, drives greater than about 500 Mb and without LBA 
    enabled, For these drives there can be problems booting.

Earlier fdisks (I think including Warp 3, possibly fixed in WC) would 
    allow one to install an unbootable OS/2.

One option you did not mention is to simply install Warp Connect's 
    networking over Warp 3. This gives a system that looks (almost) like 
    Warp Connect, behaves like Warp Connect.

I did this once and the only difference I saw between Warp Connect and the
    upgraded system was the boot-time logo.

Cheers
John Summerfield
OS/2 support @ http://www.ami.com.au/os2/
   Configuration, networking, searchable IBM ftp site index.
Note: I ignore email I receive than has invalid return addresses.