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 ... 6
Setup & Installation / Re: [SOLVED?] QuickTime in Win-OS/2 possible?
« on: August 18, 2020, 12:08:04 am »
I can't recall if it is needed for Quicktime for Windows 3.1 to work, but you might need Microsoft's Video For Windows runtime addon.  This also gives early .AVI support along with a slightly enhanced Microsoft Windows Media Player.

The runtime used to be available freely from Microsoft's FTP site, but it is long gone.  Do a google search for and you should be able to find a download of it.  Maybe it should get uploaded to Hobbes one of these days.

Marketplace / Re: eBay - UK
« on: August 06, 2020, 04:00:50 am »
If I bid one more then one item and happen to win more then one, is it safe to guess that you'd  be willing to combine shipping?

Setup & Installation / Re: QuickTime in Win-OS/2 possible?
« on: August 05, 2020, 04:22:22 pm »

The Windows 3.1 version of Quicktime does work in WinOS/2, however if you are running Warp 3 then you'll need:

-Fixpak 40 installed
-Once Fixpak 40 is installed, install Win32s Version 1.25 in a full screen, enhanced  WinOS/2 session
-After installing Win32s 1.25 you need to do a full reboot to make it work.  Once that's done you can confirm it is working by running Freecell (which should run as long as WinOS/2 is running in Enhanced mode)
-To get Win3.1 Quicktime to work / install, make sure you're running WinOS/2 in Enhanced mode and if I recall correctly it has to be installed in full screen mode (it'll run in seamless once it is installed)

To get Win32s 1.25 you can find this on Hobbes at:

Also there is reference on the Hobbes file that for Warp 3 Win32S to work you need "".  This is no longer correct. contains an older version of the driver that allows Win32s 1.25 to run, there were some updates to that driver and it got bundled into a fixpak.  By having Fixpak 40 installed you'll already have the most up to date version of the driver that allows Win32s 1.25 to work in Warp 3.


I just found one of my previous messages where I reference several other posts I made on getting Warp 3 up and running.  If you're looking to get Warp 3 connect up and running and updated, check it out (follow all 4 links),1350.msg12753.html#msg12753


You mentioned Warp 3 Connect. Somewhere I had a list of all the updates needed for this, but I can't seem to find that list, so I'm going from memory here.

To get it installed you'll probably need to update the installation disk drivers, at least for the IDE drivers.  Probably the best is to go with danis506.add driver, find it on Hobbes.  As I recall the CD Rom driver that shipped with Warp was also buggy, you can find an update at:

For fixpaks, once you get it installed Fixpak 40 is the latest for Warp 3 Connect.  There was / is a hack that'll allow you to install Fixpak 42 from Warp Server, but beware - some people who have used that on some machines with Warp 3 (non-server) have run into stability issues.

Don't install the MPTS that comes with Warp 3 - it is an ancient 16 bit version which is buggy.  Go with the 32 bit version from Warp 4.  It is wr08610 for the base and then there's a fix of wr08621

Once that's installed there's an additional tcp/ip fix that is on hobbes that can fix other TCP/IP crashes / issues.

For the TCP/IP stuff, Warp 3 Connect comes with TCP/IP 3.1.  Once you've installed TCP/IP from Warp Connect you'll want to install UN00959.  There's probably a better way to install it, but IBM's files are still at:

If you want Win32s 1.25a support in your WinOS/2, once you've installed Fixpak 40 you can grab that from Hobbes:

Once that's installed you'll need to do a reboot before it'll work properly.

There is an issue with Warp 3 where on some machines it won't see memory above 64 MB.  If that's the case then run Patchldr on your boot loader.  Actually you can probably just run this anyways even if you don't have the 64MB issue, I've never had it cause any trouble.

For SNAP on Warp 3, you'll need Fixpak 40 (or 42 if you decide to go that route)

If you want to use Truetype fonts in Warp 3 there is a Freetype driver that'll do this for you.  I think it is on Hobbes.

I'm sure there are other fixes that I've had on my list, but that's quite a few of them.

Applications / Re: ArcaOS panic
« on: May 27, 2020, 11:40:25 pm »
Yes, it is probably something with vsio causing the crash.  I'd boot to a command prompt and REM it out.

Also I'm not sure if you're using the original SIO or SIO2K (s2kv202 on hobbes).  The sio2k allows for a lot more virtual or real serial ports, if I recall you can set up as many as 256 serial ports with sio2k (either real or virtual) and turn all of those ports into telnet ports via vmodem.  It is tricky to get it set up and working, you'll have to use a configuration file for this, but it can be done.  I can recall years ago setting up a test Maximus BBS system with the potential for something like 25 incoming connections. 

