Information
 - About VOICE
 - VOICE Bylaws
 - Code of Ethics
 - VOICE Goals
 - Meeting Info
 - Mirror Sites
 - Sponsor Info
Departments
 - Announcements
 - Events
 - Events Calendar
 - EZ Reference
 - Help Desk
 - Mailing Lists
 - Newsletters
 - Transcripts
Membership
 - Join VOICE!
 - Members Only
Projects
 - Warpdoctor
 - Freedom of
   Choice Project

 - Hear Our Voice
 - Warpstock '98
 - Warpstock '99
OS/2 Info
 - FAQs
 - Links
VOICE Help Desk


CDROM
  1. A: I have a SB AWE32 MM kit. It uses the Sony CDU75E CDROM drive. This is an ATAPI drive. If yours is ATAPI also and you are running it from the sound card this is what I had to do.
    Before WARP installation:
    Modify (on Disk1 - not the install disk) the following line in config.sys:
    BASEDEV=IBM1S506.ADD
    to read:
    BASEDEV=IBM1S506.ADD /A:2 /P:1E8 /IRQ:11
    where /P: is the address of the CD used by the sound card.
    /IRQ: is the interrupt request used by the sound card.
    Your *address* and *IRQ* can be found in the SB manual.
    Additionally, the CD should be set to *master* (default - usually).

    WARP already installed:
    You still need to do the config.sys modification, however, I have never done this *after* WARP is installed, so I don't know if that is enough to get WARP to access the sound card/CD.

  2. A: A number of suggestions were made to change settings for the 2940UW card. None of the changes made any difference. I just tried again, only this time I inserted media into both the ZIP and JAZ drives. The CDROM is now properly recognized. Note that I also tried with media in only one or the other and the CDROM could not be read. Media must be in both units if they are connected to the scsi card. No changes were made to the basic SCSI card setup. This would appear to be a BUG. I only tried this with WARP 4.0 but I'll bet that the solution will also work with WARP 3.0.

  3. A: SoundBlaster Discovery CD 8X contains a SoundBlaster 32 PnP card, a SamSung CSR-830 8X IDE CDROM, and a bounch of cable and stuff. I did install the CD successfully, even if Selective Install didn't actually recoginize it. Three steps:
    1. Set the CD to Master or StandAlone mode.
    2. Connect the CD to an IDE connector on your motherboard. I use Primary
    (Connector 0) although Secondary (Connector 1) is more recommended.
    3. Use Selective Install to install "IDE CDROM" then reboot.
    4. Put the following line in your config.sys:
    BASEDEV=IBM1s506.ADD /!V
    The driver will automatically recon your IDE connectors. The IDE CD driver will take care the rest. If you don't want to use Selective Install, just make sure you have these two lines in your config.sys:
    BASEDEV=IBMIDECD.FLT
    DEVICE=C:\OS2\BOOT\OS2CDROM.DMD
    IFS=C:\OS2\BOOT\CDFS.IFS
    if it's your first CDROM. The /!V switch will give you a detailed description of your IDE controllers. You can remove it if you don't want it.

    The SoundBlaster 32 PnP is a little more tricky. I used Selective Install (with maximum hard detection) as instructed. The program would detect it as a SoundBlaster AWE PnP and install drivers for me. But after I rebooted as instructed, there's no sound or anything. I tried to use different IRQ and DMA but none worked. By the time I got a email from Jens about this CreativeLab's ftp site at WWW.CREAF.COM/WWWNEW/TECH/FTP/FTP-SB16AWE.HTML So I went there and got the file AWEOS2.EXE. I decided that that's what I needed after all. So I expanded the files and ran install. It went smoothly utill close to finish it mentioned some error in MMOS2.INI and it said the installation is incompleted.
    I started to feel a little frustrated. But a glance at the MMOS2.INI showed that it filled with references to ProAudio Spectrum 16 card, which is my original card when installing the Warp 4. That's definitly not right. So I used Selective Uninstall to remove the MMOS2 support, rebooted, and then re-installed it using the auto-detected SB AWE PnP card, then rebooted. Then I heard this beautiful system start wave sound!
    It's amazing! OS/2 Warp 4 does support this card after all (I haven't re-installed the downloaded AWEOS2.EXE yet!) I checked my system, First thing is that my MMOS2 folder is empty. A little further investigate revealed that all the executables, templates and everything else are there, it's just that the install program seemed to forget to re-create the objects. No big deal! I thought, I just drag-n-drop them myself and I got everything I wanted in less than 5 minutes. I played around and everthing seemed to be working!

    I then installed the AWEOS2 again, which has some nice features and added this nice AWE control panel. Everything went fine this time. After rebooted, I have great sound and a not-very-useful AWE control panel. I decided to let everybody know the news, so I hurried to my iLink and hit dial. But the modem didn't respond.
    After a while, I decided that there must be some conflicts between the sound card driver and the modem since the modem worked all the way prior to the sound card installation. I called up Hardware Manager and voila! the PnP sound card decided to use IRQ 5 which is exactly the one my modem used. I followed the readme file which came with AWEOS2.EXE and put in my own parameters:
    DEVICE=C:\OS2\DRIVERS\SBAWE32\SBAWED2.SYS /C:1 /D:1 /H:5 /I:11 /A:220 /M:330 /N:SBAUD1$
    where IRQ 11, DMA 1 and 5 are known to be available on my system. Rebooted, everything's working!


