Sgraphrecorder question

[Epelic]

I am utilizing your Sgraphrecorder program. It is a very cool ... And useful program.

I am having one problem which I hope you can advise me on. When I specify an external tuner (ExeTunerPath= ...) a Dos window appears for a split second and the program specified never executes. I know others have used this setting successfully and I have determined it must have something to do with my (Windows XP) system, since I cannot get anything to execute ... Including a batch file with only a "pause" command.

What I would like to know is how is the command specified executed within the program. Is it a Dosshell command or ...? I would like to know so I can create a program which executes the steps to be used to debug my problem. I don't know of any other way to figure this out.

Thank you very much!

[Epelic]

Originally Posted by Epelic

I am utilizing your Sgraphrecorder program. It is a very cool ... And useful program.

I am having one problem which I hope you can advise me on. When I specify an external tuner (ExeTunerPath= ...) a Dos window appears for a split second and the program specified never executes. I know others have used this setting successfully and I have determined it must have something to do with my (Windows XP) system, since I cannot get anything to execute ... Including a batch file with only a "pause" command.

What I would like to know is how is the command specified executed within the program. Is it a Dosshell command or ...? I would like to know so I can create a program which executes the steps to be used to debug my problem. I don't know of any other way to figure this out.

Thank you very much!

I have determined that the cause of the error I am experiencing is that the path provided (ExeTunerPath=path) contained a space. Although I put quotes around the path as a test, it appears that the path cannot have a space in it ... otherwise the MS-DOS session invoked will fail because MS-DOS will interpret the command differently than intended and attempt to execute the command up to the space ... and treat the rest as parameters.

I wanted to point this out, although I assume this is known to the developer so as to suggest something that should be added to the documentation ... namely no spaces are allowed in the path.