Article View: comp.sys.acorn.tech
Article #646Re: Finding the CSD
From: banks_p
Date: Wed, 16 Dec 1992 00:46
Date: Wed, 16 Dec 1992 00:46
21 lines
1326 bytes
1326 bytes
In article <1gke2bINN2up@swan.doc.ic.ac.uk>, mybg@doc.ic.ac.uk (M Y Ben Gershon) writes: > dbh@doc.ic.ac.uk (Denis Howe) writes: [bits deleted] > -Set FS <FileSwitch$CurrentFilingSystem> > -SetEval CSD "<FS>:"+FileSwitch$<FS>$CSD > > I am sorry to disappoint you, but this does not work either! It remains > constant and is not altered when the csd is changed. Of course it doesn't. It is not a code variable. To do what you want would reqire writing some short assembler. This approach is designed to allow you to find out the CSD at a *particular point in time*. This is useful for Obey scripts that need to know the CSD or whatever but is by no means intended to be a continually updating CSD variable. And of course it is considerably simpler to do than repeated calls to OS_GBPB and popping up directory layers which was what was required under RO2. Philip
Technical Details
Message-ID:
<1992Dec16.124633.1@kosmos.wcc.govt.nz>Path:
arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!comp.vuw.ac.nz!newshost.wcc.govt.nz!kosmos.wcc.govt.nz!banks_pReferences:
<1gke2bINN2up@swan.doc.ic.ac.uk>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!comp.vuw.ac.nz!newshost.wcc.govt.nz!kosmos.wcc.govt.nz!banks_p From: banks_p@kosmos.wcc.govt.nz Newsgroups: comp.sys.acorn.tech Subject: Re: Finding the CSD Date: 16 Dec 92 12:46:33 NZST Organization: Welligton City Council, Public Access. Lines: 21 Message-ID: <1992Dec16.124633.1@kosmos.wcc.govt.nz> References: <1gke2bINN2up@swan.doc.ic.ac.uk> NNTP-Posting-Host: kosmos.wcc.govt.nz