OS2 World Community Forum

OS/2, eCS & ArcaOS - Technical => Setup & Installation => Topic started by: Dj Koelkast on May 15, 2020, 04:28:05 pm

Title: Installing Warp 3 issues
Post by: Dj Koelkast on May 15, 2020, 04:28:05 pm
Hi all,

I wanted to install OS/2 Warp for a long time and finally made room to do it.
I have an IBM 330 486 DX2/66 and an MWave soundcard + modem and a nice network card. That should be enough to get me going.
It has a whopping 32mb of memory.

The BIOS doesn't understand anything above 4GB, so to test I installed a 2GB CF card (I want to use this system with a small DOM eventually).
It gets recognised and it seems to work. OS/2 install works, the cdrom works (I'm installing the blue spine version, 2 boot disks and a cd-rom).
I've used the advanced setup to remove partitions (reboot) make 1 partition of 2gb (reboot) and make it installable (reboot), ok, then it installs and seems to work fine, until it needs to boot.
I just see a cursor on the top left.

When I boot from the disks again and get to the command line I see almost all files are 0b in size.
So clearly it has problems with it, is the partition of 1900mb too large maybe? Or do I need to set things differently?

I haven't really worked with OS/2 before, so all help is welcome. I do know these kind of problems exist with more old os'es, like AmigaOS.
So maybe making 4 partitions of max 500mb is the quickest solution?
Title: Re: Installing Warp 3 issues
Post by: Dave Yeo on May 15, 2020, 05:34:14 pm
You need to upgrade IBM1S506.ADD and perhaps other stuff. The easiest way is to use updated boot floppies to install.
Start here for most all updates, http://web.archive.org/web/20060926004818/www.warpupdates.mynetcologne.de/english/site_contents.html (http://web.archive.org/web/20060926004818/www.warpupdates.mynetcologne.de/english/site_contents.html) and follow the Installation Diskettes link. Some of the links might be dead but give a name to Google.
It's also possible to update the files on your install diskettes but a little more involved if you need to.
IIRC, Warp 3 should be able to be upgraded to handling about 500 GB disks. HPFS has a 64 GB limit and I'd advise more like 60 GB's.
Edit, make sure your boot partition is at the beginning of the disk, perhaps after BootManager and do all partitioning with OS/2 tools.
Title: Re: Installing Warp 3 issues
Post by: Dj Koelkast on May 15, 2020, 07:41:04 pm
Thanks!

I've found the files here:

ftp://service.boulder.ibm.com/ps/products/os2/fixes/v3.0warp/english-us/warpinst/

I expected a new install disk, but it updates the "old" one, I'll be trying this in a few minutes. At least the disk updated correctly.
Title: Re: Installing Warp 3 issues
Post by: Dj Koelkast on May 15, 2020, 07:58:37 pm
That didn't work, this is with an updated disk 1

Title: Re: Installing Warp 3 issues
Post by: Dj Koelkast on May 15, 2020, 08:18:51 pm
I found there are installation diskette images on the cd itself, maybe it was just a mismatch between installation diskettes and the cd, because the Warpinst doesn't want to update the Diskette 1 I made.

-- edit --

Tried it, but with the same result, a flashing cursor at the 1st boot and nothing else happening.
And the updated diskettes gave me the error
Title: Re: Installing Warp 3 issues
Post by: ivan on May 15, 2020, 09:40:25 pm
How are you doing the updates?  I have found using the right tools help a great deal.  Also you will need to download the dani driver from hobbes (it is an advanced version of the ibm disk driver).  You will then have to add it to the boot diskette and adjust the config.sys as necessary.

Unfortunately I don't have the Warp 3 version you are using (I have 3 connect) otherwise I would send you the disk images that you could use to make the updated diskettes.  Also you must have 'copy from floppy=1' at the end of the config.sys otherwise the updates will not get copied to the hard disk.
Title: Re: Installing Warp 3 issues
Post by: Dj Koelkast on May 15, 2020, 11:25:21 pm
How are you doing the updates?  I have found using the right tools help a great deal.  Also you will need to download the dani driver from hobbes (it is an advanced version of the ibm disk driver).  You will then have to add it to the boot diskette and adjust the config.sys as necessary.

Unfortunately I don't have the Warp 3 version you are using (I have 3 connect) otherwise I would send you the disk images that you could use to make the updated diskettes.  Also you must have 'copy from floppy=1' at the end of the config.sys otherwise the updates will not get copied to the hard disk.

I am using 3.0 connect blue spine English.

I have made the disks on a modern pc with an Imation Super Disk drive (USB) with WinImage.
Then I extracted the update file through DosBox, mounted the floppy drive and did the update through there.
It was the quickest way I could find. I also do have some real dos machines to do this on (but no OS/2 ones)

I only did the update from the archive, it did not say I had to modify anything.

I use the IBM PC 330, which seems to be a standard 486 DX2/66 with standard IDE and standard ISA (even a Vesa Local Bus, but I use the on board VGA).




Title: Re: Installing Warp 3 issues
Post by: Martin Iturbide on May 16, 2020, 01:35:33 am
Hi

Just as a quick reply. I have a little page with the "Updated Installation Disks" I was able to find around:
https://www.os2world.com/wiki/index.php/OS/2_Updated/Modified_Installation_Diskettes (https://www.os2world.com/wiki/index.php/OS/2_Updated/Modified_Installation_Diskettes)

Maybe you can give it a try.

Regards
Title: Re: Installing Warp 3 issues
Post by: Dave Yeo on May 16, 2020, 02:02:45 am
You can download https://hobbes.nmsu.edu/download/pub/os2/system/drivers/storage/ibmide12062003.zip (https://hobbes.nmsu.edu/download/pub/os2/system/drivers/storage/ibmide12062003.zip) and replace the drivers as described in the readme.txt, add SET COPYFROMFLOPPY=1 to the config.sys on IIRC, disk 1 and install.
If you need more room on the floppy, delete a scsi driver or two and remove their statements in the config.sys on disk 1.
It is also possible you got the trap for a different reason. The usual advice is turn off the ram cache in bios. Warp was particular about hardware timings with reports of even a mismatched SIMMs causing failure to install.
BTW, you can do the diskette update on real DOS machines,which might be best. They're just regular FAT diskettes until you get to disk 2 or 3, or in your case start reading from the CD.
Title: Re: Installing Warp 3 issues
Post by: Dj Koelkast on May 16, 2020, 10:07:10 am
The ibmide12062003.zip-file contains a zipped DSK-image, but that image has a strange size and can't be read my WinImage, so I have no idea how to make a disk out of that.

edit: I didn't see my config.sys file, but it's there, so I'll be testing that route now.
Title: Re: Installing Warp 3 issues
Post by: Dj Koelkast on May 16, 2020, 10:39:12 am
It went allright until it wanted to copy stuff from disk 1 at the end of the installation.
When, after viewing the log, I get the command prompt and dir c: then again all files are 0 bytes?

Title: Re: Installing Warp 3 issues
Post by: Pete on May 16, 2020, 12:33:27 pm
Hi Dj

The photo shows the file sizes in the 3rd column. The "0" column is EA size.

Too long time since I last installed Warp3 to be of any help with the missing file problem, Sorry.


Regards

Pete


Title: Re: Installing Warp 3 issues
Post by: ivan on May 16, 2020, 01:46:03 pm
OK, I dug out the disk images for first disk - install and disk 1 for my Warp connect.  The install disk is as supplied while the disk 1 is modified to a) update some files, and 2) clear out unwanted files for space and update config.sys.

