Dave Davidson wrote in a message to Ian Moote:

 DD>> The two drives currently in that machine in question are Segate
 DD>> 4.3GB and a Western Digital 2.5GB.

 DD>  Yes. When I run the OS/2 install disks and it gets to
 DD> FDISK, it shows a  Type B partition, with the only options
 DD> available is to delete the  partition. When I delete it and
 DD> exit FDISK, the partition doesn't appear  to be there.
 DD> However, upon re-booting, it's there again.

If you did any drive swapping, or moving around, make sure that the
master/slave jumpers are correct, and that the bios has the correct, or the
same drive paramaters that it had for those drives before you switched them. 
(I recently have done that, so I remember some of the things I forgot to
do:-))

Also, once you delete the partitions, you must create new partitions.  Did you 
do that?

I am having a difficult time believing that FDISK recognized you had a type B
partition, yet refuses to delete the partition.  I suspect you are doing
something simple that is wrong here.  I have also been in exactly your
situation, where things were not saved, and it was always something simple I
was doing wrong, never was a mysterious partition that couldn't be deleted.  I 
never ran FAT32  though, but still, seems very strange FDISK can see the
partition, but not do anything about it.  Doing a LL format for 12 hours is
overkill for deleting a partition, but if that didn't work, then almost for
sure FAT32 is not the problem, something much simpler is at work here.  

 IM> Andy reported that FDisk was not removing the FAT32 partition.
 IM> You're the one running the software, does FDisk say that the
 IM> partition is still there or not? How much free space is it
 IM> reporting?

 DD>   It's only showing half the HD or around 2GB. I don't
 DD> remember the exact   numbers, but it is weird! When the Type
 DD> B partition is _deleted_ by   FDISK, OS/2 reports there's
 DD> not enough room to load Boot Manager or   anything else.

I'll bet the CMOS has the wrong paramaters for the drive.  Try telling the
CMOS that the drive is only 504 megs, then do it again, with no LBA
addressing, no diskmangler stuff on the drive.  I'd bet money it will work.

If it does, then you can go back and try using whatever you guys use to get
the IBM platform to recognize large drives.  No need to do that though, you
don't really need LBA when using OS/2.

 DD>   As I mentioned in a previous post, each of the three
 DD> drives discussed,   4.3GB Seagate, 2.5 WD and 10.3GB Seagate
 DD> were installed as a single drive   while trying to load
 DD> OS/2, as well as being in a Master/Slave   configuration.
 DD> Each with the same results. I spent almost 24 hours trying  
 DD> to get OS/2 loaded on that machine.

Are you certain you didn't have the drives defined wrong in the CMOS when
flipping them around, and that the jumpers for slave/master were correct?


 DD>> IM>> Once he _does_ get it installed, who do you think he's going
 DD>> to IM>> call whenever he has a problem with his OS/2 system? [:)
 IM> DD>
 DD>> Obviously, I'll call Andy, 

Nah, don't do that, just ask in here, he will answer w/o asking as soon as 12
of us give an answer that he doesn't like:-)  

 DD>  No, I was exposed to OS/2 before I met Andy, and a few
 DD> local Sysop's used  to run Adept. Now, I'm the only system
 DD> left in my local area. 

We had 130 systems in our net, now we have around 20, and most of those will
likely disappear at Y2K.  Hurry up and ask your questions before that.  You
have about 2 months left, and getting stuff might get difficult after that.  I 
might not be here for one (that might make it better..., but you get the idea)
Besides, I want to know what the problem turned out to be, so do it before
1/1/00.

                                              Jack 
--- timEd/2-B11
278/111