🚀 go-pugleaf

Archive-name: os2-faq/user/part4
Version: 2.1A

[Part 4 of 4]


o If you want to move an icon a small distance, "grab" it from the edge 
nearest the direction you want to move the icon.  

o If you wish to place program output in the REXX queue (for processing by 
a REXX program), try 
    
    DIR *.TXT | RXQUEUE 
    
as an example.  (In other words, pipe the program output to RXQUEUE.)  To 
use this program output in your REXX program, try 
    
    /* Sample */
    WHILE QUEUED() > 0 
    PARSE PULL X 
    SAY X 
    END 

o A clever way to manipulate files that are locked when the Workplace Shell 
is running (e.g.  display drivers) is to add the line CALL=CMD.EXE at the 
end of CONFIG.SYS.  Then Shutdown and reboot.  The system will restart with 
an OS/2 command line prompt.  Type EXIT to proceed into the Workplace 
Shell.  Using CALL is also a convenient way to configure OS/2's serial 
ports using the MODE command.  For example:  
    
    CALL=C:\OS2\MODE.COM COM2:38400,N,8,1,OCTS=OFF,RTS=ON,BUFFER=ON
    
configures COM2 for high speed RTS handshaking and buffered I/O.  You can 
also use either CDD2 or SHIFTRUN; both utilities are available from (3.2) 
Shareware and Freeware Sources.  

Another way, which works well with display drivers, is to copy the new 
DLL(s) to its(their) own directory (say, C:\NEW), then place that directory 
name first in LIBPATH in CONFIG.SYS.  Shutdown and reboot.  OS/2 will use 
that(those) DLL(s) before it attempts to use the one(s) located in 
\OS2\DLL.  [This method is required when using a 16-bit OS/2 2.0 display 
driver with OS/2 2.0 CSD Level 06055 or later.  See (4.6) Corrective 
Service Diskettes.] To switch back to the old driver, edit CONFIG.SYS and 
remove C:\NEW from LIBPATH, then Shutdown and reboot.  

o To shutdown without a mouse, press CTRL-ESC, select the Desktop, then 
press the spacebar (to deselect any icons, if necessary), SHIFT-F10, and 
select Shutdown.  

o If your video driver does not support "seamless" Windows, try running the 
Win-OS/2 Program Manager in a DOS window.  

o Selective Install should be used with caution when changing mouse or 
display drivers.  Verify that proper changes have been made to CONFIG.SYS.  

o If your settings notebooks (or PM Sticky Pads) do not display but are 
listed in the Window List, click on the name of the settings notebook in 
the Window List (brought up with CTRL-ESC) with mouse button two and select 
Cascade.  

o If your \OS2\*.INI files have grown large, use the CopyINI or WPSBackup 
utilities to shrink them.  Both are available from (3.2) Shareware and 
Freeware Sources.  

o To restart the Workplace Shell (without saving desktop settings, perhaps 
after an accidental Arrange), use a utility such as psPM [available from 
(3.2) Shareware and Freeware Sources] to terminate PMSHELL.  

o To get rid of a WPS object that cannot be deleted, try one of the 
following:  

- Insert a blank diskette in Drive A, click on the stubborn object with 
mouse button two, select Move, select the Path page, enter A:\, press 
ENTER, then format the diskette; 

- Use the WPSTools or Black Hole, available from (3.2) Shareware and 
Freeware Sources.  (The WPSTools can also recreate desktop objects that 
have been lost.)  

o To load a device driver into high memory in a particular DOS session 
change the DOS_DEVICE setting for the session and add SIZE=0 before the 
path and filename for the device driver.  For example, the following 
DOS_DEVICE entry:  

    SIZE=0 C:\OS2\MDOS\ANSI.SYS 

loads the ANSI.SYS device driver into high memory in that particular 
session.  

o If you wish to create diskettes from MAKEDSKF (.DSK) image files, such as 
those contained on the CD-ROM version of OS/2, and you do not wish to use 
the DOS and OS/2 utility LOADDSKF, you may use a workstation.  For example, 
on an IBM RS/6000 you may use the command:  

    dd if=(input filename) of=/dev/rfd0 ibs=1b obs=60b conv=sync 

o To reboot the machine from the command line, use:  
    
    SETBOOT /IBD:C
    
Change the last letter (C) if you want to boot from another drive.  

