Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Tue, 20 Sep 2005 14:03:32 -0400, John Peacock <jpeacock at rowman.com> wrote: >Tony Hoyle wrote: >>> And of course I could not put my repo on this drive either, it moved >>> to C:\DATA when I switched PC... >> >> In theory I suspect you could do it, but it'd be a horrid hack - make >> something that logs in as LocalSystem and did the subst on bootup. > >You can't do it with subst, but you might be able to do it with junction >points (which are softlinks at the OS level as opposed to the user level). > I just mentioned how I have restructured my new PC from having 3 physical disks on the old one to having a single one on the new and still being able to see the same disk structure for most of my work. I have a subst batch fioe in my startup folder so that E: and F: get created at login. But I never even considered keeping my repository on my F: disk, I just moved it over to C:\DATA and then I configured CVSNT to feed that new location out as the repo names used before. What this possibly is proof of is the ease with which one can restructure the repository location without the users even noticing. But considering Windows Installer's inability to run a setup from a subst: drive, I guess that it also is unable to run it from a network share for the same reson (the service not having access rights to the shared drive on the other PC). This points to yet another reason not to use the MSI engine to install stuff.... /Bo (Bo Berglund, developer in Sweden)