Farid,
This is not a simple issue.
Here are a couple of possibilities:
1) The application needs to do direct disk I/O (block level). In this case,
you're out of luck using a network drive and should look at SnapDrive VLD or
FCP. Examples: Microsoft Exchange 2000, some products like some FileNet
modules that do block I/O.
2) The application does a check and won't install. However, you may be able
to install on local disk then move the location to a network drive later.
Example: SAP R/3 on SQL Server.
Hope this helps.
-----Original Message-----
From: Farid Hamjavar [mailto:hamjavar@unm.edu]
Sent: Tuesday, 11 March 2003 11:24 AM
To: toasters(a)mathworks.com
Subject: why should app care?
NetApp Release 6.3.1
greetings,
We have encountered situations where when an
application is installed on windows (2000 for example)
, the application complains whether or not drive onto
which it is installed is a real physical disk or a
mounted CIFS share coming from the Netapp filer. If the
drive happens to be a mounted CIFS share coming from the
Netapp filer application either does not get installed
and/or operates erroneously.
Anyone encountered this? If so what's the solution or
workaround?
Thanks,
Farid
UNM
**** ASI Solutions Disclaimer ****
The material transmitted may contain confidential and/or privileged
material and is intended only for the addressee. If you receive this in
error, please notify the sender and destroy any copies of the material
immediately. ASI will protect your Privacy according to the 10 Privacy
Principles outlined under the new Privacy Act, Dec 2001.
This email is also subject to copyright. Any use of or reliance upon this
material by persons or entities other than the addressee is prohibited.
E-mails may be interfered with, may contain computer viruses or other
defects. Under no circumstances do we accept liability for any loss or
damage which may result from your receipt of this message or any
attachments.
**** END OF MESSAGE ****