We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I am trying to link my already existing MS Source Safe Projects with the project in uV2. But all commands except "SourceSafe Explorer" result in an error like Error: can't execute '"C:\Programme\Microsoft Visual Studio\Common\VSS\win32\Ss.exe" CP $/"eeprom" -I-' By the way I don't want uV2 to make the directory structure in Source Safe but to use my already existing one. Best, Ernst
Has anyone managed to get SVCS working properly in uv2? I'm getting the same errors as discussed above. I get an error message as follows: -- Error: can't execute '"C:\Program Files\Microsoft Visual Studio\Common\VSS\win32\Ss.exe" Get "454.asm" when I select the menu option Get actual version on '454.asm' The path shown above in the error message is the correct path to the Ss.exe command on my computer.
Is the command name enclosed in quotes? Check the following knowledgebase article and let us know if this helps. http://www.keil.com/support/docs/1624.htm Jon
Adding quotes around the command and path string makes no difference, I still receive the error messages such as: --- Error can't execute '"C:\Program Files\Microsoft Visual Studio\Common\VSS\win32\Ss.exe" Get "480.asm" when selecting an option from the SVCS menu. The path shown above in the error message is the correct path for the file Ss.exe. The first menu option in SVCS (SourceSafe Explorer) works ok and starts the Source Safe Explorer. It gives the following message in the build window of uVision: "C:\Program Files\Microsoft Visual Studio\Common\VSS\win32\Ssexp.exe" Simon Bagley.
Hello Simon, I has the same problem as you. Did you in the meantime already find a solution? That would be nice, if they could communicate these to me. Thanks Ronny.
I must have missed something. I didn't see the fix anywhere and I'm having the same problems. Can anyone help?