>You could register components that reside on the server using REGSVR32; if you do, their registry entries will point to them on the network. There is a problem in that when they register, the path must be permanently available to reference the file; either a UNC, or a permanently mapped drive letter, is suitable. REGSVR32 should reference the file to register with a path based on a UNC or permanently mapped drive to ensure this.

Good point. So it's probably safest to to put the runtime files on the local drive. I've saved your msg so I can implement the other ideas in it - a two part Setup, and a post-setup executable to copy stuff from the Net. Thanks!