Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!helios!aim1!jlr1801 From: jlr1801@aim1.tamu.edu (Jeff Rife) Newsgroups: comp.windows.ms Subject: Re: Sharing violation in a DOS Window Message-ID: <13610@helios.TAMU.EDU> Date: 22 Mar 91 05:07:06 GMT References: <1991Mar21.004309.28940@zeus.mgmt.purdue.edu> Sender: usenet@helios.TAMU.EDU Organization: City of College Station, Texas Lines: 36 In article <1991Mar21.004309.28940@zeus.mgmt.purdue.edu> landers@zeus.mgmt.purdue.edu (Chris Landers) writes: >Running in 386 mode (9mb memory), I opened Norton Commander in a window, >then wanted to use pkunpak to test an archive. After pkunpak started >testing the archive, DOS 4.01 interrupted with > Sharing Violation reading drive A: > >Windows and pkunpak are on c:, the archive is on (subst) e: and I hadn't >accessed a: since rebooting. I tried the same again with the same result. >Share was not explicitly loaded. > >Any suggestions? > >Also, can someone please post just what Share is supposed to do; the >discriptions in DOS manuals indicate that Share does nothing >unless you are networked, but I've heard people say otherwise. > SHARE, SUBST, and Windows in 386 enhanced mode don't get along. Get rid of one of them. I had to get rid of SHARE, and am praying that nothing mucks up my disk drive. There was a long thread on SHARE, but it boils down to this: SHARE protects you from having two processes write to the same file and destroy data. It also (in DOS 4.0 and up) has the code to support > 32 MB drives for programs that use FCB's (File Control Blocks), a DOS 2.0 and earlier method for accessing files. dBase III+ is an example of a program that uses FCB's. Let's put this SHARE explanation into the FAQ, ok? -- Jeff Rife P.O. Box 3836 | "Because he was human; because he had goodness; College Station, TX 77844 | because he was moral they called him insane. (409) 823-2710 | Delusions of grandeur; visons of splendor; jlr1801@aim1.tamu.edu | A manic-depressive, he walks in the rain."