Off Topic discussions / Re: COBOL revived
« on: April 12, 2020, 12:09:51 am »
Pete, you never know, you just might be able to dial into that mainframe in New Jersey to help them out.  Time to dust off the old 300 baud Hayes!

Applications / Re: DOS VDM and Win-OS2 Fans ?
« on: March 22, 2020, 11:06:26 pm »
I think seamless all depends on the hardware and resolution that you have.  I have one machine it works fine on and another that seamless does not work (both running SNAP).  I admit that it never occurred to me that one might be a different resolution then the other, I'll have to check that.

For me the Windows apps that I find myself using most include Wordperfect 6.1 for Windows (with the WPS add-on extensions) and Pagemaker 5.

For must-have, the 2 things I generally always install in WinOS/2 are Win32s version 1.25a (the latest one to work with OS/2) and the Video for Windows runtime update.  While I admit that not a lot uses the Win32s stuff, I do find that there are a lot of video files that won't play without the VFW runtime.

For DOS, I think my most creative use is at an FM radio transmitter site to generate RDS data.  At one site I have an old RDS-ISA card used to generate RDS data.  Its "remote" capability consisted of communications over a serial port with DOS software to make it work.  When it is run on a straight bare bones DOS machine it is also very picky about CPU speeds, the hardware it runs on, and system timing.  I wanted to give it the capability of having its dynamic text updated over a network connection.  So with the help of OS/2 (Warp 3 Connect to be precise), Ray Gwinn's SIO driver, and some REXX scripting I was able to make a system that grabbed my needed data via REXX and then bounce it through to the DOS serial port as RDS radiotext data.  It works like a charm.  It also ran fine on the first machine (an old P3 with an ISA port and Warp 3) that I tried it on, despite the fact that the manufacturer of that card told me I'd probably have trouble making it work on anything faster then a 486 (when I was given the card it came from a 386).  It has been rock-solid stable for about 8 years now.

General Discussion / Re: OS/2 Article on Ars Technica
« on: December 02, 2019, 04:23:23 pm »

I also did a lot of Windows 95 and 98 support back in the day, lots of trying to figure out issues that didn't work as expected, random crashes, and more.

OS/2, especially Warp 3 - sometimes would be a challenge to get it initially installed and running.  Once up and running (and after at least Fixpak 5 had been installed) it was solid. I can recall being asked one time how OS/2 was working for me.  My reply was something along the lines of "It works, it is still working.  By the way I have not rebooted due to a crash yet" (note that I did reboot due to having both Warp and Windows available via Boot Manager).

Of course I will qualify the above with the note that Fixpak 17 was a bit of a exception, while it introduced some significant features (such as the initial SIQ fix) it also caused some instabilities that had to be worked around.  Fortunately those issues were fixed in a subsequent fixpak.

General Discussion / Re: OS/2 Article on Ars Technica
« on: November 29, 2019, 11:15:26 pm »
Not a bad article, mostly accurate but a few things I'd disagree with.  In particular

I'd strongly disagree with the claim that Windows 95 was faster, smoother, and crashed less then Warp on the same hardware.  I recall having Windows 95 and Warp 3 on the same system with boot manager and I found the opposite to be true - Warp (running on HPFS) ran smoother and almost never crashed, yet Windows 95 would frequently give me a BSOD and / or make me wait for things to happen.  But I will also point out that both systems were picky about hardware drivers.   When I had issues with Warp crashing I'd frequently find it was related to a bad driver.  I recall I had an ATI video card and an ESS-chipset sound card - both of which would be troublesome if using the stock drivers that came with OS/2.  Using the updated drivers from ATI and ESS fixed many problems (not to mention using drivers such as SIO for the serial port) .   But to be fair the stock drivers that came with Win95 for this hardware didn't work well either until the manufacturer's updated drivers were installed.  And Microsoft's stock serial port driver in Wind95 didn't work very well either.  In retrospect both OSes had issues in this area.

In my view the biggest benefit that Windows 95 had was Microsoft's bundling agreements and the per-processor license agreements which eventually became the subject of antitrust actions.  Microsoft presented Win95 as the upgrade path to Dos/Win3.1 while leveraging their OEM contracts to lock vendors into paying for licenses for every computer shipped, even computers shipped with someone else's OS (or no OS at all).  Then to kill additional competition they offered MS Office license add-ons for low costs that other software vendors couldn't compete with.  This more then anything is what killed other OSes from gaining any foothold in the x86 market. 

