Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Non descriptive naming

Status
Not open for further replies.

kylebellamy

Programmer
Jan 24, 2002
398
US
When sending plate negs to the RIP station I use, since my upgrade to OS 10.2, the name of the file which used to be something like "#9-7-2365(K)" which includes the job number and color, has become just "(K)" with none of the other stuff. Anyone have an idea what has changed and what to do about it?

Quark 5
OS X 10.2.6 ( I think... the latest patch)

Incendentaly, It works fine in Pagemaker.
 
If you are referring to an apparent file name change from OS9 to OSX, get used to weirdness like that - - and start renaming your documents and linked files. OS9 and below was way too forgiving with what kind of crazy characters that you could include in a file name (#, /, etc.). I suspect there are a lot of Mac users that need to learn how to name files for the new millenium. You would find the same weirdness if you tried to use the file on Windows.

- - picklefish - -
 
Actually, the print server that runs the RIP has OS 8.5 on an 8500/120 (upgrading that whole system shortly) so the filenaming is going from 9 to 8.5 and has never had this trouble before.
 
So where is the OS10.2 coming into play?

- - picklefish - -
 
This didn't begin happenening untill the upgrade to 10.2.
Before that I had 10.1 going with Classic and it worked great. Since then it's lost the file name that was listed in the print que and only show the color. In my case its a lot of black so I have a long line of (K) and no distinction as to what's what.
 
Ok, new developments in the mystery.

From the Mac that was just upgraded to OS 10.2, the file name shows up fine in the print Que ie. "#9-7-2430 (K)" but from the new G4 which I had to install Quark 5 and update on I get just the (K). So where do I go from here?

Does this sound like a Printer problem? Should I copy the preference file for Quark from the working machine to the new one? Is it a quark setting at all?
 
From reading the previous posts, I can't quite follow what kind of set up you have. Is it a print server running OS 8.5, and two other Macs, one with OSX 10.1, and the other 10.2? Maybe you could spell out the exact configuration, because it seems a little vague. Specify the configuration that works, and the one that doesn't.

Perhaps you could also try renaming your files, as jimoblak suggested, and see what the results are. For example, change "#9-7-2430 (K)" to "9_7_2430 K" and see if it works. This information could help narrow your problem down.

I don't know if this is related or not, but could it be the length of the file name? If it has more that 31 charactors, OSX has no problem with it, but previous versions of Mac OS might have problems. I know longer file names show up differently in Quark 5's 'Open' dialog box, and they include # signs, so maybe this is confusing the OS.
 
Ok here goes:
Mac 1 - Upgraded from OS 9.2 to 10.2 with classic. Dual G4 500Mhz. Quark Xpress 5.1

Mac 2 - New G4 1.25Mhz with preloaded OS 10.2 and classic. Quark Xpress 5.1 loaded by me onto machine.

Mac 3 - PowerMac 8600 which has RIP software to run neg printer. OS 8.5

Mac 1 prints fine with file names intact in the print que. My previous G3 had 10.1 and it printed fine. Pagemaker prints fine on the Mac 1 and 2. Everything but Quark on the new machine sends the file name along with the file to the RIP. I guess I'm looking for a setting or something that allows my upgraded machine to send this info, pound signs and all, to the RIP server. It has to be something like that because it does work on the upgraded OS. Just not on the new machine.
 
As an update, I finally took the ultimate step and installed OS 9.2.1 over the existing OS 9.2.2 from an upgrade disk I had from my last Mac. Then d/led the 9.2.2 update and installed and everything is fixed.

This is wierd but the version pre-installed on my new machine must have been messed up or lacking something because everything works great now. Go figure.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top