(I’ll assume your path question relates to the failed installs.)
File system: too tired to run this down. But my machine is a pre-loaded 100% flash hard drive pre-installed with Windows 10. I didn’t change my file system, simply knocked down the size of C: and created a D: partition. (Is your “D:” a true “D:” (an actually different physical device)?
Paths varied with failure, as intuition led me down to the path as the culprit. The first two (3.5.1 and 3.4.2 FAIL1) were "D:\$Root\$Apps\Audacity\{version number}\"here" . (The the bulletin board posting program modifies that path. It should read: D: - backslash - DollarRoot - bs - DollarApps - bs - Audacity - bs - {version number} . The version number is just numbers and dots - no soft parens.) The 3.4.2 FAIL2 was all of that, with an “Audacity” under the version number and then the files below that. (Maybe the program loads, finds the “Audacity” folder, and doesn’t keep looking below it (into the version number and below that) to find its modules?)
Wacked the old stuff, rebooted. Wacked all running programs, did the install. Didn’t have the installer Launch the program, did it manually. That little transient “peek-a-boo” window of configuration activity after the Audacity splash screen never appeared until the 3.4.2 “Program Files” load that worked. Was wearing street clothes on the failures, pajamas on the one that finally worked. Was also fasting on the one that worked. I play bass left handed.
Feel free to request more details.
Thanks for the feedback and followup.
(As I said earlier, I’d like to know if your “user displaced” installs work on a machine that has zero Audacity on it in other places. But I’m assuming you are a virtual crowd contributed operation and don’t actually have a physical test lab of 40 machines where you can grab one, do a clean Windows install, and then drop Audacity into a virtual partitioned D: drive with no other Audacity presence.)
But again, I appreciate your efforts and your feedback.
Peace unto thee.
OK, it appears that the $ is the problem: If I install it to D:\$Root\$Apps\Audacity\3.5.1\ I can reproduce your problem, if I install it to D:\Root\Apps\Audacity\3.5.1\ it works. Thank you for your help!! Bug will go up momentarily
Wow. Outstanding work by you. If I was there, I would buy you a pizza.
(As a side note, the “$” is a legacy habit from DEC VAX 11/780 development - back in the days when VAX was a totally positive cool thing.)
Thanks for the work, the solution, and the information.
{
And, just as essential … I apologize for the attitude I included in the original “report” of this post. Other issues were boiling inside me and “then this!?” popped in unsuspected. I tried to edit it to make it more respectable, but couldn’t. 100% wrong on my part. Forgive me. If I could, I would double the pizza order.
}
That tells us way more than you think. That means the problem exists in the older, classic Audacity and was not caused by all the advances and changes in 3.5.
