A quick way to find out what files are living off the fat of the hard drive is
in your URL Location box. To see the memory cache, type
Finally, to see just the images stored in your cache, type
The STARTUP.CMD file is akin to the DOS AUTOEXEC.BAT file. It's a plain text
file that, if present, will execute at startup, right after the WPS loads, and right
before the STARTUP folder items are started.You can use it to start any application
you wish, and you can add parameters. I use it to automatically log into my LAN
each time the workstation starts.
To create one, just create a plain text file with the commands you want to run,
and save it to the root of your OS/2 boot drive as STARTUP.CMD (note: it's case
insensitive, so all caps is not needed).
Unlike the DOS autoexec.bat file, startup.cmd is a REXX command file, and the
full power of the REXX scripting/programming language is available. You can use
it for tasks as simple as a logon to the LAN (LOGON <userid> /P:<password>
or, if you're proficient with REXX, you can write a script to start the dialer from
the command line, retrieve mail and news, etc. The possibilities are near endless.
To automatically close the startup.cmd window when it completes, add the word
"exit" (without the quotes) as the last line of the file.
Then Mark added some more info for use with the startup.cmd with the Alt-F1 boot
You can key it to be knowledgeable about what configuration you start up up in
via the REXX value command. What I mean is that you can setup the \os2\boot\altf1bot.scr
file to list your own boot up configurations:
L) Lan boot
N) No Lan
The first letter in each line must be the letter on the config.? extension in
\os2\boot etc, where the letter matches a special copy of config.sys file in your
\os2\boot directory: like config.L and config.N for the example above (you can't
use 1,2,3,M, or X since they are reserved by os/2, see the already existing config.?
files of those letters in \os2\boot). Put whatever special stuff in the config.?
file(s) that you want different from the default config.sys in the root (altf1bot.scr
is readonly, to edit do attrib -r altftbot.scr). Now go to the desktop properties
"Archive" page and select "display recovery choices at each system
startup" and a timeout so that \config.sys boots after that many seconds.
Finally, you can then have startup.cmd know which special config.sys has run
by putting an environment variable in each that ID's it:
for example in config.L put:
and in config.N
now in your startup.cmd file in the root directory
config = value("BOOTFILE", , "OS2ENVIRONMENT")
if (config == "CONFIG_L") then
put unique things to do for "LAN" state here
if (config == "CONFIG_N") then
things for NO LAN here
if you have lots of these, use a REXX select statement
Obtaining and *installing* ICQ is pretty easy: You must have JAVA installed if
you wish to use the JAVA version of course. I have Java 1.1.6 installed, and it
works without any problems. You must have Java 1.1.4 or 1.1.6. It will NOT work
with Java 1.0.2.
1) Get ICQJava_Preview.ZIP (from http://www.mirabilis.com/index.html)You are now ready to dial up to the Internet, and connect with ICQ.
Go to "Other Operating systems" in the menu at Mirabilis, and it will take you to "OS/2". Don't forget to register, while online, so that you have your user id and password assigned.
2) Go to http://hobbes.nmsu.edu/ and get ICQSETUP.ZIP (it will create an object on your desktop *after* you have created the ICQ directory.
3) Unzip ICQJava_Preview to include the subdirectories
4) Edit your config.sys as per the INSTALL.TXT in the ZIP, to show
Shutdown and reboot your system.
5)Unzip ICQSETUP.zip into your \icq directory.
6)Open the properties notebook of the ICQ Java object on your desktop and edit the path (If is is NOT the default drive C:), otherwise you can skip this step
7) Start ICQ JAVA (offline, you don't have to be online to do this)
8)From the button marked "ICQ",
select "Current User",
"View/Change my listings"
then [you MUST] fill in your ICQ number, Names, Email address, and Password. Any other information that you choose to enter is optional. SAVE the information.
All Warp related redbooks are now on-line at:
First, add the following to your CONFIG.SYS and reboot:
where x: is your OS/2 boot drive. This should get you the desktop, but a malfunctioning WarpCenter. If it doesn't and you have other Desktop directories (x:\Desktop1, etc.), try those.
Once you have your desktop, run the following REXX script:
/**/B. Allberry has suggested this a number of times. It seems to have worked for folks. Be sure to follow other people's advice here and run chkdsk x: /f:2 from a booted floppy and then try this trick.
call RxFuncAdd 'SysLoadFuncs', 'REXXUTIL', 'SysLoadFuncs'
call SysSetObjectData value('DESKTOP',,'OS2ENVIRONMENT'),,
I see that IBM's Redbook "VisualAge for Java" is online and downloadable
That's the URL for the Table of Contents. Each chapter listed is one file. Looks
like the book is complete and in final form to me.
The 02/98 versions of Netscape including the 128 bit encrypted version all report
as Version 2.02-980101 in the title area, if you use the URL about:.
You have to look at the date on the executable to tell which version you are running,
or look inside the netscape.pkg file to see what servicelevel is reported. The latest
version from February reports LEVEL = 000007 and the 128bit encrypted reports LEVEL
Netscape Navigator for OS/2 can be downloaded from the IBM Software Choice Site
or via FTP from ftp://service.boulder.ibm.com/software/asd/ns202/en_us
CDINST.BAT which will run in DOS
Also if you have made any major hardware changes in the past year or so, especially
getting a larger IDE drive, remember to update the install disks with new drivers.
You can get the updated drivers from http://service.software.ibm.com/os2ddpak/html/os_2comp/installa/index.htm.
Also remember to add SET COPYFROMFLOPPY=1 to the beginning of the CONFIG.SYS file
on your install disks so Warp knows to use these new drivers instead of the ones
on the CD.
The simple fact is, the higher the printer resolution, the smaller the openings
of the printhead. And the easier they can get clogged by dried ink, minute dust
particles etc. Hence maintenance issue #1 is cleanliness. If you're using Epson's
paper, they included a special sticky paper to clean the printer roll every 100
sheets. In case you're using the printer only occasionally, it may be a good idea
to do a normal cleaning cycle every now and then to get rid of any ink dried-in-place.
Sometimes a new cartridge helps to "flood" away some particles (but
is now guarantee). Last resort is the power cleaning: I've checked with the
German Epson website. Here is the recipe: First the original in German for
those who can read it. My own translation in the end:
POWER CLEANING for Epson printers:
1. Open the printer cover
2. Press PAUSE
3. Keep ALT pressed for ca 5 seconds, until the printhead moves into the position
for exchanging cartridges. At this point you should already know which printhead
(color or monochrome) is creating your problems. Use the the left cartridge's lever
for color problems, and the right cartridge lever in case of monochrome.
4. Slowly pull up the selected (see above #3) lever until the warning light "no
ink cartridge" just starts to light. DO NOT raise or remove the cartridge itself.
Then put the lever back down again until it snaps in (again).
5. Press ALT.
Now, the printer will perform a power cleaning cycle.
Power cleaning may only performed once. In case the print quality goes down again,
the ink cartridge is used up and must be replaced. If problems persist with a new
cartridge, call your Epson dealer.
I'm no expert in CDs, but let me try to help you. I just read a message on alt.comp.periphs.mainboard.abit
from Sam Detweiler, a programmer for IBM who writes many of their drivers. Sam said
that OS/2 looks to track 1 on a CD. If track 1 is not data, it cannot proceed. I
may not be quoting exactly right. Check it out.
Editor Note: Yes Martin that is correct. Sam has said that OS/2 supports the
original standard. Unfortunately the times, they are a changing and IBM hasn't seen
the need to keep up with them as far as multi-session compatibility.
If you haven't already, I highly recommend you visit...
...and read this important FAQ. Hopefully it will give more insight to the
nature of things.
Editor's note: For more details on setting java up I recommend the following
sites as well - http://www.3cat.com/java_os2/javaos2.html
A question has come up as to whether one can rearrange the trays in the WarpCenter.
I'm not free to experiment at the moment but someone might try renaming the "dock?.cfg"
files in \OS2\DLL These are the trays (I have a whole bunch of empty dock files??)
but by looking in the files you can find the correct ones and renumber them (they
are loaded in order (dock0.cfg,dock1.cfg, etc). I am going to try removing the abandoned
trays to see if that affects anything the next time I have to reboot.
Thanks for the hint. I switched DOCK5.CFG with DOCK6.CFG while I was in OS/2
"regular" session. Shut down WarpCenter and restarted it. - No change.
Shut down PC, no change after reboot. Shut down again and rebooted with a DOS boot
disk in drive A. Made the changes, rebooted into OS/2 the two trays have changed.
One probably be able to make the changes if booting into OS/2 command line.
Editor's note: It will work if you boot directly to an OS/2 command line as well.
(pmmail general page)
FWIW in case anyone missed it. (I like the new way better)
Try using the SETBOOT command. Type HELP SETBOOT at an OS/2 prompt for detailed
info and examples. You can set the various Boot Manager parameters, as well as the
default boot partition with this command.
There is a separate fixpack for each printer driver available from (I think)
There's also one for the spooler in ftp://service.boulder.ibm.com/ps/products/os2/fixes/printerpak/english-us/xr_wspl
And "is it not true that the functionality of this fixpack is already included
in the regular fixpacks?"
The spooler fix is in fixpack 33 (and higher) for Warp 3 and in fixpack 4 (and
higher) for Warp 4. Printer drivers never are.
right click on the printer object and select properties - printer driver "tab"
select the ibmnull driver as your new printer driver close and reboot
right click on the printer object and select properties
printer driver "tab"
right click on the lexmark driver and select delete
should be gone... you could now go to the \os2\dll\lexmark? subdir
and remove the .dll files to really make sure...
and then reboot, the WarpCenter will now work like the Windows 95/98/NT4 taskbar
does. That is to say, to view the contents of any folder in the WarpCenter, you
only need to put the mouse pointer over its icon, and the folder will automatically
Using assoed: open the "file filter" list and select "*.txt"
and remove the association for NOTEPAD.EXE then add an association for EPM or for
OS/2 System Editor and then set this new association as DEFAULT (click the "Set
as default" button at the bottom - which should move this new association to
the top of the list) Then scroll to the bottom of the filters listing and find an
entry for "*TXT". Notice no '.' (period or dot) in this association. Set
it the same as the "*.txt" filter.
Renaming the .EXE doesn't work because the WPS tracks the REN operation and just
changes the pointer for the association to the new file name.
For those of you who have dual booting installed you might want to try this:
I have installed a number of 'Windows Only' programs that work under OS/2. Example: Quick Verses from Parson's Technology.
If you try to install it under WinOs2 it says that it needs to install a newer
version of the WIN32 extensions. It will not work if you try to install the higher
version WIN32 extensions. I booted into WinNT and installed it under NT. I ran it
this way for a while. One time when I was in OS/2 I decided to try to run it under
OS/2. IT RAN FINE! This doesn't work with all programs but it is worth a try.
Duane Chamblee of Indelible Blue has set up a web page which describes how to
install CSDs, MPTS updates, TCP/IP updates, Navigator/2, Java, Feature Installer,
etc., etc. I haven't tried it myself, but I believe they're designed to be download-and-install
without making floppies and with as little pain as possible. http://duanec.indelible-blue.com/fixes/LatestWarp4.html
Xavier Caballe (email@example.com) reports that IBM has released a new IBM1FLPY.ADD
driver for OS/2 that allows one to use more than 11 local drives (i.e. floppy drives
and IDE hard disks) on a machine:
Also, there's a new IBM1S506.ADD driver that supports IDE hard disks up to 8.2
(This driver is dated January 23st, but it was released on April 24th. The readme
file for this driver can be found at:
The URL for the Intellimouse driver is:
Also from Warpcast:
In addition to the new IBM ScrollPoint and Microsoft IntelliMouse drivers reported previously on WarpCast, IBM has also released drivers for the Logitech MouseMan+. These drivers can be found at:
In addition, the previous message reported the URL for the Microsoft IntelliMouse
driver, but not the URL for the IBM ScrollPoint. The ScrollPoint drivers can be
Beware: When you install the Microtek scanner program, it will put its driver
in your config.sys file. You must comment that out, and add it to the dos devices
in the settings for the scanner program.
What did you have prior to FP6? If you have an IDE hard drive, since I think
FP4 or FP5 they reversed the defaults on the IDE driver (IBM1S506.ADD) to now turn
bus mastering on. If your ide controller doesn't support that, it chokes, and the
system freezes. Boot to a floppy and either restore the archived version of IBM1S506.ADD
or add /A:0 /!BM to the BASEDEV=IBM1S506.ADD line in config,.sys to turn bus mastering
off. If that does not fix your problem then you have to give more information. Try
hitting Alt-F2 when you boot and the little white square appears in the upper left
corner of your screen. That will display each driver as it is processed by config.sys
and where she stops should give a clue as to what is hanging.
When you're looking at POPUPLOG.OS2, you need to look two lines above the C0000005
error line. You'll find something that looks like this:
04-23-1998 08:37:34 SYS3175 PID 0057 TID 0001 Slot 007d
Notice that after the date and time there's a "SYS3175" -- which is
the error code that you can look up using help. It also tells you what process (PID)
and thread (TID) were active when it crashed, but you probably won't be interested
in that unless you are the programmer.
The C0000005 error code is the hexadecimal code that tells the type of error
and the error code. In order to figure out what the code means, you have to break
it up into a few pieces and then decode it from there. Suffice to say that the "C"
at the beginning means that it's an error (instead of warning, information, or success);
the "0005" is the error code which means "access exception."
(In other words, the program tried to access memory that it didn't own.) If you
want to see what all the error codes are, you'll need to get a copy of the OS/2
toolkit and look in the BSEERR.H file. There's over 300 of them, so I'm not going
to post them all here. ;-)
However, the errors you're most likely to find in POPUPLOG are:
C0000005 - Access exception
C000009B - Integer divide by zero
C0000095 - Float divide by zero
C000001C - Illegal instruction
There's another line in the POPUPLOG entry that further classifies the error.
Look for a line that begins with "P1" like this:
P1=00000002 P2=0000001b P3=XXXXXXXX P4=XXXXXXXX
For a C0000005 error, a P1 value of 2 (ignoring all the leading zeroes) means
that the access error was on writing to memory. The possibilities are: 0 (unknown),
1 (read), 2 (write), 4 (execute), 8 (space), and 10 (limit). If the program ran
out of stack, it's most likely going to be a limit error. Almost all the access
exception errors that you'll see will be either unknown, read, or write.
So, now that you know a little more... Go poke around in POPUPLOG and see if
you can figure out how some of your programs went belly-up.
flushes the table and lets In-Joy connect and resolve successfully the first
time and each time with my ISP.
That means you are trying to change routing tables for the interface that is
not up. What network setup do you have? This error is possible if you have 'route
add ...' entries in the x:\mptn\bin\setup.cmd for some ppp/slip links which are
established later after boot, or simply have placed some 'route ...' commands before
'ifconfig ...' in setup.cmd.
This caused lots of lockups for me (no traps though) when I would use ping. It
wasn't consistent but the machine would freeze tight ... Also make sure that there
are not multiple copies of DLLs in the MPTN\DLL and TCPIP\DLL directories. I've
seen this cause some problems when installing IP4.1 over previous versions.
TCP/IP 4.1 needs some real attention, they are ALMOST there because when it is
finally configured properly it is fast! (also adds Multicast stuff)
I picked this up from a 'tuning' site in the UK (I think it was anyway), with
the following excerpt from same.
Note 2: the on-line help for CACHE says that DISKIDLE
must be greater than BUFFERIDLE. You should ignore
this, it's a documentation error. For most people DISKIDLE
should be a lot smaller than BUFFERIDLE.
Here is my cache results.
DiskIdle: 20000 milliseconds
MaxAge: 7500 milliseconds
BufferIdle: 40000 milliseconds
Cache size: 2048 kbytes
32 Lazy write worker(s) are enabled.
1 Read ahead worker(s) are enabled.
Actually I would like to have more read ahead, but for some reason or other,
it will only let me set it to 1. If I set it to 2, it disables all caching. I've
never been able to figure that one out, yet!
I was having problems with an S3 - 968 (#9 board) and I was lead to S3's web
site by a fellow member of a forum on Compuserve that was using an S3 Trio64+ chip.
The video driver at the S3 Web site (www.s3.com/bbs). I forget just where they are,
but the navigation links are easy to follow. Suggest you get the "S3ID.EXE"
and run that and it will give you a read out from the chip as to version specifications,
then use that data to look up in the table as to the proper OS/2 driver for your
chip. The one for the Trio64+ and the 968 turned out to be "EN30316.ZIP"
(English - version 3.03.16). This cleared up some of the problems I was having with
a peer network that defied pinning down. It may not be your problem but I think
worth a look.
After weeks of trial and error I have finally managed to configure my Dell Inspiron
3000 to work with OS/2. So here's my notebook configuration and setup to help anyone
who may one day wish to setup a similar notebook to run with OS/2.
Dell Inspiron 3000 (Pentium 266MMX)
24x CD ROM
2 PC-Card Slots (Texas Card Bus 1131)
Neomagic 128bit Graphics (4237B)
1. Straight out of the box OS/2 should install fine.
2. Install the PCMCIA services in the install process.
I chose the Dell Latitude in the list (This won't work
anyway, but it'll install the required software.)
3. Don't worry about the sound card drivers, new ones can
can be found in the Online Device Driver Kit on the net.
4. Booting during the install and the first time will give
errors with the device driver IBM2MT1.SYS, find it in the
CONFIG.SYS and REM it out. This is the PCMCIA driver that
5. Go to the ODDK on the net http//service.ibm.com/oddk.
a. Go to the PCMCIA Socket Services
b. Choose Texas Instruments.
c. Choose Extensa 900 CDT
d. Download the file SS2PCIC2.EXE. This is in BETA but
works ok. Its for the 1130 PC-Card Bus but it works with
the 1131 on the Inspiron.
e. Goto Display Adapters, Choose Neomagic, Choose MagicGraph 128XD
and download the drivers (These are buggy I think but it gives
you high resolution)
f. Goto the Crystal site (www.crystal.com) and follow the link to the
Audio drivers and download CWOS2202.zip.
6. Reboot and goto to you BIOS setup and set the following:
Plug & Play O/S: [No]
Serial Port [Auto]
7. In OS/2 install the Crystal Device Drivers, using the Multimedia
Install in the instructions.
8. Reboot and your Sound should be audible.
9. Install the SS2PCIC2.EXE files as per the instructions, Reboot and
your PCMCIA drivers should load.
10. Goto to the Plug and Play for PCMCIA folder and run the program of
the same name. This should see the PC-Card slots and show:
Card: Serial Status: In
11. Goto the Auto Configurator Utility and choose the Modem Card (3E8)
and Add it to the Selected Cards list and Save.
12. Reboot and your PC-Card should be recognized. Just open the
Plug and Play for PCMCIA program again and it should assign a
COM port to the PC-Card and Status should be Ready.
That's it! OS/2 should be utilizing all the Dell Inspiron fully. Though the video
does scroll (in my case any way), and the video drivers aren't the best. I sometimes
need to refresh the desktop manually. I am hoping that there will be an upgrade
to video driver that will fix this.
For those of you interested in VisualAge, there is an IBM Redbook on it at http://www.redbooks.ibm.com/SG242232/javafor.htm
First, make a copy of the corrupt file. Then try running fixacc, this may fix
it for you. If it does, but the server can't fbe found in it, let me know and I'll
give you the method for fixing that problem. If fixacc doesn't work then... My guess
is that you haven't been running backacc, since that's the very reason you run it,
to protect your net.acc
If you *have* run it, then restacc will recover you to the net.acc you had last
time you ran backacc. If you *haven't* run it then your only recourse is to copy
the net.acc from the IBMLAN\INSTALL directory. This will return you to the default
net.acc. You'll have to rebuild all your domain information. Do you have a backup
DC? If so, you can get the domain information from it.
Running BACKACC with no parameters backs up the net.acc. Specifying a path backs
up the ACL's for the directories and files specified.
In config.sys you need lines something like this:
Then set the parameters for the serial port near the end of the config.sys:
This would set up com3 with irq 5 and location 3E8 and hardware handshaking.
You will need to edit these lines for your OS2 drive and the parameters.
From Ed Mortimer:I've got the internal IDE/ATAPI ZIP in a Warp 4 fp5 system.
First, you don't need the OAD drivers, they are not for the ATAPI Zip. You need
the IDE/ATAPI Removable Disk Driver from the OS/2 Device Driver Site (REMOVE.EXE,
I believe). Follow the instructions included with the download (very straightforward
and simple), -and- place the *FLT line in your config.sys -after- all the other
BASEDEV lines (they don't mention that one). One other stumbling block, OS/2 does
NOT recognize the Zip disk as being pre-formatted -- OS/2 has to format it.
And from Mark Henigan:
Actually, I have parallel port drives on a 386 and a Pentium, and an ATAPI (internal) drive in a K6 machine. I have never had a true IDE drive, which may explain my experience since they require the newdasd package or Warp4 fp6. With the parallel port drives, the OAD setup works well. For the ATAPI internal, it is necessary to install IBMATAPI.FLT or have Warp4 fp6. And, the IBMATAPI.FLT will not work unless you also install OS2DASD.DMD.
The newdasd package presents some significant problems, in my view. I am glad
not to have needed to use it. I noticed that its documentation says a great deal
about needing to reformat disks. Yechhh!
An important issue is whether you have the straight IDE version or the ATAPI
version of the internal Zip drive. Both connect to an IDE channel. However, the
ATAPI version is much more user friendly, from what I can see from other people's
difficulties with the IDE version. Is the Zip drive recognized by the BIOS during
the boot process? If so, is there a line that identifies it as ATAPI or IDE?
A good source of information is the comp.os.os2.setup.storage
newsgroup. Sam Detweiler, a stalwart of OS/2 for many years, spends significant
time there, and will be able to answer any questions you might have regarding disk
storage devices and OS/2.
Finally from Walter Schmidt:
I'm running the so-called beta version of os2dasd with an SCSI ZIP drive, and I've not experienced any significant problems, just 2 minor ones:
* Shutdown seems not to complete, if the latest zip disk read was HPFS formatted.
You may, however, switch off the PC without any problems; the file system is indeed
shut down properly.
* The eject button of the drive is not locked, so you can eject the disk with
the file system being incomplete. This is not a real problem; just don't get used
to eject disks via the button; do it always via the context menu of the drive icon
or the "eject" command.
IBM's drivers are much faster than Iomega's original ones, one can use either
FAT or HPFS on the ZIP disks, and FAT is compatible with the format the disks are
shipped with. The drivers should run with IDE and ATAPI, too.
The best source of information on this topic is
See especially section 3.2.1 which discusses the various drivers and modes of
operation available for ZIP drives!
As I understand it, the parallel port version can be accessed through Iomega's
original OAD drivers, thus using the factory media format. This should be compatible
with IBM's new SCSI/IDE/ATAPI drivers.
The installation is painless and involves starting an executable and going through
a few straightforward dialog boxes. It also comes with an uninstall program.
You may get it under support and software at the Kensington site whose web address
is guess........ http://www.kensington.com.
I posted this up on the internal IBM Warp 4 forum, but I think it is something
that might be useful.
1. Don't let Warp 4 install any video driver except VGA. a) It may not work,
and b) you will probably wind up having to reset to VGA anyway to install an updated
2. Don't let Warp 4 install ANY printer driver. It probably won't be the latest
version, and you will wind up installing it again.
3. Don't let Warp 4 install TCP/IP unless you really want Web Explorer, Newsreader/2,
UglyMail (oops), etc. After the install completes, go back in the CD to x:\CID\IMG\TCPAPPS
and run the install.exe. This will lead you through a selective install of TCP/IP.
FWIW, you can uninstall all of TCP/IP from the System Setup folder and use the above
method to eliminate those things you didn't want in the first place. The only bug
I have found is that the tcpcfg.hlp file gets put into the wrong sub-directory.
Just find it and move it. Don't forget to re-apply the latest TCP/IP fixes after
I'd stuck this in my notes, for when I was teaching OS/2 classes for Learning
Tree. I got the information from the *extremely* knowledgeable guy who trained me
to teach the class... when I started, I was overwhelmed at the idea of covering
every single line in the config.sys. By the end of my tenure, I spent 2-3 hours
doing so. :-)
This is mostly a 1.3 relic. You can turn off the ability for OS/2 to go to the
disk drive. NOSWAP means that there is no swapper file. You probably want to leave
this as-is unless you have a LOT of RAM (and even then you probably don't want to
mess with it). You can turn this to NO to turn off virtual memory. It's very rarely
NOMOVE = OS/2 will not move memory -- to approximate a real time OS.
COMMIT= makes OS/2 ensure that the memory is allocated. System will run more
reliably but slower; swap file will get really big.
An undocumented parameter: SWAPDOS. OS/2 will not swap DOS memory in and out
usually. This lets you tell it to do otherwise.
And since it seems relevant to the discussion... I think I grabbed the following
from a Compuserve message, but I no longer remember for sure.
How OS/2 addresses RAM above 16M
OS/2 will attempt to address all RAM directly but it can be limited by device
drivers to 16M of directly addressable RAM. OS/2 queries loaded device drivers (using
a DOSDevIOCtl, Category 8, function 63h API call) to determine if a given device
driver can access more than 16M of RAM. If any device driver on the system returns
that it cannot address more than 16M of RAM, then OS/2 will only directly address
16M of RAM. RAM above 16M is reserved for an "in memory" swap file which
will be used before SWAPPER.DAT is used. Note that if NOSWAP is set in the MEMMAN
statement, the "in memory" swap file is not disabled.
Below are a few reasons that a device driver may not be able to address RAM above
16M. The most common is that the device driver is a block device driver (a device
driver which uses DMA) whose DMA channel is only 24bits and the device driver was
not programmed to work around the DMA's limitation of addressing 16M of RAM. Another
reason is the device driver may have been programmed for OS/2 1.3 and is therefore
subject to the maximum amount of RAM which OS/2 1.3 could address which is 16M.
Also if the greater than 16M bit in the Device Driver Attributes which are returned
from the API call is not set, this will occur.
The server must support reget first, but I bet that Caldera's ftp server will
support it. After that, you need an ftp client that supports reget... FTPBrowser,
NFTP, NcFTP and wget (this latest one is not exactly an ftp client, but you will
love it after a while :) at least, that all can be found at hobbes, supports reget.