* Original message posted in area OS/2 Discussion
* Cross posted to area OS/2 BBSing
OS/2 Hardware
OS/2 Hardware Discussion (Gated)

I'm in the process of trying to install OS/2 Warp 4 on a PIII.
I have all original software from my days in Team OS/2 and there is no way I can get the install to format the HD to HPFS (or FAT for that matter).
The HD size that it gives me is not the same as I have partioned it using the FDISK from my windows disk.
It has been a LONG time since I ran Warp and eventually would like to have another BBS running again. (Used to run Bob's Bored/2 in Toronto)
Can anyone please help me get over this hurdle?
My email address is rob905@msn.com.

Thanks

---
* Origin: Midnight's Hour - midnightshour.org - 618.529.9296 (1:11/200)

Hello Robert!

02 Jun 03 10:09, you wrote to All:

I'm in the process of trying to install OS/2 Warp 4 on a PIII.
I have all original software from my days in Team OS/2 and there is no
way I can get the install to format the HD to HPFS (or FAT for that matter). The HD size that it gives me is not the same as I have
partioned it using the FDISK from my windows disk. It has been a LONG time since I ran Warp and eventually would like to have another BBS running again. (Used to run Bob's Bored/2 in Toronto) Can anyone
please help me get over this hurdle? My email address is
rob905@msn.com.

You may have hit the HDD limits. What size did you setup using Fdisk? If
above 4gb reduce down to 1-2gb load up OS/2 then if you have it resize using Partition Magic or similar. I think the max limit was 4gb within OS/2 v4 without fixpaks. I would also suggest (if you can) is burn a new OS/2 v4 disk with the latest fixpak installed (#16) prior to running the install.


Vince

--- Linux/Mbse/GoldED+/LNX 1.1.5-20709
* Origin: Air Applewood, Linux Gateway for Essex (2:257/609)

Am 30.06.03 19:21 schrieb Stewart Arnett

Hello Robert.

02 Jun 03 10:09, you wrote to All:

* Original message posted in area OS/2 Discussion * Cross
posted to area OS/2 BBSing OS/2 Hardware
OS/2 Hardware Discussion (Gated)

I'm in the process of trying to install OS/2 Warp 4 on a PIII. I
have all original software from my days in Team OS/2 and there
is no way I can get the install to format the HD to HPFS (or FAT
for that matter). The HD size that it gives me is not the same
as I have partioned it using the FDISK from my windows disk. It
has been a LONG time since I ran Warp and eventually would like
to have another BBS running again. (Used to run Bob's Bored/2 in
Toronto) Can anyone please help me get over this hurdle? My
email address is rob905@msn.com.

Hard disk size is the problem here.

No and yes.

Make a partition of less than
2.4 gb and leave the rest of the disk as free space. Install OS2
on the partition and get it running, then, use OS2 to partition
the rest of the disk into 2.4 gb partitions and format them as
HPFS with OS2. I only use the first C: partition for the OS2
itself, the BBS is on D: mail on E: and files on the rest of the partitions. This is on a Compaq deskpro 4000 (P1 166 machine)
with a 20gb drive and a stock standard (no updates) OS2 warp4 installation.

With any OS/2 version prior to WARP4.51 (that includes WARP4.50) there are some
limitations:

- the installation partiton must be completely inside the 1024 zylinder limt. As none of this versions supports the BIOS extension that makes it possible to boot from a partiton above that limit.

The size of a data partiton is anyway only kimited by the file system on it:
- FAT16 2 GB
- HPFS 64GB
- HPFS386 84 MB.

With WARP4.51 and newer (that includes eCS) there are news:
1. A bootable partiton can be anywhere on the disk
2. the 1024 zylinder limit is fallen completely - when the BIOS
is new enough to handle the new extension
3. HPFS can be spanned over more than one volume
but for that you have to reformat it thereafter
4. the new filesystem JFS allows a volume size up to 2 TB
int can be spanned over multiple partitons on multiple
drive
it uses a much bigger cache (default: 10% of RAM)
it can hold files bigger than 2GB (but not all applications may be able to handle such big files.

Even as there was never a limit for the size of bootable partion (except the 1024 zyliner limit and the limit a specific filesystem may have) it ould be always a good idea to hold the size of the system partiton so small as possible.

That means:
WARP older als 4.50: up to 0.5 GB
newer as 4.5: up to 1 GB.

And beside the system partiton one or more partitons to hold data and applications.


--- Sqed/32 1.15/development 702:
* Origin: Recht haben ist gut, Recht bekommen ist besser! (2:2476/493)

Hello Herbert.

04 Jul 03 22:28, you wrote to me:

Am 30.06.03 19:21 schrieb Stewart Arnett

Hello Robert.

02 Jun 03 10:09, you wrote to All:

Hard disk size is the problem here.

No and yes.

Make a partition of less than
2.4 gb and leave the rest of the disk as free space. Install OS2
on the partition and get it running, then, use OS2 to partition
the rest of the disk into 2.4 gb partitions and format them as
HPFS with OS2. I only use the first C: partition for the OS2
itself, the BBS is on D: mail on E: and files on the rest of the
partitions. This is on a Compaq deskpro 4000 (P1 166 machine)
with a 20gb drive and a stock standard (no updates) OS2 warp4
installation.

With any OS/2 version prior to WARP4.51 (that includes WARP4.50) there
are some limitations:

- the installation partiton must be completely inside the 1024
zylinder limt. As none of this versions supports the BIOS extension
that makes it possible to boot from a partiton above that limit.

The size of a data partiton is anyway only kimited by the file system
on it: - FAT16 2 GB - HPFS 64GB - HPFS386 84 MB.

With WARP4.51 and newer (that includes eCS) there are news:
1. A bootable partiton can be anywhere on the disk
2. the 1024 zylinder limit is fallen completely - when the BIOS
is new enough to handle the new extension
3. HPFS can be spanned over more than one volume
but for that you have to reformat it thereafter
4. the new filesystem JFS allows a volume size up to 2 TB
int can be spanned over multiple partitons on multiple
drive
it uses a much bigger cache (default: 10% of RAM)
it can hold files bigger than 2GB (but not all applications may be
able to handle such big files.

Even as there was never a limit for the size of bootable partion
(except the 1024 zyliner limit and the limit a specific filesystem may have) it ould be always a good idea to hold the size of the system partiton so small as possible.

That means:
WARP older als 4.50: up to 0.5 GB

C: partition 2Gb D: - E: - F: partitions set to 2.33Gb = 10Gb one hard disk.
OS 2 Warp 4, no fixpacks off the first series CD, proof that it works is the fact I am writing this on the machine and this message is posted from the Rockbbs.

The reason I use it this way is simply because it works, it sits here for months doing it's thing and I only empty the trash every so often.

The real fun was setting it up on an old 486 that wouldn't see the hard disk, that was on an HP Vectra 66, you tell me how I made that work ;)

newer as 4.5: up to 1 GB.

And beside the system partiton one or more partitons to hold data and applications.

-+- Sqed/32 1.15/development 702:
+ Origin: Recht haben ist gut, Recht bekommen ist besser!
(2:2476/493)

Cheers,

Stewart

--- GoldED/2 3.0.1
* Origin: The RockBBS Auckland NZ 64-9-5799600 (3:772/100)

Am 05.07.03 23:35 schrieb Stewart Arnett

That means: WARP older als 4.50: up to 0.5 GB

C: partition 2Gb D: - E: - F: partitions set to 2.33Gb = 10Gb one hard disk. OS 2 Warp 4, no fixpacks off the first series CD, proof that it works is the fact I am writing this on the machine and this message is posted from the Rockbbs.

Oh, I'd started the first install of OS/2 3.0 on amn I486/50 with

phys.
HD size
C: 500 MB system
D: 2 GB programs
E: 4 GB data
F: 4 GB data
G: 4 GB data

Then I go a CD drive inserted as H:

No problem even with WARP3 GA. The trick is: I had not a single drive FAT formatted. All HPFS.

As the C: was died I'd changed the hard disks around and got
C: 2 GB only because I like to have 1 physical drive == 1 partiton!
D: 4,5 GB because the new drive was so fat.

In the meantime I'd changed the system to a P100
1 physical hard drive 8 GB:
C: 1 GB
D: 1.5 GB
E: 1.5 GB
F: 4.5 GB
G: 18 GB

There is really NO limit that requires that a partiton can not be more than 2 GB. When you've got problems with ibm1s506.add you should replace it with danis506.add, because it is more stable, works better (producesd more throughput), works together with more IDE controllers.

If you're running now your WARP4 at GA level you're living errornous, because there are so many fixes who are remoing instability and bugs in all subsystems AND there are many programs around who won't never work with a system prior to FP 5 - even as the unfixed FP 5 is really crap.

So required fixes for WATP4.0 are
- FP12 - basis system
- DD03 - device drivers as since FP10 no devce driver is in the base fix package.
peer fix to get peer services working right
tcp/ip fix to get the IP stack really functional
tcp/ip app. fix to get the tcp/ip applications doing what they designed for

FP15 with all its associated fixes is the most stable OS/2 I've ever seen since
OS/2 2.0 was released and prior FP15. But FP15 is the first working fix after the faulty FP13 and FP14 who are merged the WSoD kernel with the WARP4 kernel. FP15 needs the latest kernel fix (14.094) from testcase to be so stable as FP12.

The reason I use it this way is simply because it works, it sits here for months doing it's thing and I only empty the trash every so often.

FP12 or 15 works quite better. The last device driver fix fixes lots of problems with some hardware you notes as problems when they are gone!

WARP4 GA is known as to be an early beta in reality. It is problematic to get it installed on so modern computers as a P100 or 133 is. The WPS is not so stable as it should be, the WarpCenter crashes more often as it is functional....

To get most bugs of the WPS removed you needs FP5. To get a nearly error free WARP4 you needs FP12 + the fixes mentioned above.

To be compatibe with most newer applications you need FP15. Don't experiment with FP13 or 14. Both are crappy.

The real fun was setting it up on an old 486 that wouldn't see the hard disk, that was on an HP Vectra 66, you tell me how I made that work ;)

Fixup the system and it works.

--- Sqed/32 1.15/development 51:
* Origin: Windows NT: From the makers of EDLIN! (2:2476/493)