Hi Warry. I've tried to replicate your results but so far I haven't been able to. Maybe I found a different issue though.

At first I created a Test A project in a Test A folder and used sample clips in the root directory of the same drive. There were no problems opening that project when double clicking it after renaming the Test A folder to Test B, and no issues when opening the new Test B project from the same folder.

I then moved the clips from B:\ to B:\Test B and both projects opened normally even though the file pointers no longer referenced the correct location. I assume it's because PD was able to find them in the same folder as the project. This was true even after I changed the Import folder setting to a different drive.

I then created a new folder called Sample Clips and moved the clips there, and this time PD was unable to locate them. I went through the steps of creating a Test B1 project but again, everything went normally whether I opened the project from within PD or double-clicked on it in File Explorer.

In your tests, what folder are the sample clips located in? TESTA/B or a separate folder?

Thanks for the testing.
In my project the samples files were both in the CL sample directory and later also in packed project folder.
I received a reaction from CL, telling me to complete uninstall PD21, which I did.
After installation is created a small project with 2 images in the timeline, saved it and closed PD and started PD by clicking on the project file. PD opened the image files in the mediaroom and hung with the message Update timeline data 60%
I have shared the project and the information from the Windows Hang reports (before and after reinstallation) with CL.
It is not a big deal, since I still can open the project from with PD, but apparently there is something wrong with my Windows installation or with the PD installation, which I'd like to have resolved.

FYI
I received a reaction from CL product support with confirmation that starting PD by clicking on a PDS file is not supported.

With reference to your concerns, please be advised that after further checking with the engineering team, PowerDirector does not support the operation via the Windows command line/arguments. The normal software functionality of using the command line is not guaranteed nor offered in CyberLink software.

Quote FYI
I received a reaction from CL product support with confirmation that starting PD by clicking on a PDS file is not supported.

With reference to your concerns, please be advised that after further checking with the engineering team, PowerDirector does not support the operation via the Windows command line/arguments. The normal software functionality of using the command line is not guaranteed nor offered in CyberLink software.

Interesting, I'm not sure why double clicking a file name was even associated with using the command line in this thread as it is not. There is no "double mouse click" equivalent in command line interface as the double click is in fact a combination of a file picker and a list of registered file types. Command line interface is only interaction from a form of lines of text, typed, passed, or from an input files.

But I guess I agree with CL's easy out statement of launching PD from a Windows command line/arguments via text input is not supported. Namely from a command window cmd with C:\> prompt is not supported, like C:\>PDR.exe test.pds which in no way is equivalent to double clicking a file!

Jeff

Quote

Interesting, I'm not sure why double clicking a file name was even associated with using the command line in this thread as it is not. There is no "double mouse click" equivalent in command line interface as the double click is in fact a combination of a file picker and a list of registered file types. Command line interface is only interaction from a form of lines of text, typed, passed, or from an input files.

But I guess I agree with CL's easy out statement of launching PD from a Windows command line/arguments via text input is not supported. Namely from a command window cmd with C:\> prompt is not supported, like C:\>PDR.exe test.pds which in no way is equivalent to double clicking a file!

Jeff

Indeed! I mentioned (I think) the double clicking only, as from the command line and double clicking are different things.
PDR(.exe) is not even recognized in command line mode as a command. In the windows default apps list there are a number of extensions coupled to PDR, including PDS, PDL (library) and PDM (menu). In my system PDM and PDL work fine: PDR is started when files with that extention are double clicked. As mentioned the PDS (project) files sometimes open correctly.
At least we have confirmation from CL :

Quote Indeed! I mentioned (I think) the double clicking only, as from the command line and double clicking are different things.
PDR(.exe) is not even recognized in command line mode as a command. In the windows default apps list there are a number of extensions coupled to PDR, including PDS, PDL (library) and PDM (menu). In my system PDM and PDL work fine: PDR is started when files with that extention are double clicked. As mentioned the PDS (project) files sometimes open correctly.
At least we have confirmation from CL :

It was given as example syntax only, you'd obviously have to give the proper path for the command, like "C:\Program Files\CyberLink\PowerDirector21\"pdr.exe and then a list of launch arguments or modify your default path. Again, this true CLI it is not the same as double clicking a pds file.

Jeff