-
Notifications
You must be signed in to change notification settings - Fork 447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error 1327: Invalid Drive - Error while Installing BOINC 6.4.5 #792
Comments
Commented by SETI@Home friend [on 25 Aug 38996378 22:13 UTC |
Commented by SETI@Home friend [on 3 Nov 38996464 09:46 UTC Installation stops.[[BR]] |
Commented by SETI@Home friend [on 19 May 38997011 11:06 UTC [installing BOINC you can reassign the old Data...''Not nice but operational...''[[BR]([BR]] |
Commented by Richard Haselgrove on 21 Oct 39027896 18:13 UTC
In my case, I had an earlier BOINC (v6.2.18) installed, with both program and data folders installed on drive D: That disk started developing faults, so I recovered all available data, un-installed BOINC, and removed the drive for testing and RMA. Trying to re-install BOINC on drive C: as a temporary measure, I got the error 1327 at the first Installshield 'computing space requirements' screen (as per [Founder]'s screendump), and it skipped immediately to an 'interrupted - run setup again - finish' screen - no remedial action possible. My workround: !RegEdit to HKEY_LOCAL_MACHINE\SOFTWARE\Space Sciences Laboratory, U.C. Berkeley\BOINC Setup, and change all D: references to C: But you can't expect end users with failed drives to resort to !RegEdit. Suggestion: assuming you can get network maps accepted as valid drives, trap error 1327 and revert to default installation paths. That would work for ordinary end users, and allow power users to re-select their bespoke paths from the currently-valid drive list. |
Commented by romw on 11 Apr 39159099 08:26 UTC |
Commented by SETI@Home friend [on 6 Feb 39475594 11:06 UTC There is an another strange behavior when You try to install from a local drive under Win7... There is already a BOINC Client (V6.6.31) installed, the message tab reports that there is a new Version. If you try to install you get the Message: The strange thing is, that i can't find a String "Y:" anywhere in my registry ??? Perhaps it help fixing the bug... Bye! You do a great job! |
Commented by Richard Haselgrove on 5 Oct 39963392 16:53 UTC
|
Commented by romw on 4 Jun 40859063 10:40 UTC |
Commented by Richard Haselgrove on 30 Nov 44536420 06:50 UTC |
Needs to be evaluated if this still applies. |
I have just uninstalled BOINC from my system, moved the boinc_7.6.33_windows_x86_64.exe installer to my NAS (which in effect is a massive network drive), started the install from there. No problems. BOINC is installed and running. In then uninstalled BOINC again. Now mapped the folder the BOINC installer is in on my NAS as a network drive, started the installer from there and installed BOINC without problems. However, error 1327 indicates a problem with the mapped drive letter, as in it no longer existing. So I again uninstalled BOINC, then made a shortcut of the BOINC installer to my desktop, disconnected from the mapped network drive, and started the shortcut. It took a little while, but eventually the installer started and installed BOINC. Meaning that with the present 7.6.33 and Windows 7 64 bit I cannot reproduce this. |
Anyone else able to still reproduce the problem? |
Closing because no one answered. Assuming it's fixed. |
Reported by SETI on 12 Jun 38996368 01:46 UTC
'''System'''[Vista Enterprise (32-Bit)[[BR]([BR]]
Microsoft)]
Personal Files are in a network Folder (H:)[is reachable
'''How did I found this Issue?'''[[BR]([BR]]
H:)]
Install the Core Client from a local HDD[starting the install process I got the Message:[[BR]([BR]]
while)]
"Error 1327: Invalid Drive H:[[BR]]
[OK]"
see the BOINC_Screen1.png
Migrated-From: http://boinc.berkeley.edu/trac/ticket/815
The text was updated successfully, but these errors were encountered: