Обновление

 
Программы

 
(Санкт-Петербург)

 
Преимущества (1)

 
Разработчику (1)

 
(Пайпы программ)

 
Компании: (1)

 
История (1):

 
(Бонусы)

 
Советы:

 
(Барьеры и решения)

 
Технологии: (1)

 
(Применение в науке, лаборатории, ..)

 
Готовые решения:

 
Новая eComStation:

 
Будущее: (1)

 
(Ссылки на другие сайты)

 
(Картинка дня)

 
Артефакты OS/2

 
Гаджеты

AUTOFAIL

BUFFERS

CODEPAGE

COUNTRY

DEVINFO

DISKCACHE

DLLBASING

DUMPPROCESS

EARLYMEMINIT=TRUE

FAKEISS

I13PAGES

IOPL

IROPT

LASTDRIVE

LIBPATH

MAXWAIT

MEMMAN

MODE

PAUSEONERROR

PRINTMONBUFSIZE

PRIORITY

PRIORITY_DISK_IO

PROTECTONLY

PROTSHELL

REIPL

REMOTE_INSTALL_STATE

RESERVEDRIVELETTER

SETBOOT

SOURCEPATH

SUPPRESSPOPUPS

SWAPPATH

SXFAKEHWFPU

SYSDUMP

THREADS

TIMESLICE

TRACE

TRACEBUF

TRAPDUMP

TRAPLOG

TRUEMODE

VIRTUALADDRESSLIMIT

VME

WORKPLACE_NATIVE

WORKPLACE_PRIMARY_CP

WORKPLACE_PROCESS

WP_OBJHANDLE

=YES or NO (default)

In the default setting, when an error occurs, OS/2 will only display a window informing you of the problem. If you wish to see the actual error code information, set AUTOFAIL to Yes.

<<=NOTE=>> This command can't be run from an OS/2 prompt.

<<=TIP=>> Paul Kurr writes: "I set this value to YES on my machine so that I'm not interrupted with those pesky drive not ready popups and such. AUTOFAIL=YES takes the "first" option in those windows presented (usually return error code to program).

"This can be seen most easily when running WIN-OS2 with a CDROM installed - either empty or with a music CD in the drive. With AUTOFAIL=NO (default) OS/2 pop's up the window stating that my
drive "E" is not ready. With AUTOFAIL=YES, the first "selection" from that error is executed -- returning the failed drive status to WINOS2, which just keeps running fine."

BUFFERS
[Table of contents] [Index] [GENERAL]

=n (from 3 -100)

Tells OS/2 how many disk buffers to set aside. Each buffer takes up to 512 bytes of RAM. The install default usually works well. If you are using HPFS only, see <<=Tip=>> below.

Disk buffers are blocks of memory set aside by OS/2 for use in reading and writing blocks of data. For example, if a program wants to change 80 bytes of a file, it needs to read the 512 byte sector that contains the original data, change the information and then write the corrected 512 byte sector back out. A "buffer" is the 512 byte temporary staging area for this partial sector operation. According to a source at IBM, "OS/2 allows multiple simultaneous I/O operations to be queued up for both diskette and hard disk. Each 'concurrent' operation may need a buffer. If there are not enough buffers, overlap can be inhibited. Because OS/2 has more 'simultaneous' queued I/O than DOS, it needs more buffers."

<<=TIP=>> Generally, if you are running FAT on one or more of your hard drives, you can speed up your system by increasing the number of BUFFERS. But, keep in mind that as you increase the number, you reduce available memory. Be careful about using a lower number unless you only have 4MB of RAM. With 4MB of RAM you may wish to set BUFFERS to 20.

<<=TIP=>> If you are using only HPFS (i.e., no FAT partitions), try setting BUFFERS to 3. With HPFS you generally don't need BUFFERS. Remember that 3 is the minimum parameter. If you set BUFFERS to 1 or 2, OS/2 will default to 30 since 1 and 2 are out of range. There is one exception to this tip. If you access your floppy disks or FAT formatted removable disks a lot, then a reduced BUFFERS setting could impact the performance of these drives. (Thanks to Andrew Stephenson for reminding me to integrate removable drives also).

CODEPAGE
[Table of contents] [Index] [GENERAL]

=ppp,sss,

Lets you use the alphabet of various countries and languages. ppp is the number of the primary national alphabet to be used and sss is a secondary alphabet number. From an OS/2 command line, you can use the CHCP command to switch between these two code pages. This can be useful in order to type, display or print data in a different language from the version installed. CHCP can be used either without a parameter to query the current code page, or with one parameter in order to switch between primary
and secondary code pages. CHCP cannot be used to change to a code page not defined in the CODEPAGE= config.sys line.

See the OS/2 Reference book for a complete list of parameters.

437=US English alphabet and 850=multinational alphabet. The multinational alphabet contains most of the accented letters used in various European languages. Several other alphabets that can be supported by your version of OS/2.

<<=WARNING=>> Japan, Korean and Chinese require a special version of OS/2 and special hardware.

<<=WARNING=>> The choice of code page is made at installation time and should only be changed by using Selective Install.

<<=NOTE=>> If there is not a CODEPAGE statement in your config.sys, your keyboard will use an alphabet based on the COUNTRY statement found earlier in your config.sys, but your screen and printer will use their built in defaults.

