Path: utzoo!attcan!uunet!cs.utexas.edu!sdd.hp.com!usc!apple!portal!cup.portal.com!Carra_its-me_Bussa From: Carra_its-me_Bussa@cup.portal.com Newsgroups: comp.windows.ms Subject: Re: Real Mode Windows under 386 Enhanced Mode and SHARE Message-ID: <31979@cup.portal.com> Date: 22 Jul 90 06:18:26 GMT References: <1990Jul12.041057.6055@sbcs.sunysb.edu> Distribution: na Organization: The Portal System (TM) Lines: 31 > I have the same setup with a 122meg drive. I have had the same experience. > I did find out that SHARE is the reason you are getting the error. Both > Windows are trying to open the same files. I don't know if you absolutely > have to have SHARE loaded, but if you don't you get a message at boot time > that claims that you need SHARE with >32 meg partitions. > Hope this helps a little. > > Mark R. Gibaldi > AT&T Bell Laboratories > mrg@cblph.att.com Apparently, SHARE is there to prevent old (v1.0) programs from opening files using FCBs. There is a problem when an FCB nears the 32 Meg boundary...your FAT table dies. (At least, that's what I've heard.) Someone has written a NOSHARE.exe program, 1K in size, that simply denies all FCB opens. See the IBM binary group for NOSHARE.UUE, or write to me and I'll ship. [extracted from the noshare.doc file....] > From: toma@tekgvs.LABS.TEK.COM (Tom Almy) > 2. Not run SHARE.EXE and get your disk corrupted by lingering old programs > that do DOS 1 ("CP/M") style file accessing? > > Well I had enough of this, and was seriously contemplating going back to > DOS 3.3 when I got the great idea of writing NOSHARE.COM. > > This tiny TSR simply returns the "failed" code to any program which tries > to open a file using functions 0FH or 16H.