OS/2 Shareware BBS: 8 Other

home *** CD-ROM | disk | FTP | other *** search

/ OS/2 Shareware BBS: 8 Other / 08-Other.zip / cfgmt100.zip / howto.dat < prev next >

Wrap

Text File | 1999-03-28 | 56KB | 1,214 lines

----------------------------------------------------------------- HOW TO's The best way to optimize your system is 1. to use only HPFS 2. Use OS/2 without dos and windows sessions (so you get also rid of those nasty little algorithms called virus) 3. Don't use voicetype if you don't need it, you can also make different boot options (with and without VT) see How to set multiple configurations. 4. Use small apps (like Papyrus) and not those Ram-Hogs like Staroffice 5. Use native apps (not Java, Windows, Mirrorports like Word- perfect for OS/2) 6. Delete the OpenDoc-Part by using 'selective-delete', as OpenDoc is deplorably death. 7. Use as LESS ! partitions as possible. Explanation: OS/2 checks during bootup all partitions, so having less partitions speeds boot-time. Btw. when you compare the speed of windows and OS/2 on the same system, remember that windows can only boot from the first partition, the one which is on most drives the fastest ! Using removable media together with OS/2 and newer Fixpaks slows bootup significantly. As a bargain (compared to windows, all versions) you get dynamically assigned drive letters, a feature that saves you from the drive-letter chaos in Windows whenever you change a partition, drive etc. ------------------------------------------------------------------ If your only internet connection is via a modem, then you can comment out (or delete) the following lines from CONFIG.SYS in Warp 4 ------------------------------------------------------------------ REM DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S REM DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM REM RUN=C:\OS2\SMSTART.EXE REM CALL=C:\IBMCOM\PROTOCOL\NETBIND.EXE REM RUN=C:\IBMCOM\LANMSGEX.EXE REM DEVICE=C:\MPTN\PROTOCOL\AFOS2.SYS REM DEVICE=C:\MPTN\PROTOCOL\IFNDIS.SYS REM CALL=C:\OS2\CMD.EXE /Q /C C:\MPTN\BIN\MPTSTART.CMD >NUL REM DEVICE=C:\IBMCOM\MACS\NULLNDIS.OS2 ------------------------------------------------------------------ If you don't run DOS/Windows TCP/IP programs, then you can remove the DOS TCP/IP support. The relevant lines in CONFIG.SYS are: ------------------------------------------------------------------ REM DEVICE=C:\tcpip\bin\vdostcp.vdd REM DEVICE=C:\tcpip\bin\vdostcp.sys REM RUN=C:\tcpip\bin\VDOSCTL.EXE ------------------------------------------------------------------ If you don't use Voicetype remove the following ------------------------------------------------------------------ Remove all statements in LIBPATH, SET PATH, SET DPATH and SET HELP pointing to Voicetype (normally they start with x:\vt) Then delete the following lines: SET SPCH_RUN=X:\VT\SPCH_RUN SET SPCH_RO=X:\VT\SPCH_RO SET SPCH_RW=X:\VT\SPCH_RW SET SPCH_BIN=X:\VT\SPCH_BIN SET SPCH_PATH=X:\VT\SPCH_RO\LANGS\%L\POOLS SET SPCH_TRN=X:\VT\SPCH_DBF <<=TIP=>> You can also make two different configurations and boot them alternately by pressing ALT-F1. See how to get multiple configuration files in Warp 3 or 4 ----------------------------------------------------------------- Removing Artchron and other 'unwanted' autostarts ----------------------------------------------------------------- There is a clean way of removing the register program from your system. Navigate *through the Drives ICON* to /OS2/install/Installed Objects and double click on "Install Object - Inventory". Then check the box next to "art" and then click on "uninstall" and then select "art" in the next box that opens and then "uninstall" again...this will totally uninstall the "art" directory and all components relating to registration. Some applications (like Staroffice, Smartsuite, Amipro) install some 'reminders' or 'speeders' in the autostart-folder remove or delete them, they are normally not needed. ----------------------------------------------------------------- HOW TO RESTORE A DAMAGED CONFIG.SYS FILE FROM A BACKUP COPY. ----------------------------------------------------------------- In OS/2 Warp, IBM provides an archive feature which can be activated by opening your Desktop settings, click on the Archive Tab, and then click on "Create archive at every system restart". With this feature activated, you can simply press Alt+F1 at boot and be presented with a menu which will allow you to boot with an alternate (backup) config.sys file. See your user documentation for details. For managing your archives there is the FREE tool warco13.zip, developed by Stefan Milcke (Stefan.Milcke@t-online.de), available at the usual internet sides (hobbes, leo etc.) ----------------------------------------------------------------- HOW TO GET MULTIPLE CONFIGURATION FILES IN WARP 3 or 4 ----------------------------------------------------------------- Save your config.sys Make an ALTF1n.CMD file in /OS2/BOOT with the following content 'copy \os2\boot\config.n \config.sys' Copy your Config.sys to \OS2\BOOT\CONFIG.N Edit CONFIG.N Repeat for ALTF1y.CMD ... Repeat for ALTF1z.CMD ... Now edit ALTF1TOP.SCR in \OS2\BOOT Insert 'N - Start config.N' 'y - Start config.y' 'z - Start config.z' ATTENTION ! for every line you insert you have to delete one !! for N and y you can use every letter that is not occupied by the Boot-Menu: According to IBM the following characters cannot be used: C, M, V, X, 1, 2, 3; with Warp 4 additionally 4 and 5. <<=TIP=>> The alternative config.* files can be easily edited with ConfigMaint by choosing a alternative config.sys. The correct settings in ALTF1TOP.SCR, and the generating of the ALTF*.CMD files can also be done by ConfigMaint. Here's one sample for a German Warp 4 WIEDERHERSTELLUNGSOPTIONEN Waehlen Sie die zu verwendende Systemkonfigurationsdatei aus, oder geben Sie die Option ein, die dem gewuenschten Archiv entspricht. ESC - Der Systemstart wird mit der ungeaenderten Datei \CONFIG.SYS fortgesetzt. F2 - Eine Befehlszeile wird aufgerufen (keine Dateien werden ersetzt, die urspruengliche Datei CONFIG.SYS wird verwendet). F3 - Der Primaerbildschirm wird auf VGA eingestellt, und das System wird neu gestartet. F4 - Das System ueber die Option 'Installation anpassen' starten. F5 - Die Hardwareerkennung wird aktiviert. F6 - Die Hardwareerkennung wird inaktiviert. D - Mit Dos und Windoze P - OS/2 Pur (ohne Dos und Win) Durch Auswahl eines Archivs aus untenstehender Liste werden die aktuelle Datei CONFIG.SYS, das Verzeichnis der Arbeitsoberflaeche und INI-Dateien durch aeltere Dateien ersetzt. Diese aelteren Versionen koennen sich von den aktuellen Dateien unterscheiden. Die aktuellen Dateien befinden sich im Verzeichnis \OS2\ARCHIVES\CURRENT. ----------------------------------------------------------------- HOW TO ENABLE REXX SUPPORT FROM WITHIN THE CONFIG.SYS FILE. ----------------------------------------------------------------- The question of whether REXX programs can be called from within the config.sys file has been asked by a number of people. Russ Williams wrote to All: RW> Can anyone tell me what restrictions there are on running RW> REXX programs from config.sys (via "CALL=")? It doesn't RW> work for me, and the on-line help is no help. You cannot. The DLLs required to support Rexx are not loaded until Presentation Manager is loaded. If you require Rexx support earlier, look for a program call SRVREXX at a fine BBS near you. Adding the line RUN=SRVREXX.EXE to the config.sys will immediately initialize Rexx. You will then be able to access Rexx with or without PM being loaded. ----------------------------------------------------------------- HOW TO SET THE CACHE IN SYSTEMS WITH LESS RAM ----------------------------------------------------------------- ======================== Table 5 =============================== If you have formatted your system with only HPFS partitions, the cache size in this statement, as set by OS/2 during installation, is that noted under ONE FILE SYSTEM in the table below. If you have both FAT and HPFS partitions, then OS/2 sets the cache sizes to those noted under TWO FILE SYSTEM. The file system which uses the greatest amount of your disk space gets the larger default value. MEMORY SIZE IN MB TWO FILE SYSTEM ONE FILE SYSTEM* 4 128/64 128/48 5 128/64 128/48 6 256/64 256/128 7 256/128 256/512 8 256/256 384/512 9 256/256 384 10 - 16 512/512 1024 17 - 32 1024/1024 2048 * Defaults in Warp are different and are shown as the second number. On systems with more than 8MBs of RAM, the default is 10% of available RAM to a maximum cache of 4MB. ========================== Table 1 =========================== You can get better performance from your system by using your available RAM in the most efficient and effective way. Select the case that best describes the file system or amount of RAM you use. CASE 1: You use only HPFS or only FAT, but not both. HPFS only. FAT only. System memory of at least: Set CACHE to: Set DISKCACHE to: 16 MB+ 2048 2048 12 MB 1536 1536 8 MB 1024 1024 CASE 2: You use both HPFS and FAT with HPFS active and FAT passive. System memory of at least: Set CACHE to: Set DISKCACHE to: 16 MB+ 2048 512 -1024 12 MB 1536 256 - 512 8 MB 1024 128 - 256 CASE 3: You use both HPFS and FAT with HPFS passive and FAT active. System memory of at least: Set CACHE to: Set DISKCACHE to: 16 MB+ 1024 2048 12 MB 768 1536 8 MB 512 1024 <<=NOTE=>> For purposes of the table above, "active" and "passive" are descriptors for the way a partition is used. If it is seldom used, it is "passive." If a lot of disk intensive I/O occurs on the partition, it is "active." --------------------------------------------------------------------- HOW TO INSTALL PCMCIA DRIVERS --------------------------------------------------------------------- The probably easiest procedure has been described on OS/2 Online (http://www.os2-online.de): Unpack the file PCMCIADD found on disk 17 of the OS/2 Warp install CD (directory OS2IMAGE), best into the OS2 directory on your harddisk. Then replace the line BASEDEV=IBM2TOS1.SYS with the following lines in your CONFIG.SYS: BASEDEV=IBM2AMB1.SYS BASEDEV=IBM2AST1.SYS BASEDEV=IBM2CAD1.SYS BASEDEV=IBM2CMQ1.SYS BASEDEV=IBM2MAT1.SYS BASEDEV=IBM2NCR1.SYS BASEDEV=IBM2NEC1.SYS BASEDEV=IBM2SS01.SYS BASEDEV=IBM2SS02.SYS BASEDEV=IBM2TOS1.SYS BASEDEV=IBM2ZEN1.SYS BASEDEV=IBM2ZOS1.SYS BASEDEV=SS2PCIC1.SYS BASEDEV=SS2TCIC1.SYS When OS/2 boots press Alt-F2 when the rectangle appears in the top left corner of the screen, and OS/2 will tell you which driver was loaded. It is possible that your machine works with more than one, you'll then have to find out yourself which one works best! If you have specific drivers for your notebook computer Do not install the PCMCIA support when installing OS/2 on your machine. Instead, once you are done with the installation of OS/2, chose Device Installation from the System/System Configuration folder and install the PCMCIA driver from diskette or use the installation program provided with your driver. Check the information provided with your driver before installing OS/2 Warp or the PCMCIA support. If your driver comes only in the form of the driver files, you need to do a manual installation, i.e. you need to edit the CONFIG.SYS file yourself. In that case install any PCMCIA support (as explained above). Then copy the driver files into the directory x:\os2\boot. After that, open the CONFIG.SYS in the editor and change the line BASEDEV= PCMCIA_driver (replace "PCMCIA_driver" with the driver name you installed) into BASEDEV=newdriver where "newdriver" is the name of the driver file you got). Take care that the PCMCIA drivers precede any COM drivers. In some machines, an additional line has to be included in the CONFIG.SYS file: BASEDEV=RESERVE.SYS /mem:nnnn mmmm (nnnn has to be replaced with the address where PCMCIA usually would start and mmmm has to be replaced with a value of 1000 or more (increased in steps of 1000)). First run rmview /mem to find out at which address PCMCIA is located. This would be the hex number that comes in place of nnnn. Then try out whether it works with 1000 (in place of mmmm). RESERVE.SYS actually prohibits the PCMCIA driver to use this area and thus avoids a conflict which otherwise arises. If 1000 doesn't work try 2000 etc. Xircom's own drivers don't work: For some PCMCIA cards (particularly XIRCOM with their own drivers) the IBM PCMCIA socket for the particular socket in which the card is inserted has to be disabled by installing socket services with the parameter /S0=1 which will disable socket services for the second PCMCIA slot (if there are two slots; if there is just one slot it won't do any good). An alternative is the switch /ig0=1 (1 is the port number). By using a proper script, it may even be possible to go without any of these switches. PCMCIA doesn't work: In some notebook computers the BIOS has to be modified so that the PCMCIA becomes compatible with the available OS/2 driver. The mode in which the PCMCIA functions may need to be set from Busmaster to 16-bit or PCIC compatible. Check the info for individual notebooks on this page and consult your notebook's manual! IBM Token Ring PCMCIA adapter doesn't work: Try setting in MPTS the IRQ to 5 and the adapter type from primary to alternate (address X=20). --------------------------------------------------------------------- JERRY ROWE's WARP REMOTE INSTALL PAGE --------------------------------------------------------------------- This page is a preliminary FAQ about installing OS/2 Warp 4 over a laplink cable from a Server to a Client. First, you must set the Server up to use the parallel port (SSW Parallel MAC driver) network driver. You do this from MPTS [just type MPTS at the command line]. Select the driver, and add Netbios as a protocol. Then Edit the SSW Parallel MAC driver in MPTS and Note its address. It should be 40000000000A. Then open up the OS/2 Warp Remote Install object. Create the remote install disks. Be sure to use the same SSW Parallel MAC driver. Then edit the protocol.ini file on the 2nd disk. Inside it, insure that the MAC address is something other than 40000000000A. Using 40000000000B will work fine. Save the file. Now, shutdown and reboot the machine. Then examine \ibmcom\lantran.log and look for the reference to the Adapter # for the parallel port adapter. If you have another adapter in the Server, the number may be 1, otherwise it will be 0. Find Server Adapter # Note that the Adapter #=1 in the file below. If your parallel port is setup for adapter #=0, then lantran.log will be different. ==file lantran.log========================================= PARALLEL PORT MAC V 1.0 by Savant Software Inc. Copyright (C) 1994, 1995 SAVANT SOFTWARE: PORT ADDRESS(ES): LPT1 SAVANT SOFTWARE: PORT ADDRESS CONFIGURED: LPT1(378) IBM LANVDD is loaded and operational. IBM OS/2 LAN Netbind IBM LANDD is accessing IBM 802.3 LAN Interface. Adapter 1 was initialized and opened successfully. Adapter 1 is using node address 40000000000A. The Token-Ring format is 02000000 IBM LANDD was successfully bound to MAC: pmac_nif->VECTOR. ==end file lantran.log========================================= Install service.exe and other files. If they were not installed during the Warp install, follow these instructions. Given that my CDRom drive is I:, and My Warp 4 drive is H:, issue this command: [H:\]I:\CID\SRVIFS\thinsrv /s:. /t:h:\cid\SRVIFS /r:h:\ibminst\tables\service.ini /tu:h:\ THINSRV completed successfully. This creates a line in startup.cmd and creates startup.cmd if necessary. START H:\CID\SRVIFS\SERVICE.EXE /INI=SERVICE Thinsrv also adds: h:\cid\SRVIFS; to the PATH and DPATH statements in CONFIG.SYS. Because these changes will not take effect until a reboot, the command in STARTUP.CMD will not work until then. However, you can: cd \cid\srvifs service /ini=service to start it right away from the command line. You will probably want to remove the commands from Startup.cmd at this time to prevent the Server facility from running all the time. You may also want to create another cmd file with the service command in it if you would like to run it interactively. Edit h:\cid\service.ini Note Alias's and Path near bottom. Should be correct for the CD Note Adapter #. Should match # from Lantran.log. ============================================================= ;SRVIFS INI file for OS/2 Warp Remote Install Server - 7CPESGDV Name = 7CPESGDV GroupName = NO Adapter = 1 MaxClients = 5 MaxFiles = 9999 ClientWorkers = 8 Path = I:\ Alias = ReadOnly,Single,CDROM,I:\ Alias = ReadWrite,Single,STATUS,H:\IBMINST\RSP\REMOTE ============================================================== With these changes made, shut down the computer and reboot. After it comes up, the GUI front end for the Remote install should work. ===Config.sys on disk 1 =================== CALL=A:\SRVATTCH.EXE z: \\7CPESGDV\CDROM DEVICE=A:\SRVIFS.SYS IFS=A:\SRVIFSC.IFS * /T CALL=A:\SRVATTCH.EXE w: \\7CPESGDV\STATUS RUN=Z:\CID\LOCINSTU\SRVREXX.EXE libpath=.;\os2\install;\os2\dll;z:\cid\locinstu; set os2_shell=cdboot.exe set oemprogram=\ibminst\npconfig.exe set exitwhendone=1 set ADAPTER_NIF=PMAC.NIF set SRVNAME1=7CPESGDV set SAVECONNECT=1 ================================================ Now, change to H: [warp 4 drive] and start server. cd \cid SERVICE.EXE /INI=SERVICE Now, boot the client off the disk set. Should work. If it does not, check the hardware configuration of the parallel ports and insure they are set to bi-directional if that option is offered. I successfully installed Warp 4 on a Thinkpad using this method. After the install, you should also be able to network between the two computers over the laplink cable using OS/2 Peer. --------------------------------------------------------------------- How to install XFree86/OS2 3.3.3 by Jim Jaworski --------------------------------------------------------------------- e-mail:jjaworski@wpcusrgrp.org Attention the e-mail address of Jim Jaworski can't be accessed :-( available also at http://www.geocities.com/SiliconValley/Network/6571/xfree86os2.html <<=TIP=>> See also the excellent guide by Rob Fargher in Voice 2/99 I take absolutely NO responsibility for messed up software configurations, or messed up video hardware. Use this information at your own risk. This document contains information for the installation and configuration of XFree86/OS2 version 3.3.3, which is at X11R6.3. Before proceeding with the information provided here, please read the http://borneo.gmd.de/~veit/os2/x11os2faq.html XFree86/OS2 FAQ. It will have the latest information on how to install and configure your system for X. First of all, what is this XFree86/OS2? Well, XFree86/OS2 is a freeware implementation of the X Window System, commonly found on Unix workstations. One of the things that you can do with an X Window System is to run X clients (applications) remotely. Say there was an X application running on an IBM RS/6000 running AIX 3.2.5 and you wanted to run it, but that application does not exist yet on your, typically Unix, platform. Well, you just load X Window System onto your workstation, and configure it to load that X app. remotely, as if it were running right on your own machine. One of the other nice things about the X Window System is that, unlike a certain Microsoft OS, you can make X look like anything you want: Motif, Amiga, Windows95, or NeXtStep. This is made possible by using the various 'window managers' that are out there. You can, however, only use one window manager at a time, although you can have several configured and installed on your hard drive. You need the following to install XFree86/OS2 on your OS/2 workstation: OS/2 Warp 3.0 at Fixpack 17 or higher level; An OS/2 HPFS partition with approximately 30 Megabytes free space; Copy of Info-Zip's unzip.exe utility; Copy of XFree86/OS2 .zip files, outlined below; Your video monitor's instruction manual; Your video adapter's instruction manual; Alot of patience. ftp the following files, and store the files on the root directory of the partition where you want to install XFree86/OS2. I installed to the G: partition, so I copied all the *.zip files to G:\, but your available drives may be different: ftp://hobbes.nmsu.edu/pub/os2/dev/emx/v0.9d/emxrt.zip/"emxrt.zip EMX Runtime 0.9d. EMX\DLL muse be located somewhere on your LIBPATH statement, while EMX\BIN should be somewhere in your PATH statement. Required XF32base.zip XFree86/OS2 Base files. Includes the SuperProbe utility. XF32bin.zip XFree86/OS2 Binary files. Includes main utilities like: XKill, XMag, xvidtune, etc... XFree86/OS2 Server. Use the XFree86/OS2 server that matches your video adapter hardware (e.g. for the widely spread Matrox cards SVGA is the correct one). XF32fnts.zip XFree86/OS2 75 dpi fonts. XF32f100.zip XFree86/OS2 100 dpi fonts. Optional XF32fscl.zip XFree86/OS2 Type 1 and Speedo fonts. Of primary importance is to retrieve a copy of the correct XServer for your video adapter. In this short help section I am using the XFree86/OS2 SVGA server because the system I configured for was a SVGA. If you don't know, or are not sure of what video adapter hardware you have, use the \XFree86\bin\SuperProbe utility (Not for Matrox). Most of the time it accurately detects your video adapter, but I've heard that it can sometimes 'miss', so be very careful which one you use. Add the following lines to your OS/2 config.sys file: SET DISPLAY=localhost:0.0 SET ETC=D:\MPTN\ETC SET HOME=D:\MPTN\etc SET HOSTNAME=localhost SET LOGNAME=jim SET MANPATH=G:\XFree86\man SET TERM=ansi SET TERMCAP=D:/emx/etc/termcap.x11 SET TMP=D:\TMP SET USE_HOSTS_FIRST=1 SET USER=jim SET X11ROOT=G: SET XSERVER=G:/XFREE86/bin/yourXserver.exe DEVICE=G:\XFree86\lib\xf86sup.sys <<=NOTE=>> Regard the difference between a backslash \ used in OS/2, DOS and WINDOWS and a slash / used in UNIX and LINUX ! Then add the following to the end of your PATH statement: ;G:\XFree86\bin; and finally, add the following to the end of your LIBPATH statement: ;G:\XFree86\lib; Create/modify the <em>\MPTN\etc\hosts</em> file to read: 127.0.0.1 localhost And add the following line to your \TCPIP\bin\tcpstart.cmd: ifconfig lo 127.0.0.1 up OS/2 Warp 3.0 users don't have a tcpstart.cmd file. You must you add the following line to your OS/2 config.sys file instead: RUN=E:\tcpip\bin\ifconfig.exe lo 127.0.0.1 up Reboot your OS/2 workstation. When your WorkPlace Shell desktop is up, run: \XFree86\bin\checkinstall.cmd If there are no error messages, test to see if you can 'ping localhost' by typing the following at an OS/2 command prompt: ping localhost You're now at the midway part of the installation of XFree86/OS2, now comes the more involved/scary part. This is the part where you configure your video monitor and your video adapter for XFree86/OS2. Run the following in a full-screen OS/2 Command Prompt: \XFree86\bin\XF86Config.exe There are about 20 questions that XF86Config.exe will ask you. Generally, the questions around info about your keyboard, mouse, video monitor and video adapter. Along with the question, there is are short, usually 10 to 15 lines of description of what it is asking for. For some reason, I've never come across a list of the questions that XF86Config asks, so I'll summarize here: 'Use XKB (11R6.1 XKeyboard extension)?' -- I answered yes to this question, since it recommended that I do. Otherwise you might have to 'adjust your keyboard layout with xmodmap.' 'Select from the list of preconfigured keymaps' -- this is just what type of keyboard you have, if you have a standard IBM PC AT 101-Enhanced, select 1. If not, then choose your keyboard type from the list. 'Horizontal sync rate of monitor (in KHz)' -- you're on your own here, get this info from your monitor manual, although there is a menu list of acceptable ranges. 'Vertical Sync range (in Hz)' -- you're on your own here, get this info from your monitor manual, although there is a menu list of acceptable ranges. 'Identifier for monitor description' -- doesn't matter too much what you enter here, it's like a title. 'Enter the vendor name of your monitor.' 'Enter the model name of your monitor.' This information can be found on the front of your monitor, on the back or on the front cover of the monitor manual. 'Do you want to look at the card database?' -- I'd answer 'y' to this one, especially if you're installing for the first time. It produces a list of over 200 video adapter cards and which chipset they use. 'Enter a number to choose the corresponding card definition.' There is a list of over 200 video adapter cards listed. XF86Config.exe then reports what kind of video adapter you have selected in the form of the 'Identifier', Chipset, and Server. 'Now you must determine which XServer to run.' 'Enter amount of video memory that your video adapter has.' This will vary according to what you actually have or how much RAM it can 'see'. 'Enter an identifier for video adapter definition.' 'Enter the vendor name of your video adapter.' 'Enter the model (board) name of your video adapter.' 'The RAMDAC setting only applies to S3, AGX, W32 servers, and some drivers in the SVGA servers. Some RAMDACS are auto-detected by the server.' This is where I was a bit confused. Someone else that I know that configured XFree86/Linux said that using 'normal' would be fine, but if you have a different, newer, or even a totally different video adapter you'll have to find this one out for yourself. Sorry I can't help out here. 'A Clockchip line in the Device section forces the detection of a programmable clock device; with a clock chip enabled, any required clock can be programmed without requirring probing of clocks or a clocks line. Most cards don't have a programmable clock chip. Just press Enter if you don't want a Clockchip setting.' Configuring for the Matrox G200 it came up with a Warning message 'Do NOT probe clocks or use any clocks line.' Sorry I didn't make enough notes on this one, you're on your own here. 'For most configurations, a Clocks line is useful since it prevents the slow and nasty sounding (?) clock probing at server startup, along with other server and hardware config info. Be warned that Clock probing is inherently imprecise, some clocks may be slightly too high (varies per run). 'Do you want me to run 'X -probeonly' now?' The answer to this quesion will depend on what kind of video adapter you have. Video Modes -- This will select what video resolution modes that you will be able to select from. 'For each depth, a list of modes (resolutions) is defined. The default resolution that the server will start-up with will be the first listed mode that can be supported by the monitor and card.' 'I am going to write the XConfig file now. Make sure you don't accidently overwrite a previously configured one. Shall I write it to the default location of drive:/XFree86/lib/X11/XConfig? If you answer no to the previous question you'll get another question like this: 'Do you want it written to the current directory as XConfig?' This will write out an XConfig file without overwriting the one in XFree86/lib/X11/. 'Please give a filename to write to.' At this time, if you're comfortable with the XConfig settings, you can type (in a full-screen OS/2 command prompt session): startx and hopefully the X Window System will come up, with the default twm window manager. Keep your finger ready to quickly power off your monitor if something starts to crackle, smoke or something like that. OK, now that you have X Window System up and running, it's time to select a nicer looking interface than twm. You don't like twm, do you? If not, then here are some rather attractive window managers that you can use in its place: You can have as many window managers as you want, but only run one at a time. --------------------------------------------------------------------- How to protect TCP/IP 4.0 and 4.1 against SYNFLOOD and 'Ping of Dead' --------------------------------------------------------------------- Here is a tip from IBM's TCP/IP document site http://service5.boulder.ibm.com/pspsdocs.nsf/ c7a34b35e55986f9862563cc00604815/8a384023f92790f18625653e004eab22?OpenDocument (It seems that IBM wants to get named in the Guiness Record for the longest URL ;-) For TCP/IP 4.0 - apply the latest MPTS/TCP/IP update. This will give you a new program -SYNDEF.EXE. This works as follows: SYNDEF.EXE ON (enables SYN defenses) SYNDEF.EXE OFF (disables SYN defenses) SYNDEF.EXE -? (displays SYNDEF syntax) For TCP/IP 4.1 - The ability to protect against this type of attack is built in to TCP/IP 4.1. To enable this protection: 1. To GET the current status of the SYNATTACK parameter in the INETCFG.INI file, go to an OS/2 command line and type: INETCFG -G SYNATTACK, then press Enter. 2. By default, SYNATTACK is set to 0, which means OFF. 3. To SET the SYNATTACK parameter in the INETCFG.INI file to an ON state, (1), type the following at an OS/2 command line: INETCFG -S SYNATTACK 1 4. This new setting in TCP/IP 4.1 will now prevent the SYNATTACK from occurring. --------------------------------------------------------------------- How to identify what a certain Trap means --------------------------------------------------------------------- General List of OS/2 Traps 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. --------------------------------------------------------------------- How To identify a partition type number by it's HEX id --------------------------------------------------------------------- The partition type number (hex id) are as follows: 01 FAT12 (supported by OS/2) 02 XENIX_1 root 03 XENIX_2 usr 04 FAT16 <32MB (supported by OS/2) 05 EXTENDED 06 FAT16 >32MB (supported by OS/2) 07 HPFS(386) (supported by OS/2) or NTFS 08 AIX 09 AIX BOOTABLE 0A BOOTMANAGER (supported by OS/2) or OPUS 0B FAT32 0C FAT32_XINT13 or FAT32X 0E XINT13 0F XINT13_EXTENDED (e.g. used by PQMAGIC 4.0) 35 JFS 40 VENIX 80286 41 PREP 51 NOVELL 52 MICROPORT 63 UNIX or GNU HURD 64 NOVELL 75 PC/IX 80 OLD MINIX 81 LINUX/MINIX 82 LINUX SWAP or SOLARIS UFS 83 LINUX or NT Stripe and Mirror Set B7 BSDI FS B8 BSDI SWAP C7 SYRINX DB CP/M E1 DOS ACCESS E3 DOS R/O EB BeOS Filesystem F2 DOS SECOND FF BBT FE PS2S PS/2 System Partition 10 Hidden partition (bits OR'd with partition type) <<=ATTENTION=>> If you install different OS (e.g. Solaris and Linux, or OS/2 and NT) you can run into serious troubles whenever the id's aren't unique. Together with a disk-tool like e.g. the FREE DFSEE by Jan van Wijk, the fdisk out of LINUX, or the Norton Diskdoctor for Dos and naturally the Gammatech and the Graham utilies (both for OS/2) there are many useful options for recovering and not so useful for DESTROYING a partition table. So be careful whenever editing a partition table. It is wise to get accommodated with these tools JUST BEFORE an accident happens, cause when something went wrong you're to much excited. --------------------------------------------------------------------- How to install Linux parallel to OS/2 --------------------------------------------------------------------- As Linux gets more and more common here some BASIC rules for the installation, so that you can have a trip back in times ;-) 1. Have the IBM OS/2 Bootmanager installed. Using LILO is not advised, although you can also use LILO as bootmanager. 2. If you posess the Gammatech-Utilities make an backup of your partition-table for an easier recovery if anything went wrong. Naturally this can also be done with the Graham-Utilies, but as I don't have 'em I'm not familiarized with them. 3. Make the partitions for Linux with OS/2 fdisk but DON'T format them. Linux can - like OS/2 - boot from any logical partition. And - again like in OS/2 - the boot partition has the same limitations (e.g. if no support for LBA is in your Motherboards BIOS the partition on (E)IDE Drives has to be inside the magical 528MB range). Minimum is one partition to mount the root (/) and one smaller partition for the swap drive - its size depends on your installed memory and your needs, maximum size is 128 MB with kernel 2.0x, as a 'simple' rule, make the swap partition as large as your installed memory. 4. Add Linux to your Bootmanger menu. 5. Now you can install Linux itself (see your Linux Guide for doing this). Install the Linux Bootmanager LILO ONLY in the partition where you have mounted the Linux root (/) e.g. /dev/hdc5. NEVER NEVER INSTALL LILO IN THE MBR if you want to avoid a lot of troubles. (I know what I'm talking of). Naturally this is not true if you decide to use LILO as bootmanager. 6. If you should have the curious idea to change your partitions AFTER the installation of Linux (e.g. you want to make out of two small ones one big, or the other way round). You'll get CERTAINLY a KERNEL PANIC whenever you try to boot Linux: In this case you have to boot from the (hope you've done it before) generated Linux rescue disk(s) and then change your mounted drives (e.g. /dev/hdc5) in Linux, install Lilo new ... (see your Linux reference for how to do this). 7. Together with the ext2.ifs you can read-write access the linux drives from OS/2. See cm2cfg.dat for more informations. 8. To read-access the OS/2 HPFS formatted drives compile the Linux kernel with the HPFS-MODULE option. There are also modules for read and write access of HPFS. Look at ftp://sunsite.unc.edu/pub/Linux/ or at http://artax.karlin.mff.cuni.cz/~mikulas/vyplody/hpfs/index-e.cgi. Actually they are available for the kernel 2.0x, 2.1x. and 2.2x. --------------------------------------------------------------------- How to install Windows NT parallel to OS/2 --------------------------------------------------------------------- <<=NOTE=>> OS/2 recognizes NTFS formatted drives falsly as HPFS, as NT recognizes EXT2FS falsly when the fault-tolerance options are used, as Linux recognizes the Solaris UFS falsly as swap partition ... Using the FREE EXT2FS necassary for Linux the NTFS partition can be hidden by inserting BASEDEV=EXT2FLT.FLT <options> See cm2cfg.dat for a complete list of options. E.g. if you have one disk, the OS/2 Bootmanager installed and NT is on the first partition the correct options are BASEDEV=EXT2FLT.FLT /A /W /M 1 <<=TIP=>> Windows NT 4.0 can use HPFS-Partitions if you have the pinball.sys out of NT 3.51 and the utility hpfs_nt4.zip by Chris Behnken, available at http://www.htc.net/~nbehnken. ATTENTION pinball.sys can only operate with disks or partitions up to 4GByte. <<=TIP=>> There is also an ALPHA NTFS.IFS by Daniel Steiner, available at http://npw.cgnet.de/dsteiner and a newer vfat.ifs with NTFS read-support. But as some users reported problems be very careful when using it. The best would be to make a complete backup of your installation. --------------------------------------------------------------------- How to install and tune the HPFS386.IFS --------------------------------------------------------------------- To install HPFS386 do the following: remove the HPFS.IFS line you have already: for example: REM IFS=C:\OS2\HPFS.IFS Now add IFS=C:\IBM386FS\HPFS386.IFS /A:* if your boot drive isn't C: change it to correct drive Next still in config.sys, add the directory C:\IBM386FS somewhere in each of your PATH, DPATH and LIBPATH. Next still in Config.SYS, if you have a RUN=CACHE.EXE line, comment it out with a REM. Insert RUN=C:\IBM386FS\CACHE386.EXE. Save the config.sys. This is it, you are ready to shutdown and reboot. try a cool cache monitor in cache386 bye typing this: CACHE386 /STATS:D this will show a constantly updated display of all the cache statistices, reads, writes, cache hits, percentages etc. Press CTRL-C to stop. Do not use CACHE.EXE anywhere, it's not made for this <<=TIP=>> You should also create bootdisks or a maintanance partition with HPFS386 by using btos2 (see cm2.inf). For tuning the HPFS386.IFS you have to set the HPFS386.INI here's one example: ;============================================================================= ;This file contains the initialization parameters for the 386 HPFS. The ;parameters are grouped into components. The component groups start with the ;component name enclosed in square brackets. Each component name appears on ;a line by itself (a comment is allowed). The components include the ;following: ; ;[filesystem] ; General file system parameters ;[lazywriter] ; Lazy writer parameters ;[DASD_Limits] ; DASD Limits parameters ;[UltiMedia] ; UltiMedia parameters (added when LAN Server Ultimedia ; ; is installed) ; ;General rules: ;- The component names and parameters are not case-sensitive. They can be ; entered in upper case, lower case, or a mixture of upper and lower case. ;- Wherever a blank appears in the syntax for a parameter, it can be left out ; or additional blanks can be added. For example, the following syntaxes ; are all valid: ; parameter = yes ; parameter=yes ; parameter= yes ; - Any text after a semicolon (;) up to the end of the line is treated as a ; comment. ; - All components and parameters are optional. If you do not specify a ; parameter, the 386 HPFS uses a default setting for the parameter. ;=============================================================================== [filesystem] useallmem = YES lanroot = D:\IBMLAN cachesize = 8192 ;------------------------------------------------------------------------------- ; The [filesystem] section specifies general file system parameters. If you ; make any changes to these parameters, they do not take effect until you ; reboot the system. ; ; useallmem = [yes|no] ; This parameter specifies whether the 386 HPFS should use memory above the ; 16M boundary, provided this system is configured with more than 16M. ; Some adapters, for example the IBM Token Ring Busmaster Server/A, cannot ; do direct memory access (DMA) to memory above the 16M boundary. If you ; have a LAN or disk adapter that cannot do DMA to memory above the 16M ; boundary, the 386 HPFS must use only memory below 16M so that the adapter ; can put data into the file system buffers. Set useallmem to yes if all ; of your adapters can access memory above the 16M boundary. Set useallmem ; to no if any of your LAN or disk adapters cannot access memory above the ; 16M boundary. If useallmem is not specified, the default setting is no. ; ; cachesize = nnnn ; This parameter specifies how many kilobytes of memory the 386 HPFS should ; claim for its cache. The cache size must be a minimum of 256KB. The ; maximum value is determined by the size of available memory. If ; cachesize is not specified, the default is to use 20% of available ; memory, if the amount of available memory is below 20MB, or 60% of ; available memory, if the amount of available memory is 20MB or more. ; ; maxheap = nnnn ; This parameter sets a limit on the size of the heap. nnnn is the maximum ; number of kilobytes to which the heap can grow. The 386 HPFS allocates ; heap memory as needed. If this parameter is used, the 386 HPFS only ; allocates memory for the heap up to the amount specified. If this ; parameter is not used, there is no limit on the heap size. Use this ; parameter only if you need to reserve memory on the system for other ; applications that may be running. The minimum value is 64KB. The ; maximum value is determined by the size of available memory minus the ; size of the cache. If maxheap is not specified, the default is to have ; no limit on the heap size. ; ; lanroot = d:\path ; This parameter specifies the drive and path of the directory for the LAN ; Server software. The installation program fills in this parameter for ; you. You do not need to change this parameter. ; ; fsprealloc = nn ; This parameter specifies how many big buffers to allocate when the file ; system is initialized. If neither fsprealloc nor srvprealloc are used, ; the file system allocates big buffers as needed. The allocation of big ; buffers can take a little time. Allocating the big buffers at ; initialization improves the performance of the first requests that need ; big buffers. The buffers are not freed until the system is shut down. ; The minimum value for fsprealloc is 2. The maximum is 64. If both ; fsprealloc and srvprealloc are specified in this file, fsprealloc is used ; and srvprealloc is ignored. srvprealloc = nn ; This parameter specifies how many big buffers to allocate when the server ; is started rather than when the file system is initialized. This ; parameter, like the fsprealloc parameter, can improve the performance of ; the first requests that need big buffers. The buffers are freed when ; the server is stopped. The minimum value for srvprealloc is 2. The ; maximum is 64. If both fsprealloc and srvprealloc are specified in this ; file, fsprealloc is used and srvprealloc is ignored. ;------------------------------------------------------------------------------- [lazywriter] lazy = *: ON maxage = *: 5000 bufferidle = *: 500 ;------------------------------------------------------------------------------- ; The [lazywriter] section specifies settings for the lazy writer. If you ; make any changes to these parameters, they do not take effect until you ; reboot the system. You can use the CACHE386 program to change the internal ; setting of these parameters while the system is running. When you reboot ; the system, the parameters are set to the values in this file. ; ; lazy = [drives:] on|off ; This parameter specifies whether the lazy writer is to be turned on or ; off for the specified drives. The [drives:] can be a series of drive ; letters. For example, "lazy = cdfg: on" would turn on the lazy writer ; on drives c:, d:, f:, and g:. It would not change the settings for drive ; e: or h:. An asterisk (*) can be used for the drive letter to indicate ; that all drives are to have the setting. This line can be used multiple ; times to achieve the settings you want for your drives. If lazy is not ; specified, the default value is to turn the lazy writer off for all ; drives. ; ; maxage = [drives:] nnnn ; This parameter specifies the maximum number of milliseconds that can pass ; before the lazy writer writes the contents of a buffer to the disk. The ; [drives:] can be a series of drive letters. For example, ; "maxage = cdfg: 5000" would set the maximum buffer age to 5000ms on ; drives c:, d:, f:, and g:. It would not change the settings for drive e: ; or h:. An asterisk (*) can be used for the drive letter to indicate that ; all drives are to have the setting. This line can be used multiple times ; to achieve the settings you want for your drives. The minimum value is ; 0. The maximum value is 1000000. If maxage is not specified, the ; default value is 10000 for all drives. ; ; bufferidle = [drives:] nnnn ; This parameter specifies the maximum number of milliseconds during which ; a buffer is not used before the lazy writer writes the buffer contents to ; the disk. The [drives:] can be a series of drive letters. For example, ; "bufferidle = cdfg: 500" would set the buffer idle time to 500ms on ; drives c:, d:, f:, and g:. It would not change the settings for drive e: ; or h:. An asterisk (*) can be used for the drive letter to indicate that ; all drives are to have the setting. This line can be used multiple times ; to achieve the settings you want for your drives. The minimum value is ; 0. The maximum value is 500000. If bufferidle is not specified, the ; default value is 1000 for all drives. ;------------------------------------------------------------------------------- [DASD_Limits] ThreshAlertNames = *: ADMINS ThreshAlertDelay = *: 10 ThreshAlertUser = *: yes DirFullAlertNames = *: ADMINS DirFullAlertDelay = *: 10 DirFullAlertUser = *: yes ;------------------------------------------------------------------------------- ; The [DASD_Limits] section specifies settings of parameters for the DASD ; Limits function. If you make any changes to these parameters they do not ; take effect until you restart the server. (To stop and restart the server, ; at an OS/2 command prompt, enter the command "net stop server" and then the ; command "net start server".) ; ; ThreshAlertNames = [drives:] [user1] [user2] [group1] [group2] ... ; This parameter lists the users or groups that are to be notified when a ; DASD Limits threshold is crossed on the specified drives. Any mixture of ; user names or group names can be used. All of the names must appear on ; one line. This line can be used multiple times to achieve the settings ; you want for your drives. If ThreshAlertNames is not specified, the ; default is to have no user or group names. ; ; ThreshAlertDelay = [drives:] nn ; This parameter specifies how many minutes to wait before sending another ; alert for a threshold that was previously crossed on the specified ; drives. If a threshold is crossed more than once within the delay ; period, an alert is sent only for the first occurrence. An alert is sent ; if a higher threshold is crossed during the delay period. This parameter ; is used to cut down on the number of alerts that can be generated when ; there is a lot of disk activity and the disk size is within the ; threshold. This line can be used multiple times to achieve the settings ; you want for your drives. If ThreshAlertDelay is not specified, the ; default is 10 minutes on all drives. ; ; ThreshAlertUser = [drives:] yes|no ; This parameter specifies whether to send an alert to the user whose disk ; usage caused a threshold to be crossed on the specified drives. This ; line can be used multiple times to achieve the settings you want for your ; drives. If ThreshAlertUser is not specified, the default is yes for all ; drives. ; ; DirFullAlertNames = [drives:] [user1] [user2] [user3] ... ; This parameter lists the users or groups that are to be notified when a ; DASD limit is reached. Any mixture of user names or group names can be ; used. All of the names must appear on one line. This line can be used ; multiple times to achieve the settings you want for your drives. If ; DirFullAlertNames is not specified, the default is to have no user or ; group names. ; ; DirFullAlertDelay = [drives:] nn ; This parameter specifies how many minutes to wait before sending another ; alert for a DASD limit that was previously reached. If a DASD limit is ; reached more than once within the delay period, an alert is sent only for ; the first occurrence. This parameter is used to cut down on the number ; of alerts that can be generated when there is a lot of disk activity and ; the DASD limit is reached several times. This line can be used multiple ; times to achieve the settings you want for your drives. If ; DirFullAlertDelay is not specified, the default is 10 minutes on all ; drives. ; ; DirFullAlertUser = [drives:] yes|no ; This parameter specifies whether to send an alert to the user whose ; request failed because a DASD limit was reached. This line can be used ; multiple times to achieve the settings you want for your drives. If ; DirFullAlertUser is not specified, the default is yes for all drives. ;------------------------------------------------------------------------------- --------------------------------------------------------------------- How to display files correctly with Wordperfect for OS/2 5.2 --------------------------------------------------------------------- Although this tip has nothing to do with the system I publish it here cause I've had for many years troubles with Wordperfect for OS/2 displaying the right colours and have now found a working solution. Thanks to Lynn Scott McCarty (lmccarty@interlog.com) :->> If you have a Matrox card first install the newest drivers (V 2.23, Attention there are some problems reported with the PCI-Cards for V 2.22 and V 2.23, AGP Versions work fine). The next two steps are not necessary when you have version 5.2a! After the installation of Wordperfect copy the OS2SHCWP.DLL from your X:\WPCOS2 directory to X:\OS2 (X=DriveLetter) execute patchwp.cmd. Now reboot OS/2, during bootup press 'AltF1' then F2 (in warp 4) to boot with a command line. Move the patched OS2SHCWP.DLL from X:\OS2 to X:\WPCOS2, this overwrites the unpatched OS2SHCWP.DLL. Reboot. After booting add the parameter /fl to your Wordperfect for OS/2 Object (do a 'right-click on the object, select settings and add the /fl switch in the parameter line on the first page). Thats it, no more inverted colours :-). But when opening a file by doing a double-click on it the switch isn't active so you'll get the inverted colour again :-(. BTW. When using Checkini or Unimaint you'll get a message that the classes for wordperfect documents and wordperfect graphics can't be found. You can deregister them without any harm. --------------------------------------------------------------------- How to get a Lotus Notes 4.6X Client --------------------------------------------------------------------- Although there is no official release POULIAS@IBM.NET has found out that the Notes 4.6X Client is hidden within the server install. To install it do the following steps: Copy the contents of SERVER\OS2\INSTALL direcory and its subdirectories from the Cd-Rom on your harddrive (e.g. into the tempory directory) so that you can edit and save some files. Edit the P32WKS.PKG file and change the line DISPLAY=NO' to DISPLAY=YES' Edit the NOTES.INI file and add the line UNSUPPORTEDCLIENT=1 Run INSTPM.EXE. Go trough the custom server install.You now will see WORKSTATION listed in the modules you can install. Once installation is completed and you've rebooted, go into the NOTES.INI in the \NOTES\DATA directory and change the line KitType=2 to KitType=1. Rename the 'Domino Server Administration' icon to 'Lotus Notes 4.6.1'. Click on the icon and set up the client. <<=ATTENTION=>> According to POULIAS@IBM.NET sending internet mail to the SMTP gateway doesn't work correctly. Pulling mail from the POP server works fine.