Brisque4-InkPro -> longer Output-Filenames possible?

[fighterofglory]

Hello,

we use for our Jobs often long filenames to exactly identify them.

But when InkPro is running on them, the Output-Filenames are cut off to 31 Characters like this:

Input-Filename: ReallyLongJobFilename.job
Output-Filename: lyLongJobFilename-S1-W1-F0.ch_c

These filenames take our printers much time to identify the right CIP-Job for the right Print-Job.

Is there a way to say InkPro that it won't cut off the filenames? Until now I couldn't find any way, even output on a NT-Server is no solution.

Maybe it is possible with the Brisque 5 Update?

Thank you and sorry for my bad English!
Hope you can understand everything.

[zox]

Heck, I didn't know there was a client for NT??
Anyway we are using it on Mac and I suppose that is limitation of a Mac.
I think NT is also limited in a similar way but don't hold me to a word.

If there is a client for NT, did you try running it on Win2000 as I know for sure Win2000 and up have no problems with long file names.

There is an option of renaming after you've done inkpro.

Sorry if I am no good help

[fighterofglory]

There is no NT-Client, but you can mount a NT-Volume on the Brisque.

Maybe it is really a limitation, so the InkPro-Mac-Software can handle the filenames.

Manually renaming is not really useful, as we are processing many jobs in an automated workflow.

I don't know, if the Brisque 5 Update enables longer InkPro output filenames.

Thanks anyway!

[gig0]

I'm not familiar with InkPro at all but am with the Brisque so I'll take a stab.

I can tell you that the NFS (Unix file system) has a 32 character limit. You need to name the jobs shorter otherwise you'll run into other problems like trapping because the Brisque renames trapped files.


Also, how are you mounting an NTFS volume to the Brisque (NFS)? Those are 2 different file systems which UNIX doesn't do natively unless you're using a third party utility, like Samba.

[fighterofglory]

Thanks!
I didn't know, that Unix has this limitation.

I haven't set up the Windows NT Server, from which I have mounted the volume, but I think you have to run a NFS-Service on it.

[zox]

gig0, I think you've got it wrong here.

NFS does not have 32 characters limit, it is netatalk that is limited to 32 characters.
netatalk is Apple talk service on Unix/Linux.
The only reason netatalk has this limitation is actually MacOS limitation, so there you have it , it all comes down to old Mac again.

[jim_t]

Best advice i always give is to keep your file names short and don't use any wildcard characters it will prevent alot of headaches in the longrun.

[gig0]

Originally Posted by zox

gig0, I think you've got it wrong here.

NFS does not have 32 characters limit, it is netatalk that is limited to 32 characters.
netatalk is Apple talk service on Unix/Linux.
The only reason netatalk has this limitation is actually MacOS limitation, so there you have it , it all comes down to old Mac again.

My bad. Thanks for clarifying.

I should have known because Windows file servers do the exact same thing with SFM installed. Thanks Apple!