_____
Hello All,

Tried to build OS/2 Warp 4 (from IBM CD Part No.84H3109) using
installation floppies that have a DASD driver to accommodate 8 Gb hard
disks. The build failed to install the network. The error message i
got was "not enough disk space for network .....". Yet, the partition i
attempted to use was 4 Gb in size. I had installed this Warp 4
version succesfully on a smaller partition some time ago. As a test, i
dropped the partition size to 2 Gb. The installation program builds the
entire OS just fine on the 2 Gb partition, including all the networking
software.

Is this a known problem, and if yes, what does one do about it?

As a work-around i hope that i can enlarge the 2Gb partition to 4 Gb
with Partition Magic V5. Have not yet done that yet. FDISK had no
problem seeing all the 6.5 Gb on the disk, and was able to create a 4 Gb
or a 2 Gb primary partition (preceded by the IBM Boot Manager).
--
Regards / JCH

Sir:

jch wrote:
Way back when 4GB drives were new & the latest, BIOS had a problem with
booting (loading code) from beyond the terrible 1024 cylinder limit that
DOS CHS (cylinder/heads/sectors) configuration required. Now days BIOS
uses a different API to fix this problem for OS/2. Since OS/2 uses BIOS
to start its Initial Program Load, old BIOSes will exhibit this problem.
Anyhow, what this means to you is the limit of 1024 cylinders, which is
about 3.8 GB of capacity. Your first attempted boot disk was partially
outside that size limit. So to protect you (and itself) OS/2 install
will fail (making a virtue of a bug). Don't make the boot partition so
large. Keep it below the 1024 cylinder limit that Fdisk will show (I
think after a few fixpacks it will). In fact OS/2 (Warp 4) will install
onto a partition that is a half GB in size and still have room. Use the
remainder for a few logical partitions: one for your applications, and
one for data.
--
Bill
Thanks a Million!

William L. Hartzell wrote:
William,

Aha! That makes sense. I was aware of the 1024 cyl limit, but did not
remember to check it for this build. I think that Partition Magic can
actually "see" this problem and report on it. I will confirm that
tonight, and make the partition a more suitable size. And you are quite
correct. A typical OS/2 installation is quite small. I really wanted
to get DeScribe 5 and PMFax working again in concert. It is one of the
best word processors around. It allowed me to write some nice macros to
hook up automatically with PMFax.

Have you had any luck getting SAMBA for OS/2 to work properly? I have
tried the NFS approach, but ran into trouble with permissions and
extended attributes. My file server is an OpenBSD machine. It runs
samba server just fine with a Windows 2K Pro client.

Plan to update OS/2 with FixPack 15, and a recent kernel from 2005.
--
Regards / JCH

Sir:

jch wrote:
Others have gotten Samba to work with OS/2. I believe Paul Smedley has
a port that has favorable reports. I've not tried this. Google on
these groups to get recent information on this.
--
Bill
Thanks a Million!

On Sat, 19 Apr 2008 07:48:52 UTC, "William L. Hartzell" <wlhartzell@tx.rr.com> wrote:

http://samba.netlabs.org/en/site/index.xml


--
Allan.

It is better to close your mouth, and look like a fool,
than to open it, and remove all doubt.

Hi,

that's most likely due to the fact that the network install utility overruns
on the attempt to compute your disk size.
If you look into "readme.ins" on your Warp 4 installation CD-ROM, it tells
you that you can specify the following to eliminate this test and others.
In config.sys on disk 1 specify this:

1.) CONNECT_DASD=NO (turns off size check)
2.) CONNECT_PREREQ=NO (turns off check for any necessary
prerequisites)
3.) CONNECT_SNIFF=NO (turns off check for installed network
adapter)

1.) fixes your problem
2.) I don't know what prerequisites there would exist. I think you can
safely turn that off.
3.) you can safely do this as the sniffer only detects ISA adapters. I guess
that is over and out ...

Note that these are NOT environment variables ! That is, they are NOT
preceded by "SET".


Lars


"jch" <jch@nowhere.net> schrieb im Newsbeitrag
news:KV7Oj.72025$rd2.34956@pd7urf3no...