Sharing Violation Reading Drive C:
Dave Mueller
Reading Drive C:" error messages. It seems to be getting worse.
There is nothing special about my hardware. It's a Gateway2000 486/33mhz,
250meg hard drive (whatever brand it normally is). It's all one big
partition. We do run some fairly disk intensive programs on it (accounting
software), but I rarely get a message using it. It seems to always come
when I want to delete a file(s). If I answer 'F'ail to the message the
command quits normally (does what it should have).
Once in awhile (when I'm having the problem), the disk really slows down.
I was also told by a support person (over the phone) that it seems like a
system this fast was installing their software very very slowly.
Following is a copy of the autoexec.bat & config.sys. Any help you can give
me would be very appreciated. If I can't get this solved, I'm gonna format
the drive and reinstall everything. Hopefully that works. Oh ya! I'm using
MS-DOS 5.0.
Thanx!
[config.sys]
install=c:\dos\share.exe /f:4096 /l:750
buffers=4
device=c:\windows\himem.sys
dos=high
stacks=9,256
files=40
device=c:\dos\setver.exe
[autoexec.bat]
set temp=c:\temp
c:\dos\smartdrve c /q
c:\dos\fastopen c: 30
c:\vga\vgamode 72 60non-interlace
set fxconf88=c:\fx
set ofc_adv=c:\fastdata
break=on
set workstation=1
prompt $p$g
c:\msmouse\mouse
mirror c: /tc
That's it!
Rick Troha
Dave,
That "sharing violation" message comes from share.exe, which
you are loading in your config.sys. Unless you have a specific
program that requires that it be loaded, delete the "install=
share..." line from your config.sys.
Also, I notice you have both Smartdrv and Fastopen loading
in your autoexec.bat. This is a not recommended. Get rid of
Fastopen.
I notice you are not using upper memory blocks. You'd have a
lot more conventional memory available for your applications
if you loaded some of your drivers into UMB's.
Rick Troha
ci...@cleveland.freenet.edu
Leonard Erickson
>[config.sys]
>install=c:\dos\share.exe /f:4096 /l:750
>buffers=4
That's *way* too few buffers! Try raising this to 20 or 30.
>device=c:\windows\himem.sys
>dos=high
>stacks=9,256
>files=40
>device=c:\dos\setver.exe
>[autoexec.bat]
>set temp=c:\temp
>c:\dos\smartdrve c /q
>c:\dos\fastopen c: 30
Fastopen is *notorius* for causing problems. Usae a real disk cache
program instead.
See if the above make any difference.
--
Leonard Erickson leo...@qiclab.scn.rain.com
FIDO: 1:105/51 Leonard....@f51.n105.z1.fidonet.org (preferred)
jb...@mswe.dnet.ms.philips.nl
> BJ02...@NDSUVM1.BITNET (Dave Mueller) writes:
>
>>[config.sys]
>>install=c:\dos\share.exe /f:4096 /l:750
>>buffers=4
>
> That's *way* too few buffers! Try raising this to 20 or 30.
>
Without smartdrv 20 to 30 is a good range
>>device=c:\windows\himem.sys
>>dos=high
>>stacks=9,256
>>files=40
>>device=c:\dos\setver.exe
>
>
>>[autoexec.bat]
>>set temp=c:\temp
>>c:\dos\smartdrve c /q
>>c:\dos\fastopen c: 30
>
> Fastopen is *notorius* for causing problems. Usae a real disk cache
> program instead.
>
> See if the above make any difference.
> --
> Leonard Erickson leo...@qiclab.scn.rain.com
> FIDO: 1:105/51 Leonard....@f51.n105.z1.fidonet.org (preferred)
Vinc Duran
As far as buffers are concerned, if you're using DOS=HIGH you can use
about 30 buffers without using any more memory.
On the "Sharing Violation Reading Drive C:" issue I get that occasionally
but only when I use Share. I "think" Share is required for OLE 2 to
function too.
Vinc
Leonard Erickson
>In article <1993Aug25....@qiclab.scn.rain.com>, leo...@qiclab.scn.rain.com (Leonard Erickson) writes:
>> Fastopen is *notorius* for causing problems. Usae a real disk cache
>> program instead.
>It *is* notorious, but it's *not* a disk cache...
I never said it was. But what it *attempts* to do is better done by a disk
cache.
Ted Schulze
: For the past few months I've been getting a lot of "Sharing Violation
: Reading Drive C:" error messages. It seems to be getting worse.
: [autoexec.bat]
: set temp=c:\temp
: c:\dos\smartdrve c /q
: c:\dos\fastopen c: 30
Microsoft has at tech memo out that states that smartdrve and fastopen
should not be used together. They both try to do some of the same things
but in different way. If you can access Microsoft Knowledgebase on
Compuserve or other source, search for SMARTDRV AND FASTOPEN to find the
memo.
Ted
--
Ted Schulze tsch...@netcom.com
Livermore, CA