o The settings notebooks now support drag and drop operations for assigning 
icons and for changing menus.  

To change the icon for an object, first open the settings notebook (click 
on the object with the secondary mouse button, then select Open -> 
Settings).  Click on the General tab.  Then drag any other object to the 
icon located on the General page of the settings notebook.  The object's 
icon will change to match.  If you want to restore it to its former state, 
click on the Undo button.  

To assign actions to menus, open the settings notebook, then click on the 
Menu tab.  Click on any of the items in the Available menus section (or 
Create another).  To add an Action, drag the desired program object to the 
Actions on menu section.  

o To quickly maximize a window, double click on its title bar.  To restore 
the window to its former size, double click on the title bar again.  

o Select the Flowed setting (on the View page of the settings notebook) for 
fastest display when opening folders.  

o If you have UNDELETE enabled, but you want to delete an occasional file 
without the overhead incurred by having UNDELETE capability, use the /F 
parameter with the DEL command.  Using this parameter (in either a DOS or 
OS/2 Window) will bypass the routine which moves the file(s) to the 
directory specified by the DELDIR environment variable.  The file(s) 
is(are) deleted faster, but you will not be able to undelete it(them).  The 
/N parameter will prevent prompting ("Are you sure?").  

o OS/2 2.1 now includes the ability to set a power on password.  However, 
if you have forgotten your password, and you cannot unlock your desktop 
when you turn your machine on, try the following.  Start OS/2 from a 
diskette boot [see (4.4) Starting OS/2 from Diskette] to get a command line 
prompt.  At the prompt, enter the following commands:  
    
    C:
    
(assuming OS/2 is installed on Drive C; change if necessary) 
    
    MAKEINI OS2.INI LOCK.RC
    
  
  
  Related information: 
  
  (3.2) Shareware and Freeware Sources 
  (4.4) Starting OS/2 from Diskette 
  (4.6) Corrective Service Diskettes 
  

(5.11) REXX

 How do I use REXX?  What does it do? 

REXX is built into every copy of OS/2 (where it is also known as Procedures 
Language/2).  It is a general purpose, interpreted programming language 
which was first released on IBM mainframes over a decade ago.  REXX is 
extremely easy to learn and use.  It is particularly strong at string 
manipulation, and it has features which are difficult to implement in 
compiled languages (like the ability to read its own source code or execute 
a string as a command).  

OS/2 applications can use REXX as a common scripting language, which means 
that users need not learn separate macro or script languages for each 
application.  For example, the OS/2 versions of Lotus 1-2-3 and Borland 
ObjectVision will interface with REXX.  OS/2's multimedia extensions 
(MMPM/2) contain a REXX interface, so REXX programs can play, record, and 
manipulate sound and video files.  And REXX can be used to create complex 
batch files (with interactive prompting), since it is integrated so tightly 
into OS/2's command processor.  

A pair of REXX visual builders (programming tools which help create even 
complex REXX applications quickly and easily using simple, drag and drop 
manipulation of on screen objects), HockWare's VisPro/REXX and Watcom's VX 
REXX, are now available.  [See (0.2) Recent Developments for more 
information on these two programming tools.] 

For more information on OS/2's REXX interpreter, see the REXX Information 
online documentation located in the Information folder.  For more 
information on REXX generally, consult the REXX Frequently Asked Questions 
List [available from (3.2) Shareware and Freeware Sources].  

 
 Related information: 
 
 (0.2) Recent Developments 
 (3.2) Shareware and Freeware Sources 
 (3.6) Multimedia (MMPM/2)
 

(5.12) ANSI Escape Sequences

 What ANSI escape sequences can be used? 

ANSI escape sequences provide cursor and screen control in OS/2 character 
mode sessions.  By default ANSI support is turned ON (although it may be 
turned off with the command ANSI OFF).  ANSI support is also available in 
DOS sessions if the device driver ANSI.SYS is loaded.  See the online 
Command Reference for details.  

