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 [2] 3 4 5
Utilities / Re: best process killer application
« on: January 17, 2019, 10:03:47 pm »
I know it is quite old by the standards of others that have come out since, but I still like WatchCat

Applications / Re: The Java drama and the OS/2 Community.
« on: November 10, 2018, 08:45:39 pm »
The dissapointing part of all of this is how far Java has diverged from its original promise.

Originally it was "write once, run anywhere".  Part of this  implied that your apps would run on all future versions of Java on all future platforms.  The idea that all versions of the Java runtime were (in theory) going to be backwards compatible with previously released versions. 

Unfortunately this got abandoned quickly.  Java apps that require a specific version of the Java runtime, and in some cases I've even seen Java stuff that requires both a specific version of Java on a specific OS.

Setup & Installation / Re: OS2 Warp Version 3 wont boot from Hard Drive
« on: October 19, 2018, 10:19:30 pm »
This could be two things.  Just re-reading your original post it sounds like it'll boot with a CD drive installed, but once you disconnect the CD drive it won't boot.

First double check the jumpers on your hard disk.  There will either be a jumper setting for "single" *or* if there is no setting for "single" try pulling the jumper out entirely.  Some of those old drives would default to single if no jumper was installed.  Some BIOSes -  especially older ones, if they see a "master" drive on the IDE bus they'll then look for a "Slave" on that bus too.  If they don't find it they'd come to a grinding halt.

The second thing it could be, if it is starting to initially boot but then stopping, the original release of Warp 3 had a very buggy IDE driver (ibm1s506 and others).  Back in the day I had a 386 which would boot Warp 3 when the CD drive was *not* plugged in but as soon as it was plugged in it would crash.  IBM released a fix for the buggy drivers on the install disks at:

If it is a driver issue that might fix it.


For Warp 3 non-connect, you'll need to install MPTS.  Technically MPTS is only licensed for Warp 3 Connect or Warp 4, Warp Server, Warp Server for eBusiness, MCP, but it'll work on plain old non-connect Warp 3 and IBM still has it posted on one of their public FTP servers.  I doubt IBM is all that worried about people using MPTS on non-connect Warp 3...

