The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here
Installing on WIndows 7
Kirk_Fleming
Member Posts: 3 
Contributor I
Well, I've attempted installation at least a dozen times now, and get a new problem each time. Issues have included:
- installation failed because the network name is no longer available
- installation failed because [manual.pdf] is open by another application
- installation failed because UNC path names cannot be used for the local directory (elevated command prompt)
- installation failed because somebody in the script attempted to use a drive letter to find something it needed*
* In this case, I ran the script from C:\windows\system32, calling it using the UNC path to the .bat file. This began execution okay, but at some point the drive letter currently associate with the UNC path to the .bat file was used to call something, and the script crashed at that point ("Y:\ does not exist" or something like that).
and several more errors. So, what I'm hoping for is some key element of installation that I'm missing.
I'm running the RapidAnalytics-Installer.bat from an elevated command prompt
Specifying first a networked drive (using UNC path name), and when that failed
Specifying the c:\windows\system32 path for installation
The .zip file containing the installer and everything else is located on a NAS drive, so when I execute the .bat file it looks like:
C:\windows\system32>\\bigdrive\dev\rapid\RapidAnalytics-Installer.bat
Do I need to unzip everything into C:\windows\system32 in order to install it there with an elevated cmd prompt?
- installation failed because the network name is no longer available
- installation failed because [manual.pdf] is open by another application
- installation failed because UNC path names cannot be used for the local directory (elevated command prompt)
- installation failed because somebody in the script attempted to use a drive letter to find something it needed*
* In this case, I ran the script from C:\windows\system32, calling it using the UNC path to the .bat file. This began execution okay, but at some point the drive letter currently associate with the UNC path to the .bat file was used to call something, and the script crashed at that point ("Y:\ does not exist" or something like that).
and several more errors. So, what I'm hoping for is some key element of installation that I'm missing.
I'm running the RapidAnalytics-Installer.bat from an elevated command prompt
Specifying first a networked drive (using UNC path name), and when that failed
Specifying the c:\windows\system32 path for installation
The .zip file containing the installer and everything else is located on a NAS drive, so when I execute the .bat file it looks like:
C:\windows\system32>\\bigdrive\dev\rapid\RapidAnalytics-Installer.bat
Do I need to unzip everything into C:\windows\system32 in order to install it there with an elevated cmd prompt?
Tagged:
0
Answers
Can anyone guide with the series of steps or the prerequisites?
Thanks in Advance.
Ravi