General discussion


Mapping a Local Folder to a network drive

By dave ·
Map a local folder to a network drive as in....

S: is the network drive on a server.
C:\server is the folder I want the S: drive mapped to, so as when you click on c:\server you will see the contents of S:

This is due to the fact that my company has a program that was written back in 19** that uses btrieve as a base. Unfortunately this system has all of the folder calls hard-wired in so it looks for the C:\Server folder on the server drive. The old system used 10base2 and boot roms to connect to the Server using lantastic as the server so the remote computers booted using the server's c: drive as thier own.

Yesterday I gathered the server folder and moved it to the drive on the new server and when I tried to run the program I got a "Can not find c:\server\programX" I was shocked.

Any help would be great.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Mapping a Local Folder to a network drive

by richard In reply to Mapping a Local Folder to ...

There is a number of ways that this can be done however the easier way would be to create c:\server as a shortcut to the s: drive. For this you will need to the know the server name and folder path (it will look something life \\servername\folderpath). Then all you need to do is create a shortcut under the c: drive to the \\servername\folderpath and call this shortcut server

Collapse -

i tried that

by dave In reply to Mapping a Local Folder to ...

I tried that but at a command prompt it does not see the shortcut as a folder...keep in mind the program i am trying to run is a dos based program so I have to be able to see the S: drive from doing a "DIR c:\server" at a command prompt. This is very easy to do in Linux/UNIX but using the Micro$oft mountvol command, will not allow me to map virtual drives to folders.

Collapse -

Ugly Possibility

by CharlieSpencer In reply to Mapping a Local Folder to ...

The trick is to get your client operating system on a drive other than C:. If you can boot the OS from , then C: becomes available at boot.

Next create a new folder on the server and share it; let's call it btrieve. Copy the server folder into the btrieve share. Then you can map C: to the \\servername\btrieve, and C:\server will be the folder the \\servername\btrieve\server folder. app wants.

As I said, the tricky part is getting the OS on another drive letter. It may require creating two partitions on the drive; one tiny one and one large one for the OS. Format the first one and call it C:, then format the second one and call it . Install the OS on , then go back and disable / delete / rename C:, freeing the drive letter up for reassignment.

Collapse -


by dave In reply to Ugly Possibility

Your right that would work but it is going to have a hard time getting a prom date. I was hoping for something a litte less time consuming. Like an app or a reg fix etc.

Collapse -

Emulate old environment on the new server

by stress junkie In reply to Mapping a Local Folder to ...

It's not clear from your post if you are in the planning and testing phase of this project or if you have already made the change and are now discovering this problem in a production situation. Also we don't know if you have simply changed the server to new hardware or if you have also changed the desktop machines. The desktop machines already have a boot prom to boot from the network. If you have replaced those with machines that cannot boot from the network then that makes a lot of difference in what approach you could take.

In all cases I think that you should try to replicate the old environment as closely as is possible. If you still have the old desktop machines then I would go back to using the thin client approach on them. You just have to boot them from the new server.

If you have a new server and new desktop computers that can boot from the network then I would say do the same thing.

If you have new desktop computers that cannot boot from the network then you may be able to emulate a thin client by using Microsoft's remote desktop or by using Citrix software.

Collapse -

sorry for the lack of clarity

by dave In reply to Emulate old environment o ...

This is a situation that evolved in the implementation phase. The old system had 4 PCs as dumb terminals. Right next to them was the new network with windows XP systems. The server for the software died and rather than replacing the defective components I decided to merge the two networks. It wasn't till I finished moving the data and prgrams over to the new server and mapping the drives that I discovered the problem. The owner of the business is really insistant on only having one network due to the age of the old machines.

Here are some of the "On the table" solutions I am considering.

1: Thin-Client software like WinConnect XP to run terminal services on the server.
2: Total software overhaul with a new package to manage this company (my favorite).
3: Find a mapping solution to map the drive to a c: folder to run the current software.

Collapse -

Try this

by badbrewb In reply to Mapping a Local Folder to ...

Try a program called Winbolic Link. Should work fine on XP and Vista. I personally have not tested with server OS's yet. I will be trying 2003 tomorrow.


I have a share mapped as M:

I opened Winbolic Link and in the right pane clicked on M: and in the left pane I clicked on C drive and then below typed my folder name. I used the NTFS Junction option. (READ WARNINGS!!! and help...) This shows up in windows as a local folder. You can even share this newly created folder. (The reason I figured this out.)

Collapse -

What if you actually moved it to the C:\Server?

by cody In reply to Mapping a Local Folder to ...


Hope I'm understanding your problem correctly.

What about the possiblity of having a TERMINAL SERVER and moving the data into that Terminal Server's C:\Server? Then have clients connect to it using Terminal Services?

Otherwise since it was done in 19**, I would highly recommend to them to go with a NEW SYSTEM. Do they still support it after 17 years? Tell them about the advantages of moving to a new system, more features, better efficiency and more productivity. Find some alternatives and say that "Hey, it can now do this and merge with that and can steamline the processes making it faster to complete tasks"...?

I think the biggest problem is SUPPORT for it after 17 years. It's like someone still running Windows 3.11 in 2010.

Collapse -

automatic setup for local drive to map drive

by narendra2636 In reply to Mapping a Local Folder to ...

this is Narender
i am trying to Automatic setup from Local Drive to map drive which it was connected to server..
it is possible to

Related Discussions

Related Forums