There are 2 versions - a 16 bit version and the 32 bit version.  Pick one of them but not both.  Both will work with the TCP apps included in the bonuspack (although I think there were a few minor incompatibilities with the 32 bit stack and the Bonuspack TCP apps, but it didn't cause major problems).  As I recall some newer apps will only work with the 32 bit version, but (and it's been a while since I've set up a Warp 3 box) there was some file in the 32 bit stack that if I recall you had to swap out to make it work.  Anyways, here's where you can grab what you need.

The 16 bit version you can grab from here:

And then there is a fixpack for it at:

Or the 32 bit stack is at:

With a fixpack

Additional fix to fix a random stack crash in the 32 bit stack:

If I recall you first install the TCP internet connection kit from the bonuspack (use the selective install - some of the stuff like the newsreader and email client you don't really need).  Then install the base MPTS, then the fixpak for the MPTS you've installed, and then if you've gone with the 32 bit stack the

You'll want to use one of the newer Firefox builds.  Most should work with Warp 4.52, but I can't recall what the last one to work with Warp 3 was.  You'll definitely need to instal Warp Fixpak 40 if you're running 3.

I still have a couple of Warp 3 connect systems that I maintain running.  To be honest it has been so long since I set them up that I can't recall all the steps, but like Warp 3 has always done for me, they just keep on doing what they do best without crashing.

Programming / Re: SIO, SIO2K
« on: August 08, 2018, 09:38:19 pm »
As Neil said, I am guessing similar - if someone familiar with 386 assembler can meet with Ray for a period of time to learn what can be learned about the source, then this would be much more useful then just a bunch of code and having to guess at how to build it.

As a registered user of SIO, I still use it to this very day.  There continue to be things it can do which IBM's drivers can't.

Storage / Re: Help! I don't want losing my data.
« on: June 15, 2018, 11:13:52 pm »
I agree that the last time I tried the NTFS driver in OS/2 it did not work very well and is read-only.  I would not recommend it.

As suggested the best-case situation is to make your common data partition a FAT32 partition.  Then you can see it from both OS/2 and Windows.  It works but you do have to jump through a few hoops to make it work.

The other option - if the system is going to be used in a home environment (not a mobile environment) is to put your data drive on a network drive, build something like a NAS.  There are a few benefits to this:

1. If Windows, OS/2, or any other OS you might run (Linux, BSD, etc) can see your NAS then you can likely access your files.
2. If you have more then one computer at your location, you can access your files from any computer
3. If a end-user computer happens to crash or die - due to either hardware or software failure - your files should still be safe if your NAS is still safe
4. It is easy to backup a NAS - either build another NAS as a backup for your files, or use any of the "cloud-based" backup options and have the NAS automagically backup/sync your files to a server somewhere on the internet
5. If you want to test another OS, you can safely wipe your computer without having to worry about your files - they're on another system after all.

I know for many people running a network share at their home would be overkill, but depending on the situation sometimes it is a better option then storing files on a local PC.

Setup & Installation / Re: OS/2 Warp 3 Installation Issue
« on: March 26, 2018, 03:44:03 am »

A few thoughts.

If you have not already, grab warpinst.exe from IBM and copy replace older files on your boot disk(s) with files in the archives. Especially anything dealing with SCSI since you're working with a SCSI system - with perhaps the exception of the drivers that actually work with your SCSI card.  You can grab this file from:

Yes, IBM still has OS/2 files available on its FTP servers!

The system memory should not be a problem.  The main issue with Warp 3 was that if the system had more then 64 MB, then Warp would not see memory above 64 MB. Once installed and up and running you can use patchldr from Hobbes to see the "extra" memory - up to 512 MB as I recall (the Warp 3 kernel has  a 512 MB limit)

For the hard disk, there is a limit on how big the boot drive partition can be in Warp 3.  The boot partition for OS/2 must be with the first 1024 cylinders of the disk - if the end of your boot partition is beyond the first 1024 cylinders then the install won't complete, the system won't boot.

For starters - try the install using the Advanced install, go into FDISK when it lets you do so, and delete all partitions on the drive.  Select the option to write the changes to the disk and then reboot - power down, boot back up with your floppies selecting the Advanced install.

After the reboot see if it'll let you install Boot Manager and create a parition on your drive.  Your boot partition does not need to be very big.  Remember this is Warp 3 which came out originally in 1994.  200 MB is adequate for the OS install, in fact the original manual recommends 25 to 55 MB for the boot partition (although I do recommend more since - after you get things like TCP/IP, stuff from the bonus pack, and Fixpak 40 installed you'll need more then 55 MB).  Assign your Boot partition as Startable and assign it as Drive C (if FDISK doesn't do this already, I can't recall - it has been a few years since I did a Warp 3 install from original install disks).  Exit FDISK and select the option to write the changes to disk.

On Warp 3 installs I've often gone with 500 MB boot drives with success.  Note that making sure the boot partition is within the first 1024 cylinders of the drive should take care of the issue that Bogdan is talking about suggesting a smaller then 8 GB drive.   If Warp can see the drive itself (which is suggested based on the posted screen shots), then it is more likely a problem that the partition is just too big.

Note - if Warp 3's fdisk won't let you partition the drive properly you may have to use something like DFSee as suggested in an earlier post.

If I recall correctly you'll have to reboot again with your floppies, again select the Advanced install.  See if you can get it to the section where it'll let you format the partition - use HPFS - and if it'll do that then hopefully it'll go through the rest of the install.

** On some systems it'll get through the first part of the installation process, will try and boot to the hard disk to continue the process, and it'll fail to boot.  On these systems if it gets through the text-based install but fails to boot to the graphicall install part, try the following:

1.  Boot with your floppies, when it gets to the "select easy install or advanced" it also has an option to press F3 to go to a command prompt/exit.  Press F3

2.  From the command prompt, type:

sysinstx c:

You might need to search around to figure out which floppy the sysinstx utility is on - if I recall it is on either disk 1 or 2, you can do a dir command at the promot to see the floppy directory / contents.

Assuming it does not come up with an error, pull your floppy out and reboot with CTRL-ALT-DEL

Sysinstx is a utility on one of the boot floppies that'll transfer some of the main boot files over to the hard disk specified.  The installation app is supposed to do this for you, but it doesn't always work.

Also a few hints during install.  If you do get to the point of the graphical desktop and graphical install, do NOT try and install video drivers / sound drivers during install.  Just let it do its thing using VGA and such.  I've seen the installer crash while trying to install these drivers during an initial install. You can always install them once your desktop is up and running.

Hope this helps.

This sounds fantastic, I can't wait to try it out.

Are the additional sample rates available to any audio adapter, or just USB?

Just wondering - I've got a couple of Warp boxes running audio logging 24x7, I'd love to be able to up the sample rate (they're using onboard audio cards supported via Uniaudio). 

I could of course switch these 2 systems over to using USB audio cards if needed.

General Discussion / Re: Abandonware
« on: December 01, 2017, 06:16:51 am »
I would not support this.

Going back to the book analogy, if I write a book I expect to own the copyright to that book for the period of time that it is protected.  That generally means that I'll own the rights as long as I am alive, and then my estate / family / etc will continue to own the rights for 50 years after my death.

Whether or not I chose to update or support that book is not relevant.  Whether or not I chose to have the book available in publication that entire time is not relevant.  What is relevant is that I spent the time and effort to write the book, provide the product, and for the duration that it is protected under law it should be up to me (or those to whom the ownership has been passed) to decide on the fate of that work.  If I chose to offer it to the public domain / a free to use  license / a creative commons license / etc - then that should be up to me, not up to some law.

Software should be treated similarly.  Time and effort goes into the development and coding of software and that work should be protected - whether or not the software gets updates, support, etc.  If something becomes abandoned then as long as it is still considered protected then it should be up to the owner of those copyrights to decide its fate.

Applications / Re: IBM's Windows 95 Emulator
« on: June 03, 2017, 04:57:11 pm »

As I recall at around the same time that this so-called "screen shot" turned up, an OS/2 port of the BOCHS 386 emulator turned up around the same time.  It was slow and painful to run even on the fastest processors available at the time, but you could install (if you were patient enough) a full copy of Windows 95 on it similar to how you can install Win95 on Virtualbox today.

There was speculation at the time that this "IBM emulator" was simply a screen shot of BOCHS with Windows 95 running which someone had tweaked a bit.  It is anyone's guess if this was actually done inside IBM or if it was someone who just decided to have some fun.  With the lack of anything other then a screen shot it is all speculation, but it would not surprise me to hear that someone inside IBM might have looked at this. 

At the time of Windows 95's release I suspect there was a lot of discussion within IBM about OS/2 - while Lou Gerstner may have already made up his mind, there was also momentum behind OS/2 - the Just Add Warp marketing campaign - aimed at home users - was released in the fall of '95, resulting in December 1995 with OS/2 having more sales then Windows 95 had to home users (ie, I'm not talking about pre-installed on new PCs. but rather people going to the store and purchasing the OS).  Then early 96 - with the PowerPC version still not being completed (although they had "shipped" a version to select customers in December '95) - this was a huge part in the decision (recall that back in those days IBM still thought the PowerPC chip was going to be the next big thing!).  From what we know of the Power PC port of OS/2, it was a strange beast.  From what I recall it could run Dos and Windows software without modification, but in order to run OS/2 applications - the apps would need to be recompiled from source.  And many parts of it were still very much "beta" level code.

If I recall correctly there was also some discussion around a comment that one of the IBM developers had made surrounding the win32s driver (the driver that allows win32s 1.25 to run in WinOS/2).  The discussion had something to do with the driver having the capability to be modified / extended to allow other 32 bit code to run within the OS/2 Dosbox sub-system.  Some speculated that this might be a route for Win95 to be able to function within OS/2, although my own suspicion is that it was more in reference to the fact that Win32s version 1.3 had been released by Microsoft, and IBM wanted the potential to support this within WinOS/2.


Setup & Installation / Re: OS/2 Warp 3 - Installation
« on: April 23, 2017, 09:23:53 pm »

Note: I always wanted to create the "Updating Warp 3" wiki page just like I have for Warp 4.52 but I never got the time to create it.


At on point I'd actually had a long set of instructions on getting Warp 3 running on more recent hardware, back in the day I found myself regularly supporting Warp 3.  I'm not sure where my original file is but I did find through searching stuff that I've posted much of the information at:,378.msg3311.html#msg3311 (referencing the German language updates),378.msg3312.html#msg3312 (referencing the German language updates),158.msg1227.html#msg1227,177.msg1401.html#msg1401

Checking the various download links in those messages, most of them refer to the original IBM ftp locations and the files still appear to be available.

Setup & Installation / Re: OS/2 Warp 3 - Installation
« on: April 22, 2017, 06:03:32 pm »

The original warp 3 CD requires a lot of hand-holding to get it installed.  By its lonesome and without updates you'll at a minimum need to create some boot disks to get the process started.  If I recall there is a batch (or .cmd) file in the root folder of the CD that can create the disks for you.

But - the original install disks didn't work well with most hardware out there, so you'll need to update the boot disks with IBM's Warpinst - a package that IBM first released shortly after the release of Warp 3 when they started getting endless phone calls from users who couldn't get past the install without a trap.  You can grab it from:

For the original unpatched CD you will need either older hardware, or access to a Warp machine that is up and running.  For those with a copy of Warp up and running it used to be possible to create a patched install CD that you could boot directly from with a packaged called updcd but I don't know if this is still possible - I have not tried this package in several years.

I do see that updcd is still available on Hobbes, but I know that updcd would download fixes and patches from various sources on the web to do the magic that it does.  I don't know if it'll still work or not.

Ultimately it is still possible to make a working Warp 3 box if you have older hardware and the time to spare.  I've done it on Pentium 4 era PC's (around 12 years old now).  If you're working with the original CD the trick is to 1) find a machine with floppy drive, 2) create your fixed install disks, 3) if the machine is SATA based for its hard disks then you'll need the Danis506 drivers on the install media, 4) Don't use too large a hard disk or it'll fail, 5) If you do happen to get it up and running to a desktop you'll want to install the latest FP available for the machine or it'll be unreliable for you (the last one that IBM made available for Warp 3 is FP40, Warp 3 server they did release a FP43). 

