Annoyances.org
Home » Windows XP Discussion Forum » Message 1255580030 » Entire Thread Search | Help | Home
  
How to make a mapped drive consistently connected?
Showing all messages in thread #1255580030
Windows XP Annoyances Discussion Forum


The following are all of the messages in this thread (5 in all), shown in chronological order. Click any message subject to view that message by itself or to view the thread hierarchy.
How to make a mapped drive consistently connected?
Wednesday, October 14, 2009 at 9:13 pm
Posted by Francis (19 messages posted)

Hi guys, i have a mapped drive and i wanted this mapped drive to be connected consistently without losing connection. Is it possible? Can i have a script which will run every 30 mins to login to the mapped drive, just to keep it alive? Looking forward to all the advices. Thanks.

[Reply or follow-up to this message]

Tip: Run a free scan for common Windows errors ad

re: How to make a mapped drive consistently connected?
Thursday, October 15, 2009 at 6:59 am
Posted by MartinM (7551 messages posted)

You shouldn't be losing this mapping in the first place, if the drive is still there and accessible ! Mappings normally persist through all sorts of events, including re-booting the host device. Can you describe how you set this up, and the circumstances where you are finding a re-map necessary ?

[Reply or follow-up to this message]

re: How to make a mapped drive consistently connected?
Thursday, October 15, 2009 at 10:36 am
Posted by Francis (19 messages posted)

As i have a program that is constantly writing to some files in this mapped drive. But whenever there is an intermittent lost of network connectivity, the mapped drive may have lost the connection although the mapped drive still exist. And the files at this mapped drive may get corrupted when this happens. So i wanted to make sure that i constantly have the network connection to this mapped drive. Even when the network is intermittent, i am able to re-establish back the mapped drive connection when the network is back. Is it possible? Thanks.


On Thursday, October 15, 2009 at 6:59 am, MartinM wrote:
>


>You shouldn't be losing this mapping in the first place, if the drive is still there
>and accessible ! Mappings normally persist through all sorts of events, including
>re-booting the host device.
>
>Can you describe how you set this up, and the circumstances where you are finding
>a re-map necessary ?
>

[Reply or follow-up to this message]

re: How to make a mapped drive consistently connected?
Thursday, October 15, 2009 at 3:44 pm
Posted by MartinM (7551 messages posted)

Not really possible in the way you want. Once the connection is interrupted and the transfer interrupted, re-establishing the connection is not going to uncorrupt (if there is such a verb !) your files. The flaw in the setup you have is in the transfer mechanism which is not resilient enough to what it is having to cope with. You need the equivalent of a download manager, but its the applications which are driving the transfer which you need to be changing. That of course may be impossible. But the underlying issue is really one of the design of your application architecture. For instance why not have the program write to a local drive and then use a separate process to copy to your network drive - then you can re-copy if the oringianl copy process fails through interruption ?

[Reply or follow-up to this message]

re: How to make a mapped drive consistently connected?
Thursday, October 15, 2009 at 6:14 pm
Posted by Francis (19 messages posted)

yes, i agree with you. Thanks alot for the advice.


On Thursday, October 15, 2009 at 3:44 pm, MartinM wrote:
>


>Not really possible in the way you want.
>
>Once the connection is interrupted and the transfer interrupted, re-establishing
>the connection is not going to uncorrupt (if there is such a verb !) your files.
>
>The flaw in the setup you have is in the transfer mechanism which is not resilient
>enough to what it is having to cope with. You need the equivalent of a download manager,
>but its the applications which are driving the transfer which you need to be changing.
>That of course may be impossible.
>
>But the underlying issue is really one of the design of your application architecture.
>For instance why not have the program write to a local drive and then use a separate
>process to copy to your network drive - then you can re-copy if the oringianl copy
>process fails through interruption ?
>

[Reply or follow-up to this message]

Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread
Return to the Windows XP Discussion Forum


All content at Annoyances.org is Copyright ©1995-2012 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.