SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Tue, 8 Oct 2002 09:26:09 PST7
From:	waynec@linkline.com
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: MS Word stopped working...???

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Michael Rakijas writes:

>
> Friday September 27 1996 02:23, Peter Arnold wrote to All:
>
> PA> I also are having the same problem. I have a OS/2 Warp Ver3 DOS session
> PA> where
> PA> I run a application that opens a *.dbf file. This application allows other
> PA> applications to access the dbf file if 'SHARE.EXE' is loaded. I have
> PA> included share in the autoexec.bat file but get the error 'Incorrect DOS
> PA> version' when loading it. I am using dos 6.20. In the DOS Settings
> PA> DOS_VERSION I have entered SHARE.EXE,6,20,255 but still get the error.
> PA> Does anyone give me a fix for this?
>
> I solved such a problem a while ago by loading a dummy share.exe.
> I can't remember what the filename was, but I got it from Hobbes or CDROM.
> It's a little program that loads itself in mem (like the real share), but it
> doesn't do anything, it just sits there. Normal DOS/windoze programs look in
> mem. for a program called share.exe and they find it.
> The functions of share are handled by OS/2.
> I'd like to suggest you take a look in /network/* dir, and maybe the utils or
> sysutils dir.
> You have a good chance it's called share.zip. ;)
>
> I'm not sure it'll work, because you're not using the same apps as the person I
> helped did, but you can always try.

I appreciate the reply.

I still have the problem, and I was not able to find the share.exe program
on shareware sites. I did find the following at the Microsoft website,
although it didn't work:

Just searched the only Win95 OSR2 cdrom I have (contained win95_02.cab to
win95_28.cab) using extract, but share.exe was not found.

Then I went to Microsoft's tech database and searched on share.exe, found
this:

****

Share.exe Is Not Supported in Windows 95 OSR2, Windows 98 or Windows Me

The information in this article applies to:

Microsoft Windows 98
Microsoft Windows Millennium Edition
Microsoft Windows 95 OEM Service Release 2
Microsoft Windows 95 OEM Service Release 2.1
Microsoft Windows 95 OEM Service Release 2.5

Summary

The Share.exe tool is not included with Windows 95 OEM Service Release 2
(OSR2), Windows 98 or Windows Me.
File sharing and locking capabilities are provided by APIs in IFSManager and
are not supported in MS-DOSmode. You may not be able to install or run some
MS-DOS-based programs or 16-bit Windows-based programs
that require Share.exe in OSR2, Windows 98 or Windows Me.
More Information: In earlier versions of Windows, Share.exe is used only in
real-mode MS-DOS. In order to support the FAT32 file
system, Share.exe support has been disabled in the real-mode MS-DOS kernel
regardless of whether or not you have any drives using the FAT32 file
system.

Some programs look for a file named Share.exe in either the root folder or
the DOS folder. This file can be azero-byte file created with a text editor
(such as Notepad). Other programs may simply look for the string
"share" in the Autoexec.bat file.

****

Aparently share.exe is not really needed, but may need to simply exist in
order to satisfy some older programs that look for it (like Word?).

I do have a zero-length share.exe file in the C: root, it was there when I
started having the problem. I had renamed it and copied
D:\os2\system\share.exe into C: root as a test, but that didn't help. I have
now changed it back to the way it was.

Word (under Warp using OfficePro 4.3) is still not working. Wonder if it has
something to do with FAT32, which is the format I tried to change the C:
partition to at one point in all my finagling while trying to increase the
size of C: partition. After more use of PQMagic, C: supposedly is now FAT
with a 32k cluster size, and everything I've tried under Win95 is working,
including a later version of OfficePro, but there are still chkdsk and
scandisk errors.

Scandisk run under the standalone PQMagic rel7 DR Dos diskette says there is
a too-long path or filename, but does not give me the name of the file, it
just says to run scandisk under windows to fix the problem. But, scandisk
under Windows95 will not run to completion, it keeps starting over from
scratch after a running a few minutes, saying another progam is altering the
disk. No other programs are started, so far as I know, and I even moved the
swapfile to another partition, to no avail.

Chkdsk, run under the PQMagic standalone diskette, reports invalid
cluster(s) in nearly every file... yet, as I said, Win95 (and application
programs) seems to be working fine.

I've tried putting the zero-length share.exe file in other folders
accessible to Word at startup time, but nothing changed. I even re-installed
OfficePro 4.3, but it still says I have to "exit Windows and load SHARE.EXE
in order to run Word".

I am beginning to wonder if Word somehow requires the share.exe program to
be installed in a C: FAT partition with a 16k cluster size.... which I
cannot do because there is not enough room in a FAT partition w/16k clusters
(it is limited to 1mb). I may experiment by hiding the Win95 partition and
creating a small C: partion with FAT and 16k clusters and putting share.exe
in that partition.

Wayne

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 08 | October | 2002 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.