I seem to recall that one time I tried to do a Warp 3 install with an unpatched CD I ran into an issue where it trapped if I had more then 512 MB installed.  Getting down to 512MB (or less) involved digging through old memory and such - but eventually I got it up and running.  After installing FP40 it would run when I put 2 GB into the machine (it still didn't recognize the full 2 GB as available due to the way the kernel handles memory on Warp 3).

Good luck!

Something to consider - given the fact that Warp 3 was released 23 years ago (1994) unless you're doing this for fun you might just want to wait for Blue Lion. 

Applications / Re: Do you really need DOS/WIN16 Support?
« on: March 21, 2017, 02:32:32 am »

I definitely need the DOS support. 

One piece of hardware that I run at a radio station that I work at is an RDS encoder that lives on a PC card.  The hardware is quite sensitive to hardware timing, and the custom software runs on either real DOS and a 286 / 386 *or* I've been able to make it work on a newer computer with OS/2's DVM by tweaking the various hardware and timing settings that IBM so nicely provided.

The same hardware won't run under Dosbox, Freedos, and the like.  It doesn't work under Windows (and there has been no software update to it since the original DOS release)

The benefit of running it under OS/2's dosbox is that I can not only keep the thing running with newer hardware, but by tweaking various settings and using the SIO drivers I've been able to add in network capabilities to a system that was never designed to be network capable beyond a simple serial port and modem access.  Between REXX, OS/2's Dosbox, SIO, and  network stack I've got it doing things that it was never designed to do.

As for WinOS/2 support, I still use Pagemaker quite a bit.

So yes - I still find value in these aspects of OS/2.

Multimedia / Re: USB Audio
« on: March 04, 2017, 04:55:23 pm »
The CM108 chip in the Trend only appears to support the playback of 16 bit 44.1 and 48kHz PCM data, so the 10 & 20 kHz system audio files sound distorted for that reason, while a frequency converter in the system would fix that, a simpler solution is to replace the system sound files with 16bit 44.1kHz versions.

Good to hear that it is working with the CM108 (as long as the sample rates of the original files are correct).  There is a ton of USB stuff that uses that chipset - from the cheap USB audio dongles that you can find on ebay for $1 to $5, a ton of USB headsets.  I'd also be interested to find out if it works with the Texas Instruments PCM-2900/2902  series chipset which also gets used in a lot of USB audio gear.

Multimedia / Re: USB Audio
« on: March 02, 2017, 02:09:04 am »
I also tried some cheapo chinese USB Audio stick (which broke after about 2 weeks of use).
In general any USB Audio device should work but manufacturers are free to support dedicated sample rates.
They will almost always support 44.1 kHz Stereo because it is so common, then the good stuff will also support 48 kHz Stereo (the Terratec Aureon does) because that is the sample rate for professional sound equipment (as far as I know).


You're correct on the 44.1 and 48, but the other 2 sample rates that are sometimes supported on the higher end USB audio stuff is 96000 Hz and 192000 Hz.  Admittedly these are much less common as they're usually only used in industries where audio is the product (recording industry, radio broadcast production, etc).  I regularly work with a number of sound cards (both USB and non-USB) that support these sample rates.

Admittedly these sample rates are rarely used on consumer-based stuff, and considering that OS/2 doesn't have any current and up to date professional audio production software, I would not suggest that this be a priority.  44.1 and 48 kHz are more then adequate to cover pretty much all the needs that OS/2 would run into.  And given the limited market for high-end audio production I don't really see anyone running out to develop or port high-end audio recording / production software to OS/2.

Pages: 1 [2] 3 4 5