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
46
Hardware / Re: Compaq Armada 1750 [Laptop]
« on: October 29, 2014, 11:26:58 pm »
Hi,

I've actually got an old compaq Armada - it isn't the same model, but from the same time frame.

Mine only had the trackpoint / pointer option (no touch pad), but I found the trackpoint was flaky under the OS/2 mouse driver.  I found that the amouse driver worked well though.

Not sure where amouse lives these days, it used to be on Hobbes but I'm not finding it there right now.  Maybe if you google for it you'll find it.


47
Applications / Re: About eComStation Pricing
« on: October 10, 2014, 01:14:14 am »
> eCS Home/Student gives you the right to be installed on 5 PCs

it's wrong

* 1 license = 1 computer

* if you need 1, 2, 3 or 4 eCS licenses  then you should buy Home/Student.

* if you need >= 5, .. 10, 20, .. licenses then you should buy Business

Hi,

As I seem to recall the above is *almost* correct.

The last version of the eCS license that I actually took the time to read through, the license gives you the right to install it on 2 computers - 1 desktop and 1 laptop - as long as the laptop and desktop are not both in use at the same time.

Of course that may have changed with more recent versions of the license.


48
Applications / Re: Regina REXX vs. OS/2 REXX
« on: October 01, 2014, 03:05:12 am »
I do lots of stuff in classic REXX.  Admittedly on OS/2 I use the built-in REXX support, it just plain works.

I've used Regina quite a bit on both Linux and Windows.  I've found that in general all the REXX stuff that I've developed on OS/2 works fine on Regina in either Linux or Windows (sometimes with very minor modifications).  The only things which don't work are times when I've tied into some specific part of OS/2 or if I've done a quick hard-code of a drive folder / path into the code itself (I generally try and avoid this, but sometimes just to quickly get something up and running to test a concept out I'll do this).  I admit I'm not doing anything hugely complex, usually the projects I put together are either things that I just need to be done for some particular purpose and / or the "commercial software" which will do the same thing costs lots of money.  Sure, I could do any of the same projects in something like Python or PHP, but I've found that I can usually achieve the same end result a lot quicker in REXX.

What I like about REXX is that while it may not be considered the most modern language, for many projects I find it to be one of the quickest languages (at least for me) to go from a concept or idea to having actual working proof of concept code.  And then it is equally quick to take that code, finish development of the project, easily debug, put into production, and run the same code unmodified on multiple platforms (Linux and / or Windows) - even if it was developed on OS/2.

The one thing that I have found - when I talk to other people in the IT world that I know, I'm one of the only ones who knows much of anything about REXX - regardless of whether it is Classic or Object REXX.  I know lots of developers who will turn to Python or PHP to do do things that I would normally do in REXX. 

Keep in mind that one of the original design goals for REXX was to be a  common language that could be used across the varying range of incompatible models of mainframe computers that IBM had on the market.  That design goal led to REXX code being extremely portable while being able to handle both simple and more complex tasks.

As for something like Python - I have no problem with having Python on OS/2, however I'd point out that Python is ported to OS/2.  There's a couple of older versions on Hobbes. Paul Smedley has also ported Python (along with his port of PHP) available on his site too.

Regina on OS/2 - I admit I've never actually tried it.  When I'm working on OS/2 I just use the built-in REXX support. 

49
Setup & Installation / Re: Finished setting up Warp 4?
« on: July 25, 2014, 06:52:31 am »
If you're running Warp 4 with FP15, add in the SMP kernel and loader, SMP doscall and the PSD driver it should be possible to get SMP running on a Warp 4 system... But...

The PSD driver talked about in the link is using the older SMP setup where you have multiple physical CPU's in the system (I had an old Proliant 1600r with dual P3's and wseb smp - the thing could run circles around the 'latest and greatest' p-4 stuff that came out just a few years later!).  I've mostly seen this on servers.  Most of the new systems (the multi-core CPU systems, etc) are using ACPI.  For that you'll need the newer ACPI driver developed for eCS (and the only way to legally get it is a license for eCS). 