I'd also disagree with the claim that early versions of NT were stable and fault tolerant and did everything advertised, that isn't what I recall of my early experiences with NT.  I'd suggest that NT didn't really become the product it needed to be with regards to stability and usability until NT version 4, and even that didn't start to shine until after a service pack or two.  Although I will give props to NT 3.5 which was almost there.  Of course this is one of those things which could be debated.

I'd agree that the failure of the PPC and the PPC port of OS/2 did significant damage to OS/2.  IBM put a ton of money into that project and it was a huge failure.

Overall not a bad overview of the history.

Setup & Installation / Re: Trying to solve server crash
« on: November 18, 2019, 09:38:03 pm »

If it has been running for a while with XFolder without problems, then it is unlikely to be an issue there.  Over the years with OS/2 I've generally found that OS and software problems normally turn up fairly quickly, they don't normally just show up after a long time of stability.  But if that was the last major change made then certainly remove it and see if the problem fixes itself.

One thing to check though - make sure you've got free space on your drives, especially the one that the swap file is on.

Also - you mentioned this is running as a server.  Check log file sizes on any server software that you're running.  I recall once I had a situation where a MySQL server started crashing - eventually I figured out that the log that MySQL kept had become too big.  After deleting the log file (and I think I tweaked the configuration file to limit the log size or something) the stability came back.

You could also try running checkini on the system - just in case it is something wrong with the ini files.  Before you do this make a backup of your files just in case  something goes wrong.

And as previously mentioned, make sure that logdaem.exe and errlog.dll are not corrupted.

Just checking a few things, logdaem.exe is part of the first failure support technology diagnostic stuff, you could try REMing it out of your config.sys and see if the problem goes away.  I admit that after some googling I'm not finding a lot on logdaem.exe, but there is one article  suggesting it isn't really needed for everyday use and to try REMing it out.

I still am not willing to rule out power supply and / or hardware issues.  FFST could be picking up a hardware problem and throwing the error with logdaem catching it for display/logging.  I've also found that a lot of times when a system is completely locked up (3 finger salute, mouse, keyboard, all don't work) and the problem just starts happening after years of stability, those are the situations where I've often found a hardware issue to explain it.

Not sure if any of this will help.

Setup & Installation / Re: Trying to solve server crash
« on: November 15, 2019, 05:01:49 pm »
Only you know how old your system is and if you've used the cheapest parts or ones with better quality. F.i. if you're running a 2 years old Lenovo or HP standard system probability of failing power supply (capacitors) is much lower as when you're running a 15 years old server build up from the cheapest components available at ebay or alibaba.


I'm not trying to cause a big debate here, but just about 2 months ago I had to replace a bunch of failing capacitors on a 4 year old HP enterprise-grade sever.  I also just took some 5 year old HP desktop machines out of service which have capacitors showing signs of failure.

Poor quality capacitors are still a problem.

Setup & Installation / Re: Trying to solve server crash
« on: November 13, 2019, 09:19:33 pm »
Also when you're looking inside the system, have a look at the capacitors on the motherboard.  If any are showing signs of bulging or leaking, this is a good indication for the cause of a crash.  If this is the case then spend some money on new capacitors and replace them (or find someone who's good with a soldering iron and see if they'll replace them for you).

Applications / Re: Polarbar Mailer
« on: October 03, 2019, 09:12:26 pm »
I admit that I wish the source for PostRoad Mailer had been made available.  It was my preferred email app back in the day and I'd love to see the source become available for updating.

Does anyone know if Dan Porter is still around and if he'd be willing to open the source (presuming he still has it)?  I recall at one point he was open to the idea.  At this point I have no idea if he even still has the source code.


It is probably a combination of 2 things.

First, if you have one of the original shipping releases of Warp 3 red spine (floppy version), the original release shipped with bad IDE and CD drivers that didn't work properly.  I recall a few days of frustration when I first got Warp 3 back in the day, until I called IBM and they pointed me in the direction of the fix.  You'll need to create updated install disks (with tweaked config.sys) using files from the warpinst.exe package.

Second, I think it is correct that Virtualbox may not support the XDF format.  You might be able to get around this - I recall back in the day there was an article I read somewhere about how to create a Warp 3 installation CD if you had the floppy XDF version - if I recall it involved extracting the disks to a hard disk and then burning a CD, then using the 2 boot floppies to get to the point where Warp recognized the CD and you could then run the install from the CD.  Don't ask me where this article might be found - it was a long time ago.  If I were to try and do this now I'd likely just start with one my copies of Warp that came on a CD rather then trying to mess with the floppies.

On another note, I still have a Warp 3 (red spine) install running in a production capacity.  For several reasons it is still probably my favourite release.

Pages: [1] 2 3 ... 6