Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!sdd.hp.com!caen!hellgate.utah.edu!dog.ee.lbl.gov!nosc!manta!north From: north@manta.NOSC.MIL (Mark H. North) Newsgroups: comp.os.msdos.misc Subject: Re: Thanks and another question about DOS 4.01 Message-ID: <1954@manta.NOSC.MIL> Date: 2 May 91 00:06:34 GMT References: <1991Apr24.193839.22130@leland.Stanford.EDU> <9397@sail.LABS.TEK.COM> Organization: Naval Ocean Systems Center, San Diego Lines: 29 In article <9397@sail.LABS.TEK.COM> toma@sail.LABS.TEK.COM (Tom Almy) writes: >In article <1991Apr24.193839.22130@leland.Stanford.EDU> garygm@leland.Stanford.EDU (Gary Brainin) writes: >> Anyway, 4.01 is up and running just fine now, except for one thing: >>every time I boot up it tells me that I should be using SHARE.EXE with >>'large media' (my hard drive is 85 meg. or so). [...] What purpose does >>share.exe serve wrt my hard drive? I've seen replacements for share.exe (the >>3-line notshare.com comes to mind) - why are these better > >(The author of "noshare.com", the original replacement for share, speaks:) > >Well they are different, not necessarily better. > >The problem occurs when writing to a file using FCBs (an obsolete technique >discouraged by Microsoft), when the file is more than 32 megabytes displaced >into the drive. The disk gets corrupted. SHARE.EXE maps the FCB calls into >acceptable "handle" calls, allowing the old application to run. > >The problem with this is two fold: Share takes valuable memory, and some >programs refuse to run if it is loaded (the primary purpose of share is >to maintain file sharing in network applications). > >NOSHARE (and the NOTSHARE reverse-engineered rewrite -- it's even smaller >because it frees the environment segment) take a different tact. When a ^^^^> I think you mean tack. Anyway, if you're the Tom Almy who invented CapsLock --> Cntrl I'm sure you know what you're talking about it's the best thing since sliced bread. Where can I send a contribution? Mark