As for issues with items such as SNAP and TCP/IP, from what I understand the newest version of SNAP had sorted out the SMP issues.  TCP/IP issues are solved if you install the TCP/IP fixpak, the 32 bit MPTS update and the newstack.zip update from Hobbes. 


50
Setup & Installation / Re: Finished setting up Warp 4?
« on: July 21, 2014, 04:10:14 am »
Hi,

The last public FP available for Warp 4 (without a SWC subscription to bring you up to 4.52) is FP15.  I think there was a FP16 and 17 for folks who had paid support.

There is a public device driver fixpak 2 that can be installed (they'd separated the drivers out by the time of FP15), but honestly - if it is working then you probably don't need it.  If you do want it, you can get it here:

ftp://service.boulder.ibm.com/ps/products/os2/fixes/ddpak/xr_d002/

For those with paid support there is also a Device Driver FP3.

The newstack.zip file mentioned will fix some TCP/IP bugs / crashes which could happen with mpts 08621.  It makes the TCP/IP networking more stable, but if you're not experiencing any crashes then you might not want to bother installing it.  To find out what TCP/IP stack you're running, type:

inetver

and it'll tell you.  I can't recall what newstack.zip brings it up to off the top of my head and right now I'm not at my Warp4 machine. 

If you're running Peer, there is a Peer fixpak at:

ftp://service.boulder.ibm.com/ps/products/lan/fixes/ibm.peer/english-us/ip08414/

Of course there are the other standard "must haves" for OS/2 that I put on just about every install, items including:

-DANIS506.ADD driver (get rid of the ibm1s506.add driver)
-EMX Runtime
-info-zip and unzip
-The various libc / gcc runtimes (for running the later builds of Firefox)
-Warpin
-re-activate the launchpad
-Watchcat (along with the following)
  -xf86sup.sys (from xfree os/2 - allows the death process killer for watchcat to work)
  -death9.zip (there are times when a process hangs that only this can kill it)
-Dossleep  (I can't tell you how many times this has come in handy in CMD files)
-Uniaud (although I don't  know if this would have any use on Virtualbox)
-Various USB drivers (but you've mentioned you don't really care about USB)
-Fat32 ifs driver (useful for all those flash drives formatted with fat32, but if you don't care about USB, then this may be pointless too)

Back in the day I used to also install the win32s 1.25a windows 3.1 update and the Windows media player / multimedia update add-on, but now days not so much.


51
Setup & Installation / Re: driver trouble with Warp 3
« on: May 19, 2014, 05:22:32 am »
Just to toss in $0.02, for me it all depends on what I want to run.  I do keep some copies of Warp 3 around, I also have Warp 4 and eCS.

If I'm looking to run the more up to date stuff that is available for OS/2 then no doubt I'll use my eCS desktop.

However for some stuff, I find that Warp 3 does quite well. 

As an example, I have a machine set up as a print / file / web / ftp / MySQL / time / plus a few other things server.  All of that stuff runs fine under Warp 3, the computer I have it running on runs fine on Warp 3, and since I  have  6 Warp 3 licenses kicking around I didn't really see a need to purchase an eCS license for that computer.

Another Warp 3 box I have running is mainly being used for its DOS support.  Its got a custom hardware card in it which came out around 15 or so years ago and only has DOS software to make it work (its actually at a radio station I do support for).  Originally the software was never written to be TCP/IP aware (although it will take commands via a serial port) I found that by using the DOS support in OS/2 and writing a few REXX scripts,  I can control the system over the internet.  While I'm sure I could make it work on Warp 4 or eCS, it runs just as well on Warp 3's dos support.  Note that I probably could have achieved the same result under Linux, although it likely would have taken a little more work and troubleshooting to get working.

I've also got an older Compaq laptop (a P2, about 15 years old) that I've used as a demo of what it was like using laptops / computers 15 years ago.  Its got Warp 3 and Win98 on a dual-boot (boot manager!) basis.

Even though it is old, Warp 3 can still have a place.  Although I agree that some of the memory limitations it has do limit what newer apps can be made to run on it.

And just for full disclosure, I also use Linux and Windows (XP and 7) on a regular basis.




52
Setup & Installation / Re: driver trouble with Warp 3
« on: May 08, 2014, 02:27:50 am »
Hi,

It is true that Warp 3 (stock) doesn't normally see memory over 512MB, although you can run it on a machine with more memory, it just won't see the extra memory.

Although, I do have 1 Warp 3 machine which I must have applied some type of hack to, it is seeing 768MB Ram (it has a 512MB and a 256MB memory sticks in it).  I can't recall what the hack I did to it was, I'll have to see if I can find it one of these days.

Of course if you want to go for a really retro browser, you can always install the last released version of WebEX (IBM's browser) at:

ftp://service.boulder.ibm.com/ps/products/webexplorer/webxv11h/

It won't be much use on current websites, but interesting to see what the tools were like circa 1994

A lot of the older OS/2 apps do run on Warp 3.  The ones with difficulty are the more recent ports which use API's from Warp 4 (or eCS), or the KEE stuff in the newer kernel.


53
Setup & Installation / Re: driver trouble with Warp 3
« on: May 07, 2014, 07:39:13 am »
Hi Mathais,

I'm beginning to suspect that IBM put out a version with a few extras for what you've got there.  My thinking is that for XR?3000 on syslevel.os2 and syslevel.mpm normally means you've got the original OS/2 Warp (non-connect) version (see the previous CSD level below).

Quote
C:\OS2\INSTALL\SYSLEVEL.OS2
IBM OS/2 Operating System
Version 3.00 Component ID 562260100
Type W
Current CSD-Level: XRGW040
Previous CSD-Level: XRG3000
 
C:\MMOS2\INSTALL\SYSLEVEL.MPM
IBM Multimedia Presentation Manager/2
Version 3.00 Component ID 562137400
Current CSD-Level: XRGW040
Previous CSD-Level: XRG3000

However I also note that you have a couple of items that normally only get installed if you've got the Warp Connect or Warp Server version, specifically:


Quote
C:\MPTN\SYSLEVEL.MPT
IBM OS/2 TCP/IP Stack
Version 5.10 Component ID 5639B1700
Current CSD-Level: WR08400
Previous CSD-Level: WR08210

C:\IBMCOM\SYSLEVEL.TRP
IBM OS/2 LAN Adapter and Protocol Support
Version 5.10 Component ID 5639A5700
Current CSD-Level: WR08400
Previous CSD-Level: WR08210

C:\MPTN\SYSLEVEL.DHC
IBM OS/2 Dynamic Host Configuration Protocol Services
Version 4.00 Component ID 562290901
Current CSD-Level: WR08400
Previous CSD-Level: WR08210

Normally these show up on the Connect version after you've installed MPTS, although the version of the "IBM OS/2 LAN Adapter and Protocol Support" is the version that was in Warp Server (the version of Warp Server built on top of Warp 3).  It isn't all that big a deal though - it'll all work together.


Have a look at your install CD and see if you've got folder:

\cid\img\tcpip

or

\cid\img\tcpapps

(something to do with tcp in the cid\img folder on the install CD).

If you do have this, then in there you should find an install .exe file, this will install the full TCP/IP stack, as opposed to the Internet Access Kit you found in the bonuspack. Go ahead and install that version of TCP/IP, it should have a full stack in it.

Here's a little background of what's going on (history lesson time!).  At the time that Warp 3 was released, IBM put out Warp with the Bonuspack, which included stuff like the internet access kit, IBM Works, that software to access Compuserve, and a few other items.  The internet access kit in the Bonuspack was based on an older version of TCP/IP - Version 2.0 which had been developed for the older OS/2 version 2.x.  But it wasn't the full stack - it was a more crippled version - missing some stuff, and limited to only accessing the internet via dialup modem.  As a side note, Warp 3 at the time also had a flaky-buggy serial port driver which worked on some modems / ports, but not on others.  This led in part to the popularity of Ray Gwinn's SIO driver (which always seemed to work), and also added to some of the early complaints about OS/2 Warp being difficult to install and not always working properly with hardware, but that's a different story.

Fast forward a month or two from the initial release and IBM releases Warp 3 Connect, and then Warp Server (and eventually Warp Server Advanced).  Warp 3 Connect was Warp 3 with the LAN stuff added (MPTS, IBM Peer, TCP/IP).  IBM released it with the newer TCP/IP 3.0 (which contained everything in the Internet Access Kit, plus a bunch of other stuff) and MPTS to be able to communicate over network cards.  However (in its infinite wisdom of wanting to make things simpler maybe?) IBM continued to include in the box the same exact Bonuspack that was in the earlier (non-connect) version of Warp 3.    This meant that you could install the newer (and better) TCP/IP Version 3 (which came with the Connect stuff) or you could install the older "Internet Access Kit" from the Bonuspack.

As for the client desktop version of Warp, even though they released a few updated versions of Warp 3, they didn't actually remove the Internet Access Kit from the Bonuspack until the release of Warp 4.

*end of history lesson*

Anyways, you should be okay installing the 32 bit MPTS as outlined in the earlier message, it includes the base 32 bit tcp/ip stuff to at least get network connectivity.   I know there are versions of firefox which will run on Warp 3, although I can't recall what the latest one is that'll run.  For Firefox you will need the 32 bit TCP/IP stack.

Or you can install the 16 bit MPTS - with the 16 bit version you'll for sure be able to run the old Netcape Communicator 4.61, although I'm not sure if there are any websites which will still work with that.

-Fahrvenugen

54
Setup & Installation / Re: driver trouble with Warp 3
« on: May 06, 2014, 03:48:57 pm »
Now that you mention it, I think there was at some time an application that someone wrote to allow for the automatic download and install of a lot of these fixes, I seem to recall it was set up for Warp 3 and Warp 4 - to scan your system, figure out what to install, and install it.  Does anyone have the URL to that site?

This app was different from the RSUINSTL.EXE one that IBM came out with, but used some of the same techniques for install.  I'm not sure if it is even still around, a quick google and I'm not finding it.

Martin - maybe one of these days I'll work on an article for the wiki about getting Warp 3 up and running.

55
Setup & Installation / Re: driver trouble with Warp 3
« on: May 06, 2014, 03:42:14 pm »
Hi,

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.


56
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:

ftp://ps.boulder.ibm.com/ps/products/tcpip/fixes/v2.0os2/un64092/

with the latest stack being at:

ftp://ps.boulder.ibm.com/ps/products/tcpip/fixes/v2.0os2/latest/stack/

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:

ftp://ps.boulder.ibm.com/ps/products/tcpip/fixes/v2.0os2/

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:

ftp://ps.boulder.ibm.com/ps/products/mpts/fixes/german/wrg8423_conv/

And of course there is a fixpack for it at:

ftp://ps.boulder.ibm.com/ps/products/mpts/fixes/german/wrg8425_conv/

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.

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

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:

http://hobbes.nmsu.edu/h-search.php?key=dskxtrct&pushbutton=Search

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

ftp://ps.boulder.ibm.com/ps/products/os2/rsu/xrgw040/

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

ftp://ps.boulder.ibm.com/ps/products/os2/rsu/csf143.zip

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:

c:\fp40

c:\service

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:

ftp://ps.boulder.ibm.com/ps/products/tcpip/fixes/v3.1os2/un00959/german/

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:

ftp://ps.boulder.ibm.com/ps/products/mpts/fixes/german/wrg8610_conv/

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:

ftp://ps.boulder.ibm.com/ps/products/mpts/fixes/german/wrg8621/

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

http://hobbes.nmsu.edu/h-search.php?sh=1&button=Search&key=newstack&stype=all&sort=type_name&dir=%2F

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:

ftp://ps.boulder.ibm.com/ps/products/lan/fixes/ibm.peer/german/ipg8196/

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.

http://hobbes.nmsu.edu/h-search.php?sh=1&button=Search&key=countmem.zip&stype=all&sort=type_name&dir=%2Fpub%2Fos2%2Futil%2Fmemory


If you find that you're only seeing 64 megs, then grab patchldr.zip 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.

http://hobbes.nmsu.edu/h-search.php?sh=1&button=Search&key=patchldr.zip&stype=all&sort=type_name&dir=%2F

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. 

Fahrvenugen


58
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.

59
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.


60
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.


Pages: 1 2 3 [4] 5