Suppressing "Network Path Was Not Found" Message

  • Thread starter Thread starter TC
  • Start date Start date
T

TC

I have two computers networked together. When I turn on one computer only, I
get an error message saying "The Network Path Was Not Found" during boot-up.
The computer won't finish booting until I hit OK. This is very annoying. Is
there any way I can tell Windows to connect if possible, but not to bother
me with a message if it can't connect?

-TC
 
TC wrote in
I have two computers networked together. When I turn on one
computer only, I get an error message saying "The Network Path Was
Not Found" during boot-up. The computer won't finish booting until
I hit OK. This is very annoying. Is there any way I can tell
Windows to connect if possible, but not to bother me with a
message if it can't connect?

You need to find the cause and remove it. Possibly a persistent
connection to a (unavailable) remote resource.

OS?
When do you see the message?
 
TC said:
Mark,

I didn't explain my question well. There is no mystery why the error comes
up. I have a persistent connection to an unreliable resource. Therefore, I
frequently get an error during the boot sequence.

I want to instruct my computer to make the connection if the resource is
available and to drop the connection if the resource is unavailable, but
under no circumstances should it bother me with an error message. The error
message does nothing for me except delay the boot procedure. Is there any
way to suppress it?


-TC

You can use the following approach if you embed your connection
command inside a batch file:

@echo off
ping SomePC -n 1 | find /i "bytes=">nul && net use x: \\SomePC\SomeShare

If SomePC is not available then your PC will not attempt to make
a connection to it.
 
TC wrote in
Mark,

I didn't explain my question well. There is no mystery why the
error comes up. I have a persistent connection to an unreliable
resource. Therefore, I frequently get an error during the boot
sequence.

I want to instruct my computer to make the connection if the
resource is available and to drop the connection if the resource
is unavailable, but under no circumstances should it bother me
with an error message. The error message does nothing for me
except delay the boot procedure. Is there any way to suppress it?

Not that I know of. Perhaps there is a way unknown to me.
Personally I'd do something like "Pegasus" suggests. You also could
just do a NET USE and test the errorlevel, then branch, from a batch
as well.
 
Back
Top