<<=NOTE=>> Arabian, Greek, Hebrew, Thai and DBCS Codepages are only fully supported in OS/2-Versions developed for those countries.

<<=TIP=>> In Warp 4 are many new Codepages, Codepage 1004 is according to the WINDOWS ANSI Standard, this is important for an correct interpretation of German 'umlauts' and to convert documents between Windows and OS/2

COUNTRY
[Table of contents] [Index] [GENERAL]

=XXX,drive:\OS2\SYSTEM\COUNTRY.SYS

Customises your system for the country you wish to use. It establishes which defaults to use when it comes to decimal separators, date and time formats, currency symbols, etc.

XXX is a three-digit code number that tells what country to use. The number is usually (but not always) the same as the international telephone dialling prefix for the country desired. If in doubt consult your OS/2 online-reference.

DEVINFO
[Table of contents] [Index] [GENERAL]

DEVINFO=KBD,XX,drive:,\OS2\KEYBOARD.DCP

Tells the keyboard which international character set to use and where to find the file KEYBOARD.DCP which translates keystrokes. The parameter XX equals the character set to be used, e.g. US = United States.

See OS/2 Reference book for character set codes.

<<=TIP=>> Keyboard Layer/2 is a FREE alternative keyboard layout switcher between national and latin keyboard layouts for OS/2 4.0 and 3.0. Look at http://www.os2.spb.ru, or http://www.geocities.com/SiliconValley/Vista/7567/software/
ATTENTION: Pages are only in Russian and cyrillic letters.

DEVINFO=SCR,VGA,drive:\OS2\BOOT\VIOTBL.DCP

This command prepares your monitor to display information based upon the CODEPAGE specification. VIOTBL.DCP is the file that contains the video fonts for displaying characters for each of
the CODEPAGES supported by OS/2.

DISKCACHE
[Table of contents] [Index] [GENERAL]

=D,LW,32,AC:CD+E

If you are using one or more FAT partitions on a hard drive, this command sets up a disk cache for those partitions. The default cache size used by OS/2 during installation is based on how much RAM your system contains. See Table 5. The minimum cache size is 64k and the Maximum FAT cache size is 14MB.

Parameter:

D: If you leave the "D" setting, then OS/2 will set your FAT diskcache based upon the amount of RAM you have as follows: 7 or 8MB of RAM, "D" is set to 512k; and more than 8MB, "D" is set to 10% of RAM.

LW: Enables lazy writes. If you don't want lazy write enabled, then remove ",LW".

<<=NOTE=>> Lazy-writing provides significant performance improvements to your system. If you disable this feature, the performance of your system will suffer.

32: Sets the threshold size. It is express in number of sectors which are 512 bytes each. Data requests from your disk that are larger than this number will not be cached. The default is 4. Thirty two (32) is said to be an optimum number. One hundred twenty eight (128) is the maximum allowable. This setting has no impact on RAM.

AC:CD+E: If you want CHKDSK to automatically check any partition after an improper shut down, then add this parameter to end of the DISKCACHE command: AC:n where n is the partition(s) to check,
e.g. AC:C. If you add a + (plus) sign before any drive letter, OS/2 will automatically run CHKDSK on that drive each time you boot.

<<=IMPORTANT NOTE=>> Under Warp, during installation the letter "D" is used instead of the usual numeric value. On the "nets", several users have reported that their disk I/O was significantly reduced when they replaced the "D" with a value as was the case in OS/2 2.x..

<<=NOTE=>> This command is for hard drives only. DISKCACHE does not cache FAT based floppy drives.

<<=TIP=>> If you are only using HPFS, then you should REM this statement and save 64k of RAM (don't delete, you may need or want it later). If you have a FAT partition on your hard drive and you REM this statement, OS/2 will automatically set up a 64k cache by default.

<<=NOTE=>> From the IBM Fixpak40. TRAP 000E WITH REMOVABLE MEDIA. This trap will happen to anyone who uses DevIoCtl that does things like EJECT, PROTECT, etc. for Removable Media and has
removed all FAT cache from CONFIG.SYS. Workaround is to add DISKCACHE=64,LW to CONFIG.SYS.
This problem will be fixed in Fixpak 41 and above.

<<=TIP=>> If you have the RAM, increase the size to improve system performance, but don't get carried away by using to much of your RAM; this can hurt performance.

If you have formatted your hard drive(s) with only FAT partitions, the default cache size in this statement will be that noted under ONE FILE SYSTEM. If you have both FAT and HPFS partitions,
then OS/2 defaults to the cache size 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 SYSTEMS ONE FILE SYSTEM*
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.

DLLBASING
[Table of contents] [Index] [GENERAL]

=ON (default) or OFF

New setting in Warp Server for e-business

The dllbasing parameter prevents fragmentation of the shared environment, allowing more efficient use of virtual memory. The dllbasing parameter may be set to ON or to OFF. If dllbasing is set to ON, then the system will attempt to honor the base addresses (preferred load addresses) for DLLs. Honoring base addresses for DLLs is preferred because it improves system performance for loading DLLs. However, sometimes there is an interaction between the DLL basing and an application's memory usage which will cause the system to run out of private memory. In this case, you should set dllbasing to OFF so that the system will ignore base addresses for DLLs. The system performance for loading DLLs may degread marginally, but there will be more free private memory.

<<=TIP=>> By Istvan Kovacs: ON: better general performance; OFF: more private memory (just in case an app needs it)

DUMPPROCESS
[Table of contents] [Index] [GENERAL]

=drive

Activates the Dump Process. Any application process that traps will cause a process dump. The information will be written to a dump file named PDUMP.xxx where xxx is an index that is incremented each time a new process dump is created. This dump file resides in the root directory of drive specified.

EARLYMEMINIT=TRUE
[Table of contents] [Index] [GENERAL]

Setting used with kernel 14.062e or higher

will allow device drivers, etc.,

access to the memory above 16mb early in boot. Previously, this was only available after DD and IFS init was completed. This has various implications when enabled:

a) large VDISKs are possible. I tried DEVICE=\os2\vdisk.sys 16000
b) AHA154X.ADD may do bad things to your system. Don't even ask.
c) There may be some settings of HPFS386 cache that are incompatible.

