I find that a lot of programs using .msi installers fail unless I create a fake h: drive using subst. Why?

Hmm... it must be something with the way that a drive letter is automatically assigned vs. the virtual linking of drive letters with subst. When a usb drive is connected, windows looks up the next available or most recently used letter. The letter is assigned to the drive physically and access is given to the Kernel.

When a drive letter is virtually created with subst (or similar method) a link is created unless colon is used to identify a physical drive. MSI installers have limited access to some system resources in both Vista and XP. Windows Security wraps itself around drive, file and system access.My first step would be to disable windows security (completely) on a safe test system or virtual (vmware) image.

If Windows Security wasn't to blame, I would delve deeper into the MSI installers themselves to see how they are connecting to the install location drives. If this is a system wide problem and you're a sysadmin, the easy fix might be to create a batch script that will automatically assign a subst letter to media drives that are inserted. Piggyback this script on every autoplay launch but ensure to release the drive letter when the device is ejected / removed.

This isn't a good solution, but if you're installing something system wide and need a quick fix, it's the only one I can think of without having more information about the exact MSI installers, your system(s), etc.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.