Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Fahrvenugen

Pages: 1 ... 4 5 [6]
Setup & Installation / Re: driver trouble with Warp 3
« on: May 06, 2014, 03:42:14 pm »

This was a pre-load?  Things might be different then!

TCP/IP Version 4.0 was introduced with Warp 4, I'm not sure why it would be on Warp 3, unless it was a unique version that I havn't seen (which is possible)

If you've got network access via a network card already then you've already got a version of MPTS of some level.

Run syslevel from a command prompt.

What is the syslevel.tcp output?  That'll tell us which  tcp/ip you have

There should also be one for mpts and such.

If you can do that, then we can help figure out which fixpaks apply.

Setup & Installation / Re: driver trouble with Warp 3
« on: May 06, 2014, 08:27:26 am »
Hi again,

One thing I didn't think to ask - are you running Warp 3 Connect, or just plain Warp 3 (without the Connect stuff)?

If you're running Warp 3 (non-connect) with just the Internet Access Kit from the Bonuspack, then things can get a little more interesting.

Do an inetver at the command line - if it says anything about tcp/ip version 2 (or if the box does not contain the word "connect" on it) then you're probably running the original Warp with the Bonuspack internet access kit - based on an even earlier version of TCP/IP - Version 2.0.

I could be incorrect, but I *think* the the important updates for version 2 are at:

with the latest stack being at:

There is a whole bunch of updates for TCP/IP V2.0, I can't recall what you actually need and what you don't:

Originally Warp 3 (the non-connect version) was not shipped with any network drivers - it was only set up to access the internet via dialup modem (using difficult-to-configure PPP software at that).  If you wanted the full network stuff you were supposed to buy the Connect version.  But...  If I recall correctly (and this is going back many years - the last time I used a non-connect version of Warp 3 was a long time ago) it is possible to add the 16 bit version of MPTS to a non-connect version of Warp 3 with the Internet Access Kit by downloading it directly from IBM.  I *think* that TCP/IP 2.0 was limited to the 16 bit MPTS - if I recall there were reports that it didn't like the 32 bit stack, but it has been so long ago I could be incorrect on that.

The 16 bit mpts installation can be found at:

And of course there is a fixpack for it at:

Note that IBM did not officially support running the full 16 bit MPTS on the non-connect version of Warp 3 (and some have suggested this may not be supported by the MPTS license).  At this point I'm not sure IBM is all that concerned about the way an individual user uses a license on Warp 3 (a 20 year old product), and of course IBM no longer supports Warp 3 at all (at least not for consumers) however it is worth the note of caution if you are concerned about such things.

Of course if you're running Warp 3 connect, then you can ignore all this TCP/IP Version 2 / MPTS 16 bit stuff.

Setup & Installation / Re: driver trouble with Warp 3
« on: May 06, 2014, 05:46:50 am »

Unless you want to go hacking syslevel files, then you are best to stick with Fixpak 40.  For the base Warp 3 (the  client desktop version)  the last fixpak that IBM released was 40.  Warp Server (the server version built on top of Warp 3) did come out with Fixpak's 41 and 42, these both can be made to work on Warp 3 desktop, however it is unsupported and there are a few files that can introduce instabilities on the client version.  40 is pretty stable and fixes the majority of the issues.

To get GRADD or SNAP to work you will need at least Fixpak 35, however I recommend 40 since it fixed some of the problems that still existed in 35.

Note that I've only used Warp 3 on real hardware, I have no idea if the following suggestions work on Virtualbox.  Having said that, not long ago (about 4 months) I had to set up 2 Warp 3 machines on newer hardware.  Here's some tips.