Quote
The volume label in drive A is DISK 0.
The Volume Serial Number is 580A:7814.
Directory of A:\

OS2LDR   MSG     8366  12-07-95   3:59p
BUNDLE         306205   7-07-95   5:09p
README   INS    22145  30-06-95   1:49p
TEDIT    EXE     9374  24-05-95   9:40p
README   CID    50076  24-05-95   2:17p
OS2KRNLI       556234  30-03-95   4:59p
SYSINSTX COM    39472  28-02-95   3:00p
OS2DUMP         12251  28-02-95   2:59p
OS2LDR          30208  28-02-95   2:57p
DMF_PS2  CMD     9459  25-01-95   7:31p
XDFCOPY  EXE    89365  12-12-94   8:35p
XDF      MSG     1815  12-12-94   8:35p
LMS205   ADD    36388  12-12-94   3:44p
RESERVE  SYS     5686  12-12-94   3:31p
OS2BOOT          1099   8-12-94   6:46p
TEDIT    HLP    14596  31-10-94   8:03p
OS2VER             89  31-10-94   7:51p
W050101  BIO     3072  31-10-94   7:32p
W020101  BIO     4608  31-10-94   7:32p
W020100  BIO     3072  31-10-94   7:32p
FC0400   BIO    11264  31-10-94   7:31p
FC0500   BIO     9728  31-10-94   7:31p
W060100  BIO     6656  31-10-94   7:31p
FC0403   BIO     5632  31-10-94   7:31p
F80C00   BIO     5632  31-10-94   7:31p
F80904   BIO     5632  31-10-94   7:31p
F80903   BIO     5632  31-10-94   7:31p
F80D01   BIO     5120  31-10-94   7:31p
F80D00   BIO     5120  31-10-94   7:31p
F80902   BIO     5120  31-10-94   7:31p
F81B00   BIO     4096  31-10-94   7:31p
W050100  BIO     2560  31-10-94   7:31p
F88000   BIO     2048  31-10-94   7:31p
W0F0000  BIO     1536  31-10-94   7:31p
W050000  BIO     1536  31-10-94   7:31p
F81000   BIO     1536  31-10-94   7:31p
F80A01   BIO     1536  31-10-94   7:31p
F80A00   BIO     1536  31-10-94   7:31p
F80703   BIO     1536  31-10-94   7:31p
F80A02   BIO     1024  31-10-94   7:31p
F80704   BIO     1024  31-10-94   7:31p
F80000   BIO     9728  31-10-94   7:31p
F80100   BIO     8704  31-10-94   7:31p
F80200   BIO     7680  31-10-94   7:31p
F80600   BIO     7168  31-10-94   7:31p
F80404   BIO     5632  31-10-94   7:31p
F80403   BIO     5632  31-10-94   7:31p
F80402   BIO     5120  31-10-94   7:31p
000000   BIO     2560  31-10-94   7:31p
F80702   BIO     1536  31-10-94   7:31p
F80701   BIO     1536  31-10-94   7:31p
F80700   BIO     1536  31-10-94   7:31p
ABIOS    SYS      427  31-10-94   7:24p
RMVIEW   EXE    75058   7-10-94   5:51p
       54 file(s)    1421401 bytes used
                       28672 bytes free

