x mapping it's own network drive

[Chris Rizzo]

Here's a good one for you Bullines:

 

When selecting a file to open from X and browsing to my network drive (z:), mastercam will create a newly mapped drive of a differnt letter EVERYTIME I browse to the network. See picture.

There should only be z$ on 'kahn' (z:)

 

Computer is xp pro and a member of a domain. Server is running 2000 server.

 

 

[cadcam]

I tried to test this issue across my net work 2 servers one with 2003 and the other 2000 with 2 diffrent domains never saw a thing.

I am thinging it is some thing your IT did with server controler.

[Bullines]

That is strange. But I'm sure I've read something similar before, since I do recall writing a VBScript a while back to unmap the drives for a forum member using V9. I can't find the forum thread but I do still have the script that I wrote back in March on my notebook:

 

code:

---

'////////////////////////////////////////////////////////////////////////////////

'//

'// Author: Chris Bellini [email protected]

'// Date: 03/03/2005 1:18 PM

'// File Name: FixWeirdMcamMapping.vbs

'//

'// Description: Unmaps additional drives that Mastercam maps (for whatever

'// reason) based on a list of allowable drives

'//

'// Comments: Modify the DEF_ALLOWED_DRIVES constant with mapped drive

'// letters that are expected.

'//

'////////////////////////////////////////////////////////////////////////////////

 

Const DEF_ALLOWED_DRIVES = "Y:,Z:" ' follow this format

 

' call the main subroutine

Call Main()

 

 

' Purpose: The main subroutine

Sub Main()

Dim objNetwork ' WSH Network object

Dim objDrives ' Drives object

Dim strCurrMapDrive ' drive letter of a mapped drive

Dim arrAllowedDrives ' array containing allowable mapped drive letters

Dim iEnumIdx ' outter FOR LOOP index

Dim iAllowedIdx ' innner FOR LOOP counter

Dim bAllowedDrive ' allowed drive flag

 

 

' Create a WSH Network object

Set objNetwork = CreateObject("WScript.Network")

 

' Enumerate the mapped drives

Set objDrives = objNetwork.EnumNetworkDrives

 

' Prepare our array of allowable drives

arrAllowedDrives = Split(DEF_ALLOWED_DRIVES, ",")

 

' Check each enumerated network drive to see if it's a good one

' or one that Mastercam mysteriously created. If Mastercam mapped it,

' unmap the drive. We must increment the outter loop by 2 because the

' Item method returns a drive letter, then the network path and so on...

For iEnumIdx = 0 to objDrives.Count - 1 Step 2

' Init allowed drive flag

bAllowedDrive = False

 

' Retrieve the drive letter of the mapped drive

strCurrMapDrive = objDrives.Item(iEnumIdx)

 

' Test to see if the map drives is an allowed one

For iAllowedIdx = 0 To UBound(arrAllowedDrives)

If (strCurrMapDrive = arrAllowedDrives(iAllowedIdxy)) Then

bAllowedDrive = True

Exit For

End If

Next

 

' If the mapped drive isn't allowed, unmap it

If (bAllowedDrive = False) And (strCurrMapDrive <> vbNullString) Then

objNetwork.RemoveNetworkDrive (strCurrMapDrive)

End If

Next

 

' cleanup

Set objNetwork = Nothing

Set objDrives = Nothing

 

' all done

ShowString "Extraneous network drives created by Mastercam have been unmapped."

End Sub

---

This script will unmap all network drives that you don't want. You inform it which drives you want to be mapped. So for example, if your Y and Z drives are network drives that should be mapped, modify this line like this:

 

code:

---

Const DEF_ALLOWED_DRIVES = "Y:,Z:"   ' follow this format

---

Save it and run the script. It should unmap all network drives that aren't Y or Z.

 

As to why this even happens in the first place, I'm not sure. Are those Mastercam-created network drives browsable? If so, what are their contents?

 

HTH

[Chris Rizzo]

Thx for the input fellas. I indeed can navigate to any of those extraneous network drives and open them, they all are identical to the "real" z: drive. I'm at home right now but will go in later and try the script.

[nateacox]

Our MC does the same thing. It re maps the drive to a different letter every time you browse for a file. Win xp pro on the machine, windows server 2003 on the server.

[nateacox]

Update: In control panel, there is an X icon. Changing the interface style to windows from Mastercam has resolved the issue at this point.