PDA

View Full Version : OS/2 Upgrade Issue - Warp 3 Connect



mancubis
September 23rd, 2006, 12:54 AM
Hello,

I am having trouble upgrading Warp 3 to Warp 3 Connect. When I try to upgrade from within OS/2, I receive the following error:

Line 7 of available_targets in CLTINST.VRM: +++ ok= QLDrives ('DrivesStem');

Also, when I try to upgrade from boot disks, the boot hangs at the second disk. I tried the disks on a separate PS/2 OS/2 machine and they booted fine and let me choose to install connect.

The machine in question is an IBM PS/2 8580.

Any ideas what that error is or how I can finish the upgrade?

Thanks a lot.

chuckcmagee
September 23rd, 2006, 11:06 PM
OS/2 is a real pain as far as doing "in place upgrades" goes. Most people setup a 2nd copy of os/2 in a separate partition and boot from that in order to do the upgrade. Unless you get some better answers, likely you will have to backup your data somehow and do a "fresh install" (i.e. format the hard drive partition again). When I would get install errors, I was always forced to reformat and start over. Of course, that was easy for me as I had very little custom stuff installed and could afford to just wipe it and start over.

Jorg
September 24th, 2006, 01:09 AM
Little bit off the track maybe, but I'd love to have OS/2 on one of my vintage boxes- only all I have is a Warp 3.0 and bonus pack.

As this has no network capability at all, and I have all my IBM compatibles networked, that makes me deinstall it every time.

Is this Warp 3.0 Connect an OS/2 Version with network support? In that case I'll be keeping an eye on E-bay.

chuckcmagee
September 24th, 2006, 02:35 AM
Well, crud. I just looked on my Warp 4 box and says min sys req is
486/33. So much for that idea.

Jorg
September 24th, 2006, 03:24 AM
Well, crud. I just looked on my Warp 4 box and says min sys req is
486/33. So much for that idea.

Thats why I was looking into Warp 3, not 4 ;)

If found some info about a freeware TCP stack for Warp 3 though, so might try that.

DimensionDude
September 24th, 2006, 12:50 PM
Thats why I was looking into Warp 3, not 4 ;)

If found some info about a freeware TCP stack for Warp 3 though, so might try that.


I think that I may have that, I'll have to check the "floppy vault." I used OS/2 2.1 exclusively some years ago when I was a member of Prodigy, so it will at least do a net connect over a modem.

Kent

Sharkonwheels
September 25th, 2006, 02:25 PM
DD, a little OT, but you still have any Dimension 68000's available?

Tony

DimensionDude
September 25th, 2006, 08:01 PM
DD, a little OT, but you still have any Dimension 68000's available?

Tony

The ambiguous answer is "perhaps." See my reply in the Dimension 68000 thread. :)

Kent

mancubis
October 3rd, 2006, 10:14 PM
I removed references to TCPIP from config.sys, renamed C:\TCPIP to c:\tcpip1, re-installed fix pack 40, and updated MPTS.

Now the install.cmd runs the connect install. I choose advanced, IBM Peer and TCPIP, and continue. Then as the install creates the install, a new error appears:

Line 51 of chkspace in
LANSTART.VRM:
+++ freespace=
SysDriveInfo(install_drives.i);


Any idea where I go from here?


Thanks!



---Also, Warp 3 Connect has full TCP/IP and NetBIOS abilities (file sharing, Internet Access, VNC, etc.)

chuckcmagee
October 4th, 2006, 01:45 AM
Uhhhh, a guess would be out of room on the dest. drive.

mancubis
October 8th, 2006, 10:46 AM
I used seperate installs and they worked:

x:\cid\img\laps\mpts.exe

(where x:\ is your CD drive letter)

To install TCP/IP directly from the CD, run:

x:\cid\img\tcpapps\install.exe

To install Peer directly, run:

x:\cid\img\ibmpeer\Peerrmt.exe