Article View: adobe.framemaker
Article #21823.lck Files in Classic Mode
From: anthony garone
Date: Wed, 22 Jan 2003 18:16
Date: Wed, 22 Jan 2003 18:16
3 lines
1551 bytes
1551 bytes
I am the support person for the group at ASU which produces the general catalog. Recently, we upgraded our computers and are using OS X throughout the office. Of course, we have to run a few things in classic mode, such as Framemaker. The problem we are facing is that the .lck files are ineffective when running Framemaker in Classic mode. In other words, even if the .lck file is created in the directory with the original file on our network server, the user is not prompted that the file is currently in use by another user. Is there a workaround for this? Has anyone else seen this or experienced it? We are using Framemaker 7 on eMacs and G4 towers with the files being hosted on a G4 running OS X Server 10.1.4. We are all using OS X 10.1.5 on the user machines. Thanks in advance!
Technical Details
Message-ID:
<1de77fc6.-1@WebX.la2eafNXanI>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-09!supernews.com!newsfeed.gamma.ru!Gamma.RU!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.icl.net!newsfeed.fjserv.net!proxad.net!fr.clara.net!heighliner.fr.clara.net!newsfeed01.sul.t-online.de!t-online.de!WebXShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fd315,81636cc4181dafc5,start X-Google-Attributes: gidfd315,public X-Google-ArrivalTime: 2003-01-22 10:38:13 PST From: "anthony garone" <doodie@asu.edu> Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-09!supernews.com!newsfeed.gamma.ru!Gamma.RU!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.icl.net!newsfeed.fjserv.net!proxad.net!fr.clara.net!heighliner.fr.clara.net!newsfeed01.sul.t-online.de!t-online.de!WebX Newsgroups: adobe.framemaker Subject: .lck Files in Classic Mode Message-ID: <1de77fc6.-1@WebX.la2eafNXanI> Date: Wed, 22 Jan 2003 10:16:38 -0800 Lines: 13 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit