Subject: HELP: QX document damaged
From: Dejan Muhamedagic (dejan@quant-x.com)
Date: Tue Feb 01 2000 - 04:27:10 EST
Hello,
Yesterday was not a good day for netatalk/Quark. One of the
QX documents has been damaged. The document has been
created before and yesterday a user wanted to make minor
corrections just before printing. The document has been
opened OK, changes done, but then, when he wanted to save
the document back, MAC reported error -50. As this is
happening from time to time, user went on to do some other
things and just left QX running as it was. Then his MAC
wasn't responding anymore (it crashed for I don't know what
reason) and he had to reset it. From this point on it was
not possible to open the document anymore.
I've peeked into it and it looks normal, i.e. it's beginning
and ending look as in other QX docs, but then I'm no expert
on QX doc format. Tried to attach .qxd to its name---didn't
do any good.
afpd only reported that the client was not responding
anymore thus shutting down the connection but this was due
to a crash and not to a "file save error".
My users/customers/friends are a little bit worried. The
document in question was an ad worth a few hours of work.
What if it's been a 200 pages book and the dog ate last
night's backup tape. Some serious talks are due and I've
really no grounds to claim that their work is safe with
netatalk/Linux.
Now, I *really* need some assistance here, if possible. I'm
not able to find out what's going on and I don't know where
to start. On one side, QX behaves like a madman and on the
other afpd doesn't seem to take any notice. As if they
speak different languages. How should I approach this
problem? Is there a debugging tool of some sort or do I
have to burry myself in the source code? Anybody willing to
take a look at the "damaged" QX document? I've got to
resolve this and fast, otherwise...
Today I'm going to install the 37b version. I also have
there installed 2.1.3, but I'm not sure is it wise to go
back. Any advice on these? Perhaps I can use some other
version. Anybody over there using QuarkXPress v3.32?
I'll attach below my previous message to this list regarding
the similar problem to which nobody responded.
Cheers.
Dejan
----- Forwarded message from Dejan Muhamedagic <dejan@quant-x.com> -----
Date: Thu, 27 Jan 2000 16:00:31 +0100
From: Dejan Muhamedagic <dejan@quant-x.com>
To: netatalk-admins@umich.edu
Subject: quark and linocolor save file problems
Reply-To: Dejan Muhamedagic <dejan@quant-x.com>
Organization: Quant-X Service & Consulting Ges.m.b.H.
X-Operating-System: Linux 2.2.13 (i686)
Resent-From: netatalk-admins@umich.edu
X-Mailing-List: <netatalk-admins@umich.edu> archive/latest/165
X-Loop: netatalk-admins@umich.edu
Resent-Sender: netatalk-admins-request@umich.edu
Hello,
I'm in a process of moving a neat pre-press company from
Helios/Irix to netatalk/Linux/Alpha. There have been
several problems with Quark and Linocolor (the scanning
app). The netatalk installed is pre-asun2.1.4-36a, but I'm
hoping to upgrade to 37b in next few days.
Linocolor is, sometimes (around 60-70% as claimed by users),
not able to save the scan to a volume. The interesting
thing is that the application gives document a name like
"Scan 1 1-12633878068", then user is trying to save it under
different name, but the error refers to the original name.
I was not able to find a reference to this application in
the archives.
Quark (v3.32) does not want to do "Save as" and "Save all to
one folder" (please assume that these quotes may not be
exactly as they are---I'm in Austria and all of their apps
are in German). With both, the file(s) is actually saved by
afpd, but Quark reports error -54 and afpd thinks that this
was just business as usual. Because if you try to open the
"Save as..." file, it says that the file is locked (or
already opened, error -49) and it actually is (by afpd). It
seems that there's some kind of misunderstanding between
netatalk and Quark. I've found a single reference to this
error and it boiled down to disabling Autosave feature, but
my users swear that they are not using this. BTW, Passport
v3.31 has no problems with either of these save options.
The old Helios software still works and they have never had any
problems with it, so you may guess just how suspiciously they
look at me.
Many TIA,
Dejan Muhamedagic
--Dejan Muhamedagic mailto:dejan@quant-x.com UNIX and Linux Support mailto:support@quant-x.com
Quant-X Service & Consulting Ges.m.b.H. http://www.quant-x.com Phn: +43 4212 90555-0 Fax: 90555-20 Free: +800 90555 000
----- End forwarded message -----
--
Dejan Muhamedagic mailto:dejan@quant-x.com UNIX and Linux Support mailto:support@quant-x.com
Quant-X Service & Consulting Ges.m.b.H. http://www.quant-x.com Phn: +43 4212 90555-0 Fax: 90555-20 Free: +800 90555 000
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:29:56 EST