Quote
The volume label in drive A is DISK 1.
Directory of A:\

CONFIG   SYS      940   7-04-06  12:32a
IBM1S506 ADD    70894  17-11-05   3:00p
DANIATAP FLT    25338   3-09-04   3:18a
IBMIDECD FLT    39568  12-03-04  10:28a
IBM1FLPY ADD    35418   8-10-02  11:02a
CONINST  EXE    24896  11-07-95   9:53p
SYSLEVEL OS2      168  11-07-95   5:26p
DISK     NUM       30   7-06-95   3:17p
SYSINST1 EXE     4224   7-06-95   2:31p
DOSCALL1 DLL   122964  25-05-95  11:36a
HARDERR  EXE    14888  25-05-95  11:35a
TEDIT    EXE     9374  24-05-95   9:40p
CMD640X  ADD    35348  11-05-95  11:49a
DETNE2   SYS     5120   3-05-95  11:50a
CMDATAPI FLT    21498  21-04-95  11:18p
CMD      EXE    79360  21-04-95   5:42p
NPXEMLTR DLL    20684  21-04-95   5:35p
MSG      DLL      512  21-04-95   4:20p
NLS      DLL      512  21-04-95   4:19p
TESTCFG  SYS     5434   3-04-95   4:48p
OS2LOGO         16190  23-03-95  11:04a
SCREEN02 SYS     9393  14-03-95   7:14p
SCREEN01 SYS     9461  14-03-95   7:14p
FD8XX    ADD    29848   2-03-95   3:14p
HPFS     IFS   135746  31-01-95   7:54p
OS2CDROM DMD    24238  15-01-95  12:30a
CHKDSK   COM    68656   9-01-95   7:58a
IBMKBD   SYS     5572   6-01-95   8:05p
IBM2FLPY ADD    13754   6-01-95   7:17p
OS2DASD  DMD    33578   4-01-95   8:52p
COUNTRY  SYS    25610  12-12-94   9:03p
CDFS     IFS    41795  12-12-94   6:25p
BVHINIT  DLL     7999  12-12-94   5:33p
LMS206   ADD    38706  12-12-94   3:44p
SBCD2    ADD    18834  12-12-94   3:42p
BTSCSI   ADD    22737  12-12-94   3:40p
RESOURCE SYS    27650  12-12-94   3:31p
KEYBOARD DCP     7715   8-12-94   7:41p
DOS      SYS     1142   8-12-94   7:38p
IBM2SCSI ADD    32629   1-12-94  11:39a
MOUCALLS DLL     1024  10-11-94   4:15p
NAMPIPES DLL     1024  10-11-94   4:15p
BMSCALLS DLL      512  10-11-94   4:15p
BKSCALLS DLL      512  10-11-94   4:13p
ANSICALL DLL      512  10-11-94   4:13p
VIOCALLS DLL     2048  10-11-94   4:12p
OS2CHAR  DLL      512  10-11-94   4:11p
QUECALLS DLL     1024  10-11-94   4:09p
SESMGR   DLL     1536  10-11-94   4:08p
BVSCALLS DLL      512  10-11-94  10:07a
CLOCK02  SYS     3834  10-11-94  12:56a
CLOCK01  SYS     3735  10-11-94  12:56a
VTBL850  DCP    10478  10-11-94  12:44a
KBDCALLS DLL     1024   9-11-94  10:22p
TEDIT    HLP    14596  31-10-94   8:03p
DPT20XX  ADD    23898   5-10-94  10:37p
XDFLOPPY FLT    14698   5-10-94  10:33p
IBMINT13 I13     9860   5-10-94  10:32p
IBM2ADSK ADD     9798   5-10-94  10:32p
TMV1SCSI ADD    20238   5-10-94  10:30p
KBDBASE  SYS    27989   3-10-94   2:23p
MOUSE    SYS    17387   3-10-94   2:15p
       62 file(s)    1255174 bytes used
                      179712 bytes free

And modified config.sys

Quote
set copyfromfloppy=1
rem basedev=detne2.sys
buffers=32
iopl=yes
memman=swap,delayswap
protshell=sysinst1.exe
set os2_shell=sysinst2.exe
diskcache=D2,LW
protectonly=yes
libpath=.;\;\os2\dll;\os2\install;
ifs=hpfs.ifs /c:64
pauseonerror=no
codepage=850
country=044,country.sys
devinfo=kbd,uk166,keyboard.dcp
devinfo=scr,ega,vtbl850.dcp
device=\dos.sys
device=\mouse.sys
set path=\;\os2;\os2\system;\os2\install
set dpath=\;\os2;\os2\system;\os2\install
set keys=on
rem basedev=cmd640x.add
basedev=ibmkbd.sys
basedev=ibm1flpy.add
basedev=ibm1s506.add 
basedev=ibm2flpy.add
basedev=ibm2adsk.add
basedev=ibm2scsi.add
basedev=ibmint13.i13
basedev=os2dasd.dmd
device=\testcfg.sys
basedev=xdfloppy.flt

set os2_shell=cdinst.exe
set saveconnect=1
set cdrominst=1
ifs=cdfs.ifs /q
basedev=ibmidecd.flt
device=\os2cdrom.dmd
set oemprogram=\grpware\lanstart.exe
set exitwhendone=1
set os2_shell=coninst.exe

Note this is for a UK English install, if you need a US English install change the country and kbd lines to make the changes.


Edit:  I should add that the IBM1S506.ADD is in fact DANIS506.ADD renamed to prevent conflicts during install.
Title: Re: Installing Warp 3 issues
Post by: Pete2 on May 16, 2020, 03:11:36 pm
You can unpack .dsk images with diunpack or dskxtrct (which IIRC does more checking.) Both can be found on Hobbes.
Title: Re: Installing Warp 3 issues
Post by: ivan on May 16, 2020, 03:55:27 pm
Hi Pete2,

There is an even better utility that I have used for years  EMT4PM (OS/2) and EMT4WIN (windows)  OS/2 version found at
http://dvalot.free.fr/OS2programs.html  I'm not sure about the win version as he has gone to win 8 and win 10 versions now.

It allows for the creation of disk images using either a floppy or a virtual floppy, it also checks the validity of disk images and when writing a floppy from an image it tests the floppy for problems, bad sectors etc.
Title: Re: Installing Warp 3 issues
Post by: Dj Koelkast on May 17, 2020, 10:39:59 am
This is the directory of my unmodified disk 1:

Code: [Select]
Volume in drive A is DISK 1
 Volume Serial Number is 6200-0000

 Directory of A:\