<<=NOTE=>> This feature is experimental and may not work with later kernels.

FAKEISS
[Table of contents] [Index] [GENERAL]

=YES

New with Fixpak 13

Users of some security-related ISS (security) packages such as Utimaco's SafeGuard Professional, will have to add this line to config.sys. This works around a limitiation of some legacy ISS drivers. This is not a problem for the Tivoli ISS driver.

I13PAGES
[Table of contents] [Index] [GENERAL]

=1

only available with Kernel 14.062 or higher

SMP kernels could not be RIPL-booted. As part of this, there is a new config.sys parameter I13PAGES= available. Adding I13PAGES=1 to config.sys (note, no SET) reduces the memory usage of the mini VDM processes used by ibm1s506.add and the GRADD drivers. This becomes important in RIPL-boot situations.

IOPL
[Table of contents] [Index] [GENERAL]

=YES (default) or NO

When set to YES, this command lets programs that need to bypass OS/2 (and its device drivers) and work directly with hardware devices, to do so. One example is Lotus 123/G. YES means that all programs can access the hardware directly. NO means that no program can access the hardware directly. YES is the default and is generally best, since its hard for most of us to know when a program is written is such a way as to need direct access to hardware.

IOPL stands for Input/Output Privilege Level.

<<=TIP=>> You can also specify a list of programs that are allowed to work directly with the hardware. For example, IOPL=WS.EXE,123.EXE would allow only these two programs to access hardware directly.

IROPT
[Table of contents] [Index] [GENERAL]

=value

undocumented variable for IBM Dualstor

Values:

d: no FIFO
D: use FIFO
x: 0.5 MBit/s
X: 1 MBit/s

LASTDRIVE
[Table of contents] [Index] [GENERAL]

=drive

Specifies the drive LETTER of the last valid drive, including
attached drives such as CDROM, bernoulli etc.
Z is the last valid character, typically C, D, E etc.

LIBPATH
[Table of contents] [Index] [GENERAL]

Tells OS/2 where to locate Dynamic Link Libraries (DLLs).
LIBPATH is similar to DPATH and PATH, but the statement can only be used in the config.sys file and OS/2 does not search the current directory for DLLs unless you include it in the LIBPATH statement. You don't need to use the SET command with LIBPATH. It is not an environment variable.

<<=TIP=>> To reduce the search time, be sure that the various PATH statements contain the correct path to your program and other files. You can also have OS/2 search the current directory by including
a period "." right after the equal "=" symbol (LIBPATH=.;C:\....). This causes OS/2 to look in the current logged directory first.

One final item that will reduce search time: Be certain that the PATH, LIBPATH and DPATH statements in the config.sys are arranged with the most frequently accessed sub directories listed first.

<<=TIP=>> Problems can arise with duplicate filenames on the system. Sometimes you will have 2 DLL's with the same file name but for different applications, which may cause programs to misbehave. Check the ordering of directories in LIBPATH, use ".:" and enter the path in working directories for the application properties.

<<=TIP=>> Don't forget that autoexec.bat has a PATH too.

<<=TIP=>> With Warp, IBM has introduced the ability to dynamically change LIBPATH using two new environment variables: BEGINLIBPATH and ENDLIBPATH. These commands are most useful in CMD or BATCH files, but can be used in your config.sys. Any directories that appear in the BEGINLIBPATH variable are searched before directories in LIBPATH, and directories that appear in the ENDLIBPATH variable are searched after those in LIBPATH. The correct syntax is SET BEGINLIBPATH=C:\OS2.

<<=NETSCAPE TIP=>> Netscape must be in the first place of the Libpath. This means also before the above mentioned period ".". If you use Staroffice 4.0 check if that's correct, if not move the Staroffice Path behind Netscape and install Servicepak 2 for Staroffice or higher otherwise the Staroffice Browser wont function.

MAXWAIT
[Table of contents] [Index] [GENERAL]

=n (in seconds)

This command sets the longest period a program will have to wait to execute before OS/2 ups its priority. This makes sure that no program is put on hold forever while some other program hogs the system. You can set MAXWAIT from 1 to 255 seconds. The default is 3 seconds.

<<=TIP=>> When running heavy background programs, such as a BBS, change the setting to 1, i.e. MAXWAIT=1. This will keep the BBS software or other background programs running at top speed. For general use, it appears that setting MAXWAIT=2
makes the system a little livelier.