The following ANSI escape sequences are available:  

  Key       
  ESC       Refers to ASCII code 27 (i.e. the Escape key) 
  #         Replace with the appropriate number 
  ....      Replace with additional attributes, if desired 
  
  Escape Code Sequence          Function 
  Cursor Controls               
  ESC[#;#H or ESC[#;#f          Moves cursor to line #, column # 
  ESC[#A                        Moves cursor up # lines 
  ESC[#B                        Moves cursor down # lines 
  ESC[#C                        Moves cursor forward # spaces 
  ESC[#D                        Moves cursor back # spaces 
  ESC[#;#R                      Reports current cursor line and column 
  ESC[s                         Saves cursor position for recall later 
  ESC[u                         Return to saved cursor position 
  Erase Functions               
  ESC[2J                        Clear screen and home cursor 
  ESC[K                         Clear to end of line 
  Set Graphics Rendition        
  ESC[#;#;....;#m               Set display attributes where # is 
                                0 for normal display 
                                1 bold on 
                                4 underline (mono only) 
                                5 blink on 
                                7 reverse video on 
                                8 nondisplayed (invisible) 
                                30 black foreground 
                                31 red foreground 
                                32 green foreground 
                                33 yellow foreground 
                                34 blue foreground 
                                35 magenta foreground 
                                36 cyan foreground 
                                37 white foreground 
                                40 black background 
                                41 red background 
                                42 green background 
                                43 yellow background 
                                44 blue background 
                                45 magenta background 
                                46 cyan background 
                                47 white background 
  ESC[=#;7h                     Put screen in indicated mode where # is 
                                0 for 40x25 black and white 
                                1 40x25 color 
                                2 80x25 black and white 
                                3 80x25 color 
                                4 320x200 color graphics 
                                5 320x200 black and white graphics 
                                6 640x200 black and white graphics 
                                7 to wrap at end of line 
  ESC[=#;7l                     Resets mode # set with above command 
  Keyboard Reassignments        
  ESC[#;#;....#p                The first ASCII code defines what is to be
                                changed; the remaining codes define what it
                                is to be changed to; strings are permitted.
                                Examples: 
                                ESC[65;81p - A becomes Q 
                                ESC[81;65p - Q becomes A 
                                ESC[0;68;"dir";13p - Assign the F10 key to a
                                DIR command.
                                The 0;68 portion is the extended ASCII code
                                for the F10 key and 13 is the ASCII code
                                for a carriage return.  Other function key
                                codes: F1=59, F2=60, F3=61, ...  F10=68.
  
You can use ANSI escape sequences in the PROMPT environment variable to 
create complex command line prompts.  See the online Command Reference 
(under PROMPT) for details.  

For example, if you have a color monitor, try editing your CONFIG.SYS file 
so that 
  
  SET PROMPT=$e[32;40m$e[1m[$P]$e[0m
  
to obtain a more colorful OS/2 command line prompt.  (Case is significant 
in the example given.)  You can do the same for your DOS sessions if you 
edit PROMPT in AUTOEXEC.BAT, assuming you have ANSI.SYS loaded.  Note that 
the $i portion of your PROMPT will enable the help line at the top of the 
window or screen.  It is not included in the example above.  

To change the background color of your OS/2 command line sessions, modify 
your CONFIG.SYS file so that this line is changed as shown:  
  
  SET OS2_SHELL=C:\OS2\CMD.EXE /K BLUESCR.CMD
  
changing the drive letter, if necessary.  Then create a file named 
BLUESCR.CMD which contains the following lines:  
  
  @ECHO OFF 
  PROMPT=$e[32;44;1m
  PROMPT $p$g
  CLS 
  
Save the file to a directory that is named in the SET PATH line of your 
CONFIG.SYS file.  Reboot.  Then, when you start an OS/2 command line, the 
background color will be different.  You can change the numbers in the 
first PROMPT line to obtain different colors.  

If you are using JP Software's 32-bit 4OS2, and you would like the name of 
the current working directory to appear in the title bar, try using the 
following command:  
  
  PROMPT `%@exec[window"%_cwd"]$h[$p]`
  
  
  Related information: 
  
  (5.10) Clever Tricks 
  

(6.1) Promoting OS/2

 What can I do to promote OS/2? 

OS/2 is selling well, but there are steps you can take to assure that 
hardware devices and software will be available for OS/2 in the future.  
Customer requests do matter.  

o Politely, firmly, and repeatedly request driver support from printer, 
video adapter, and other hardware manufacturers.  

o When you receive a mailing for DOS/Windows software with a postpaid 
envelope, return the order form marked "Please send information on your 
OS/2 version."  

o Start a user group at your location.  Contact Gene Barlow (phone 
214-402-6456) at IBM or mail ibmpcug@vnet.ibm.com for assistance.  Think 
about how you can publicize your user group.  For instance, most local 
newspapers and television stations will print/broadcast meeting 
announcements for free.  Your local cable television company will be happy 
to broadcast a videotape of your meeting on the public access channel.  

o Correspond with members of the computer trade press.  Ask for reviews of 
OS/2 software, hardware compatibility testing with OS/2, OS/2 benchmarking, 
etc.  Respond politely but forcefully to press you think unfair; praise 
good reporting.  

o When you purchase a new system, ask the vendor to install OS/2 2.1, and 
to offer credit for dropping DOS and Windows.  If the vendor refuses, you 
may wish to take your business elsewhere.  AST, Northgate, ALR, Unisys, 
Dell, Tangent, IBM, and Ariel Design all offer systems with OS/2 2.1 
preloaded.  

o Make sure your company (or yourself) specifies OS/2 compatibility when 
purchasing new products.  

o Demonstrate OS/2 to friends, relatives, and associates.  

o Ask your computer store to stock OS/2 software titles, have OS/2 
demonstration machines, etc.  

o Pass along useful OS/2 shareware and freeware to your local BBS.  Be sure 
to register OS/2 shareware.  

o Write an outstanding piece of shareware or freeware [See (4.5) Technical 
Support for details on joining DAP].  IBM has been known to recognize such 
work with rewards.  Also, ask authors of DOS/Windows shareware and freeware 
if they would port to OS/2, or volunteer.  

o Recommend products that work well under OS/2; dissuade people from 
purchasing products that do not.  

o Wear OS/2 pins, shirts, buttons, and other souvenirs.  Contact Sue at 
Lees/Keystone (phone 914-273-6755) or the IBM OS/2 Hotline (phone 
800-3-IBM-OS2) to order such items.  

o Join Team OS/2, the international organization for OS/2 enthusiasts.  For 
information on Team OS/2 events you should monitor the TEAMOS2 echomail 
conference on your local FidoNet BBS.  If your local BBS does not carry 
TEAMOS2, ask your system operator to get it.  See (4.11) OS/2 BBSes for the 
names and numbers of several BBSes which carry TEAMOS2.  To join Team OS/2, 
send your name, address, and telephone number to Vicci Conway 
(76711.1123@compuserve.com).  
  
  
  Related information: 
  
  (3.2)  Shareware and Freeware Sources 
  (4.5)  Technical Support 
  (4.11) OS/2 BBSes 
  

(6.2) Creating INF Files

 How can I create INF files? 

Creating INF files (like the OS/2 Frequently Asked Questions List) is 
remarkably straightforward.  All you need is the Information Presentation 
Facility Compiler (IPFC), part of the IBM Developer's Toolkit for OS/2 2.1 
(available separately as IBM part no.  61G1416 or as part of many 
development environments such as Borland C++ for OS/2), and a text editor 
(like the Enhanced Editor included with OS/2).  

Online IPFC documentation is included with the Toolkit, but you may also 
wish to order the printed Information Presentation Facility Guide and 
Reference, IBM Publication No.  S10G-6262.  See (4.9) Books and Magazines 
for ordering instructions.  Note that the Toolkit is part of the low cost 
OS/2 Professional Developer's Kit CD-ROM.  See (4.5) Technical Support for 
details.  

If you wish to include illustrations in your INF file you can use any 
graphics software which can generate OS/2 bitmaps and/or metafiles.  (For 
example, you may create your illustration in PM Chart, paste the 
illustration into Picture Viewer, then save the illustration as a metafile.  
Both PM Chart and Picture Viewer are included with OS/2 2.1.)  A screen 
capture utility [like PM Camera or Galleria, available from (3.2) Shareware 
and Freeware Sources] can also prove useful.  

 
 Related information: 
 
 (3.2) Shareware and Freeware Sources 
 (4.5) Technical Support 
 (4.9) Books and Magazines 
 
[End of OS/2 Frequently Asked Questions List.]

-- 
Timothy F. Sipples       |READ the OS/2 FAQ List 2.1A, available from
sip1@kimbark.uchicago.edu|192.153.46.254, anonymous ftp, in /os2/all/info/faq,
Dept. of Econ., Univ.    |or from LISTSERV@BLEKUL11.BITNET (send "HELP").
of Chicago, 60637        |[Post to ONE newsgroup only AFTER reading the List.]