Re: PowerPro 5.3.35r (no unicode) and 5.3.37h (Unicode)
| Newsgroups | gmane.comp.windows.power-pro |
|---|---|
| Message-ID | <[email protected]> |
Thanks, that is very helpful. I believe the last three of your tests (the one's where explviewU.dll was first missing) were actually done with 37h (Unicode)debugging. I can tell by the messages in the debug box. The explviewu.dll is only put in plugins folder by the 37h unicode install, so if you had just copied the 37h debug over a 35r install, that explains why explviewu was missing. I'm afraid I don't really understand why the original, non-debug version of 37h failed for you while the original version 35r worked. They both use short paths, both for the exe path to pprogdix and the path the plugins. And the path to the pcf folder too, although this only matters if it contains blanks, which it would when you store pcf in same folder as exe. I continue to suspect there was some relationship to the fact that you put your pcf in to the exe folder and run with powerpro.exe as admin. But I don't really know. In any event, I did learn that it is theoretically possible to turn of short paths, so I will add an option to next release to have PPro avoid them. The tests with long file names in the debug version did work on your machine for pprogdix.