<<=NOTE=>> MAXWAIT only has an effect if PRIORITY=DYNAMIC.

<<=NOTE=>> The smaller the number you use, the more system overhead there will be.

MEMMAN
[Table of contents] [Index] [GENERAL]

=value

OS/2 can run more programs and use more data than can actually be stored in memory at any given time. This is done by swapping large amounts of memory to your hard disk and then reading the data back into memory when needed. This is called virtual memory. For example, if you have 4MB of memory you will see lots of disk activity while you are working with your system. A lot of this is OS/2 swapping memory to and from your hard disk. Lots of memory swapping slows down your system and can cause your hard disk to fragment quicker than normal.

Values:

The MEMMAN command controls the swap process. The syntax is MEMMAN=s,m,PROTECT,COMMIT where s=SWAP or NOSWAP; m=MOVE or NOMOVE.
The default is to have virtual memory on. To turn off virtual memory, which is NOT recommended, the config.sys file line should read: MEMMAN=NOSWAP. See <<=CAUTION=>> below.

PROTECT allows the allocation and use of protected memory for certain DLLs. This is done to protect those DLLs from being trashed by an errant program. Unless you are a programmer who needs this set to NOPROTECT, leave the default.

COMMIT. OS/2 will allocate space in the swap file whenever a program commits memory, i.e., a page in the swap file is allocated for every page of memory committed by a program, even if the data never actually gets swapped out. Your system should be more stable, but it will be slower also, since your swap file will grown when it doesn't have to. If you use this parameter, increase the size of your SWAPPER.DAT file by the amount of memory you are likely to use when using the COMMIT parameter. Most people "in-the-know" suggest that COMMIT not be used unless it is required by 16-bit OS/2 applications.

<<=TIP=>> You can also use the COMMIT parameter another way. Without COMMIT set, the minimum free noted in you SWAPPATH specified the point at which OS/2 gives you a message warning that your disk space is running low. When you set COMMIT, the minimum free value noted in your SWAPPATH statement becomes the amount of hard disk space that will always remain free on the swap file
partition. Thus, with COMMIT set, you can never run out of disk space on your swap file partition.

<<=CAUTION=>> When messing with the MEMMAN line, I changed it to MEMMAN=NOSWAP. As a result, I had to boot from my OS/2 installation disk and recover my backup config.sys file to get the system to boot. According to Blake Stover, "The reason MEMMAN=NOSWAP, PROTECT chokes is because of the hat tricks OS/2 does while loading the WpS, Desktop, Bitmaps, Folders, Cache buffers, MMPM/2, etc..OS/2 likes to load all of these, then swap or discard the inactive code. If there is no where to swap to it dies during boot, unable to initialise the resources it needs. NOSWAP,PROTECT should only be used for boots from floppy to do maintenance, in most cases. (People who use TSHELL on a machine with a good
amount of RAM may also use it to speed operations). IBM does not recommend that you set MEMMAN to NOSWAP unless you have more than 8MB of RAM.

<<=NOTE=>> The MOVE/NOMOVE parameter is only provided for OS/2 1.x compatibility.

<<=NOTE=>> NOPACK PARAMETER. When OS/2 initially loads a 16-bit OS/2 application, it packs the segments into pages and copies them to the swap file for faster recovery when needed. This can be disabled by using the NOPACK option on the MEMMAN line. However, the performance decrease and larger working set will rarely offset the potential of a reduced swap file size.

<<=NOTE=>> DELAYSWAP. No information at this time. SWAPDOS and NOSWAPDOS parameters from OS/2 1.x are not valid in OS/2 2.0 and later.

<<=TIP=>> From Warp Server for e-business docs: If DOS real mode is required, set the memman parameter to SWAP, MOVE,SWAPDOS to enable swapping of the DOS real-mode window. This might be a left-over from older docs, though.

<<=TIP=>> By William L. Hartzell: Setting "Memman=No Swap" will prevent OS/2 from using all memory under some conditions. Example: If the system board has a maximum memory size per slot of memory of X, then putting more memory than X
will cause the memory over X not to be used, even though no one slot has more than X. Futher example: SIMM Maximum size of 256 MB per slot, with the system board having three slots. Placing three 128 MB simm into the slots will cause the equilivant of the third simm to not be used (384 MB is greater than 256 MB).

MODE
[Table of contents] [Index] [GENERAL]

MODE is a multipurpose command that allows you to control printer ports, serial ports, modems, video monitors and disks. For example, if you want to "lock" in the baud rate on COM2, add the following MODE command to your config.sys file:

MODE COM2 baud (where baud is the rate you want to lock)

PAUSEONERROR
[Table of contents] [Index] [GENERAL]

=YES or NO

This command tells OS/2 to pause during boot, and display an error message, if an error is detected in your config.sys. If this statement is not in your config.sys, OS/2 defaults to YES. If you set this to NO, the error message will scroll off the screen so quickly that you will certainly be unable to read it, and probably may not even notice it.

PRINTMONBUFSIZE
[Table of contents] [Index] [GENERAL]

=n,n,n, (in byte)

This command sets the size of the print buffers for your parallel ports. The syntax is PRINTMONBUFSIZE=LPT1,LPT2,LPT3 where LPT1 is the buffer size for the parallel port LPT1, LPT2 is the buffer size for LPT2 and LPT3 is the buffer size for LPT3. The default and minimum is 134 bytes and the maximum is 2048 bytes.

