Thread 'BOINC installing to non existent drive'

Author	Message
jfmoonan Send message Joined: 8 Dec 16 Posts: 2	Message 74672 - Posted: 8 Dec 2016, 3:01:34 UTC I'm trying to install BOINC to a second Windows 10 computer. Installation starts, then get error that drive J: in invalid (there is no such drive) and installation fails. Where is this usage of drive J: coming from? How do I fix so I can get BOINC running on a PC. Thanks, John M ID: 74672 ·

Jord Volunteer tester Help desk expert Send message Joined: 29 Aug 05 Posts: 15632	Message 74680 - Posted: 8 Dec 2016, 8:39:05 UTC - in response to Message 74672. Use Microsoft's Fix-It program to fix that. ID: 74680 ·

jfmoonan Send message Joined: 8 Dec 16 Posts: 2	Message 74730 - Posted: 10 Dec 2016, 23:04:19 UTC - in response to Message 74680. Microsoft FixIt program did not fix it. It install the Oracle VM VirtualBox fine. Then depacks the files and starts install and I immediate get a message the there is an invalid drive J: and when I acknowledge the error message it terminates. This computer has is running Windows 10 64 bit, has I7 with 8 GB ram. Drives A: and B: are mounted file servers, C: is main drive 1 TB, D: and E: are DVD drives, G:, H: I: and K: are memory card slots. There is no drive J:. Any idea what's going on and how I fix it? Thanks, John M ID: 74730 ·

Richard Haselgrove Volunteer tester Help desk expert Send message Joined: 5 Oct 06 Posts: 5149	Message 74731 - Posted: 10 Dec 2016, 23:14:26 UTC - in response to Message 74730. This is one of the very many bugs which have been reported to BOINC developers over the years, but never attended to. By chance, I was looking up the references for a renewed attempt at getting developer attention a couple of days before you started this thread. Try reading through the workrounds in https://github.com/BOINC/boinc/issues/792 http://boinc.berkeley.edu/trac/ticket/815 ID: 74731 ·

Gripper Send message Joined: 26 May 14 Posts: 3	Message 74765 - Posted: 13 Dec 2016, 19:06:34 UTC Why is this Invalid Drive error still coming up. I had it last time I tried to update and have it again. As per others all I have is "My Documents" on a NAS Drive. What is so difficult about that? I think that I can edit the Reg to find the Data drive but I have 6 projects running with the Data files on the NAS box without problem so why does the upgrade fail? Gripper ID: 74765 ·

Gripper Send message Joined: 26 May 14 Posts: 3	Message 74769 - Posted: 13 Dec 2016, 20:37:08 UTC Update - Solved it by editing RegEdit: HKEY_LOCAL_MACHINE\SOFTWARE\Space Sciences Laboratory, U.C. Berkeley\BOINC Setup Changed DATADIR from Q:\Bonic\ to C:\Bonic\, installed update and then changed it back to Q: ID: 74769 ·

HAL9000 Help desk expert Send message Joined: 13 Jun 14 Posts: 81	Message 74776 - Posted: 14 Dec 2016, 23:20:45 UTC I wonder if creating a link between Q:\BOINC and C:\BOINC would have worked. ID: 74776 ·

Richard Haselgrove Volunteer tester Help desk expert Send message Joined: 5 Oct 06 Posts: 5149	Message 74777 - Posted: 14 Dec 2016, 23:42:44 UTC Another pair of unresolved issues from the olden days are https://github.com/BOINC/boinc/issues/824 http://boinc.berkeley.edu/trac/ticket/847 I found that the Windows installer (but not BOINC itself) distinguishes between local and network drives. A normal installation will default to local disks: an administrative installation (setup /a) will default to network drives. I din't have any reason to check whether "normal installation to network drive" was forbidden, but it might be an explanation for the installer's refusal to use the NAS on Q: ID: 74777 ·

Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.