If you know of some undocumented OS/2 Warp v4 tricks, or a nice tip, send it to us and we'll post it here!
If you wish to link to this page, feel free. We do not take kindly to others stealing these pages, and not giving credit where it is due!
Here is what we know so far:
| Index | ||
|---|---|---|
| Tip 1: Change WarpCenter Clock | Tip 2: WarpCenter Enhanced Kill | Tip 3: Warp 4 Cache parameters |
| Tip 4: HPFS Undocumented | Tip 5: Easter Eggs! | Tip 6: More WarpCenter tricks |
| Tip 7: Specifying your FIND Utility | Tip 8: DIR undocumented | Tip 9: Webexplorer problems |
| Tip 10: Run Win32s, WinNT/95 (some) under Warp | Tip 11: Warp 4 Registration | Tip 12: OS/2 for the PowerPC? |
| Tip 13: Two misc WPS tips | Tip 14: Warp 4 & RODENT.SYS | Tip 15: Scrolling text in non-active windows |
| Tip 16: PCMCIA Support on NEC 2400, others | Tip 17: Mouse Tricks | Tip 18: WinOS2 Print Manager |
| Tip 19: SC-200 SCSI & AWE32 issue | Tip 20: WarpCenter, Drives and Icons | Tip 21: Warp 4 Cache expert advice |
| Tip 22: WarpCenter and Bootup Wierdness | Tip 23: JPEG background images | Tip 24: Adobe Photoshop v3 under Warp (with Win32s v1.25) |
| Tip 25:Windows applications hang when having the MS-Windows HP Deskjet 600 device driver installed. | Tip 26:Installing Warp 4 with an IOMEGA Bernoulli PC1600 board. | Tip 27:Solving the NumLock problem |
| Tip 28:Solving problems with Dial Other Internet Providers | Tip 29:Solving problems with HP Deskjet 850 windows drivers | Tip 30:The cure for OS/2 Sound & MIDI is the ESS 1868 Sound Card |
| Tip 31:Lotus Smartsuite 96 for OS/2 tip | Tip 32:IBM Device Driver CD tip | Tip 33:IOmega 2GB Parallel Port Tape Drive & ESS1868 Sound Card Interupt (IRQ) settings |
| Tip 34:More tips: ESS1868 Sound Card | Tip 35:Warpcenter Bug workaround | Tip 36:Hardware Detection Manager Tip |
| Tip 37:Epson Color Printer Tips | Tip 38:Speedy Fixpak application | Tip 39:Speedy Fixpak application #2 |
| Tip 40:PMDiary (from OS/2 v2.1) on Warp 4 | Tip 41:Warp 4 Fixpak 3 Print Problem workaround | Tip 42:Flakey Ultimail Icons |
| Tip 43:Reconfiguring Warp 4.0 PCMCIA support | Tip 44:Best Removeable Storage under Warp | Tip 45:
Long filename support for CD-ROMs |
SET SCUSEPRETTYCLOCK=ON
[Return to the Index]
SET KILLFEATUREENABLED=ON
Once you have added this, shutdown and rebooted, you can access the feature simply by holding down your CTRL key and clicking your LEFT MOUSE BUTTON on the Window List icon of the Warp Center. You will be presented with a list of all running processes. Click on one with your LEFT MOUSE BUTTON and you will be asked if you wish to KILL the task. Answering YES will terminate the task.
22 Oct 96: To drop the need for the confirmation box, add SET SCKILLCONFIRMDISABLED=ON to your CONFIG.SYS
3 Mar 97: Can you help me?
This line is typed in my config.sys, exactly as it appears above (I compared the two side by side), and I still get the confirm dialog pop-up when I execute a "kill."While this is not a major (or minor even) problem, I am curious to know if a reason for it can be found, as it might lead to a revalation regarding some of the more troublesome, though less reproduceable, glitches I am having with my system.
I felt you would want the info that this doesn't seem to work on at least one system.
I am running OS/2 Warp 4 on a "Winbook FX" notebook:
Intel pentium 120mhz (Mobile Triton chipset),
Pheonix NoteBIOS v. 4.0,
Cirrus Logic CL-7543,PCI interfaced, graphics controller,
Creative Tech. CT-2505 sound card,
1G IDE HD, 32MB RAM, PCI Bus
If any info regarding this problem should come to your attention, I would be indebted for a note, pointing to the details, sent to my E-Mail.
Submitted by: John Griffin (jgriffin@sfsu.edu)
[Return to the Index]
[D:\]cache /Dstg:on
DiskIdle: 1000 milliseconds
MaxAge: 65000 milliseconds
BufferIdle: 950 milliseconds
Cache size: 2048 kbytes
DirtyMax: 819 buffers
WriteCache: 65536 bytes
3 Lazy write worker(s) are enabled.
1 Read ahead worker(s) are enabled.
You will find new features and options like /DirtyMax, /Writecache, etc.
Submitted by haller@zebra.fh-weingarten.de (Pat)
[Return to the Index]". By the way, several undocumented HPFS features were mentioned, including one which can help you temporarily avoid running CHKDSK at boot up. (You should still run it as soon as possible.) Suppose you have HPFS drives C, D, and E. If you have the following line in your CONFIG.SYS file:
IFS=C:\OS2\HPFS.IFS /FORCE /QUIET /AUTOCHECK:CD
then even if Drive E was improperly stopped (you did not shutdown OS/2 Warp properly) CHKDSK will not run on Drive E at boot up, and you can get access to the drive immediately. /QUIET, which cannot be the last parameter in the line, disables any error message (and should be used with extreme caution). In fact, it's probably not a good idea to use /FORCE either, but it is available if you absolutely must have immediate access to an HPFS drive that was improperly stopped. You should run CHKDSK on that drive just as soon as possible. ".
[Return to the Index]
Make the Desktop the focus (click the LMB on it), Hit CTRL+SHIFT+ALT+O and wait. Press ENTER to exit. If you wish to get rid of this to reclaim disk space, delete the AAAAA.EXE and AAAAA.BMP files from the \OS2\BITMAP directory.
Submitted by multiple people
[Return to the Index]This makes the WarpCenter object "nukeable" i.e. you can right click and choose "Delete" which is not possible normally. Why would you want to do this? Who knows :) Maybe you just want to kill the object for some reason....
Submitted by paul@i1.net (Paul Hartman)
[Return to the Index]This allows you to define an external find utility and bypass the built-in one. Click the little flashlight icon (Warpcenter) and you get whatever you specified!
Submitted by paul@i1.net (Paul Hartman)
[Return to the Index]Submitted by ormson@gt-online.com (Benny Ormson)
[Return to the Index]After I initially installed Warp 4. I was having several annoying problems with WebExplorer V1.2. They were:
With the help of Kevin Royalty, I looked around and found an older version of a file called "explore.cat". If you have the same symptoms as those mentioned above, do the following:
[E:\tcpip\msg]dir explore* /s
The volume label in drive E is OS2 DATA.
The Volume Serial Number is A6EC:AC15.
Directory of E:\tcpip\msg
.-..-.. ..:... ..... 0 explore.cat
1 file(s) 4 bytes used
Directory of E:\tcpip\msg\enus850
7-22-96 9:29a 28454 0 explore.cat
8-27-96 2:42p 48640 0 explore.dll
2 file(s) 77094 bytes used
Total files listed:
2 file(s) 77094 bytes used
596738048 bytes free
Note the occurence of explore.cat in the E:\tcpip\msg directory. I put dots in place of the date, time, and size since I have deleted the file and I don't know what the actual values are. However, I do remember for a fact that this file was a few days older than the explore.cat file in the E:\tcpip\msg\enus850 directory. After comparing this with Kevin's machine, it turned out the version in the E:\tcpip\msg directory was bogus, hence the reason why I have since deleted it. :)
Bottom line: If you use WebExplore V1.2 that comes with OS/2 Warp V4 (gold code), the explore.cat file should only reside in d:\tcpip\msg\enus850. If it resides in any other location, rename or delete it. Once I deleted it from this directory, my WebEx problems went away.
Chris Lloyd
Cincinnati (CPCUG) OS/2 SIG and Team OS/2 User Group
Submitted by: Jack Nichols (jnichols@voyager.net)
[Return to the Index]Submitted by: Kent Rebman (krebman@vnet.ibm.com)
23 Jan 97: There is a much cleaner 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.
Submitted by: Seth McFarland (ptackbar@vnet.net>
[Return to the Index]Submitted by: George Fulk (fulkgl@austin.ibm.com)
[Return to the Index]Submitted by: Harold Horsman (Harold_Horsman@ibm.net)
2 Jan 97: With Warp 4, or at least the WarpCenter, you can get the Desktop back to fullsize without rebooting. Simply open the WarpCenter properties and switch "Show only when mouse is over Center's position".
Submitted by: Peter Franken (peter@pool.informatik.rwth-aachen.de)
[Return to the Index]The tablet / enhanced mouse driver by M. Finney was broken by the GA code of Merlin but i found a work-around. The symptoms i got was an error free driver load (including vmouse.sys), a mouse cursor on the first graphic mode screen but the mouse pointer was static ie it would not move. All that was required was to put a "basedev=reserve.sys /IO:3f8,8 /IRQ:4" as the first line of my config.sys. You will note that the values correspond to normal com1 as this is were my tablet is connected. By modifying the values to /IO:2f8,8 and /IRQ:3 this should work for com2. I dont know if the problem was present in the BETA code as i did not get a copy but it is present in the DEVCON version. I hope this will help someone because it had me looking very distainfully at a mechnical mouse for a few hours. This driver (called RODENT.SYS) supports all mice and quite a number of tablets and has better/faster/more flexable mouse support and support for more buttons.
Submitted by: Paul F. Grobler (relborg@ibm.net)
[Return to the Index]I have found, working on the Australian Help Desk, that it is possible to scroll text in the window behind the foreground one (entering call text in retain window eg.) that by holding down the LEFT ctrl key the data can be scrolled without sending the active front window to the rear and having to pull it back to the front. This is very handy here and may be of use to others.
Submitted by: Kenneth Laurie IBM Australia (lenac0032@?????????)
Ctrl-Button and window-manipulation with non-active windows:
A double-click with LMB in the title bar of a window in the background maximizes that window (and vice versa) and puts it in the forground. When you press the Ctrl-Button while double-clicking, the window stays in the background. In the same way, You can drag windows around with RMB without moving them in the foreground.
Submitted by: Sundermann-Michelsen (sundermann-michelsen@uni-tuebingen.de)
[Return to the Index]
If you are trying to get PCMCIA support on a notebook and all your pc
cards are seen as memory, try the following:
(put as the first line in the config.sys)
Basedev=reserve.sys /mem:ca00,2000
There is a problem in the algorithim used by resource manager and this allows pcmcia.sys to put itself in rom space. Use Rmview /mem to locate the area that pcmcia is in and force it to a different location. You may need to adjust the second value for machines other than the NEC Versa 2400. Thanks to Ed Tupple from the OS/2 DDK support team for helping to solve this..
Submitted by: Clark R. Tompsett (ctompset@MASTER.7cities.net)
[Return to the Index]The following appears to be system wide, from any text/graphic window so long as the application itself doesn't trap the mousebuttons for itself (Netscrape, EPM etc but fair enough I guess!).
With left mousebutton, swipe text to highlight then tap right mousebutton. This copies selected text to the clipboard.
Position cursor with right mousebutton and tap left button. This pastes clipboard at cursor point.
System wide from editors to filename input fields to command line windows and command line prompts and, I've heard, to and from WinOS2 sessions (so sayeth a Usenet User who runs WinOS2).
Essentially a neat text copy/paste operation. Great for grabbing URLS, filenames, directories, paragraphs etc.
(You can use the left mousebutton to position the cursor and tap with the right mouse as you did for the copy, but input fields will, with the slightest movement from you, enter into 'overwrite' mode which will result in you copying to the clipboard again.)
So, left swipe right tap to copy... right point and left tap to paste.
Indispensable!
Submitted by: Clive W. Humble (chumble@artin.glassnet.com)
[Return to the Index]In Warp 3, WINOS2 Printman was easy to set for non-use, but in Warp4 he
just keeps coming back up each time a WINOS2 session is opened. To fix
his wagon good, just add the following line to the first section of
System.ini in the WINOS2 subdirectory: MAVDMAPPS=
By adding this line, Printman will be dormant.
Submitted by: Tom Nadeau (os2headquarters@greenheart.com)
[Return to the Index]The Creative Labs PnP AWE32 demands IRQ 5, DMA1 & 5 at boot
The SC-200 SCSI Adapter also wants IRQ5. This results in sounds and MIDI files in OS/2 and WinOS2 being clipped, i.e., only the first part of the file(s) play.
Experiementation revealed that by setting the BIOS ROM to dedicate IRQ5, DMA 1 & DMA 5 as being used by ISA cures the problem.
The SC-200 then boots at IRQ 9, DMA 0.
Following this (or before) make sure you follow the AWE32 WinOS2 instructions provided in the OS/2 Information file...found as follows:
Submitted by: Bill Easley (forensic@internorth.com)
[Return to the Index]Here's another nifty trick I found. If you drag the individual Drive Icons from the Icon Window to the Warp Center System tray (or make another) you can instantly open a tree view of any drive. I have set up numerous trys and its the best organization I have ever had. One click and Voila...the app or whatever is up and running.
You can also change the icons by editing them, saving them to a folder and then dragging the new icon to the app's folder.
Submitted by: Bill Easley (forensic@internorth.com)
[Return to the Index]Doug: CACHE.EXE shouldn't be used in CONFIG.SYS, it should be put in STARTUP.CMD. If you type CACHE ? you will see:
The specified option, ?, is incorrect.
Correct usage: cache [OPTIONS]
where OPTIONS is one or more of:
-DISKIDLE:n Sets disk-idle time before write to n milliseconds.
-MAXAGE:n Sets maximum age of cache buffer to n milliseconds.
-BUFFERIDLE:n Sets buffer idle time to n milliseconds.
-Lazy:ON|OFF|n Turns lazy writing on, off or set to 'n' lazy writers.
-READAHEAD:ON|OFF|n Turns read ahead on, off or set to 'n' read ahead workers.
The new parameters are LAZY:n (in Warp 3 it only allowed ON & OFF) and -READAHEAD. The -n in READAHEAD isn't used, but will accept 0 or 1, and turn that into an ON or OFF.
Ron: Do you know of the /DirtyMax and /WriteCache switches?
Doug: They're not very useful - I use them in testing only. The DIRTYMAX switch sets a maximum number of dirty buffers - if this limit is reached, the lazy-writer wakes up and cleans up the cache. It is set at 80% of the cache. WRITECACHE is a parameter that sets the maximum size of a WRITE that will be put in cache. It is set to the maximum size of a write operation (64K).
Submitted by: Ron Micklin (Ron_Micklin_at_CorpSoftDallasHD@stream.com)
[Return to the Index]If you find your system hanging while the Desktop is being built after a restart/boot, try removing ",WARPCENTER" from the AUTOSTART= line in your config.sys. Instead, drag and drop a shadow of the WarpCenter icon (located in the OS/2 System folder) into the Startup folder. The effect of this is to cause the WarpCenter to be built after the Desktop is built and not before.
I start several "background" tasks from the Startup folder each time I boot the system, and found the system was frequently hanging on a blank screen. Finally I did a little research and found that the WarpCenter was being built at the same time the Desktop (and background programs) were started and that it takes a quite awhile to finish. The simple change described above completely eliminated my problem.
Submitted by: Walter F Metcalf (wfmetcalf@golden.net)
[Return to the Index]I have these tips for you, I found out they worked on OS/2 Warp 4.0, but haven't test them on earlier version (3.0, 2.x)
Submitted by: David J. van Enckevort (enckevor@dds.nl)
Addendum: 23 Oct 97
This is just the tip of the iceberg here. You cna use any image format that OS/2 can understand as a background image, GIF, PCX, PhotoCD, TIF, TGA, ... If there is a codec for the format, then it can be used as a wallpaper.
Also, a good place for PhotoCD images is the Warp 3 CDRom, which has some really nice photos on it. Time to go dig it out!
Submitted by: Henry Rieke (u6c16@wvnvm.wvnet.edu)
[Return to the Index]I have not met anyone that uses OS/2 Warp that could get PhotoShop3.0 to run under a winos/2 session. Also I read on some site (IBM's I think) that PhotoShop3.0 was one of two tested programs that would NOT work under WinOS/2's Win32s system. But while trying to beat the system I noticed that Photoshop installed a newer (and unsupported) version of win32s. I reinstalled win32s v1.25a (the setup program won't let you do this... you must first edit your win32.ini to read "setup=0") and created a seperate windowed winos/2 session of PhotoShop3.0 and it worked. All filters and saving options work correctly, I haven't run into any problems. I hope this can help all 15million OS/2 users out there.
NOTE: OS/2 Does NOT come with Win32s v1.25 support, you will need to get the installer (make sure it is for 1.25 also, newer vesions don't work).
NOTE 2: The installer is available here. NOTE 3: Further information is available here.Submitted by: Michael Langston (malisp@ibm.net)
[Return to the Index]Win-OS2 session doesn't kill the HP print manager when closing the session. If you printed something the print manager remains in memory with the ID of the calling program. You can't the reload the windows program because Warp sees it open.
To correct this you must kill the SYSINIT(xxx.EXE) where xxx is your windows program. Use the Warp killfeature, Yap.exe or similar to do it.
Submitted by: Charles Jubin (cjubin@mail.inetpc.com)
[Return to the Index]If a computer has an IOMEGA Bernoulli PC1600 board in it to support a Bernoulli drive and is not using another SCSI board to support it, upgrading to WARP 4 will seemingly disable the drive. The WARP 4 installation sees the PC1600 board as an Adaptec 152X and adds the appropriate Adaptec suppport lines to the CONFIG.SYS. This has the effect of disabling the Bernoulli. The good news is that there is an easy fix. Simply remove or REM out the Adaptec statement from the CONFIG.SYS and all is well.
Submitted by: Tom Canaday (TCANADAY@IBM.NET>
[Return to the Index]The new Pre-Release of Warp Enhancer (Version 0.20) really solves the Number Lock problem...and provides very useful information.
I run it together with X-File and both work very well. Together they greatly enhance the WPS.
Submitted by: Bill Easley (forensic@internorth.com)
[Return to the Index]I, like others I've seen posting questions, have had problems with the dial-up not working after the first online session in a boot-up. The error usually reads "slattach failed". After much playing around and noting the final message in the first loggout, I concluded that the UNIX slattach function never deactivated when hangup was ordered. To correct this all you need to do is issue the following command:
slattach -pcom? -t4
Where: ? is the comm port being used
-t4 is the timeout in seconds
The default is 60 seconds which is too long for most of us to wait. I created a program item for this, where slattach.exe was the program name and -pcom4 -t4 were the parameters. I then placed a shadow of this in the startup directory and this now loads as my default. No need to re-issue the timeout setting.
Submitted by: Dave Willis (dhwillis@one.net)
[Return to the Index]What you will read below, is the original question to a print problem Nick was having, the suggested solution from Kevin, and the real solution to the problem.
] On Fri, 13 Jun 1997, nick moll wrote: ] ] ] Text: I cannot get the hp deskjet 850 series windows drivers ] ] to see the parallel port (lpt1) in winos2/warp4. The ] ] printer works fine in windows, and in warp4. I have ] ] the irq switch set in config.sys. I had this working once, ] ] but had to do a fresh install of warp and now can't ] ] get it going again. Any tips? ] ] In winos2, set the port to be LPT1.OS2, not LPT1. Also, do NOT use Print ] Manager when in winos2. ] ] Kevin Royalty
Thanks for the tip, but this doesn't work. The answer, which I finally stumpled upon, is far more bizarre.
The HP850 driver requires direct access to LPT1. It is not a 'standard' windows printer driver, and has its own install program, method of running, etc.
It will run nicely in winos2, connected to LPT1, but ONLY IF COM.SYS and VCOM.SYS ARE INSTALLED. These weren't installed in the fresh install referred to above, since I connect to the outside world through a networked modem, and have only the mouse com port enabled.
So the really bizarre thing is this: if the serial port drivers are installed (i.e simply added manually to config.sys) winos2 has direct access to the parallel port; if they are not it doesn't. A bit of a bug, but not a big one. The only thing serious about it is that it is totally undocumented, AFAIK.
Submitted by: Nick Moll (nick@hplnm.hpl.hp.com)
[Return to the Index]Its truly PnP (unlike the AWE32), is cheap ($53 CAN), and has better sound in both audio & MIDI than any CL card I have tried.
And to add icing to your cake...it comes with the OS/2 drivers on a CD (not as recent as Warp 4 drivers tho).
The OS/2 Warp 4.0 Drivers work fine right off the Warp CD also.
The Win 3.1 drivers should not be installed in Warp as they use a driver named ESDAEMON that causes the SYSINST to hang the system. That process needs to be killed for each WinOS2 session.
But the nicest thing is that the Win3.1 utilities which includes a REAL MIXER panel actually work right. Make sure that any of the Win 3.1 apps that are loaded are set to run in Enhanced mode.
The Audio Rack apps work fine though and can be installes using the Setup program in the AudioRack directory of the ESS CD.
The referenced URL has all the drivers one could look for...and sorted correctly.
You can also goto ESS's site and get their drivers.
Submitted by: Bill Easley (forensic@internorth.com)
[Return to the Index]If you install Lotus SmartSuite 96 from a CDROM under WARP 4 as I did it will hang at about 85%. You can load the word processor separately but Freelance Graphics causes the hang. Lotus told me that the cure was to REM out the SET DIRCMD= line in the config.sys, reboot, install, remove the REM and reboot. It worked smoothly on mine and one other machine.
Submitted by: Leroy Latta (latta@ibm.net)
[Return to the Index]IBM has graced us with the best, but relatively hidden utility. If many of you passed on the Device Driver CD that comes with Warp 4.0 then know that we have missed a great gift.
To use the DDPCD you must INSTALL it and then a Desktop icon is created.
For all who have fought through the WinOS2 Sound Card installation...here is the magic answer.
There is a file on the DDPCD named WINSTALL.CMD. This file will use a control file (included or you can create one) that will automatically take the Sound Card drivers for OS/2 and INSTALL them correctly in the WinOS2 session.
Simply (for once this means exactly that) copy the WINSTALL.CMD to your OS2 directory (follow the instructions given on the DDPCD) and the proper n.ctl file to your \OS2\DRIVERS\Sound Card directory.
Then open WINSTALL.CMD from an OS/2 window. It sets all the WinOS2 files up correctly including the Win-OS2 SYSTEM.INI settings.
The Winstall.cmd file is located on the DDPCD in \DRIVERS\WININST.ZIP.
You must use UNZIP to get the WINSTALL.CMD
Submitted by: Bill Easley (forensic@internorth.com)
[Return to the Index]If you use the IOmega Ditto 2GB Tape PP External drive (running under MSR's BackMaster 3.0) and the ESS 1868 Sound Card you will find that the ESS 1868 defaults to using IRQ 7 EXC (Exclusively) which is also the IRQ for LPT1.
MSR recommends adding /IRQ to the BASEDEV=PRINT01.SYS statement in Config.sys. This will not work.
The proper method is to change the ESS1868 Device statement in Config.sys to the following:
DEVICE=C:\MMOS2\ES1868DD.SYS /I:10 /N:ES18681$
This will configure the ESS1868 to use IRQ 10 not IRQ 7 EXC.
The IOmega driver from MSR needs both IRQ 5 & 7 to access the PP tape drive.
IBM uses IRQ polling for finding a useable IRQ for the LPTn port. The /IRQ statement disables the polling, but then messes up the sound card auto configuration...so do not use the /IRQ statement.
This will allow Audio/Midi in OS/2 and provide both printer and PP Tape Backup. The settings used in Win-OS2 System.ini should reflect this as well. My System.ini is as follows:
Note the autodetect is set to NO
[auddrive.drv]
mpu401=yes
essdaemon=yes
ControlRegisterAddressing=FALSE
AudioDrive=ES1868
Synth=OPL3
portchoices=220,230,240,250
irqchoices=5,7,9,10,11,12
dmachoices=0,1,3
port=220
int=10
dmachannel=1
portchoicesMPU401=300,310,320,330
irqchoicesMPU401=5,7,9,10,11,12
portMPU401=330
intMPU401=10
DMAChoicesWave2=0,1,3
DMAChannelWave2=3
AutoConfig=No
VerifyInt=No
VerifyDMA=no
Submitted by: Bill Easley (forensic@internorth.com)
Addendum 15 Oct 97:
MSR has new driver updates out which cure many ills with IRQ's.
Latest is 3.01D and available at MSR's Web Site http://www.msrdev.com/
Submitted by: Bill Easley (forensic@internorth.com)
[Return to the Index]The ESS 1868 is by far one of the most intelligent PnP cards I have seen.
Doing some experimenting with IRQ settings the following was found.
If one changes the IRQ settings in Config.sys then when an Win-OS2 session is started the system automatically updates the Win-OS2 System.ini file settings for the Sound Card section...NICE!
However, when one wants to retain IRQ 7 and 5 for things like Parallel Port tape drives and LPT1 then one must designate both the Audio and MIDI IRQ settings in Config.sys.
Again...Note that the BASEDEV=PRINT01.SYS driver in Config.sys should NOT have the /IRQ addendum added to it else polling will interfere with MSR's BackMaster 3.0 PP driver IRQ allocation...The MSR driver needs IRQ's 5 & 7 to access the PP Tape Drive (IOmega 2GB).
So...if one sets the ESS 1868 SC with the following then both the OS/2 and Win-OS2 sound & MIDI (Madness In Digital Interfacing....you become a MIDIot) work and the PP Tape driver is happy too!
DEVICE=C:\MMOS2\ES1868DD.SYS /B:240 /D:1 /F:3 /I:10 /M:330,11 /N:ES18681$
This is the original line entered by the Installation of the SC under MMOS2:
rem DEVICE=C:\MMOS2\ES1868DD.SYS /B:220 /D:1 /F:3 /I:10 /C:4 /M:300,7 /N:ES18681$
The B: Sets the SC Address; D: the first DMA Channel; F: the Second DMA Channel; I: the first IRQ; M: sets the MIDI Address AND the MIDI IRQ, i.e., Address=330 and IRQ=11.
To check what is being used you can use RMVIEW /IRQ and /DMA from an OS/2 window session, or if your using Warp 4.0 then use the Hardware Manager located in the Desktop Folder OS/2 System. Open the System Setup Folder and then start Hardware Manager. It will display almost all the addresses, IRQ's, and DMA's for you. You can place a Shadow of this in your Warp Center Tray by Right Button Dragging the Hardware Manager Icon into the Warp Center Tray. This will require you to click on the specific system item and then goto the Tab for each Setting. Note: You cannot change the settings from within the properties window.
Now for the possible glitch. If you are using the IDE connection on the SC for your CD-ROM then IRQ 11 is needed for the IDE interface. I do not use the SC IDE interface, but have my CD attached to the Second EIDE port on the Mother board as a SLAVE!. This gives better thru-put.
I have a rather complex system which has 3 EIDE HD's, a Mitsumi CD-ROM, a combo 3.5/5.25 FD, and a SCSI RCD-ROM (Pinnacle Micro 5040i) controlled by an ASUS SC-200 Fast Wide SCSI 2 PCI card. In addition I also have 2 1.08 GB IDE Drives running from the IDE controller of a Digital Processing Systems PAR (Personal Animation Recorder) for video capture and playback at NTSC resolutions.
So much for the claims about OS/2 not being a multi-media OS.
Note: That you can open either .wav or .mid files from either the Audio or MIDI Player in OS/2.
If I can help anyone out there please email me...BUT...make sure you have a usable return email address. I have gotten several emails from folks at IBM and their system does not allow return email...BUMMER!
Submitted by: Bill Easley (forensic@internorth.com)
[Return to the Index]If you disable the Warpcenter/Properties/Monitor/ShowDiskSpace then at boorup, a CD without a valid data disk will return a "sector not found" message causing boot up to halt. This occurs when the Warpcenter is initialised, and is not alleviated by placing the Warpcenter in the Startup Folder or Startup.cmd. The solution is to always leave the W/P/M/S enabled :-(
Submitted by: Dr. Alex. (aledain@receptor.pharm.uwa.edu.au)
Update: 21 Jul 97: Warpcenter Bug workaround
Just check Warpcenter/Properties/Monitor/ShowDiskSpace and let it show selected drives. Then deselect all drives, which should avoid the bug but gives you the results you're asking for: Don't show any DiskSpace!
Submitted by: Peter Franken (peter@pool.informatik.rwth-aachen.de)
[Return to the Index]The Hardware Manager Properties Page should be checked to set the detection level for the HWM. The default is 'Use Previous' However, there are also other settings to choose from including 'Full Detection', 'Removed', 'Added', and 'None'.
The properties page can be accessed by by Right Mouse Button clicking on the HWM icon in either System Settings folder or any shadow of it, such as, WarpCenter (if you have it there).
Submitted by: Bill Easley (forensic@internorth.com)
[Return to the Index]If you have one of the 720 dpi and up Epson printers and are not satisfied with the OMNI drivers color resolution, you DO have an alternative. Novastar Software and Consulting GmbH out of Germany wrote a FREE replacement driver that gives you the resolution and color depth that your printer is designed for! Visit http://www.novastar.de/english.html for more info.
Submitted by: multiple people
[Return to the Index]If you want to load a fixpak, and not have to make diskettes, then this handy tip will make your life easier. Note that this also works for loading fixpaks from removeable media and LAN attached drives/resources.
Note: LOADDSKF.EXE must be in the OS/2 PATH or in the SIMPFIX directory you created above
Submitted by: multiple people
[Return to the Index]An easier way to install a fixpak from hard disk or removable...
Submitted by: Stephen Holden (sdholden@ibm.net)
2 Sep 97: Addendum
I don't know how to unzip a .DSK file, so I installed SVDisk. This still leaves a bit of tedium processing all those .?dk files.
This one liner really helps out at this point.
Run this from the directory where you have the fixpak *.?dk files:
for %i in (*.?dk) do loaddskf %i s: /y && xcopy s:\* x:\fixpak3 /s
Where s: is the SVD drive. loaddskf is assumed to be in the path.
For some reason, Rommel's 'forall' utility does not work properly in this application.
Submitted by: Tim Bridenbecker (tbrier@prefer.net)
[Return to the Index]When using the PMDiary applet ensemble in v2.1 and upgrading to Warp 4, save the \OS2\PMDCTLS.DLL file and add it later to Warp 4 as it will not survive the upgrade. This way, all your appointment records will be preserved through the upgrade, and you can continue to use this applet, or the new PIM which is part of the IBM Works package.
Submitted by: James F. Springfield (jspringf@visi.com)
[Return to the Index]Text: The revised PRINT01.SYS included in Warp FP3 causes printer errors on Canon BJC-610 printers. Re-install the original PRINT01.sys to overcome this until IBM finds a cure.
IBM is aware of the problem and has an APAR in progress.
The problem is inversed printing of some lines within the body of a document.
The line is printed with the bottom half first, then a line feed, and then the top half. This may occur for more than one line.
To re-install the archived file after the FP update simply goto the archive directory you specififed for the backup and UNPACK the file using PRINT01.SY_ to a directory. Then Rename the newer PRINT01.SYS in C:\OS2\BOOT to PRINT01.NEW and copy the original file to the OS2\BOOT directory...re-boot your system.
Note: When renaming the file the system will prompt you about retaining the file's association...click on NO
Submitted by: Bill Easley (forensic@internorth.com)
Addendum: 10 Sep 97
Warp FP3 causes printer errors on Canon BJC-610 & HP 660C printers from native OS/2 applications. I suspect any colour printer which uses the OMNI driver will be affected. Black & white printers using the OMNI driver do not seem to be affected.
The problem is inversed printing of some lines within the body of a document. The line is printed with the bottom half first, then a line feed, and then the top half. This may occur for more than one line.
FP3 has done something interesting to the OS/2 print engine which rasterizes each line of text from the installed fonts.
IBM is aware of the problem and has an APAR in progress.
WORKAROUND:
On the offending printer object go to [properties\Queue options] and check "Printer-specific format". On a network this need only be done on the machine that hosts the printer. This is a slower print technique, but will provide a workable solution until IBM have closed the APAR.
All my children, sorry PC's, are networked and did not respond to the PRINT01.SYS workaround. Perhaps the PRINT01.SYS workaround only works on stand-alone boxes.
On all the clients you will have to delete the offending network printer object and recreate it to reflect the new printer settings.
Submitted by: Daryl Pilkington (darylp@senet.com.au)
Addendum: 11 Sep 97
Neither the back level PRINT01.SYS or setting the print option to be "printer specific" has worked for me. I have determined that the problem seems to be with ATM fonts when printing color. I printed a problem page in Arial (a TrueType font), and the page printed fine. However, switching to a previous version (fixpack 1 or the Warp 4 GA) of PMATM.DLL has not solved the problem for me. The only workarounds that produces readable results are: Set the printer object default job settings to print in greyscale, or to use only TrueType fonts when printing in color.
Submitted by: Ryan Gray (scorpion@thuntek.net)
Addendum: 15 Sep 97
(From IBM) "As a test, you might try backing out PMMERGE.DLL from OS/2 Warp v4 Base and see if the problem still exists."
David Birk (IBM) - OS/2 Electronic Support Team
(Steven) I have unpacked PMMERGE.DLL and this appears to solve the problem. (Confirmed) The working DLL details are 1263097(size), 8/29/96. However, the fact that this did solve the problem certianly suggests a problem with the PMMERGE.DLL in FP3 for Warp4.
Submitted by: Steven van Geldern (svang@ibm.net)
Addendum: 9 Nov 97
This also applies to HP 870 printers, as I have the same exact printing problems with that printer after applying FP3. I hear that FP4 does not solve the problem yet either.
Submitted by: Paul J. Christiansen (pjchris@cpcug.org)
[Return to the Index]If you have been trying to use Ultimedia Mail/2 Lite in Warp 4, and find that the icons stop working after one or a few tries, don't get discouraged--it's probably not your system.
The first thing one thinks of with icon probelms is corrupted INI files, where running CHKDSK and/or remaking the INI files is the standard procedure. But, if your hardware is good, and hooked up right (no IRQ or base address conflicts), and your Warp 4 installation is good, then it is possible you have run into a quirk in Warp 4.
There are two workarounds for this problem:
If necessary, delete both entire folders, the one in the Internet (Modem) folder and the one in the Internet (LAN) folder, reboot, open the Internet (modem) folder, open an OS/2 window, shift to the x:\tcpip\umail directory. and run MAKEWPS.CMD from the command prompt to recreate the folder and all the icons.
THEN, DO NOT CLOSE THE UML FOLDER.
Make a shadow of one of the UML icons, say In-Basket, and either put the shadow on the desktop or in a Warpcenter Tray. Then you can close the UML folder and do whatever you please.
This should provide you with trouble free performance of your UML mail system.
The explanation for the icons becoming inoperative is due to a flaw in Warp 4 as follows:
The WPS/SOM loads most non-essential classes on demand, rather than at startup. When you open a folder, the WPS ensures each object's class is loaded, then "awakens" each object in the folder.
After you close the folder, the WPS puts the objects to "sleep". When SOM finds that no objects of a given class are awake, it unloads that class.
The first time you open your UltiMail Lite folder, the WPS loads IBMUmailWPS and all is well. Some time after you terminate Ulti-Mail itself and close the folder, the class gets unloaded. Once this happens, IBMUmailWPS never gets reloaded during the current session, which is the quirk in Warp 4.
Because the various UML objects now belong to a no-longer-existent class, they revert to a more "primitive" class: LSDataFile when installed or WPDataFile otherwise.
If you *don't* open their notebooks, they'll retain their original ..CLASSINFO extended attribute which identifies them as belonging to IBMUmailWPS. The next time the WPS is willing to load this class, for example a reboot, they'll return to being Ultimail objects. Opening any object's notebook causes its _current_ class to rewrite this EA.
Consequently, the original class identification is lost and the object permanently reverts to LSDataFile or WPDataFile, which is a class for Data objects rather than Program objects, and hence cannot run any executible file.
What makes the problem seem random comes from the way the user operates the UML program. If the user always closed the UML folder after each use of one the programs, the icons would fail after one use. However, if the folder is left open throughout the day, and the user checks for mail five times during the day before closing the folder, then the user would get five uses instead of the one. Or if the user had to reboot during the day for some reason, restoring the objects, the icons would work again--perhaps even unnoticed.
We hope this helps everyone. Now, our Ultimail works perfectly, and yours can too!
James F. Springfield Richard L. Walsh Plymouth, MN Ft Myers, FL jspringf@visi.com rlwalsh@packet.net
Submitted by: James F. Springfield (jspringf@visi.com) and Richard L. Walsh (rlwalsh@packet.net)
[Return to the Index]The standard support for PCMCIA modems on Warp 4 attampts to put them on COM1: or COM2: using the standard I/O addresses and IRQs. On my ThinkPad 365XD, the serial port and IRDA port take up both those slots, so when I attempted to get my PCMCIA modem to work, it would not come ready, since the available I/O addresses and IRQs were already in use. My first bypass was to disable the IRDA port, and modify the COM.SYS driver to only take COM1:. This did work, but at the expense of not having the IRDA available.
After asking on usenet, some kind soul told me about AUTOUTL2. There are several AUTOUTL2 files in \OS2. If you issue VIEW \OS2\AUTOUTL2.HLP, you will see the documentation. AUTOUTL2.EXE presents a list of defined cards (they are in \OS2\SCR\ in flat text format) for you to select and edit. There is already a card defined for the COM3 I/O addresses, but it normally presents only the default IRQs for COM1: and COM2:.
In order to use COM3:, I reconfigured the sound support on my ThinkPad 365XD to use IRQs 10 and 11, freeing up IRQ5. The following statement in CONFIG.SYS reconfigured the sound support:
DEVICE=D:\MMOS2\ES1688DD.SYS /B:220 /D:1 /I:10 /C:4 /M:330,11 /N:ES16881$
I then edited the .scr file for MODEM 3E8 (OS2\SCR\MODEM_3.SCR) and added 5 to the val.irq line. I then issued AUTOUTL2 and selected the card for COM3: (labeled MODEM 3E8) and edited the IRQ to 5. I believe you might be able to just type in 5 in the IRQ window, but I have not tried it this way. When you save, the AUTODRV2.SYS is rewritten with new information. After you reboot, your modem will be recognized at COM3, IRQ 5.
This procedure could be used to allow different configurations for other PCMCIA cards too, though I have never tried it.
Submitted by: E. Glenn Huff (eghuff@flash.net)
[Return to the Index]For anyone looking for great removable storage under Warp try the Syquest Syjet 1.5gig drive, I just recently bought one and it really works great using both Warp 4 and Warp Server Advanced.
You will need to install the device drivers for removable media, NEWDASD.EXE, but other than that its plug and play.
The drive is SCSI, I bought the parallel port version which is SCSI, but comes with a SCSI to parallel port adapter. (Note: There is also an EIDE version available)
I am using it for system backup with Back Again 2 Pro, I have offloaded all my image files, utils, and other things that I don't need all the time. With the 2940 the drive works great as a boot device. I used Partition Magic from Power Quest and created several bootable partitions on a cartridge. I removed Windows 3.11 partiton from my system and put it on a cartridge as well as installed a Win95 Partition on a cartridge for testing. I am also setting up a cartridge with a bootable partition with Warp 4 so I can test Beta programs and new apps without having to load them on my daily use partition until I know I like them. It works great with the boot manager as well, If I have a cartridge with a bootable partition in the drive when I boot my system it shows up on the boot manager screen, otherwise I just get the option for Warp 4.
Sorry to carry on so much, but its really rare to find a product that works as well as this esp under Warp. If your in the market for removable storage check this thing out. I've finally bought my last hard drive.
Submitted by: Gorodn Owens (email address withheld at submitters request)
[Return to the Index]If you need Joliet CD format support and you have a current FP (like 4 or 5 for Warp 4 or equivalent on Warp 3) installed, just add /W to the CDFS.IFS entry in your Config.sys.
This will look eg. like
IFS=E:\OS2\BOOT\CDFS.IFS /Q /W
After the next reboot you won't see the short names with "~" but the real long ones.
More information can be taken from the Readme file of the Beta-Version of CDFS.IFS, which can be found at the OS2DDPAK site.
BTW: Don't install that OS2DDPAK file over a new FP. The CDFS.IFS of the FP is newer and do the job!
Submitted by: Peter Franken (peter@pool.informatik.rwth-aachen.de)
[Return to the Index]