From: Jan Simon on 8 Jul 2010 03:22 Dear Vivian, > MATLAB cannot save changes to the path. > The path file, pathdef.m, might be read-only or might be in a directory for which you do not have write access. Again: Please check another time if this is true. which('pathdef.m', '-all') % Multiple files? oneFile = which('pathdef.m'); fileattrib(oneFile) fileattrib(fileparts(oneFile)) Is UserWrite enabled whereever needed? I cannot find the function which is responsible for the error message. Perhaps you have shadowed the function, which checks writabilty of the PATHDEF.M file?! Kind regards, Jan
From: Marco Rotonda on 8 Jul 2010 06:01 I've the same problem as Vivian. The funny thing is that if I add only a folder without the subfolders... it woks!
From: Jan Simon on 8 Jul 2010 06:50 Dear Marco, > I've the same problem as Vivian. > The funny thing is that if I add only a folder without the subfolders... it woks! Vivians problem seems to be, that she cannot save PATHDEF.M automatically, but manually it works. Where is the relation to "add a folder without the subfolders"? Vivians problem sounds very strange and something mysterious seems to happen. My experiences tell me, that in 99.9% of the casesl mysteriums become wrong input or wrong expectations, after the problem has been defined and explained exactly. The tiny rest is caused by damaged RAM or CPUs. Kind regards, Jan
From: per isakson on 10 Jul 2010 21:30 "Jan Simon" <matlab.THIS_YEAR(a)nMINUSsimon.de> wrote in message <i14agu$s76$1(a)fred.mathworks.com>... > Dear Marco, > > > I've the same problem as Vivian. > > The funny thing is that if I add only a folder without the subfolders... it woks! > > Vivians problem seems to be, that she cannot save PATHDEF.M automatically, but manually it works. > Where is the relation to "add a folder without the subfolders"? > > Vivians problem sounds very strange and something mysterious seems to happen. My experiences tell me, that in 99.9% of the casesl mysteriums become wrong input or wrong expectations, after the problem has been defined and explained exactly. The tiny rest is caused by damaged RAM or CPUs. > > Kind regards, Jan I have experienced the very same problem that Vivian describes. Last winter I got a new PC, which included 1. Update to Windows 7 (64bit) from Windows XP 2. Update to Matlab R2009b (64bit) from R2008b 3. Increased security, which mean I have less control over my PC. Profiles are managed remotely - I don't know the details and things happens automagically. I was not comfortable with Windows 7 and the new Ms Office. Matlab was a minor nuisance. Anyhow, I could not save my Matlab path. I jumped into the conclusion that something had gone wrong with the installation of Matlab. The permissions were too restricted. After all, why should I change files under the Matlab root? >> which pathdef C:\Program Files\MATLAB\R2009b\toolbox\local\pathdef.m The Start in: folder of the Windows shortcut was empty. (I did not check USERPATH.) Ok, I decided that this was the time to make a system to help me easily switch between different search paths. 1. I created a new folder ...\Configuration 2. Added "...\Configuration" to the Start in: folder of the the Windows shortcut. 3. Put a copy of PATHDEF in the folder named "...\Configuration" 4. Did something "clever" in STARTUP 5. I never made the switching part work properly This worked until I updated to R2010a. R2010a was not happy with ...\Configuration\pathdef.m because certain folders of the new Matlab installation was removed from the path by the old pathdef. Now I have removed ...\Configuration and cleared the Start in: field. Saving the path to C:\Program Files\MATLAB\R2010a\toolbox\local\pathdef.m works fine again. (( 1. USERPATH returned empty 2. Thus, I run >> userpath('reset') 3. Now userpath returns C:\Users\poi\Documents\MATLAB; (BTW: "Documents" is shown as "My Documents" by Windows Explorer.) 4. However, that folder is empty and I don't think I ever used it. Sometimes, both now and with my old PC, Matlab starts in "C:\Windows\system32" and I cannot understand why. )) QUESTIONS: 1. Where is "the best" place to keep pathdef.m? Should I leave the Start in: field empty? What about USERPATH? 2. I did not find a "Switch search path tool" in the FEX. (However, File ID: #23218, Project Manager, by Sung Soo Kim, does it and more.) Which are the most important things I should think about if I try to make a "Switch search path tool". Updating Matlab realese is certainly one. IMO: Matlab sometimes behaves mysteriously and in many cases the documentation could be more helpful, e.g. the documentation of USERPATH. / per
From: Gregory Teplow on 6 Aug 2010 17:43 I think that I had the same problem in Windows 7. SOLUTION!: in Windows 7, change the "permissions" for the user account that you are using so that you can write to that folder. (I editted the permission for C:\Program Files\MATLAB) I changed mine to "full control" so that I could do whatever I wanted, but less permission might work too. Hope that helps!
First
|
Prev
|
Pages: 1 2 3 Prev: GUI and external functions + popupmenu value problem Next: 3D Tumor Display |