Author Topic: Installing Warp 3 issues  (Read 1955 times)

Dj Koelkast

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 15
  • Karma: +0/-0
    • View Profile
Installing Warp 3 issues
« 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?

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 192
  • Posts: 2638
  • Karma: +5/-0
    • View Profile
Re: Installing Warp 3 issues
« Reply #1 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 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.
« Last Edit: May 15, 2020, 05:38:39 pm by Dave Yeo »

Dj Koelkast

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 15
  • Karma: +0/-0
    • View Profile
Re: Installing Warp 3 issues
« Reply #2 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.

Dj Koelkast

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 15
  • Karma: +0/-0
    • View Profile
Re: Installing Warp 3 issues
« Reply #3 on: May 15, 2020, 07:58:37 pm »
That didn't work, this is with an updated disk 1


Dj Koelkast

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 15
  • Karma: +0/-0
    • View Profile
Re: Installing Warp 3 issues
« Reply #4 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
« Last Edit: May 15, 2020, 08:34:48 pm by Dj Koelkast »

ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 2
  • -Receive: 44
  • Posts: 1213
  • Karma: +0/-0
    • View Profile
Re: Installing Warp 3 issues
« Reply #5 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.

Dj Koelkast

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 15
  • Karma: +0/-0
    • View Profile
Re: Installing Warp 3 issues
« Reply #6 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).





Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Thank You
  • -Given: 523
  • -Receive: 103
  • Posts: 2832
  • Karma: +3/-0
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: Installing Warp 3 issues
« Reply #7 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

Maybe you can give it a try.

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 192
  • Posts: 2638
  • Karma: +5/-0
    • View Profile
Re: Installing Warp 3 issues
« Reply #8 on: May 16, 2020, 02:02:45 am »
You can download 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.

Dj Koelkast

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 15
  • Karma: +0/-0
    • View Profile
Re: Installing Warp 3 issues
« Reply #9 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.
« Last Edit: May 16, 2020, 10:08:52 am by Dj Koelkast »

Dj Koelkast

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 15
  • Karma: +0/-0
    • View Profile
Re: Installing Warp 3 issues
« Reply #10 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?


Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 47
  • Posts: 1046
  • Karma: +0/-0
    • View Profile
Re: Installing Warp 3 issues
« Reply #11 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



ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 2
  • -Receive: 44
  • Posts: 1213
  • Karma: +0/-0
    • View Profile
Re: Installing Warp 3 issues
« Reply #12 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.
« Last Edit: May 16, 2020, 01:59:46 pm by ivan »

Pete2

  • Newbie
  • *
  • Thank You
  • -Given: 1
  • -Receive: 0
  • Posts: 22
  • Karma: +0/-0
    • View Profile
Re: Installing Warp 3 issues
« Reply #13 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.

ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 2
  • -Receive: 44
  • Posts: 1213
  • Karma: +0/-0
    • View Profile
Re: Installing Warp 3 issues
« Reply #14 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.