<<=Note=>> You must define a buffer for LPT2 and LPT3 even if you don't use these ports. You will get an error message at start up if you don't.

<<=TIP=>> You may be able to improve printer throughput by increasing buffer size. I have my LPT1 set to 2048. This setting will also speed-up drives attached to the parallel port (e.g. Zip-Drives).

<<=TIP=>> If you need more than three LPT-Ports get the LPT49.ZIP Package from http://www.kellergroup.com. See also the command DEVICE=drive:\path\LPT49.SYS under Device later in this file.

The following REXX-Script also adds additional printer ports 4-9 by generating the spooler-queues LPT4-9 in the OS2SYS.INI

/*LPT4-LPT9 in OS2SYS.INI*/
Call RxFuncAdd 'Sys.ini','RexxUtil','Sys.ini'
do i=4 to 9
call Sysini'System','PM SPOOLER PORT','LPT'||i,';'||'00'x
end
exit

<<=TRIVIA=>> Ever wonder where IBM got a parameter like 134? Lynn Nash passed along the following:

"Obviously you have no background on the big iron or it has disappeared into historical memory :-).
"Mainframe line standard of 132 columns plus 2 for carriage return and line feed characters. That is why all the wide carriage dot matrix printers also had 132 column lines, to be able to use that wide green bar paper. Anyone that had an early
Okidata 83 dot matrix even had an electronic format tape, but that is a story for another time."

<<=NOTE=>> By William L. Hartzell: Printmonbufsize has no value if one uses the par1284.sys driver, instead of the print01/02.sys driver

PRIORITY
[Table of contents] [Index] [GENERAL]

=DYNAMIC (default) or ABSOLUTE

OS/2 automatically assigns processing priorities to each thread of a program as it begins processing. A thread running in the foreground will generally have priority over a thread running in background. Thread priorities are adjusted, generally based
upon how active they are, by OS/2 on an ongoing basis to make sure each thread has adequate processing time. On the rare occasion that you need to run a program which must never change in priority, you should set PRIORITY=ABSOLUTE, otherwise, don't mess with it.

"To summarise: The highest priority thread always has the machine. If there are two equally high threads, they timeslice having the machine. Note that there are many Operating System threads, like the scheduler itself, that are higher priority
than any program. Now, if PRIORITY=ABSOLUTE in the config.sys file, that's all there is to it. But usually, PRIORITY=DYNAMIC, and OS/2 keeps gradually increasing the priority of a starved thread until it gets to run. Maxwait determines the maximum time, in seconds, before the scheduler intervenes to raise a low priority thread up high enough to run."

PRIORITY_DISK_IO
[Table of contents] [Index] [GENERAL]

=YES (default) or NO

This command determines whether programs running in the foreground have priority access to disks. If you want a program running in the background, like a BBS, to have equal access to your disks, then change this statement to NO. If you change this command to NO and then find that your communications program does not work, change back to YES.

PROTECTONLY
[Table of contents] [Index] [GENERAL]

=YES or NO

Allows you to choose between a shared DOS and OS/2 operating environment or just an OS/2 environment. If you plan to run only OS/2 programs, then set PROTECTONLY=YES. If you plan to run DOS programs (including Windows), then set PROTECTONLY=NO.

<<=NOTE=>> Jonathan de Boyne Pollard relayed the following: "Part of the difficulty of talking about OS/2 2.x, as opposed to OS/2 1.x, is that *all* processes run in *protected mode*. The 386 never runs in real mode in OS/2 2.x.

"Virtual DOS Machines are run in v8086 mode, which is still *protected mode*, as the paging mechanism is still active. The major difference between v8086 and normal protected mode is that the segment base addresses in linear memory are
fixed, instead of being determined by the entries for each selector in the LDT and GDT.

"So PROTECTONLY in OS/2 2.x means *don't use v8086 protected mode*. For a while there we thought that it meant *don't use real mode* and so was useless to OS/2 2.x, but it seems after all that it retains its original OS/2 1.x semantics, if not its original mechanism."

PROTSHELL
[Table of contents] [Index] [GENERAL]

=drive:\OS2\PMSHELL.EXE

This OS/2 command tells OS/2 which program you want to use as the protect mode shell (the program that determines what your user interface looks like and how it operates.) This is the first program OS/2 will execute. PMSHELL.EXE is the program which initializes OS/2 Presentation Manager. If you delete this line from your config.sys file, OS/2 will load PMSHELL.EXE by default.

<<=NOTE=>> There are several alternatives to PMSHELL.EXE. One is OS/2's own CMD.EXE. If you replace PMSHELL.EXE with CMD.EXE, you will get a full screen OS/2 session only and will not be able to run PM programs. An alternative is TSHELL.EXE, a text-based, protected-mode shell for OS/2. Any one remember OS/2 1.x? TSHELL makes OS/2 look something like OS/2 1.0, which did not have a graphical user interface. With TSHELL you can start and switch full-screen sessions only. These can be OS/2, DOS, or WINOS2 sessions depending on system configuration. You use Alt+Esc to switch around sessions and Ctrl+Esc to pop up
the task list. But please note, like OS/2 1.0, there is no Presentation Manager, OS/2 PM applications will not work. TSHELL is IBM EWS-Software found at ftp://ftp.pc.ibm.com/pub/pccbbs/os2_ews/