For starters, make sure you've got a copy of unzip (I normally use the info-zip unzip app), also you'll want  DSKXTRCT from Hobbes in order to extract the DSK files to  a folder on your hard disk (they're the ones meant to be extracted to a floppy, but no one wants to use a floppy anymore)

Here's where to find dskxtrct:

The easiest way to install a Fixpak is to use the RSU version of the fixpak.  Grab all the xrgw* files from:

Then grab the CSF Service utility (the one modified to let you install from a hard disk):

Unzip all the XRGW* files into a single directory / folder, and unzip the CSF file into another folder.

As an example the last time I set up a Warp 3 machine (about 4 months ago), I set up the following folders:



I unzipped all the XR* files into c:\fp40, and unzipped the csf file into c:\service

Also, I created a folder called c:\archive (where the FP utility will put the archived copies of the files it replaces)

Then from a command prompt, I switched into the c:\service folder:

cd c:\service

and ran the command:

os2serv c:\service\csf c:\fp40

Okay, now here's the part where I'm going by memory so it may not be 100% exact, but it should be close (I'm using a Linux machine to respond to this message tonight)

After a while it'll pop up with a CSF utility screen, it'll list a couple of products it can service (it should list OS/2 and MMPM).  Click on the OS list entry, then there is an "Advanced" check box that you can select - go ahead and tick that off.  And hit install (or something like that).  In a moment it'll pop up with the CSF install utility that you've possibly seen from days of old (the one which used to require you to play floppy-disk-toaster to install the thing - don't worry - it'll install from the hard disk this time).

It'll give you the same list of both the base OS and the Multimedia stuff - highlite them both and chose the install option again.  It'll then give you the option for where you want your backup folder (or archive folder) to be, type in your c:\archive that you created earlier.

Then hit okay - it'll give you a warning about some of the files which it won't process until it does a reboot, go ahead and select the OK (or allow it to process them on reboot) option, it should start applying the fixpak.

For some reason the last time I did this it came up on some files which it felt were newer on the hard disk then on the fixpak, I'm not sure why since the fixpak dates from around 1998, the original release came out in 1994.  Go ahead and replace the files, unless they relate to one of the drivers that needed to be replaced to get the thing to run (such as ibm1s506, or the likes).

Once done it'll give you a message that it needs a reboot - go ahead and reboot.

Note, once you get Fixpak 40 installed, if you've gone with the base TCP/IP 3.0 that comes with Warp Connect you may also want to install TCP/IP fixpak UNG0959 too - it'll add a bunch of fixes for TCP/IP.  It is at:

For UN0959 you'll need dskxtrct (they're all in .dsk files), see my note above on that.  Be sure to create another folder on your hard disk for this.  The process to start the CSF install for the TCP/IP fixpak install is the same as with the FP40 above, just substitute the directory containing the fixpak in your command line.

Once you get TCP/IP UN0959 successfully installed - reboot.  You can check your tcp/ip version from the command line with an inetver command - and see if your TCP/IP is working.

If you want you can then try to install the 32 bit MPTS stack - which will replace the TCP/IP stuff with the 32 bit version.  Most of the time the 32 bit MPTS works on Warp 3, however I have heard some stories talking of difficulty (I've never experienced difficulty)

The base MPTS 32 bit install is:

For that one you'll also need dskstrct to extract the files (create another folder to install from).  When extracted, there will be an mpts.exe file in the folder - run that and it will start up the installation routine.

The base WR8610 is buggy, so you'll need to then install the WR8621 fixpak, at:

And then even with the 8621 fixpak, TCP/IP still has a habbit of hanging, so you'll need to grab the update from Hobbes:

If you want to track the version levels of TCP/IP from the command line, you can run inetver each time and see what level it is at.

If you've installed the IBM Peer services, you'll need the Peer fixpak, for Warp 3 (German) it is at:

Are we having fun yet?

The other issue that can happen on some Warp 3 machines (and Warp 4 also had this difficulty on some machines too) is that it won't see memory above 64 Megs.  This has to do with how the loader handles initial memory allocation (or something like that).  To find out if your machine is affected, grab from Hobbes something like countmem and see what it reports.

If you find that you're only seeing 64 megs, then grab from Hobbes  and try it.  It'll patch the loader to allow OS/2 to see more then 64 megs.  I've had to use it on quite a number of the systems I've set up with Warp 3.

Okay, I think I've got most of the stuff  here that you'll need to get you up and running a stable system.  I might be missing something, if I am then I can try and figure it out with my actual Warp 3 system. 


Polls / Re: eComStation Retail Store?
« on: March 31, 2014, 10:56:39 pm »
I remember back in the mid 90's all the IBM  stores (does anyone other then myself remember these?)  had OS/2 Warp displays selling both the OS and various shrink-wrapped software available (Object Desktop and Describe were common to find, among others).  The stores also sold other IBM products (computers, laptops, software, etc).  I don't know how well any of the OS/2 stuff actually sold.

I can also recall going into my local Staples and finding OS/2 Warp on the shelf.

But at this point I would say the best option for selling OS/2 / eCS related stuff is online for software, and just pick up hardware locally.

Programming / Re: Closed source parts of eComStation
« on: January 16, 2014, 08:05:11 pm »
More important, are things like support for the majority of NICs that exist today, and in the future. Without communication (especially wireless), nobody will be able to continue using eCS. It just won't do the job. It can't always do the job today, without wireless communications. There are keyboard problems, there are video problems, there are printer problems. Somebody had better start fixing all of them, or eCS will be as dead as IBM, and Microsoft, wishes it was.

I have to agree, especially on the wireless and wired network drivers I'd put higher priority on this then I would on the 4GB barrier.

Just as a real-use example, not long ago I set up a customized desktop machine.  The machine needed to run a specific task 24x7 where it grabs information off the web and then feeds it to some old DOS-based apps which then feed the data to some custom hardware.  The system also needed the ability for someone to push specific information to it in place of the web-based data.  Originally the setup involved multiple computers (one computer receiving the data over a network and pushing it out a COM port and the DOS comptuer(s) running their apps receiving the data over the COM port and then processing the data to the custom hardware).  With OS/2 I was able to consolidate it all into a single computer - running a few DOS boxes for the DOS apps, OS/2 apps for the network stuff, and a custom REXX script to sort everything else out.  In testing it all worked out better then the original setup.

The biggest challenge I ran into was networking.  Where this computer has to be located there is no direct ethernet connection but there is stable secure Wifi.

What I ended up doing is I set up the OS/2 computer to use a standard Ethernet card that has drivers.  I then used a D-Link DIR-615 (cost of around $20) router and installed DD-WRT on it. I then set up the DD-WRT box to log into the Wifi signal and I have regular Ethernet cable connecting the 615 to the OS/2 box.  It works like a charm.

Admittedly part of my challenge was that I decided to use a spare OS/2 Warp Connect license that I had unused sitting on my shelf for this test setup.  I have no expectation to ever get Wifi working on Warp Connect, so this might seem like an insignificant example to use as an argument for good Wifi and NIC drivers.  However in this case networking and being able to find a way to connect to a Wifi network was absolutely necessary for the setup.  The 4 GB limit played no role in my decision to set up an OS/2 system.

Setup & Installation / Re: Tweaking eCS for low memory system
« on: January 16, 2014, 07:02:51 pm »
I seem to recall that in one of my collections of  books I have a "inside os/2 2.1" and a "Warp 3 certification" book, both of which I think had tips for optimizing for low memory systems.

I'll have a look and see if I can find those books, I'm sure the tips all apply to Warp 4 / eCS.

Setup & Installation / Re: Tweaking eCS for low memory system
« on: January 14, 2014, 07:54:50 pm »

Basically what I need is - WPS,

Warp 3 probably used less mem.


I keep a couple of copies of Warp 3 around, and yes - it does run nicely on low memory systems.  I have found that in many cases (depending on the application) it performs better then Warp 4 / eCS.

It *can* run on systems with as little as 4 MB, although it swaps constantly and runs very slowly.

I've had it run smoothly on systems with as little as 16 MB (with lots of tweaking), although don't expect to run more modern apps on a 16MB system. 

For Warp 3, once you hit 64 MB the system starts to really fly (although if you go above 64 MB you may need to run the patchldr utility to patch the loader so it will see memory above 64 MB).

One thing to note though - I've never tried booting Warp 3 from a CF card,  I have no idea if that is even possible.

Multimedia / Re: OS/2 Warp Sound sample 2014 - Video
« on: January 13, 2014, 10:30:42 pm »

I admit it is difficult to tell on youtube if there is much difference.  However one thing I have found over the years relating to digital audio on computers is that a lot of the audio quality has more to do with how a sound chip is implemented on a system and whether or not it is filtering out external noise rather then the actual chipset used.

A lot of times I've found that onboard chipsets pick up a lot more noise from the system resulting in lower quailty audio then actual audio cards.  I recall a few years back when I did an experiment - I had a MB with an onboard chipset (c-media based) and a PCI sound card using the same c-media chip.  When I plugged the PCI card into the MB (and disabled the onboard audio) the audio quality was significantly better then when using the onboard - and it used the same driver.

However on the other hand I've also found that some low-quailty PCI audio cards have a habit of picking up external noise too - producing low-quality audio.   A lot of times it has more to do with the circuit design on the card and quality of the components rather then the chipset or driver itself.

General Discussion / Re: Big thanks to Martin
« on: December 18, 2013, 09:16:37 pm »
Yes, I too want to say a big THANK YOU!

Having done some book-scanning myself, I can understand that was a huge task to complete.

This will nicely complement the Warp 3 certification handbook that I have.

Thanks again!


The 32 bit MPTS stack can still be downloaded right from IBM at:

You'll need to install the update at:

and also grab from hobbes.

For the TCP/IP apps, once you've installed the TCP/IP apps on the CD, you'll need to install the fixpak at:

otherwise the apps don't work properly with the 32 bit stack in the MPTS above.

If I recall correctly, you also need to have first updated the base OS/2 Warp 3 install to a newer fixpak (FP 40 or so).  Otherwise there is stuff in the newer mpts which will trap.

FP 40 is at:


Good luck!


On the Warp 3 Connect CD there is off the root a folder called something like:


or maybe it is \cid\img (or something like that... I'm going from memory here and I don't have a CD available right now)

In there you can find a number of folders, there will be one for \tcpapps
and another for \mptn or \mpts

something like that.

In each one of those there are installer EXE's which can allow you to run the individual installs.

General Discussion / Happy SysAdmin Day (July 26, 2013)
« on: July 26, 2013, 05:31:08 pm »
To all the System Administrators out there, Happy System Administrator Day!

If you're a system administrator here's to hoping that someone will bring you cake!

Networking / Re: Various Warp Connect v3 networking problems
« on: July 13, 2013, 04:29:41 am »

If you're running Warp 3 connect without any fixpaks, this may be part of the difficulty.  I know a pile of NIC drivers out there only work properly with newer versions of MPTS.  Note - most of these fixes can be installed with the IBM CSF utility, hopefully you know how to use it in mode that it'll install straight from a hard disk instead of requiring playing the game of floppy-toaster.  If you've never used CSF then let me know and I'll see if I can find the info on using it in the hard disk mode (its been a while and I don't have that info in front of me as I type right now, but I could find it).

It is possible to get the 32 bit TCP/IP stack and updated network stack running on Warp 3, but you'll need to install Fixpak 40 on your base OS first.  FP40 can be found at:

Or you can grab the zipped version at:

Then before installing the newer mpts, you'll want to install the latest TCP/IP fixpak for the TCP/IP that comes with Warp 3 connect.  (UN00959) It is at:

If you're running Peer, then you'll need the latest Peer fixpak:

Then grab the newer  MPTS which can be found at:

And once that is installed you'll want the fixpak for MPTS at:

And once all that is installed, grab from Hobbes as it fixes some problems with 8621:

I seem to recall back in the day someone had gone to the trouble of zipping all this stuff into an easier install, but I don't know where that is anymore.  You can get all these components from these locations.

Once that is installed, you'll (hopefully) find that your NIC drivers work a little better.

Hope that helps.

Pages: 1 ... 4 5 [6]