just run from terminal

ls -la

if you don’t see VCTTolls there then it’s not there, obviously


as far as I remember when you upgrade to 10.15 all not system folders in the 
root were moved to the folder

/Users/Shared/Relocated Items


also you should check folder /System/Volumes/Data not /Volumes/


/System/Volumes/Data - is a mounting point to the volume "Macintosh HD - Data”

hope it will help

dm


> On Jun 27, 2021, at 12:59 PM, Neill Smith <[email protected]> wrote:
> 
> In response to Dimitry I ran the following in Terminal
> 
> Neills-MacBook-Pro:~ neillsmith$ ls -la /VCTTools
> 
> ls: /VCTTools: No such file or directory
> 
> Neills-MacBook-Pro:~ neillsmith$ xattr /VCTTools
> 
> xattr: No such file: /VCTTools
> 
> 
> Did I do this correctly?
> 
> Neill
> On Sunday, June 27, 2021 at 12:36:17 PM UTC-4 Neill Smith wrote:
> Further information. I suspect you all are correct about a security file 
> system problem.
> 
> As I noted earlier, the BBEdit script HydroV_dbg.scpt  is invoked from within 
> BBEdit from a GEO file. The BBEdit SCPT file in turn invokes the AppleScript 
> file hdbgsub.sh. This script file runs a compiled program HydroV that reads 
> the GEO file and outputs a slew of files that are then used by other compiled 
> programs.
> 
> The reason for executing the GEO file from within BBEdit is to make sure it 
> is correct. Part of the BBEdit SCPT file opens the OUT file produced by 
> HydroV so that it can be checked.
> 
> Once a GEO file is correct, a number of Matlab programs use it. These Matlab 
> codes directly run the AppleScript file hdbgsub.sh with the GEO file as the 
> input. Other programs are then run under Matlab from the output files that 
> are created by running the GEO file.
> 
> Now the Matlab file that runs the AppleScript SH file hdbgsub.sh directly is 
> called rung.m
> This file works under either the Mac OS or the Win OS. A piece of the code 
> from rungeo.m is shown below.
> 
> if ismac
> 
>     slash = '/';
> 
>     root = 'bash ';
> 
>     ext = '.sh';
> 
> else
> 
>     slash = '\';
> 
>     root = 'C:';
> 
>     ext = '';
> 
> end
> 
> [Hstat Hmsg] = 
> system([root,slash,'VCTTools',slash,'bat',slash,'hdbgsub',ext,' ',filename]);
> 
> 
> 
> Basically, this snippet either calls  hdbgsub.sh or  hdbgsub.bat depending on 
> the OS.
> 
> This is a long winded way to get to my new info.
> 
> I directly ran rungeo.m so that it would go directly to hdbgsub.sh. I got the 
> following message.
> 
> bash: /VCTTools/bat/hsub.sh: No such file or directory
> 
> If I try to CD from my test directory to /VCTTools directly I get
> 
> K>> cd
> 
> /Users/neillsmith/NSS_Office/Veh/Low_Re_Tests
> 
> K>> cd /VCTTools
> Error using cd
> Cannot CD to /VCTTools (Name is nonexistent or not a directory).
> 
> So in Finder I can get to /VCTTools and edit files. BBEdit can open files 
> under /VCTTools and edit them.
> But other programs don't see this directory /VCTTools.
> 
> So what is the best fix that doesn't involve a lot of path edits and break 
> the simple SVN update process?
> 
> I really appreciate all of your help.
> 
> Neill
> On Sunday, June 27, 2021 at 10:58:45 AM UTC-4 Neill Smith wrote:
> In reply to Rich, I executed a Terminal command that I found online yesterday 
> to get back to bash. The response that I got was "No changes" so I don't know 
> if I am running bash or not. How do I tell?
> 
> Will respond to other responses later. Gotta go get sick wife breakfast.
> 
> Thanks,
> 
> Neill
> 
> On Sunday, June 27, 2021 at 10:34:51 AM UTC-4 Neill Smith wrote:
> I need to learn to proof better. I have read & write permissions on all files 
> and folders.
> 
> On Sunday, June 27, 2021 at 9:46:56 AM UTC-4 Neill Smith wrote:
> In response to Kreme earlier. I checked the permissions on\VCTTools using Get 
> Info. I have had & write permissions. Everyone else has read permissions. The 
> same permissions hold for the SH file hdbgsub.sh.
> 
> Is there some other way to check permissions other than Get Info?
> 
> On Sunday, June 27, 2021 at 9:38:16 AM UTC-4 Neill Smith wrote:
> 
> Yes it does exist.  I can open that file (and any other SH file) in 
> AppleScript and edit it. I can open it directly using BBEdit but of course it 
> looks like garbage.
> 
> This particular setup is from when my former company used Windows. On a WinPC 
> having VCTTools at c:\VCTTools on every computer meant anyone could add a new 
> tool (VCTTools was maintained in a SVN repository) to VCTTools and then 
> everyone could just update their VCTTools copy. No one had to edit paths for 
> their computer.
> 
> When we moved to MacOS, VCTTools was placed at the ROOT LEVEL to get the same 
> effect. Files within VCTTools have paths set under this assumption. If 
> VCTTools were a folder under a USER under MacOS, any one updating to the 
> newest version would have to go in and edit paths in a bunch of files.
> On Sunday, June 27, 2021 at 7:47:55 AM UTC-4 Ulrich Kapp wrote:
> Hi Neill,
> 
> Did you check whether the script file /VCTTools/bat/hdbgsub.sh does exist?
> 
> Ulrich
> 
> 
>> Am 27.06.2021 um 01:10 schrieb Neill Smith <[email protected] <>>:
>> 
> 
>> I recently upgraded  my macOS from High Sierra to Big Sur. A script file 
>> that has run for years under BBEdit (and TextWrangler before) has quit 
>> working. The script is invoked from within a file [fname].GEO by picking the 
>> script from my scripts list in the BBEdit top bar. The script runs a program 
>> that reads the [fname].GEO file.
>> 
>> Now the script doesn't run. I get the message
>> 
>> A scripting error has occurred:
>> 
>> sh: /VCTTools/bat/hdbgsub.sh: No such file or directory
>> 
>> This directory does exist. I uninstalled BBEdit and did a clean reinstall. I 
>> had to contact BBEdit tech support in order to install the Command Line 
>> Tools because old versions of the tools had to be removed manually.
>> 
>> I didn't write the original script. It was created by a colleague years ago. 
>> BBEdit tech support recommended that I contact this group.
>> 
>> Thanks,
>> 
>> Neill Smith
>> 
> 
>> -- 
>> This is the BBEdit Talk public discussion group. If you have a feature 
>> request or need technical support, please email "[email protected] <>" 
>> rather than posting here. Follow @bbedit on Twitter: 
>> <https://twitter.com/bbedit <https://twitter.com/bbedit>>
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BBEdit Talk" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/bbedit/a8fc6e58-41f0-4ea1-9180-efea41378b86n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/bbedit/a8fc6e58-41f0-4ea1-9180-efea41378b86n%40googlegroups.com?utm_medium=email&utm_source=footer>.
> 
> 
> -- 
> This is the BBEdit Talk public discussion group. If you have a feature 
> request or need technical support, please email "[email protected]" 
> rather than posting here. Follow @bbedit on Twitter: 
> <https://twitter.com/bbedit <https://twitter.com/bbedit>>
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BBEdit Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/bbedit/69cdc568-9dcc-4cbb-997c-506192307470n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/bbedit/69cdc568-9dcc-4cbb-997c-506192307470n%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "[email protected]" rather than 
posting here. Follow @bbedit on Twitter: <https://twitter.com/bbedit>
--- 
You received this message because you are subscribed to the Google Groups 
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/30F36062-9D71-4A89-9E1F-6FB2A660C9F5%40mac.com.

Reply via email to