01/05/1995  15:52            24.878 CONINST.EXE
31/01/1995  19:54           135.746 HPFS.IFS
21/04/1995  16:55           122.788 DOSCALL1.DLL
12/12/1994  15:44            38.706 LMS206.ADD
21/04/1995  18:03            79.360 CMD.EXE
03/04/1995  16:48             5.434 TESTCFG.SYS
12/12/1994  18:25            41.795 CDFS.IFS
11/05/1995  12:49            35.348 CMD640X.ADD
04/01/1995  20:52            33.578 OS2DASD.DMD
01/12/1994  11:39            32.629 IBM2SCSI.ADD
15/12/1994  15:57            31.058 IBM1FLPY.ADD
21/04/1995  23:28            28.900 IBM1S506.ADD
12/12/1994  15:31            27.650 RESOURCE.SYS
03/10/1994  14:23            27.989 KBDBASE.SYS
12/12/1994  21:03            25.610 COUNTRY.SYS
21/04/1995  17:17            20.684 NPXEMLTR.DLL
03/10/1994  14:15            17.387 MOUSE.SYS
27/03/1995  15:15            16.190 OS2LOGO
21/04/1995  16:53            14.888 HARDERR.EXE
05/10/1994  22:33            14.698 XDFLOPPY.FLT
31/10/1994  20:03            14.596 TEDIT.HLP
06/01/1995  19:17            13.754 IBM2FLPY.ADD
10/11/1994  00:44            10.478 VTBL850.DCP
05/10/1994  22:32             9.860 IBMINT13.I13
05/10/1994  22:32             9.798 IBM2ADSK.ADD
21/04/1995  17:53             9.374 TEDIT.EXE
10/01/1995  17:40             9.393 SCREEN02.SYS
10/01/1995  17:40             9.461 SCREEN01.SYS
12/12/1994  17:33             7.999 BVHINIT.DLL
12/12/1994  15:36            38.044 AHA152X.ADD
08/12/1994  19:41             5.177 KEYBOARD.DCP
06/01/1995  20:05             5.572 IBMKBD.SYS
03/04/1995  16:48             5.088 DETNE2.SYS
21/04/1995  19:48             4.224 SYSINST1.EXE
05/10/1994  22:33            20.324 AHA154X.ADD
10/11/1994  00:56             3.834 CLOCK02.SYS
10/11/1994  00:56             3.735 CLOCK01.SYS
10/11/1994  16:12             2.048 VIOCALLS.DLL
10/11/1994  16:08             1.536 SESMGR.DLL
08/12/1994  19:38             1.142 DOS.SYS
10/11/1994  16:09             1.024 QUECALLS.DLL
10/11/1994  16:15             1.024 NAMPIPES.DLL
10/11/1994  16:15             1.024 MOUCALLS.DLL
09/11/1994  22:22             1.024 KBDCALLS.DLL
22/05/1995  14:48             1.363 CONFIG.SYS
10/11/1994  16:11               512 OS2CHAR.DLL
21/04/1995  16:52               512 NLS.DLL
21/04/1995  16:52               512 MSG.DLL
10/11/1994  10:07               512 BVSCALLS.DLL
10/11/1994  16:15               512 BMSCALLS.DLL
10/11/1994  16:13               512 BKSCALLS.DLL
10/11/1994  16:13               512 ANSICALL.DLL
13/04/1995  18:53               165 SYSLEVEL.OS2
12/12/1994  15:36            19.716 AHA164X.ADD
22/04/1995  02:27                30 DISK.NUM
05/10/1994  22:34            17.820 AHA174X.ADD
12/12/1994  15:37            42.396 AIC7770.ADD
15/12/1994  16:01            34.092 AIC7870.ADD
12/12/1994  15:40            22.737 BTSCSI.ADD
21/04/1995  23:18            21.498 CMDATAPI.FLT
10/01/1995  15:17            31.258 FD16-700.ADD
12/12/1994  15:39            30.030 FD8XX.ADD
12/12/1994  15:38            20.848 FD7000EX.ADD
05/10/1994  22:37            23.898 DPT20XX.ADD
03/10/1994  14:02             4.736 CHINCDS1.FLT
03/10/1994  13:59             6.086 HITCDS1.FLT
06/10/1994  22:39             7.066 NECCDS1.FLT
03/10/1994  14:01             6.286 SONYCDS1.FLT
03/10/1994  14:00             6.236 TOSHCDS1.FLT
21/04/1995  23:30            20.286 IBMIDECD.FLT
05/10/1994  22:30            20.238 TMV1SCSI.ADD
12/12/1994  15:43            19.530 SONY535.ADD
15/12/1994  16:06            32.480 SONY31A.ADD
24/01/1995  20:15            20.482 MITFX001.ADD
12/12/1994  15:42            18.834 SBCD2.ADD
15/01/1995  00:30            24.238 OS2CDROM.DMD
              76 File(s)      1.420.782 bytes
               0 Dir(s)          10.240 bytes free

Then I removed SCSI lines and added the 2 files:

Quote
  2.  Copy the new versions of IBM1S506.ADD, and IBMIDECD.FLT
      device driver files onto your D1 diskette.

To make room for it I removed these files:

Code: [Select]
BTSCSI.ADD
TMV1SCSI.ADD

I also removed the original IBM1S506.ADD and IBMIDECD.FLT from the disk and replaced them with the new.
And I did this:

Quote
  4.  Add the statement SET COPYFROMFLOPPY=1 to the CONFIG.SYS on D1.


Original config.sys:

Code: [Select]
buffers=32
iopl=yes
memman=swap,delayswap
protshell=sysinst1.exe
set os2_shell=sysinst2.exe
diskcache=D2,LW
protectonly=yes
libpath=.;\;\os2\dll;\os2\install;
ifs=hpfs.ifs /c:64
pauseonerror=no
codepage=850
devinfo=kbd,us,keyboard.dcp
devinfo=scr,ega,vtbl850.dcp
device=\dos.sys
device=\mouse.sys
set path=\;\os2;\os2\system;\os2\install
set dpath=\;\os2;\os2\system;\os2\install
set keys=on
basedev=cmd640x.add
basedev=detne2.sys
basedev=ibmkbd.sys
basedev=ibm1flpy.add
basedev=ibm1s506.add
basedev=ibm2flpy.add
basedev=ibm2adsk.add
basedev=ibm2scsi.add
basedev=ibmint13.i13
basedev=os2dasd.dmd
device=\testcfg.sys
basedev=xdfloppy.flt

set os2_shell=cdinst.exe
set saveconnect=1
set cdrominst=1
ifs=cdfs.ifs /q
basedev=aha152x.add
basedev=aha154x.add
basedev=aha164x.add
basedev=aha174x.add
basedev=aic7770.add
basedev=aic7870.add
basedev=btscsi.add
basedev=cmdatapi.flt
basedev=fd16-700.add
basedev=fd8xx.add
basedev=fd7000ex.add
basedev=dpt20xx.add
basedev=chincds1.flt
basedev=hitcds1.flt
basedev=neccds1.flt
basedev=sonycds1.flt
basedev=toshcds1.flt
basedev=ibmidecd.flt
basedev=tmv1scsi.add
basedev=sony535.add
basedev=sony31a.add
basedev=lms206.add
basedev=mitfx001.add
basedev=sbcd2.add
device=\os2cdrom.dmd
set oemprogram=\grpware\lanstart.exe
set exitwhendone=1
set os2_shell=coninst.exe


Modified config.sys:

Code: [Select]
buffers=32
iopl=yes
memman=swap,delayswap
protshell=sysinst1.exe
set os2_shell=sysinst2.exe
diskcache=D2,LW
protectonly=yes
libpath=.;\;\os2\dll;\os2\install;
ifs=hpfs.ifs /c:64
pauseonerror=no
codepage=850
devinfo=kbd,us,keyboard.dcp
devinfo=scr,ega,vtbl850.dcp
device=\dos.sys
device=\mouse.sys
set path=\;\os2;\os2\system;\os2\install
set dpath=\;\os2;\os2\system;\os2\install
set keys=on
basedev=cmd640x.add
basedev=detne2.sys
basedev=ibmkbd.sys
basedev=ibm1flpy.add
basedev=ibm1s506.add
basedev=ibm2flpy.add
basedev=ibm2adsk.add
basedev=ibm2scsi.add
basedev=ibmint13.i13
basedev=os2dasd.dmd
device=\testcfg.sys
basedev=xdfloppy.flt

set os2_shell=cdinst.exe
set saveconnect=1
set cdrominst=1
ifs=cdfs.ifs /q
basedev=aha152x.add
basedev=aha154x.add
basedev=aha164x.add
basedev=aha174x.add
basedev=aic7770.add
basedev=aic7870.add
basedev=cmdatapi.flt
basedev=fd16-700.add
basedev=fd8xx.add
basedev=fd7000ex.add
basedev=dpt20xx.add
basedev=chincds1.flt
basedev=hitcds1.flt
basedev=neccds1.flt
basedev=sonycds1.flt
basedev=toshcds1.flt
basedev=ibmidecd.flt
basedev=sony535.add
basedev=sony31a.add
basedev=lms206.add
basedev=mitfx001.add
basedev=sbcd2.add
device=\os2cdrom.dmd
set oemprogram=\grpware\lanstart.exe
set exitwhendone=1
set os2_shell=coninst.exe
SET COPYFROMFLOPPY=1

