error trying to run Distance 6.2

[Derek Lee]

Hi all,
I am trying to run distance 6.2 on my personal laptop, but get the error message below.
I've seen others had this issue on work machines, but I am running this on a personal computer where I am administrator.
Any ideas?
-Derek Lee



Initializing
Making Data File
Making Data Selection Queries
Making Input File
Engine started with the following command:
 C:\PROGRA~2\Distance 6\ec "C:\PROGRA~2\Distance 6\MCDS.exe 0, C:\Users\Derek\AppData\Local\Temp\dstA96C.tmp \options 2>C:\Users\Derek\AppData\Local\Temp\dstA96B.tmp"
-- Start of Analyis Engine Log File --
-- End of Analyis Engine Log File --
** Warning: Analysis engine wrote some output to the console error stream, reproduced below. **
-- Start of Console Error Stream --
'C:\PROGRA~2\Distance' is not recognized as an internal or external command,
operable program or batch file.
 
-- End of Console Error Stream --
Analysis engine status 'OK'
Reading Results
Run finished

[Eric Rexstad]

Derek

We receive reports of this regularly.  As you note, it has to do with privilege of using some of the file locations in Windows.  Even if you are not on a network, some versions of Windows are 'sensitive' to writing in certain directories.  Not clear which version of Windows you are using (7,8,10--note too there are 32 and 64 bit versions at least of 7).

a) Notice that Distance is trying to write to the location "C:\Users\Derek\AppData\Local\Temp\dstA96B.tmp".  Check to see if your administrator privilege will let you create such a file either in Windows Explorer or from the C> prompt.  That will verify whether the problem is a result of administrator privilege.

b) Note, that when I use Distance 6.2 on my Windows 7 machine, my log window shows a slightly different incarnation of the execution command:

C:\PROGRA~1\DISTAN~2\ec "C:\PROGRA~1\DISTAN~2\MCDS.exe 0, C:\DOCUME~1\eric\LOCALS~1\Temp\dst9F2.tmp \options 2>C:\DOCUME~1\eric\LOCALS~1\Temp\dst9F1.tmp"

Notice for me "Distance 6" has been transformed to "DISTAN~2" circumventing the offending space within the command string.  My version conforms to the DOS 8.3 file name convention (note the 10 character string "Distance 6" has been converted to an 8 character "DISTAN~2" string.

c) As a long-shot, print out your PATH (type "path" from the DOS prompt). 
  i) Does your current path contain "c:\windows\system32" ?
  ii) If no to i), see if adding "c:\windows\system32" to your path resolves the problem.

--
You received this message because you are subscribed to the Google Groups "distance-sampling" group.
To unsubscribe from this group and stop receiving emails from it, send an email to distance-sampl...@googlegroups.com.
To post to this group, send email to distance...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/distance-sampling/4dd5764b-45f5-4240-8f0c-3c71b4b85b9d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
Eric Rexstad
Research Unit for Wildlife Population Assessment
Centre for Research into Ecological and Environmental Modelling
University of St. Andrews
St. Andrews Scotland KY16 9LZ
+44 (0)1334 461833
The University of St Andrews is a charity registered in Scotland : No SC013532

[Sam Shanee]

Dear Erik, I am having the same problem as Derek (With versions 6.0, 6.2 and 7 beta). I have administrator privelages and also checked this by creating the folder that you suggest in a). My log shows

C:\PROGRA~2\Distance 7\ec "C:\PROGRA~2\Distance 7\MCDS.exe 0, C:\Users\sam\AppData\Local\Temp\dst6E37.tmp \options 2>C:\Users\sam\AppData\Local\Temp\dst6E07.tmp

Could you explain how to fix this as I cannot figure this out from your previous reply to Derek. I am not great with computers and don't fully understand how to add anything in the DOS prompt.

Thank you,

Sam

[Eric Rexstad]

Sam

The very simplest way to avoid this problem is to install Distance to a location other than the default directory.  During the setup process of *all versions* of Distance, you are given the option of where to install Distance at this dialogue screen:

simply choose a directory that does not have spaces in the path.

[Alain Licoppe]

Dear all, the same kind of error occured when installing distance 7.1 on my personal laptop running under Win10. Error was fixed by using a pathway without any space during setup, as suggested by Eric.