home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 17 Fixes30
/
17-Fixes30.zip
/
sharefix.zip
/
SHAREFIX.DOC
< prev
Wrap
Text File
|
1995-01-04
|
5KB
|
94 lines
╔═══════════════════════════════════════════════════════════════════╗
║ SHAREFIX.COM - A workaround for OS/2 Warp's SHARE detection bug ║
╚═══════════════════════╤═══════════════╤═══════════════════════════╝
│ Version 0.1 │
╘═══════════════╛
This TSR was developed to act as a temporary workaround for use
with programs running under OS/2 Warp that are failing because
they are unable to initialize the SHARE environment. (The programs
do not think SHARE is loaded).
Unlike MS-DOS, OS/2's DOS emulation does not need an external
program (SHARE.EXE) to enable file sharing support. This support
is totally integrated into OS/2, thus SHARE.EXE is not needed.
The main thing to remember is that there is no need to enable this
support under OS/2. File sharing support is ALWAYS there. You can't
"turn it off".
There is a SHARE check that certain programs use that IBM "broke"
when developing Warp. PLEASE NOTE that file sharing itself under
OS/2 Warp is NOT broken. It's actually a certain way that some
programs check for the existence of SHARE that is not functioning
properly.
In a nutshell, certain programs check for the existence of SHARE
by attempting to set the number of retries SHARE does on a locked
file. This function call under DOS returns successful if SHARE is
loaded, and since OS/2 Warp ALWAYS has file sharing enabled, it
should return successful under OS/2 as well. Up until Warp, it
did. With OS/2 Warp, this function call returns unsuccessful
when it SHOULD be returning successful. And that's where the
problem comes in. Programs that are set to use DOS Share fail
because this call is not working properly under OS/2 Warp 3.0.
SHAREFIX.COM remedies this problem. It actually intercepts the
unsuccessful error that WARP produces and returns it to programs
as being successful. Thus programs that check for the existence
of SHARE by the locked file retry method described above will now
work properly.
To use SHAREFIX, simply type SHAREFIX in an OS/2 DOS session, or
load SHAREFIX in your AUTOEXEC for your DOS session(s). There
are no command-line parameters. Once loaded it will intercept
the unsuccessful SHARE function call and return it as successful.
This program, when installed, installs itself as SHARE, not
SHAREFIX. Thus any programs that check for share by actually
looking for SHARE physically loaded should work properly as well.
Typing mem /c at a DOS prompt will show that SHARE is loaded.
(It really is SHAREFIX, but we'll make that our little secret) :)
IMPORTANT NOTE: This is designed only as a TEMPORARY WORKAROUND
until either IBM releases a fix, or programs begin to use a
different SHARE detection routine. This TSR should ONLY be used
if you are experiencing problems with programs that are failing
when checking for the existence of SHARE. Once IBM releases a
fix (it is a known problem), and/or programs have begun to
use a different routing for detecting SHARE, this program no
longer needs to be used.
This program is public domain, and may be freely distributed.
Disclaimer
──────────
THIS PROGRAM IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. THE
ENTIRE RISK AS TO THE RESULTS AND PERFORMANCE OF THE PROGRAM IS ASSUMED
BY YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE ENTIRE COST
OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. FURTHER, THERE IS NO
WARRANTY, GUARANTEE, NOR REPRESENTATION REGARDING THE USE OF, OR THE
RESULTS OF THE USE OF THE PROGRAM IN TERMS OF CORRECTNESS, ACCURACY,
RELIABILITY, CURRENTNESS, OR OTHERWISE; AND YOU RELY ON THE PROGRAM
AND RESULTS SOLELY AT YOUR OWN RISK. NO PERSON OR ORGANIZATION WILL
BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SYSTEM DAMAGE,
SERVICE, REPAIR, CORRECTION, LOSS OF PROFIT, LOST SAVINGS, OR ANY OTHER
INCIDENTAL, CONSEQUENTIAL, OR SPECIAL DAMAGES OF ANY NATURE WHATSOEVER
RESULTING FROM THE USE OR INABILITY TO USE THIS PRODUCT.
Technical Information
─────────────────────
When loaded, this TSR will force the INT 21h ax=440b (set retry count)
function to always return success. Although I don't particularly like
this method of working around this problem, "when all else fails...".
Additionally, it will modify it's own MCB so that it contains the
the name "SHARE", just for those programs that are picky.
Use at your own risk. This program is specifically for OS/2 VDMs.
╒══════════════════╤═════════════════════════════════════════════════
│ Revision History │
╘══════════════════╛
0.1 (01-04-95) Initial Release.