I could probably do with a whole lot less, so I'll be trying the config.sys posted by ivan (with US keyboard layout)
Title: Re: Installing Warp 3 issues
Post by: Dj Koelkast on May 17, 2020, 12:11:56 pm
Copying went well now, but the same result. I tried HPFS and FAT (FAT takes a looooooot longer to install).
I disabled all cache options in the BIOS, as well as all other features that didn't need to be on.

Result is the same every time: when it wants to boot after the initial install it gives me just a black screen with a blinking white cursor in the top left corner. That's all.
Title: Re: Installing Warp 3 issues
Post by: Dj Koelkast on May 17, 2020, 02:33:12 pm
Something did change, after installing, rebooting the installation disk and entering the command prompt now gives me (to my eyes at least) more accurate hdd info:

Title: Re: Installing Warp 3 issues
Post by: ivan on May 17, 2020, 04:13:36 pm
What do you get with dir /a  at the moment you are not showing the system files like OS2BOOT, OS2KRNL, OS2LDR, OS2LOGO, OS2DUMP all of which are necessary for OS/2 to boot.

Another thing, you might need to run SYSINSTX.COM (on the boot disk) to make the root partition bootable.
Title: Re: Installing Warp 3 issues
Post by: Dj Koelkast on May 17, 2020, 09:37:24 pm
Ok with DIR /A everything does show up.

SYSINSTX.COM C: does not work unless I copy SYSINSTX.COM to c:\ and do it from there, but it results in the same thing, the blinking cursor.

So I did something radical: made new floppies, from a different source (and did the update). Made a new cd, different brand media, different burner, different software to burn, different drive to burn, different drive to read on the IBM.
After installing this: 100% the same result.

So there is no other option than to think there is either an incompatible part in this IBM (note: it has no cache memory, or at least the SureBIOS says 0kB) or some other thing is going on. I might try a small IDE HDD soon.
The PC 330 was shipped with OS/2 Warp 3 as an option, so it should be able to run on it is my best guess.

