I have a program that accepts command line arguments. Show The scheme I've adopted is that every command line argument is shaped like this: -x::argument where x is a letter that stands for a switch ( like a mode of operation, and argument is an argument that goes along with that switch ). :: is my separator. I ran into a problem with the following command line: If I run the following directly from Windows command line: "C:\Test\Program.exe" "-c::C:\Documents and Settings\maciej\Desktop\Measurement and Automation\test\current.cfg" -m::a All works fine. If I try to use the System Exec.VI: And pass the following string to it cmd /c "C:\Test\Program.exe" "-c::C:\Documents and Settings\maciej\Desktop\Measurement and Automation\test\current.cfg" -m::a I get the error as in the title of the post. Does anyone have any ideas how to make it work from System Exec? It seems that system exec parses the: "-c::C:\Documents and Settings\maciej\Desktop\Measurement and Automation\test\current.cfg" part ... figures that this is not a file name ... I don't want it do to that I know it isn't but it is still a valid cmd argument for me. Maciej Part Number: MSP-EXP430G2 I ran the blink example on my board a couple days ago with no problem but today no code (not even blink) will upload to the microcontroller giving me this error message Energia: 1.8.11E23 (Windows 10), Board: "MSP-EXP430G2 w/ MSP430G2553" C:\Users\USERNAME\Documents\energia-1.8.10E23-windows\energia-1.8.10E23\hardware\energia\msp430\cores\msp430\atof.c: In function 'atof': C:\Users\USERNAME\Documents\energia-1.8.10E23-windows\energia-1.8.10E23\hardware\energia\msp430\cores\msp430\atof.c:71:9: warning: floating constant exceeds range of 'double' [-Woverflow] Sketch uses 810 bytes (4%) of program storage space. Maximum is 16384 bytes. Using new (SLAC460L+)
API I've already tired updating the drivers and that didn't solve the problem. Problem descriptionNAS backup fails with the filename, directory name, or volume label syntax is incorrect error. You might encounter this error at the initial stage of the Windows NAS backups. You get the following errors:
CauseYou might get many errors if the Share is not accessible from the NAS proxy. Resolution
|