Desktop - Workplace Shell
  1. A: This green icon is from a program that was deleted from the drive. If you have no pull-out drawer next to this thing it will not delete because there isn't another to fill its place. So drag something to the drawer button next to it then it should delete.

Device Drivers
  1. Crystal Semiconductor and OS/2 Web Page - Timur Tabi's page with alot of information, links and available drivers.

  2. Device Driver Support for Hard Disk Drives >4.3GB >8.4GB - FixPak 35 (FP35) for Warp 3 and FixPak 6 (FP6) for Warp 4 extended support for fixed Enhanced IDE drives to sizes up to 8.4GB and added new caching HPFS and FAT file system support for removable media drives such as SCSI Syquest Syjet 1.5GB portable hard drive and the Iomega jaz 1GB and 2GB personal hard drives. This package contains updates to the support in FP35 and FP6, extending support to fixed Enhanced IDE drives greater than 8.4GB, fixing some problems, and adding additional documentation on removable media support. If you install or have installed fixpaks newer than FP35 or FP6 then this package is not required.

  3. Epson Drivers - - Full version of EPSON OS/2 printer drivers. List of supported printers on site.

  4. FAT32.IFS - FAT32.IFS for OS/2 will allow you to access FAT32 partitions from OS/2

  5. GRADD Drivers - GRADDBB.071 - ATI Rage II/Mach 64, Chips & Technology 6555X, Matrox Millenium/Mystique, S3 864/TRIO and S3 Virge/Virge VX. Also included are generic VGA and SVGA support.

  6. Hobbes - Index of ftp://hobbes.nmsu.edu/os2/drivers/

  7. HPFS386 - Support for HPFS386 on removable media for OS/2 Warp LAN Server.

  8. Installation Diskette Updates - OS/2 v 3.0 and 4.0 Component updates.
    Adaptec 7870 Hardfile Controller Support
    Greater Than 4.3GB IDE Hardfile Support
    IDE CD-ROM Support
    PIIX PCI Busmaster/Ultra DMA Support

  9. OS/2 Device Drivers - FAQ's for those writing or planning to write OS/2 device drivers.

  10. OS/2 Device Driver Pak On-Line - IBM offers updated and or additional device drivers that were not included with OS/2 Warp.

  11. The Ultimate Sound Page - Sound card drivers plus tips on installation and troubleshooting. Offered in several languages.

  12. SIO - SIO is a set of "Serial Input Output" drivers and utilities for OS/2 authored by Ray Gwinn.

  13. StWTV - Application for the WinTV/PCI from Hauppauge -

  14. Twain - CFM TWAIN for IBM OS/2

  15. Twain - Solution Technology provides a list of applications

  16. Warp TV - WinCast FAQ Install and setup.