REIPL
[Table of contents] [Index] [GENERAL]

=ON or OFF (default)

OFF automatically restarts the system when a system trap or internal processing error occurs.

<<=TIP=>> This command along with the SUPPRESSPOPUPS command can be very useful to those running a BBS. If a trap or internal processing error occurs while your BBS is unattended, having these two command in your config.sys will cause your system to log the error and then restart the system, so your BBS is back online.

REMOTE_INSTALL_STATE
[Table of contents] [Index] [GENERAL]

=X

Variable used for CID installations.

<<=ATTENTION=>> If defined, all installation programs created with Software Installer/2 will not display.

RESERVEDRIVELETTER
[Table of contents] [Index] [GENERAL]

=driveletter

New in Warp 4, Warp 3 with Fixpaks higher 24.
<<=NOTE=>> Multiple RESERVEDRIVELETTER statements are allowed but only the last one is used. Valid Driveletters are D - Z.

During the processing of CONFIG.SYS, OS/2 allocates drive letters for all BASEDEV= statements. In general, the only BASEDEV= statements that allocate drive letters are those for the Disk Device Driver, which will allocate 1 drive letter sequentially for each local disk partition. Three local disk partitions would allocate C:,D:,E:.

After processing BASEDEV= statements, the system will honour the RESERVEDRIVELETTER statement(s). If the RESERVEDRIVELETTER statement
conflicts with any drive letter already assigned to a local disk partition, an error message will be generated and that RESERVEDRIVELETTER statement will be ignored.

The next processing occurs for DEVICE= statements. DEVICE= statements for local block mode devices will assign drive letters, starting sequentially immediately after the highest drive letter specified in a RESERVEDRIVELETTER statement. Examples of local devices which use drive letters are CDROM, R/W OPTICAL, TAPE, Virtual Disks (VDISK).

So on a network, for example, the administrator can reserve specific drive letters for his later use in CMD files, or login scripts, so that drive references across the network remain stable.

SETBOOT
[Table of contents] [Index] [GENERAL]

=value

This command lets you configure Boot Manager in OS/2, if it was installed, otherwise you will experience an error message on boot.

Values:

/T:x Number of seconds that the Boot Manager menu will remain on the screen before the default system starts. A 0 (zero) setting causes the menu to be bypassed. A NO (as in /T:NO) causes the menu to remain displayed until a selection is made.

/Q Queries the currently set startup environment, and displays the default logical disk alias, timeout value, mode, and drive letter assignments for each system index.

/X:x Sets the system startup index to indicate the partition that the Boot Manager should start, where x is from 0 to 3.

For complete information and other parameters available, refer to the online OS/2 Command Reference.

SOURCEPATH
[Table of contents] [Index] [GENERAL]

Sets the path for the OS/2 Installation program SYSINST2.EXE

SUPPRESSPOPUPS
[Table of contents] [Index] [GENERAL]

SUPPRESSPOPUPS=0 will restore behaviour of WARP3 to pre-FixPak 29 behaviour. That is, to disable logging and to have trap screens displayed unless specifically overridden by an application's use of the DosError API.

SUPPRESSPOPUPS=x: will disable trap screen display for all processes and will log trap screens in x:\POPUPLOG.OS2, where x: is a drive or partition.

If SUPPRESSPOPUPS is omitted then the behaviour is as described above under "Automated Trap Screen Logging".

<<=NOTE=>> The log file name cannot be overridden.

SWAPPATH
[Table of contents] [Index] [GENERAL]

=drive,path,mmm(in kb),nnn (in kb)

OS/2 can allocate more memory than it actually has available. It does this by swapping memory to a hard disk file called SWAPPER.DAT.

Parameter:

mmm is a number from 512 to 32767 which specifies how large the SWAPPER.DAT file can grow before it stops consuming hard disk space. The size is stated in the negative. In other words, if you have the mmm set to 512, then the SWAPPER.DAT file can grow until there is only 512k left on your hard disk.

nnn is the starting size of the SWAPPER.DAT file.

<<=TIP=>> When your swap file grows beyond the initial size you have specified, OS/2 starts to manage the swap file. This increased overhead can negatively impact your systems performance. Therefore, if your swap file always exceeds its initial size, consider increasing the files initial size. For example, if your swap file usually grows to 8MB, set the initial size of 8MB.

<<=TIP=>> As time progresses, OS/2 will gradually swap dormant code from real RAM to the swap file. So if you tend to use a few programs for a long period of time you will notice a gradual performance improvement. Try and avoid application hopping

<<=TIP=>> Normal operation of OS/2 can involves considerable disk activity as operating system functions are loaded and pages are moved in and out of the swap file. Here are a couple of tips to improve performance. (1) Consider dedicating a separate partition for the swap file. This helps avoid fragmentation of the swap file, because other files will not be added or deleted from the dedicated partition. (2) If you have both FAT and HPFS partitions, put the swap file on the HPFS partition to take advantage of the better performance of HPFS. (3) If you have a system with two hard disk controllers, put the swap file on a disk managed by the least used controller. (4) Keep your swap file on the MOST used partition of the LEAST used hard drive.

<<=WARNING=>> Never put your swap file on a networked drive.

<<=NOTE=>> Your swap file will grow (in 1MB increments), but it also shrinks when two conditions are met. One, when the amount of free space in the swap file is greater than 1.5MB, the swap file will be compressed during system idle time. (It will not shrink if there is a constant "hit" on the drive by a program such as a swap file monitor.) Two, during the compression, free space is moved to the end of the swap file. When this free space at the end of the swap file exceeds 1MB, the swap file will be shrunk.

<<=NOTE=>> See the discussion of the COMMIT parameter for the MEMMAN config.sys line including the <<=TIP=>>.

<<=WARP NOTE=>> Your swap file in Warp will be larger than in earlier versions of OS/2. This is normal. The most significant change that has been made is how system DLL's get loaded and what is now valid data for swapping. System DLL's include: DISPLAY, SOM, PMMERGE, PMWP, DOSCALL1, PMATM, PMMLE, IBMDEV32, PMCTLS, PMSPL, IBMVGA32, PMGPI, and PMVIOP.

In the previous versions of OS/2, DLL code was never copied to the swapper file. In WARP, code for system DLL's can be written to the swapper file and, in addition, during boot, PMMERGE, DOSCALL1, PMGPI, PMWP and PMVIOP will be swapped out. This means that there will be an overall increase in swapper size. This was done to increase overall system performance.

To control the size of the swap file use the FREE SmartBar by Alessandro Rossi available at http://www.freeweb.org/software/AlessandroRossi/

SXFAKEHWFPU
[Table of contents] [Index] [GENERAL]

=1

Activates fix for a 'math rounding error'. Warp 4 only.

SYSDUMP
[Table of contents] [Index] [GENERAL]

The SYSDUMP command forces a System Dump to be initiated, regardless of the TRAPDUMP settings. This command is provided for the use of service personnel to allow Dump Initiation to be automated through use of a command file.

<<=Warning=>> The initiation of a System Dump causes an immediate termination if the system without any shutdown. No file system shutdown is performed. The system behaves as if a fatal crash has occurred thus under rare circumstances data can be lost.

The command syntax is:

SYSDUMP [/NOPROMPT]

where:

NOPROMPT allows the Dump to proceed without the prompt and response to message:

"Do you want to force a system dump? (Y/N)"

THREADS
[Table of contents] [Index] [GENERAL]

=n (in numbers)

OS/2 programs can have several different processes running at the same time. These are called threads. This command sets the maximum number of threads (from 32 to 4095 in OS/2 2.x and from 64 to 4095 in Warp 3) that OS/2 can run at the same time. If this command is not included in your config.sys file, OS/2 will default to 64. Jim Gilliland commented on what happens if OS/2 runs out of Threads: "If an application tries to start a new thread, and OS/2 has all of its threads already in use, then OS/2 will generate an error. It may result in a popup, or it may return the error information to the application."

<<=TIP=>> If you have more than 8MB of RAM and run lots of OS/2 specific programs, you may be able to improve system responsiveness by increasing the number of threads. Why? Because well written OS/2 programs will use threads to improve program performance. Therefore, the more well written OS/2 programs in use, the more threads that could be needed. But still keep in mind that this only holds true only when you are using a fair number of OS/2 specific programs at the same time.

<<=SERVER NOTE=>> On a server it is generally considered better to have 512 threads.

TIMESLICE
[Table of contents] [Index] [GENERAL]

=x,y (in milliseconds)

This command allows you to manually control the minimum and maximum amount of processor time any thread can receive at once.

Parameter:

x is the minimum time slice (in milliseconds and must be at least 32)

y is the maximum length (must be less than 65536).

Jim Gilliland once posted: "The Timeslice parameter controls the minimum and maximum timeslice that OS/2 will allow an application to use. If you make the timeslice longer, OS/2's dispatching overhead will be reduced, but the system's multitasking operation will be "choppier". Increasing the length of the maximum timeslice (the second parameter) will allow OS/2 to gradually increase the length of the timeslice used by an application when it is not competing with any other apps for CPU time (that is, when it is the only app running or all others are blocked)."

<<=TIP=>> OS/2 handles time slicing dynamically. This means that the system is adjusting the time slice values based on the actual processes active on the system as the workload changes. Therefore, it is best not to attempt to manually set TIMESLICE. OS/2 can handle this process far better than most of us can.

TRACE
[Table of contents] [Index] [GENERAL]

=ON, OFF, n

The system trace facility is used to record a sequence of system events, function calls, or data. The record is usually produced for program debugging purposes. After the trace data is recorded, the System Trace Formatter is used to retrieve it from the system trace buffer (see TRACEBUF below) and format the data to either your display, printer, or to a file. Start tracking system problems by turning TRACE on which will establish a 4KB default buffer. (You can increase this using the command TRACEBUF) to store tracing data. You can also start TRACE from an OS/2 command prompt.

<<=NOTE=>> You can turn TRACE=ON and then set TRACE=OFF for major or minor codes. For example, TRACE=OFF 24,50,98.

<<=NOTE=>> IPE ON BOOT AFTER FIXPAK 35 INSTALLED ON UNI SYSTEMS If you experience a kernel trap (black screen trap) or get a messages stating that device drivers (such as CLOCK01.SYS) were not able to install at boot time add the following statement to the end of CONFIG.SYS: TRACE=OFF,6

TRACEBUF
[Table of contents] [Index] [GENERAL]

