da OS/2 Kokua Line


Created on: 09-Oct-1997
Last Changed: 02-Dec-1997 v1.05

One of our main goals is to help other OS/2 users. So here's some kokua ... some help... from our members. Feel free to link to this page on your website or to quote our members. We only ask that you give credit where it's due: Hug-OS/2 & our members ... Mahalo.
INDEX
Legalese: This page ©1997 by HUG-OS/2 and the respective members who retain all rights.
  1. How to kill the registration "elephant": Dave Tholen wanted to know how to get rid of the annoying registration "elephant". This is how I did it:
     - open the DRIVES object (NOT the thing on the WarpCenter)
           OS2
           INSTALL
           Installed Features
           Install Object-Inventory
     - check the "Art - Inventory" item
     - click Uninstall
     - re-boot
    [Return to index] 
    
  2. Where to get ColorWorks/2 for cheep. Deane Yamane wanted to know about the Colorworks firesale. This is what was posted on the OS2-L listserv:
       From: sales@os2store.com
       To: James Ssemakula 
       Date: Wed, 10 Sep 1997 11:31:32 PST
       Subject: LIQUIDATION SALE
                        J3 Computer Technologies
                         http://www.os2store.com
       **********************************************************
                            LIQUIDATION SALE
       Hello, as a registered member of our 'Guest Book' you are
       receiving notice prior to the general public of our hot
       liquidation sale on SPG Colorworks v2 and v1+ products. Once
       inventory is gone that is it, no more will be produced or made
       available. These products are, and will be, fully supported
       by SPG, Inc. (confirmed on Sep. 10, 1997)
    
       Colorworks v2 - $49.00
       Colorworks v1+ - $10.00 (with the purchase of any other product)
    
       As an added bonus to our registered guests we are also having a
       while supplies last blow-out on SmartSuite 96 for OS/2:
       SmartSuite 96 for OS/2 (full, single user version) - $299.00
       * SAVE $150.00
    
       Remember these offers are good while supplies last.
       Orders can be placed on-line at http://www.os2store.com
       Special pricing will be calculated by J3 at the time of purchase
       and will NOT be indicated on our Web site until these offers
       are made available to the general public.
    
       Please send questions to sales@os2store.com
       If you have not visited our Web site recently you should, many
       new products have been added.
    
       As always we welcome your comments.
       Sincerely,
       -Jim
       Need a scanner? Check out our Epson/Applause bundles.
    .............................................................
       Serving the Global OS/2 Community
    
       J3 Computer Technologies
       http://www.os2store.com
       Tel: 800-787-0930
       International: 909-985-6786
       Fax: 909-981-5423
     [Return to index]
    
  3. Users Group relations: For Glenn (Hamamura), check out:
       http://www.software.ibm.com/os/warp/pspinfo/pcugos2.html
       It has a variety of topics on user groups.  Check out the last section:
       "How Can IBM PC User Group Relations Help You?"
    [Return to index] 
    

  4. How to search LISTSERV archives: I originally sent this to my staff.
    This is how I search the LISTSERV archives for the information I need:
    
       To search a LISTSERV archive, you send e-mail to LISTSERV@xxx and
       include a "job deck" in the body of the message.  I've indented it
       here, but it should start in column one in your e-mail:
    
            //ListSrch JOB Echo=No,Reply-Via=Mail
            Database Search DD=Rules OutLim=10000
            //Rules DD *
            SEARCH ORACLE in ADSM-L
            INDEX
            PRINT ALL OF x,y,z
            /*
            //  EOJ
    
       You should do this in two steps.  Send the job with just the "SEARCH"
       and "INDEX" commands first.  That will retrieve an index of all the
       "hits".  Then you can look through the "Subject:" lines to see if you
       want to see the rest of the message.  Note the message numbers and
       then send another job with the SAME "SEARCH" and "INDEX" command
       followed by the "PRINT" command.
    
       For example, suppose you send:
    
            //ListSrch JOB Echo=No,Reply-Via=Mail
            Database Search DD=Rules OutLim=10000
            //Rules DD *
            SEARCH 'storagepool' OR 'backuppool' IN ADSM-L
            INDEX
            /*
            //  EOJ
    
       LISTSERV will send you an index listing for all of the messages that
       have "storagepool" or "backuppool" (or both) in them.  You then decide
       that you want to read say messages 1, 2358, 5942, and 7916.  You send
       the following to retrieve those messages:
    
            //ListSrch JOB Echo=No,Reply-Via=Mail
            Database Search DD=Rules OutLim=10000
            //Rules DD *
            SEARCH 'storagepool' OR 'backuppool' IN ADSM-L
            INDEX
            PRINT ALL OF 1,2358,5942,7916
            /*
            //  EOJ
    
       Some rules you need to be aware of in the "SEARCH" command:
         1.  SEARCH xxx yyy zzz IN ADSM-L
             will search for any messages that have "xxx" AND "yyy" AND "zzz"
             in them (i.e. all three).  as specified above, the search is not
             sensitive to case.  i.e. "xxx" = "Xxx" = "xXx" = "XXX" etc.
         2.  if the thing you want to search for has imbedded blanks, then
             you need to put quote marks around it:  SEARCH 'ADSM API' IN ADSM-L
         3.  single-quotes and double-quotes will result in different answer
             sets.  strings in single-quotes result in non-case-sensitive
             searches.  strings in double-quotes result in case-sensitive
             searches.
         4.  you can do complex queries by using AND, OR, and parentheses. 
    	SEARCH (api OR pipe) AND (AIX or NT) IN ADSM-L
         5.  you can limit the scope of the search by using "UNTIL" or
             "SINCE".  for example, to retrieve only messages that were sent
             after July 1996 you would send:  SEARCH SQL/Backtrack IN ADSM-L SINCE JULY 1996
    
       There are lots more options you can use.  To find out more, send a
       message to any LISTSERV (except ours -- something happened ... I
       broke it) with the message:  GET LISTDB MEMO
    [Return to index ]
    
  5. The CONFIG.SYS for the rest of us
    IMHO (InMyHumbleOpinion), the plain, vanilla OS/2-Warp CONFIG.SYS is seriously flawed. 
    At the very least, you should add or update the following in your CONFIG.SYS file using the 
    OS/2 E.EXE editor immediately after any install or re-install of OS/2.
    
    === [START] CONFIG.SYS updates ========
    SET TZ=HST10					[Line #01]
    SET ScUsePrettyClock=On				[Line #02]
    SET KillFeatureEnabled=On			[Line #03]
    SET RestartObjects=StartupFoldersOnly		[Line #04]
    SWAPPATH="X":\ 2048  "NNNNN"			[Line #05]
    === [END] CONFIG.SYS updates ==========
    
    [Line #01] - This line sets your TimeZone to HST(HawaiianStandardTime) instead of EST5EDT. 
    [Line #02] - This built-in feature changes the WarpCenter time from grey to green on black.
    [Line #03] - With this line, you can "kill" anything with Ctrl & WarpCenter's  SwitchTo 
    AnotherApplication. It's very useful and free.
    [Line #04] - This line insures no never ending loop when you ShutDown & Reboot. 
    [Line #05] - If the "NNNNN" initial size of the SWAPPER.DAT file is 2048, you should make it 
    bigger. How big depends on your system, how many windows you have open etc etc. You can use 
    say MEMSIZE in our FTP site to watch what happens when you adjust the size between Shutdowns. 
    The first 2048 is the expansion in KBs. Replace "X" with your desired drive letter no quotes.
    [Return to index ]
    
  6. Maybe Your CLOCK01.SYS is bad
    I just discovered that replacing CLOCK01.SYS in the \OS2\BOOT directory with  the one on 
    your Warp installation diskettes fixes the screen blanking problem on  at least on some 
    Toshibas.(my Toshiba T430 for instance). ... Makes me a happy camper  once again.
    [Return to index ]
    
  7. How to install Java v1.1.4
    I MD'd FEATURES etc. and the damned FISETUP didn't use
    them. So I removed them. I MD'd a FISETUP directory and
    unzipped FIRUN_NS.ZIP in there. FIRUN_NS.ZIP is the FI121
    that includes NetScape with it.
    
    I then run FISETUP from there, which installed the Netscape
    included with it. (It did create a sub-directory called
    NSINST, (The later vesion of Netscape (dated 11/13), was
    _too old_?) Then I run the FISETUP from the directory where
    I unzipped JAVA1.1.4) This brought up Netscape and
    proceeded to install the JAVA 1.1.4 Then I reinstalled the
    Netscape (dated 11/13), which asked me which JAVA I wanted
    to use. I had both at this time (1.0.2 & 1.1.4), I selected
    1.1.4 and away it went merrily on it's way. I have since removed 
    1.0.2 and everything appears to be running normal.
    
    A couple things to watch for, in config.sys the classpath
    line must NOT have the '.' (signifying the present
    directory) as the first item in the line. Also the PATH
    statement likewise. Here's an example of both those lines.
    
    SET CLASSPATH=C:\NETSCAPE\JAVA11\JEMPCL10.ZIP;C:\NETSCAPE\njclas
    s.zip;C:\JAVA11\LIB\classes.zip;.;.\.;
    
    The above is all one line of course. Note where the . has
    been placed. At the end instead of normally at the front of
    the line. Also that classes.zip has the complete path 
    C:\JAVA11\LIB\classes.zip
    I was forever getting an error which said it could not find
    ....classes.zip. This corrected that.
    
    LIBPATH=C:\NETSCAPE\JAVA11;.;C:\OS2\DLL;C:\OPENDOC\BIN;C:\IB
    MI18N\DLL;C:\MPTN\DLL;C:\NETSCAPE;C:\OS2\MDOS;C:\;C:\OS2\APP
    S\DLL;C:\BONUSPAK\IBMWORKS;C:\JAVA11\DLL;C:\MMOS2\DLL;C:\TCP
    IP\DLL;C:\TCPIP\PCOMOS2;C:\PERF_40;H:\UNIMAINT;C:\EMX\DLL;G:
    \EMBLSH;
    
    This is also one line, and again the . has been moved from
    it's normal position, this time to second in line. I don't recall 
    where I read about  the above, but it did work!
    [Return to index ]