Hi,
I have a program I need to install on a PC (with Win 2000 Pro). The PC is connected to a Windows 2000 Server, through a domain, and when the users logon, a disk I: is created, pointing to a shared directory on the server.
My purpose was to install the software on the Workstation PC, but instead of giving the directory C:\PROG for the installation, I wanted to give the directory I:\PROG. That way, the windows was tricked to work on the server, and the backups were a lot easier (data would be centralized).
The problem is that the software doesn't work on the I: disk. If I install on C:, it works fine, but on I: it doesn't enter the app, giving me an error like "The application was not correctly registered". I thought it would have something to do with the register, so I made some search on it and find no info that could unable it to work on a remote disk.
What I whant to ask is, is there another way of "tricking" windows to work with a shared directory as a local drive?
What makes it so diferent the I: drive created with NET USE command over a local disk, that a software refuses to work on it? Any ideas?
Thanks
I have a program I need to install on a PC (with Win 2000 Pro). The PC is connected to a Windows 2000 Server, through a domain, and when the users logon, a disk I: is created, pointing to a shared directory on the server.
My purpose was to install the software on the Workstation PC, but instead of giving the directory C:\PROG for the installation, I wanted to give the directory I:\PROG. That way, the windows was tricked to work on the server, and the backups were a lot easier (data would be centralized).
The problem is that the software doesn't work on the I: disk. If I install on C:, it works fine, but on I: it doesn't enter the app, giving me an error like "The application was not correctly registered". I thought it would have something to do with the register, so I made some search on it and find no info that could unable it to work on a remote disk.
What I whant to ask is, is there another way of "tricking" windows to work with a shared directory as a local drive?
What makes it so diferent the I: drive created with NET USE command over a local disk, that a software refuses to work on it? Any ideas?
Thanks