=n (inkb)

This command sets the size of the trace buffer. If any valid TRACE statement is in your config.sys, the default size of the trace buffer will be 4KB. You can modify this size with the TRACEBUF command. Maximum size is 63KB. "n" is a specific number from 1 to 63, representing a multiple of 1024 bytes.

<<=NOTE=>> TRACEBUF will allocate memory with or WITHOUT a valid TRACE statement in the config.sys. This is to allow command line tracing. So check that TRACE/TRACEBUF are correct for your use.

TRAPDUMP
[Table of contents] [Index] [GENERAL]

=value

The TRAPDUMP command allows the conditions under which a trap will initiate a System Dump to be set dynamically. Prior to Warp 3.0 FixPak 29, the System Dump setting could only be manipulated from CONFIG.SYS by use of the TRAPDUMP statement.

Use of this command should be made under the direction of service personnel.

<<=Warning=>> The initiation of a System Dump causes an immediate termination of the system without any shutdown. No file system shutdown is performed. The system behaves as if a fatal crash has occurred, thus under rare circumstances data can be lost.

<<=Warning=>> TRAPDUMP will copy memory contents to a storage location, which means the storage required = amount of physical system memory

The command syntax is:
TRAPDUMP [[ON] | [OFF] | [R0]] [x:] [/NOCHECK]


Values:

ON enables all application and system traps to initiate a System Dump.

OFF disables automatic dump initiation.

R0 enables only Ring 0 traps to initiate a System Dump.

x: specifies the Dump Partition.

NOCHECK overrides the system level check for WARP 4.0, since use of this command on a system level prior to FixPak 29 is equivalent to the SYSDUMP command.

OLD TRAPDUMP=xx,d, prior to fixpak 29 for WARP 3.0

Parameters are: OFF,drive letter
ON, drive letter
R0, drive letter

Indicates when a stand alone dump is to be taken and where the dump is to be placed. The default value is OFF and the default drive is "A".

If you are sending a memory dump to hard disk, you must first create a FAT partition labelled SADUMP and give it a size greater than the amount of physical memory in your system. The drive you specify in the TRAPDUMP statement must contain the SADUMP partition. Any existing data in this partition will be overwritten. The system will restart after the TRAPDUMP process has been completed.

<<=NOTE=>> If REIPL=ON is specified in the config.sys file, the system will restart automatically and no dump will be taken when a system trap or internal processing error occurs.

Luca Regoli, Societa' Italiana Autori Editori, provides the following information on this command.
"This way whenever a trap occurs you don't get anything on the screen. The PC beeps and [responds] as if you had depressed CTRL+ALT+NUMLOCK / NUMLOCK.
"Not very useful though I don't know how to get traps information from the dump disk (and don't want to download all 20Mb dump of memory any time I get a trap)."

TRAPLOG
[Table of contents] [Index] [GENERAL]

=value

The TRAPLOG command allows dynamic control of trap information logging.

Values:

x: specifies that trap information is to be logged in x:\POPUPLOG.OS2, x: being any partition drive letter.

NOLOG disables logging of trap information.

POPUPS enables the trap information pop-up message (SYS3175).

NOPOPUPS disables the trap information pop-up message.

TRUEMODE
[Table of contents] [Index] [GENERAL]

=1

Installs the Trapdoor feature of Warp 4, only on machines with SCSI Harddisks.

VIRTUALADDRESSLIMIT
[Table of contents] [Index] [GENERAL]

=n (in kb)

The default value for VIRTUALADDRESSLIMIT in OS/2 Warp Server for e-business is 1 GB (=1024). The VIRTUALADDRESSLIMIT parameter is also available for OS/2 Warp Server SMP Feature and Warp 4.0 Fixpak 13. Areas of memory below 512 MB have been remapped for higher availability in that region.

2048 allows max. memory allocated 2 Gigs of shared RAM. Only useful for developers.

You must have a hard disk that can accommodate the swap file. UW2SCSIs are recommended for the swap disk unless you wish to see your computer behave like a washing machine in spin dry mode.

<<=NOTE=>> The OS/2 Warp Server Advanced SMP addendum states that this number can go to 3 Gigs. Memory support has also been enhanced since now an application can access a virtual memory address space of up to 3 GB by use of the VIRTUALADDRESSLIMIT = 3072 parameter in CONFIG.SYS. Areas of memory below 512 MB have been remapped for higher availability in that region.

VME
[Table of contents] [Index] [GENERAL]

=NO

Disables the Virtual Mode Extensions introduced with the Intel DX2

<<=TIP=>> By Ron Higgin: If you get frequent Trap D and Trap E errors in DOS/Windows sessions it may provide some relief.

WORKPLACE_NATIVE
[Table of contents] [Index] [GENERAL]

=0

New setting for Warp Server for e-business. No information until now

WORKPLACE_PRIMARY_CP
[Table of contents] [Index] [GENERAL]

=1

New setting for Warp Server for e-business. No information until now

WORKPLACE_PROCESS
[Table of contents] [Index] [GENERAL]

=NO

New setting for Warp Server for e-business. No information until now

WP_OBJHANDLE
[Table of contents] [Index] [GENERAL]

=n

Contains the object handle for the current OS/2 session. This handle is unique for each session started via an WPS Object.

 
Обучение новичков

 
Статьи