OS2 World.Com Forum

Subject  :  Boot Menager problem (FAT32 present)
Author  :  Sir_T zelazny.w@gmail.com
Date  :  04 May, 2007 on 12:53
I have not found topic adressing this paticular problem, so I'm starting a new one. I know problem is common, but found no definite solution.

Yesterday I installed Warp 4 for the first time, on disc partitioned look like that:

1.Boot Manager partition: 7 MB
2.FAT32 Windows98 partition: 3 GB
3.HPFS OS/2 partition: 2 GB
4.FAT "Bridge between worlds" partition (rest, 700 MB)

After instalation, only partition bootable from Boot Manager was 3rd (OS/2). First thing I did was updating to fixpack 15 and device driver pack 2. Then, I tried to restore my Windows98, so i run fdisk and made FAT32 partition bootable by Boot Manager. After that, Windows boots without problems, but OS/2 does not boot up. It displays a
"OS/2 is unable to operate your hard disk" message and stops.

I understand problem is with Boot Manager detecting my partition but OS/2 not recognizing it.

What I want is ability to boot both systems - I don't want OS/2 to see FAT32 partition. Ideal situation would be both systems bootable, and each seeing it's native partition as C: and FAT16 partition as D:.
EDIT The boot manager now sees FAT32 partiton as C: and HPFS as D:. My installation expects HPFS partition to be C: So I need to make FAT32 one "invisible" or at least reasign drive letters...


What can I do to go around it? Is there a way to fix it and stay with Boot Manager I already have?

Or should I install over other boot managing program? Will simply using another boot program stop OS/2 from seeing my FAT32 partition? I have Air Boot downloaded already, but don't want to go head first again - i messed things up enough already.


Subject  :  Re:Boot Menager problem (FAT32 present)
Author  :  melf mikaelelf@os2ug.se
Date  :  04 May, 2007 on 13:27

Sir_T (04 May, 2007 12:5:
It displays a "OS/2 is unable to operate your hard disk" message and stops.

I wonder if this is another problem? I remember the same message, when I updated a driver pack. I had to go back to the old ibm1s506.add, and then it worked. (or instead use danis506.add)


Or should I install over other boot managing program? Will simply using another boot program stop OS/2 from seeing my FAT32 partition? I have Air Boot downloaded already, but don't want to go head first again - i messed things up enough already.

For OS/2 to see a FAT32 partition I guess you must have some line in config.sys like: IFS=C:\OS2\BOOT\FAT32.IFS /CACHE:2048 /H . You can just rem that out.

And don't trust me too much, there are other guys here who knows better!


Subject  :  Re:Boot Menager problem (FAT32 present)
Author  :  Radek hajek@vuv.cz
Date  :  04 May, 2007 on 13:42
A few notes and questions:

(1) How have you restored the windows? Windows often foul partitions they should not touch. Among others, they disable (and clobber) boot manager. This can be the reason why your OS/2 stopped working after installing windows.

(2) Windows 98 is DOS. IIRC, they must be installed on C:, more precisely, on disk ID 80h.

I have installed DOS 98 along with OS/2 successfully. Here is the correct ordering of events:

(a) Install DOS 98 first. You'd better prepare a partition for it by means of OS/2 FDISK (start OS/2 installation, create partition, quit installation) but, IIRC, it's safe to let DOS 98 to create it's own partition (DOS 98! not windows NT!)

(b) start OS/2 installation, install boot manager, mark the DOS 98 partition bootable, create the bridging partition. Continue installing the operating system.

© format the bridging partition from OS/2

(d) start DOS 98 and let its HD manager to find the bridging partition.

Now, DOS 98 will be on C:, OS/2 will be on D:, and the bridging partition will have different drive letters for DOS 98 and OS/2. If you won't install the FAT32 driver then OS/2 will not see the DOS 98 partition. Naturally, windows don't know HPFS in principle so that DOS 98 will not see the OS/2 partition.


Subject  :  Re:Boot Menager problem (FAT32 present)
Author  :  Sir_T zelazny.w@gmail.com
Date  :  04 May, 2007 on 14:56
It does not exactly solve my problem.

I had Windows already installed at FAT32 (C:) partition before I installed OS/2.

When I installed OS/2, FAT23 partition was not recognized by older fdisk, so OS/2 "thinks" it's installed on C:

I used fixpack15 fdisk to make Windows partition bootable by updated Boot Manager. It works fine, Boot Manager starts up and loads Windows when asked to.

However, Boot Manager now sees OS/2 partition as D:. OS/2 tries to recognize Windows partition duirng bootup and fails.

--------------------------------------------------------

What I want to do is to make each system boot without awareness ot other's partition, so that each system thinks is's on C: Is that possible with boot manager? If not, will installing other boot managing program (air boot?) instead help?


Or at very least, is there a way to change settings of Boot Manager without booting up OS/2 (which I can't do)? OS/2 fixpack 15 fdisk can do it, but I cannot use it without starting the system. Fdisk on installation disks is obsolete. Is there a thrid party program that can do that and be run under windows? Or rescue CD capable of that?


Subject  :  Re:Boot Menager problem (FAT32 present)
Author  :  Radek hajek@vuv.cz
Date  :  04 May, 2007 on 16:25
If I understand well then the problem consists in the following: the FDISK on the installation CD is too old and it has problems with FAT32 partitions. Updating FDISK is possible but only after installing the operating system.

Possibilities:
(1) Install windows on FAT16, update FDISK, "migrate" windows on FAT32. This should be possible somehow but I haven't tried this.
(2) Install OS/2, patch it, and then create a new installation CD using updcd. Now install.
(3) Copy the updated FDISK on the installation diskettes. Perhaps, it will work. I haven't tried this either.


Subject  :  Re:Boot Menager problem (FAT32 present)
Author  :  Blonde Guy
Date  :  04 May, 2007 on 21:58
Here's another way to solve the problem.

If you had

Boot Manager
Windows 98 Primary Partition
OS/2 Primary Partition
Shared Drive Logical Partition

The system would behave as you want with any version of OS/2 The problem is that your current system has OS/2 on a logical partition.

The solution is to

1. back up OS/2 to your shared drive (zip.exe will work well for this)
2. delete the OS/2 partition
3. recreate it as a primary partition
4. format the new partition HPFS
5. restore OS/2 from your backup (with unzip.exe)
6. tell boot manager about the restored OS/2 partition.

---
Expert Consulting for OS/2 and eComStation


Subject  :  Re:Boot Menager problem (FAT32 present)
Author  :  Sir_T zelazny.w@gmail.com
Date  :  04 May, 2007 on 22:25
Sounds great, Blonde Guy, with one exception... how can I access and backup my OS/2 partion without ability to run OS/2?

Thanks for advice, through. If everything fails and I'll be reinstalling OS/2 i'll know what to do to avoid this from happening again.


Subject  :  Re:Boot Menager problem (FAT32 present)
Author  :  OriAl alanh77@comcast.net
Date  :  04 May, 2007 on 23:40
Do you have a CD or floppies from which to boot OS/2?

Subject  :  Re:Boot Menager problem (FAT32 present)
Author  :  Sir_T zelazny.w@gmail.com
Date  :  05 May, 2007 on 01:00
Only installation floppies and CD. I din't try to make system / rescue disc.

EDIT: I just risked doing thing I know nothing about one more time and installed Airboot - it worked. It had exactly features I needed - making system partition hidden from other system's and assigning drive letter to OS/2 partition to make OS/2 think it's C:. Perhaps it was made with this and similiar problems in thougth...

Both my systems are booting up now; I think this thread may be closed.


Powered by UltraBoard 2000 <www.ub2k.com>