Re: Network Drive Issue

Tech-Archive recommends: Speed Up your PC by fixing your registry

"Gary Chanson" <gjchanson@xxxxxxxxxxxxxxxxxxxx> wrote in message

> This sounds like a hard drive problem. Your drive probably
> has one or more marginal sectors which take many retries to
> read or possibly fail altogether.

I consider this too. Trust me. I ran CHKSDK on drive G:

If that was the case, then it wouldn't matter whether it was a mapped
drive or not. However, as I said, there is no problem when accessing
the logical drive G: directly. The problem is only with the MAPPED
drive S: to G$

net use s: \\local_machine\g$

and the only time the problem appears is when loading VS 6.0 projects
which are not stored on drive s: (or g:)

When it happens, any ACCESS to drive S: is locked. Even a normal drive
switch or a API GetDiskFreeSpaceEx() call to drive "S:\\" is locked.

However, when this LOCK is active, I can go to drive G: directly and do
what I please

The only link to drive G: when it comes to VS 6.0 that I can think of is
the VS 2005 installation on drive G:.

Here is my NDIR listing again:

d:\wc5beta>ndir
ndir v3.0 (c) copyright 1984-2006 Hector Santos
-- ---------- ------------- ------------- -------------
#: Type Total Free Used
-- ---------- ------------- ------------- -------------
C: FIXED 2,146 MB 821 MB 1,325 MB
D: FIXED 11,572 MB 2,464 MB 9,108 MB
E: FIXED 6,292 MB 2,215 MB 4,077 MB
F: FIXED 2,006 MB 1,797 MB 209 MB
G: FIXED 50,675 MB 15,387 MB 35,288 MB **
H: FIXED 27,340 MB 23,889 MB 3,450 MB
I: REMOVABLE 250 MB 181 MB 68 MB
J: REMOTE 27,340 MB 23,889 MB 3,450 MB
K: REMOTE 27,340 MB 23,889 MB 3,450 MB
M: FIXED 42,952 MB 41,275 MB 1,676 MB
N: FIXED 38,535 MB 38,466 MB 68 MB
O: FIXED 38,543 MB 38,474 MB 68 MB
S: REMOTE 50,675 MB 15,387 MB 35,288 MB **
T: REMOTE 50,675 MB 15,387 MB 35,288 MB **
U: REMOTE 11,572 MB 2,464 MB 9,108 MB
V: REMOTE 11,572 MB 2,464 MB 9,108 MB
W: REMOTE 50,675 MB 15,387 MB 35,288 MB
Z: REMOTE 50,675 MB 15,387 MB 35,288 MB
-- ---------- ------------- ------------- -------------
Available Drive Letters: LPQXY

Drive S: and T: are mapped to \\local_machine\g$

I would think that if this was hard drive sector issue, then accessing
it from either drive, especially G:, would be a problem. Correct?

Trust me. I wouldn't bother with such trivial nonsense if I felt it was
a hard drive issue. Again, it has only occurred (when it does happen)
when loading a VS 6.0 projects.

When it is locked, I can do whatever I want via drive G:, but not drive
S:

If the hard ware was "locked" due to some marginal sector retry, then I
would think that accessing the drive via G: would be locked as well. It
wouldn't matter. This was the first thing I checked once I saw it was
locking on the mapped drive.

I'm thinking VS 2005 installed some IDE device driver that is now used
by VS 6.0, maybe the Machine Debugger, and when it loads the problem, it
is doing some network resource lookups and attempting to some TCP/IP
socket layer connection to the outside world - ala some "Spyware" logic
that MS has yet to admit to and its ever growing attempt to network the
world with "net services."

I'm thinking there is a BUG in this logic.

In regards to Intellisense, check out the thread in
microsoft.public.vc.ide_general, titled:

VS2005 - Disable automatic IntelliSense updating?

I am thinking Microsoft has now interfered with VS 6.0 installations
with replacements of OS dlls and/or device drives or the machine
debugger.

--
Hector Santos, Santronics Software, Inc.
http://www.santronics.com

.

Relevant Pages

  • Re: XP product ID on trashed HDD
    ... Odds are the technician had a copy of an HP OEM CD with the ... You're right that the installation key on the failed hard ... Ultimate Boot CD for Windows ... drives are jumpered correctly. ...
    (microsoft.public.windowsxp.configuration_manage)
  • Re: Disk partitioning size
    ... Your Installation Specialist ... Disk Read Error Press Ctl+Alt+Del to Restart ... large drives and none of them are failing because of problems ... XP installations on large hard drives filed to near capacity ...
    (microsoft.public.windowsxp.general)
  • Re: Disk partitioning size
    ... Disk Defragmenter analysis showed no files or clusters in use ... Your Installation Specialist ... John John wrote: ... large drives and none of them are failing because of problems ...
    (microsoft.public.windowsxp.general)
  • Re: Disk partitioning size
    ... Copied from DVD to new folders bunch of files. ... Disk Defragmenter analysis showed no files or clusters in use ... Your Installation Specialist ... large drives and none of them are failing because of problems ...
    (microsoft.public.windowsxp.general)
  • Re: Disk partitioning size
    ... that out copy that file back onto the HD while windows is running. ... Your Installation Specialist ... Disk Read Error Press Ctl+Alt+Del to Restart ... large drives and none of them are failing because of problems ...
    (microsoft.public.windowsxp.general)