(oh yeah I',m quite persistent to get it running)

Title: Re: Installing Warp 3 issues
Post by: Martin Iturbide on May 17, 2020, 11:30:08 pm
Hi Dj Koelkast.

I know this may be "Warp 3 o Burst"  ;D   but what do you think if you give a try with Warp 4 or Warp 4.52 to see if you can pass the install phase, or if you experience the same issue. Just to see if there is a different result and then you get back to Warp 3.

Uhm, just as a curiosity, when you run the Warp 3 Installer, I guess it was at the first screen asking your for input, can you do a F3 and go to command line and do a "ver /r", which release do you have? which language is it? 8.162, 8.200 ?

Regards
Title: Re: Installing Warp 3 issues
Post by: Dave Yeo on May 18, 2020, 12:01:47 am
Hi Dj, did you install BootManager? I know in theory it shouldn't be needed for C: assuming C: is the first active primary partition, but perhaps OS/2 doesn't know what drive it is on? Though I'd think that would be a can not operate hard drive type error.
Title: Re: Installing Warp 3 issues
Post by: Dj Koelkast on May 18, 2020, 09:55:35 am
I can sure try 4(.52) as well, but the aim for this machine is 3.

Bootmanager, well, I tried 3 options:

1: just do "easy install", the installer will to everything. At the end it goes looking for configuration, then I need to remove the diskette and then it reboots for the 1st time. After that I get the blinking cusror.
2: do an advanced install, partition, make it installable, exactly the same result
3: do an advanced install and just choose to format it (either FAT or HPFS) and again, same result, a blinking cursor after the 1st boot

Last image I had was 8.200, but I'll check in the command promt as well.

This BIOS doesn't work with hard drive types by the way, it recognises it (or not). It doesn't seem to like drives above 4gb, so that's why I had this 2GB CF.
I'll try a genuine IDE HDD < 2gb to see if that's helping.
Title: Re: Installing Warp 3 issues
Post by: ivan on May 18, 2020, 03:04:45 pm
Sorry, I missed the fact you are trying to use a CF disk - Warp 3 will not use that, no matter what size, as a boot disk.  It expects the boot disk to be hanging off either an SCSI or an IDE port - those are all the IBM1S506.ADD recognises, I'm not sure if DANIS506.ADD recognises other ports but I don't think so.
Title: Re: Installing Warp 3 issues
Post by: Dave Yeo on May 18, 2020, 04:43:36 pm
Sorry, I missed the fact you are trying to use a CF disk - Warp 3 will not use that, no matter what size, as a boot disk.  It expects the boot disk to be hanging off either an SCSI or an IDE port - those are all the IBM1S506.ADD recognises, I'm not sure if DANIS506.ADD recognises other ports but I don't think so.

I assumed the CF disk is hanging off an IDE port, which should work. Of course a good test would be to install DOS and see if that works.
Title: Re: Installing Warp 3 issues
Post by: ivan on May 18, 2020, 05:25:36 pm
Hi Dave,

The problem is a lot of the CF to IDE adapters carry extra electronics which I doubt IBM1S506 would recognise and if it doesn't show up on the bios screen it will never boot.
Title: Re: Installing Warp 3 issues
Post by: Dj Koelkast on May 18, 2020, 08:47:59 pm
CF to IDE, yeah, I don't like to use it, I normally use an SSD converted to IDE which always works.
But installing it on a 850mb real hard drive: it just worked right away (besides complaining about not being able to boot in DOS the 1st time, it did go through).

So would a DOM work? A direct to IDE DOM of 2GB?
Title: Re: Installing Warp 3 issues
Post by: Dave Yeo on May 18, 2020, 10:15:06 pm
In theory it should work. Of course it partially depends on your BIOS as OS/2 starts its boot in real mode and depends on the BIOS at that point. Once booted, you could probably have a secondary 500MB HD (perhaps even 2TB) that OS/2 can use.
There was a time I bought an 80 GB drive that wouldn't boot until I jumpered it to only present 32 GBs. Boot partition had to be in the 32 GBs but once booted, I could use the whole 80 GBs. Windows only ever saw the 32 GBs and Linux was similar though eventually I found the secret invocation to make the whole thing visible.
Title: Re: Installing Warp 3 issues
Post by: ivan on May 18, 2020, 10:27:45 pm
All I can say is that it might - if the bios sees it as a disk then it should but since you now have Warp 3 booting you can add a second HD and if you use the DANIS506.ADD then anything up to 80GB should be useable (search hobbes for danis and it will throw up several of her drivers).

PS. Don't forget to set the second drive to slave with the first drive set as master, also you should check the IDE cable in case it is set for master/slave sockets).
Title: Re: Installing Warp 3 issues
Post by: Dj Koelkast on May 18, 2020, 11:40:29 pm
I'll first order a 2GB DOM and try that, I really don't want to fall back to noisy old hard drives that fail every now and then.
I love all the old stuff, except for the old hard drives and old noisy fans, so I try to replace them for modern equivalents.
Title: Re: Installing Warp 3 issues
Post by: Martin Iturbide on May 19, 2020, 12:21:24 am
Hi.
I love all the old stuff, except for the old hard drives and old noisy fans, so I try to replace them for modern equivalents.

I know that there are people that like to have old hardware exactly as it was available years ago (I watch LGR YouTubes (https://www.youtube.com/user/phreakindee)), but I have a IDE-2-SDcard adapter on my old Aptiva and it is great and fast. Thanks to that the HDD no longer sound like a pop-corn machine anymore.

Regards
Title: Re: Installing Warp 3 issues
Post by: Dj Koelkast on May 19, 2020, 06:02:48 pm
Hi.
I love all the old stuff, except for the old hard drives and old noisy fans, so I try to replace them for modern equivalents.

I know that there are people that like to have old hardware exactly as it was available years ago (I watch LGR YouTubes (https://www.youtube.com/user/phreakindee)), but I have a IDE-2-SDcard adapter on my old Aptiva and it is great and fast. Thanks to that the HDD no longer sound like a pop-corn machine anymore.

Regards

I also dislike CRT monitors except VGA CRT monitors. But for example the Commodore 1084S, which is loved by many, I can't stand the noise it makes! It's so loud (very high frequency constant beeping) it drives me crazy. So I tend to use either TFT tvs (small ones) or small TFT monitors that support the strange resolutions. It's not 100% accurate maybe, but it makes me happier.
So this also counts for most hard drives. I must admit that the sound of the hard drive that LGR had in his IBM video was gorgeous, the 20MB MFM one. I would use that if I had it. I also use the original harddisk in my PS/2 (and the original PS/2 mouse and Model M clicky keyboard and a 14" CRT VGA that doesn't beep), so yeah I do have them, but not everywhere.
If it's just IDE I replace them with an SSD that I convert to IDE. Works way better than CF (but the smallest one is 8GB so in this IBM 330 it doesn't work, that's why I tried CF).