Quote:

Why not just install Band-in-a-Box in C:\bb you might ask? Because we have file systems and directory hierarchies for a reason and if any program can install itself where ever it wants to, it defeats the order of a file system.



The problem is not that BIAB is not playing nicely with your folder hierarchy, it's that Microsoft has decided that programs installed in "C:\Program Files" can only change things in certain ways. If you turn off UAC (and I mean completely, not the pseudo turn-off that Win7 now provides), you will probably find it works fine in Program Files.

The problem is that because BIAB doesn't write to the registry, but instead modifies configuration files in its own folder, Windows 7 sees that as modifying system files and doesn't let you do it.

For me, I'm glad BIAB doesn't write to the registry. That's what lets you just hook up the external drive to any computer and start working with BIAB right away. And when you are done, no traces of BIAB on that computer for someone to clean up later.

I put all my PGMusic (and other programs that behave similarly) in a folder called "C:\Apps" that I created. I then create a folder hierarchy of programs under Apps. That keeps things tidy, but doesn't cause the problems you described. Works great in "C:\Apps", whether UAC is turned on or off.

By the way, this is a Vista problem also. Vista doesn't like programs that write directly to configuration files in the Program Files folder. In fact, when I installed WinRAR (a file compression utility), it wouldn't even let me install my license file, because the file goes into the WinRAR folder. Of course, when I turned UAC off, it worked fine.

It's not BIAB; it's Microsoft trying to protect you from yourself.

John

Laptop-HP Omen I7 Win11Pro 32GB 12TB SSD
Desktop-ASUS-I7 Win10Pro 32GB 12TB SATA

BB2026/UMC204HD&404HD/Casios/Cakewalk/Reaper/Studio One/Notion/Dorico/Noteworthy/NI/Halion/IK

http://www.sus4chord.com (under rehosting/construction)