Fixpacks
    1. A: IBM Software Updates. This site has links to the latest base operating system updates and instructions on setting up your OS/2 system to enable Remote Software Updates (RSU). TCP/IP Fixes are also available.

    2. A: The readme2 file in each fixpack contains the APAR (Authorized program analysis report). This is a list of all fixes from any previous fixpack up to and including most current. If you choose to use the RSU, you can view the most current readme2 by going to the IBM Software Updates page and follow the link for Diskettes for Warp 3.x or Diskettes for Warp 4.0, select language, select latest fixpack directory. Here you will find the "readme2". Word to the wise: If it's not broken, don't fix it.

    3. A: Fixpacks don't change the SYSLEVEL (only CSDs would, but there are no CSD's for Warp), however they change the revision level, you can check it with the VER /R command from an OS/2 window, the revision level for Fixpack 6 is Revision 9.030 or you can check it with the SYSLEVEL command.

    4. A: You may use the Remote Software Updates (RSU) per instructions on the IBM Software Updates page. or install by downloading Diskettes for Warp 3.x or Diskettes for Warp 4.0. There will be readme files in the fixpack directory that will explain how to create diskimages and install the selected fixpack.

    5. A: You've either selected the name of a directory that already exists, or you've deleted the archive directory that a previous fixpack created.
      Do the following:
      1. Starting with drive C, delete CSF_SEL.xxx, if it exists, from the root drive of all partitions (xxx is 000 to 999).
      2. Rename LOGF0000.OS2 in the OS2\INSTALL directory.
      3. Reapply the FixPak.

    Install

    1. A: As you know, WIN95 apps won't run under OS/2. I just installed this setup with a friend of mine, and no problems rose. You can just install OS/2 on a seperate partition, and install bootmanager. You probably have to format your partition do get this, but it works. Be sure to install bootmanager at the start of your HDD. Then you can install a Windows 95 partition and an OS/2 partition. Then you can install OS/2. Choose "advanced install" so that you can select the partition on wich you want to install OS/2. Set this partition installable with Fdisk (is automaticly started after telling install you want to use an other partition than C:/ ). But Bootmanager wants to be on the first 1Mb of the HDD.

    Internet Access Kit

    1. A: TCP/IP support:

      1. If you installed any networking components, the system will have installed icons in the SYSTEM SETUP - Install\Remove folder. Take advantage of them, and use them. Reboot after each so that it can unlock the drivers and delete the directory. You can leave the "selective install for networking" and DON'T use the "remove selective install for networking."

      2. Check the config. sys -- remove any references to MPTN, IBMCOM or TCPIP, in the paths, sets and device statements. Reboot.

      3. Delete the IBMCOM, MPTN and TCPIP directories if they are still on the system.

      4. If you have the "Selective Install for Networking" icon in your Install\Remove folder, use it. If not, open the CDROM drive folder and use the CDROM:\IBMINST\NPINST.EXE program.

      5. If you are running from the CD, you may get asked if you want to install the "Install the network install program" msg, say yes, after selecting the drive.

      6. You will now get a "Installing IBM OS/2 Warp" popup. Take the Easy Installation. (Don't worry, we will make it advanced.)

      7. Dialog Title: Type of Activities Response: "Let Me Choose from ALL Services"

      8. Dialog title: File and Print Services Response: NO

      9. Dialog title: Netware Response: NO

      10. Dialog title: Mobil Office Response: NO

      11. Dialog title: System Mgt Client (Tivoli 10) Response: NO

      12. Dialog title: TCP/IP Services Response: YES- modem support

      13. Dialog title: Remote Access Client Response: NO

      14. Dialog title: Change Adaptor Response: "No Network adaptor"

      15. Dialog title: Confirm? Response: NEXT

      16. Dialog title: Ready to install Response: Select the drive you want to place the software on, and then INSTALL

      17. Dialog title: Shutdown Response: OK

      System will reboot about 4 times installing software. It also disables the Boot Manager during this time, but re-enables it at the end. When it gets through with its thing, you will have to reconfigure your dialers.

    2. A: With the help of Kevin Royalty, I looked around and found an older version of a file called "explore.cat". If you have the same symptoms as those mentioned, do the following:
      1.DIR d:\TCPIP\MSG EXPLORE* /S
      2.The directory structure will look something like this:
      [E:\tcpip\msg]dir explore* /s The volume label in drive E is OS2 DATA. The Volume Serial Number is A6EC:AC15. Directory of E:\tcpip\msg .-..-.. ..:... ..... 0 explore.cat 1 file(s) 4 bytes used Directory of E:\tcpip\msg\enus850 7-22-96 9:29a 28454 0 explore.cat 8-27-96 2:42p 48640 0 explore.dll 2 file(s) 77094 bytes used Total files listed: 2 file(s) 77094 bytes used 596738048 bytes free
      Note the occurence of explore.cat in the E:\tcpip\msg directory. I put dots in place of the date, time, and size since I have deleted the file and I don't know what the actual values are. However, I do remember for a fact that this file was a few days older than the explore.cat file in the E:\tcpip\msg\enus850 directory. After comparing this with Kevin's machine, it turned out the version in the E:\tcpip\msg directory was bogus, hence the reason why I have since deleted it. Bottom line: If you use WebExplorer V1.2 that comes with OS/2 Warp V4 (gold code), the explore.cat file should only reside in d:\tcpip\msg\enus850. If it resides in any other location, rename or delete it. Once I deleted it from this directory, my WebEx problems went away.

    Misc

    1. A: OSHTLIST - GENERAL LIST OF OS/2 TRAPS

      01/25/96
      ======================================================================= General List of OS/2 Traps ======================================================================= Please Read Entire Document for Full Explanation of Procedures --------------------------------------------------------------
      DESCRIPTION
      General List of OS/2 Traps
      RESOLUTION

      TRAP 0000 - DIVIDE ERROR: A program attempted to divide a number by zero. Contact software support.

      TRAP 0001 - DEBUG EXCEPTION: Contact software support.

      TRAP 0002 - HARDWARE/MEMORY ERROR: Memory or hardware failure in the system. Contact hardware support.

      TRAP 0003 - BREAKPOINT: This is a special instruction (INT 3) used in "debugging" software, which was left in the code either accidentally or by design. Contact software support.

      TRAP 0004 - OVERFLOW: An overflow occurred during an arithmetic operation. Contact software support.

      TRAP 0005 - BOUND RANGE EXCEEDED: A Bound instruction exceeded the specified limits. Contact software support.

      TRAP 0006 - INVALID OPCODE: The processor tried to execute an unreserved invalid opcode. Contact software support.

      TRAP 0007 - COPROCESSOR NOT AVAILABLE: If coprocessor diagnostic tests run error-free, contact software support.

      TRAP 0008 - DOUBLE FAULT: The processor detected an exception while processing another exception. It could be caused by either hardware or software. If TRAP 0002 also is being experienced, contact hardware support.

      TRAP 0009 - COPROCESSOR OVERRUN: The middle portion of a COPROCESSOR operand is protected or not present. Contact software support.

      TRAP 000A - INVALID TASK STATE SEGMENT: A task switch to an invalid task-switch segment was attempted. Contact software support.

      TRAP 000B - SEGMENT NOT PRESENT: The referenced segment is not present. Contact software support.

      TRAP 000C - STACK FAULT: The referenced page is not present in memory, or the procedure referencing the page does not have enough privilege to access the page. Contact software support.

      TRAP 000D - GENERAL PROTECTION EXCEPTION: All protection violations that do not cause another exception cause a TRAP 000D. Contact software support.

      TRAP 000E - PAGE FAULT: The referenced page is not present in memory, or the procedure referencing the page does not have enough privilege to access the page. Contact software support.

      TRAP 000F - RESERVED BY INTEL.

      TRAP 0010 - COPROCESSOR ERROR: The processor detected an error from the coprocessor. This could be caused by hardware or software.

      If you receive any of the above traps, please make a note of ALL information on the screen and contact OS/2 Support.
      - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
      IBM disclaims all warranties, whether express or implied, including without limitation, warranties of fitness and merchantability with respect to the information in this document. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1994, 1995 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.


    Modems
    1. A: This site offers initialization strings for several brand name and generic modems.

    2. A: Modify the line in CONFIG.SYS:
          DEVICE=C:\OS2\COM.SYS
      to read
          DEVICE=C:\OS2\COM.SYS (n,xxxx,i)
      where:
      n = COM port.
      xxxx = I/O port address (ISA/EISA computers COM4 is 02E8, COM3 is 03E8).
      i = IRQ request.
      
      No spaces within the parentheses!  And IRQ's must not be duplicated.  If you
      are unsure which IRQ's are in use, use RMVIEW from the command line in an
      OS\2 window.
      
      For example, to configure COM4, modify the existing:
      
          DEVICE=F:\OS2\BOOT\COM.SYS
      to
          DEVICE=F:\OS2\BOOT\COM.SYS (4,02E8,10)
      

    Networking
    1. A: There is a program called KALI which has been ported to OS/2 to run games via network. Take look at ftp://ftp.kali.net/pub/kali/kalios2.zip
      Open up your "Connections" folder, then select Network Services then Shared Resources and Network Connections.
      From there you can share and connect with/to the other computer(s) on your network (provided they all have the same protocol). You'll probably want to use NetBEUI for the protocol if it's just a local network not connected to the net. If it is (or if KALI requires TCP/IP) then you can use that.

    2. A: What network protocol is being used by each system? While the default for both is NetBEUI, it is also possible to configure both to use NetBIOS over TCP/IP (known as Microsoft TCP/IP in Windows 95) or even NetBIOS over IPX.
      Make sure that:

      1) All of the machines are part of the same workgroup (or domain)
      2) All machines are using the same network protocol.
      After this (assuming you installed the File and Print Client under Warp), you should be up and running.

    3. A: Reply 1. The program you are looking for is IBM Lan Distance, it will let you do what you want. You need to install the client program on the Thinkpad and the server side in a machine on the office LAN (and a modem on both). Lan Distance client is included in Warp Connect and Warp 4 and the server side is part of Lan Server (though the programs can also be purchased separately).

      Reply 2. Although I like Remote Access very much, I have had no luck connecting with Remote Access via cellular. Unless your celluar phone systems are different, it probably won't work or it won't work well. Remote access is very particular and requires low noise phone lines to work well. Cellular connections usually have too much noise. HOWEVER - it could be my service, or the data adapter for my cellphone which is causing some of my problems.
      I will answer the rest of the questions as if cellular works fine.
      * What do I need on the OS/2 ThinkPad side?
      Remote access client for OS/2 or for Windows, and a good high speed cellular modem.
      * What do I need on the OS/2 server?
      Remote Access Server and a good high speed modem. If you are going to have multiple simultaneous remote access clients connecting, you may want to consider a supported multiport adapter from DIGI International.
      * What is the IBM dialer program on both sites?
      Remote Access has its own dialer which dials from the client side and answers on the server side.
      * What PCMCIA data/fax modem card is needed?
      I use the internal MWave modem in my ThinkPad. It runs at 28800 currently, and I hear rumors that a 33600 software upgrade is in beta test now. If your ThinkPad does not have an MWave DSP (and a few of them do not) USR is a good choice. Olicom is another good PCMCIA modem.
      * What additional hw/sw components (if any) do I need?
      None. I've been investigating about this topic on the WEB, on the IBM Networking sites http://www.raleigh.ibm.com/, ... . And I think that the Remote Access via GSM in the OS/2 environment should be possible. But I have some difficulties to put all the pieces together.
      * Is there any Remote Control program in the OS/2 environment? I heard about the DCAF. Is there any other?
      SystemView, which comes with Warp Server, Warp Connect, and Warp 4 works well for this. It is not the best choice for a ThinkPad because it takes a lot of system resource (RAM and CPU cycles), but you already have it in the package.


    Sound
    1. A: If you are using the condensor headset/mic that comes in the Warp 4 package, you will need the optional battery pack with a PAS16 sound card. There's a note about it in the readme file in the root directory of your OS/2 boot drive. The address and phone number of the manufacturer is included.

    2. A: Even tho' the SoundScape isn't suppose to work outside of OS/2, it will. If the DOS program supports the SoundScape directly, just add the BLASTER and SNDSCAPE environment variables into AUTOEXEC.BAT (like it does in DOS and Windoze) and it should work. DON'T run SSINIT, or the session will hang.
      And you don't lose the sound in OS/2, either! :)
      Submitted by: VanMan

    System Requirements and Compatibility
    1. A: Processor, memory (RAM) and free hard disk space requirements will vary depending on options installed.
      Minimum requirements are an Intel 486/33* or higher with 12 to 16MB of memory.
      Speech Navigation: Intel Pentium/75 or higher with 4MB additional memory recommended.
      Speech Navigation/Dictation: Intel Pentium/100 or higher with 8-12MB additional memory recommended.
      Installation by selecting options requires 100 to 300MB of free disk space across user-selectable partitions.
      An easy installation (IBM preselected options) requires 200MB of free disk space.
      1.44 MB 3.5 inch diskette drive "A"
      An OS/2-compatible CD-ROM drive
      640x480 resolution video with 256 colors recommended (SVGA mode)
      IBM-compatible mouse
      14.4Kb or higher modem or network connection for internet/Intranet access
      Supported sound card for speech and multimedia
      Noise-cancelling microphone and adapter for speech
      * = or compatible

    2. A: IBM maintains a page with a complete listing of over 2500 devices that are supported. http://www.austin.ibm.com/psinfo/os2hw.html
      If you're using Warp 3.0 or older, there is a link at this site to a compatibility list also.

    3. A: SYSINSTX is used to place the bootable portion of OS/2 onto a hard disk. To use it, just type SYSINSTX followed by the drive letter that you wish to make bootable. This, however, will ONLY install the boot code, it won't install the kernel or any other higher level code. Primarily, this command is used when you want to move your OS/2 drive to another partition, or when you need to restore your system after a disk dies.

    Video
    1. A: You can try checking with the manufacturer or if you're using Warp 4.0 and the drivers weren't on the OS/2 Device Driver Pak that shipped with Warp, check this site.OS/2 Device Driver Pak On-Line The site is maintained by IBM and updated as new device drivers become available.

    Win-OS/2
    1. A: Yes. Make sure that the path to OS/2's winsock.dll is in the autoexec.bat dos path statement, and that the following statement,depending upon your version of OS/2 Warp, is in the autoexec.bat:
      SET ETC=x:\tcpip\dos\etc or
      SET ETC=x:\mptn\etc
      Also, make sure that you don't have the dos support REM'd out in the config.sys.
      Make sure you only have one copy of winsock.dll on your system

    2. A: WIN-OS/2 supports the following levels of Win32s: 1.15, 1.20, 1.25 and 1.25a. Of the WIN32s apps that IBM tested, the following are not supported: Adobe Photoshop, EndNote2 Plus and PSPICE.
      There is more information pertaining to this subject in the README file on your root directory.





    Contact VOICE... All pages © 2001 VOICE