Re: Printing to a file and fBsyErr

• Subject: Re: Printing to a file and fBsyErr
• From: "James W. Walker" <email@hidden>
• Date: Mon, 3 Oct 2005 16:41:37 -0700
• Delivered-to: email@hidden
• Delivered-to: email@hidden

jeremy <email@hidden> wrote:

I have not  been able to reproduce this in a standalone xcode
application, but I can get it to consistently happen in our app.  We
have tried calling FlushVol(), opening and closing the file with
different OS calls (FSpOpenDF originally, then also HOpenDF and
FSOpenFork) among other things.  Theories here range from "the OS
possibly 'indexing' this file and having a lock on it" to "the print
session not being entirely closed by the OS at this time".

How about "antivirus software checking the file for viruses"?
--
  James W. Walker, ScriptPerfection Enterprises, Inc.
  <http://www.write-brain.com/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden

• Prev by Date: Printing to a file and fBsyErr
• Next by Date: Re: Printing to a file and fBsyErr
• Previous by thread: Printing to a file and fBsyErr
• Next by thread: Re: Printing to a file and fBsyErr
• Index(es):
  • Date
  • Thread