Network drive, mapped drive problem


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Tom Fulton on April 10, 2012 at 09:11:15:

In my RI office I have migrated from a local C: comet single-user installation to a network model. My server is called //ri-win2008 and I have a sys share on it. On sys I have my comet folder and all my other source/object/file folders. On my desktop PC I have a mapping of z: to \\ri-win2008\sys. When I click on Network in Windows Explorer I can see ri-win2008, I can open it up and examine all the folders. At a command prompt I can ping ri-win2008 and it returns the correct IP address. My problem is that when I set up my INI file for sysgen the path \\ri-win2008\sys\comet folder and all other UNC paths to folders generate and Excp 1002. I can change the drive to z:\comet and that works fine, all drives register and comet runs. However, I run into big problems compiling. I continually get "No Comet directories match command file" message, and I think that it has to do with folder names greater than 8 characters (SourceDFS as Source~1). This is causing a lot of problems & wasted time. Any idea what's going on? Thanks in advance!


Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?  

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):





Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]