Installing configuring OS 2; misc. hardware drivers

installing os2, configuring os2, drivers os2, os 2 drivers, download os2, os 2 virtual pc, os 2 config sys

Archive for December, 2010

can't install new print driver

I had the old omni.drv driver going, but then wanted to
use the new Canon driver in the Canonos2.exe archive
file on the ibm DD site.  So I got it and unpacked
the file and dragged the print object from the
canonos2.drv folder for the bj200 print I have.
No matter what I do, I keep finding the old driver
in the printer driver page of the new printer’s
properties book.  If I try to delete the old driver
it says it can’t because jobs are still queued to
print, but I checked and the queue is empty.  I then
gave up and deleted the print object and tried using
a printer template and installing the new driver
for it, and it sees the old print driver, if I select
the new driver, Describe and any other app the prints
either state they can’t see the printer or like
epm, die with a divide by 0 error.

I ran checkini twice to make sure the ini’s are clean,
they seem ok.

any help would be great


posted by admin in Uncategorized and have Comments (2)

Warp4 install problems

Hello, people.

The other night I was attempting to upgrade three Warp3 systems to
Warp4.  One of the upgrades went flawlessly, the other two, not so
much.  After having accepted the C: drive as the one I wanted to install
to, the installation program informed me that it didn’t recognize the
file system on the target drive, and gave me the options to reformat or
exit.  I didn’t want to reformat, so I left the systems at Warp3 for
now.  Does anybody out there know what might be the cause of this
message?  All three systems were pretty much identical from a SW
standpoint (Warp3, FP26, HPFS, freshly CHKDSKed, running the same set of
applications), the only difference I can think of is the physical hard
drive (system that allowed itself to be upgraded had a WD 2.5GB, the
others Maxtor 1.2GB).

Any help would be much appreciated!


Tomas Hallin
Affinity Technology Group
Columbia, SC

posted by admin in Uncategorized and have Comment (1)


I am running WARP om a ASUS MB with 64MB,
Intel 200MMX and UltraWide SCSI 3940 from
Adaptec a Seagate HD + External JAZ
Bios is AWARD.

I downloaded the most recent Adaptec SCSI driver
and use it on both machines.

I am running WARP also on an old Pentium 90
with 2 IDE HD and SCSI for my external JAZ.
This machine seems running faster as my new
200MMX with complete SCSI

How come?

A. Demeyer

posted by admin in Uncategorized and have Comments (6)

SMC EtherPower problems

I am just setting up a new PC. Pretty standard stuff; Pentium II/233, 64MB, Yamaha sound,  
4.3GB SCSI disk, Symbios SCSI controller, ATAPI CDROM.

BUT…I can’t get the network card to work! It’s an SMC EtherPower (the UTP/BNC combo). It  
works fine under W95, and indeed under DOS with its little test program exchanging packets  
with another SMC/equipped machine.

Under Warp 4, it won’t work at all. I’ve tried the Digital driver that the install uses, and  
the SMC driver that came with the card. And an older one off the net. None of them even get  
the link integrity LED to light!

Any ideas or experience, anyone?


Bob Eager

email:  rde at

posted by admin in Uncategorized and have Comment (1)

CFM TWAIN – Help needed

This one has CFM tech support stumped! Open for suggestions.

      Microtek E-6 scanner

     The CFM version 5 DEMO acquired the scanner and worked as advertised so I
purchased the REGISTERED version 5. The registered version gives me a SYS3175
error in MAINDS.DS as soon as I try to acquire the scanner. I have been sent an
earlier version of this program as well as the latest update. All have met the
same error message. Interestingly enough – MAINDS.DS was NOT in the DEMO

     Has anyone else had a similar problem or have any ideas for a solution. A
Mr. Ropertz at CFM tech support indicates that they have no solution.


posted by admin in Uncategorized and have Comments (3)

Problem with WinOS2

I’m running Warp 4 on a 40M ThinkPad 755 CDV.
I have recently upgraded to FP5.
Since then I have some problems with WinOS2, especially the fast load  
feature. For example I can only lauch 1-2-3 for Windows once. It  
refuses to be lauched a second time (I have first to kill the WinOS2  
fast load process). Last night, as I was working with a native OS/2  
application, I was notified that WinOS2 made an error and that I should  
close this app.
Has anyone experienced such problems ?
They did never appear on my system with FP1 applied.
Have a nice day

Fran‡ois Hurter
email: aba…
Compuserve: 10041,1117

posted by admin in Uncategorized and have No Comments

comspec sys3015,3017 errors

I apologize in advance for the length of this note, but in the
hope that someone has an idea of what’s wrong, I tried to include as
much information as I could.

I am getting consistent sys3015 and sys3017 error messages,
telling me that "an attempt to reload failed, and
that " cannot be started" These appear (after?)
CONFIG.SYS finishes, but before the desktop appears.  This seems to be
causing a number of unexplained problems with Warp 4 w/FP4.

I have tinkered quite a bit, but have not managed to solve the
problem by myself.  I have even tried (twice) reformatting the
partitions on drive two and doing complete reinstalls (from CD)
of OS/2 Warp4.

Some odd things I see (frequently, but not constantly) are
pull-down menus that freeze up before completely loading, editor
sessions (with e.exe for example) that hang the system, or even with
JAVA114 that started to install and failed consistently at 88% of the
load.   — I temporarily solved that installation problem by setting
PROTECTONLY=YES — (wish I could leave it that way, but I can’t).

By way of background:

I purchased a new PC several months ago, which came with WIN95 on one
large (4.3GB, FAT32) partition.  With Partition Magic, I
added Boot Manager, modified the disk to change the partition
arrangement, and installed Warp4, upgrading to FP 4. I now have 2
PRIMARY partitions on that disk, one for each of the two
operating systems, and I also created a small FAT partition which both
systems could see, so that each system had a C:  and D: drive (FAT32 for
WIN, and HPFS for OS/2), and each saw the small FAT partition in
common.  The remainder of the disk was given over to OS/2 logical
drives, all HPFS.  This system has worked flawlessly (I don’t boot WIN95
much) for several months.  That is my first disk.

About two weeks ago I purchased a second HDD (6.4 MB) with the
idea that I would give that over to entirely to OS/2, and then
re-modify the partitions on the first hard disk.  (by the way,
although I have the newdasd, and have modified my installation
disks, the BIOS apparently won’t let me use anything more than
472MB for the first partition on this second disk) I gave in, and
created a primary partition of that size for OS/2 (it defaults to [D])
on this second disk, and installed Warp, adding Fixpack 4 after
installation completed (I have floppies for the FP, didn’t want FP5
until I was set up).  With a few exceptions the config.sys files for
OS/2 on the first HDD and on the second are almost identical.  I told
Boot Manager that the set default was to be this new WARP 4 on Disk 2.

Besides this 470MB first partition, I then have all logical
drives of about 1.5GB each to fill out the rest of the disk (and all the
drives on this second disk are HPFS) FDISK recognizes everything, and
all partitions work the way you would expect —  except for the kinds of
behavior descrbed here.

some info:

Here are a few pieces of config.sys:
(set copy from floppy in NOT in the OS/2 warp on
the first hard disk)

SET COPYFROMFLOPPY=1 (could move this statement further below)
    (C is OS/2 on the first disk, D is WARP 4 on disk 2, F,G
    first disk HPFS, remaining drives are on the second HDD)

PAUSEONERROR=YES (I put it there, but it doesn’t seem to pause error
messages as exepected though)
  (this version of cmd.exe is dated 9-7-97 and is 74681 bytes)

  (Yes, cmd.exe is there, and it is the same version as the one
  that works fine on the first hard disk which boots os/2 with no

  (I’ve tried adding the /P switch at the end)
  And, though the COMMAND.COM versions in OS/2 system and
  MDOS are not the same file date, it doesn’t seem to matter —
  since I’ve tried copying and renaming them to keep them in
  sync; reversed, even tinkered with one a few days older than
  what OS/2 installs by default) — no effect. The copy of OS/2
  successfully running on the first hard drive has two  different
versions of COMMAND.COM (one in OS2/SYSTEM and one in MDOS —   and
runs   fine) os2/system =09-12-96 53956 bytes; MDOS version  = 9-7-96  
53375 bytes)

  (the only other to CMD.EXE at all in CONFIG)

I’ve added the stock lines
  to the end of CONFIG (assuming these are actually run in that
  order at the end) and the sys errors do not appear until
  after these backup lines write to the screen.  So, if the .inis are
the last thing that CONFIG.SYS is doing, the system errors come after

I cannot see that I am starting a DOS session anywhere (and
restartobjects=…  (as above) should prevent that on reboot)
Although I do NOT see this now, I recall that once or twice I did see D>
(as it might look without a proper prompt configuration or as a plain
vanilla dos prompt might look) But I have not seen this at all of late
(at least that I can catch)  

I am not running a DOS image session, and certainly not on
startup;  I have no startup.cmd file on the second disk.
autoexec.bat is the OS/2 installation default and has no COMSPEC
instruction (nor  should it, I think).  There are no program reference
objects in the startup folder.

I have tried shelling out to the command line from a DOS program (with
WordPerfect 5.1 — it works fine) though in real life I never bother
with it since the desktop is there to use instead;

FWIW (on the chance that comspec errors could not account for these
problems) the mother board is an ASUS TXP4, (rev 1.02) running with a
Pentium 233; Video is a Number9 Reality 772 with 4MB running the Virge
drivers; I did make some adjustments in the bios settings to allow for

>64kMB RAM; Video ROM BIOS shadowing was enabled until I turned it off in desperation the other day.  The BIOS is Award version #401A0-01071

OS/2 help says, for the 3015 error,

1. The COMMAND.COM specified by the COMSPEC environment variable cannot
be found.
2. The COMMAND.COM specified by the COMSPEC environment variable is the
wrong version of COMMAND.COM.
3. An error occurred while trying to read COMMAND.COM from disk.

ACTION: Do the following:
1. Type SET to display the current environment variables.

 – O.K. I could post or send on  email if that would help — the values
do seem to be the ones referenced in CONFIG.SYS

2. Ensure that the COMSPEC variable is specifying a valid version of
 –  (as far as I can tell — and after playing around with
 substituting others — it is)

3. Ensure that COMMAND.COM is the version loaded when the virtual DOS
machine was started.
 (If I understand the line in CONFIG.SYS that does that, it is
  the version that would be loaded in a DVM)
  Except for the CMD.EXE or COMMAND.COM loctions noted above
  there are no other copies anywhere on the second disk, and only those
on disk one as indicated

Any help would be appreciated. TIA

Bob August
Team OS/2

please remove one "r" in return address

posted by admin in Uncategorized and have No Comments

Mustek PP Flatbed Scanners?

        Do these work under OS/2?  If not, then how about Win-OS/2?

posted by admin in Uncategorized and have Comment (1)

selective install hang

Anyone have thoughts on what might cause
selective install to hang my system. Uninstall works
fine, but selective install gives me the "virtual" clock.

Keith Cotroneo

posted by admin in Uncategorized and have No Comments

Parallel Port ZIP Drive..How?

I have been trying to get a parallel port zip drive to wotk under
warp4. Unfortunately the Iomega OS/2 utilities are just about
imcomprehensible. Can any one give me some tips on how to set one up?



posted by admin in Uncategorized and have Comments (3)