dick_simpson - Apr 22, 2005 - 10:23 am
Hi
Just installed OSX 10.3.2 on my G4 which previously had 9.2. Connect to the server was no problem - I can see everything except for one thing: every Quark file is a "Unix Executable File"...
Here's what I have tried:
I have made sure the extensions were viewable - same thing
Tried to make the quark files open with quark in the "open with" dialog box - I can make it choose quark, but it still won't open
pulled some hair out
I actually got it to work ONCE this morning on a laptop that was connected to the server, then, when I went back to show the person how to do it, it wouldn't work - nice. I have done the exact same thing every time, so something isn't right...
I noticed that the folder on the NT server is a lower-case name, but when I connect it changes to all upper-case on the desktop - does th is matter at all????
PLEASE HELP!
10+ year mac user who really didn't want to go from os9 to 10, but felt it was time to do it - now I am wondering what have I done?
ericl - Apr 22, 2005 - 1:26 pm
Hi Dick - I'll need some more info:
I am assuming the following:
(1) Files were created/modified on the Mac under os9, stored on a NT host & accessed from the Mac via a NT share
(2) Mac was upgraded to osX, nothing else was changed, then this problem occurs.
Please confirm/embellish the above
From what interface/host/application does the "Unix Executable File" message appear?
get back to me with this info
Thanks, Eric Lilleness
--------
dick_simpson - Apr 22, 2005 - 2:02 pm
OK
you were right on both (1) and (2) as well as the rest
Files were created on mac OS9 and stored on an NT server. Then, when I loaded the OS10 on the G4, all the quark files espcially (but others too) were this strange icon that a "get info" says is that Unix file. After about every which a way of connecting to the network (changing IP addresses, ect. all with the same result)I did the following:
Changed my startup disk to the CLASSIC OS9 (which I had to load on there as a clean install) and presto! things were back to normal- at least in the respect of the Quark files.
So when I change the startup to the OS10, It goes right back to the old icon thing - that makes me think it's a OS10 problem and not a quark problem...right? ALso there is a laptop with OS10 here that has always done that and I figured there was no workaround for it - hope you can offer some advice to fix em both
hmmm...making sense? Hope so, cause I am one inch from dumping it in the lake and buying a Dell.
Dick
ericl - Apr 23, 2005 - 4:54 pm
Hi Dick - what environment are you in when you see the "UNIX executable file" message?
Are you running Quark in OS9 or OSX?
Thanks
Eric Lilleness
--------
dick_simpson - Apr 25, 2005 - 7:58 am
Only in os10
ericl - Apr 25, 2005 - 10:26 am
Got some good news & some bad news. I have been able to somewhat duplicate part of your problem - I had to use the UNIX command line to do it.
Let me recap what I believe to be your situation:
(1) Your Mac ran os9 & Quark for OS9. The file created with Quark are stored on Windows.
(2) You upgraded the Mac to OSX & Quark for OSX
(3) You now cannot open any of the old files with Quark, and the Get Info function of OSX Finder says the files are UNIX executable files
Dick, please confirm the above in DETAIL!!!!!!!!!!!!!
Try the following:
(A) on the Mac, create a new Quark file. Save it locally on the Mac. Use getinfo on it. Tell me what getinfo says.
(B) Call the same file back up into Quark. Does it work?
Now do a "save as" on the Windows host. Use getinfo on it. Tell me what getinfo says. Now try to call the file saved on Windows back up into Quark. What happens?
Now, for my guess as to what is happening:
A big difference between OS9 & OSX is that OSX is UNIX. UNIX has file permissions. When you store a file like this on Windows, Windows puts this file into a Windows filesystem that does not always know what to do with UNIX file permissions - the results will probably vary between what version of Windows you are using.
Windows is changing your file permissions.
I tried changing the permissions on a PDF file to duplicate your problem. Getinfo sayed it was a PDF file. I tried the same thing on a generic file I created using the "touch" command. Getinfo sayed it was a "UNIX executable file".
It appears that Adobe Acrobat can handle a permission change with barfing and that Quark cannot. Without having Quark I cannot confirm this.
This puts the blame on Quark if all my assumptions are true - you need to confirm/verify these and report them in detail please.
Thank you
Eric Lilleness
--------
dick_simpson - Apr 25, 2005 - 10:51 am
hmmm
that's alot, but here goes:
First, I upgraded the OS only - still using the same Quark as always.
I tried what you suggested already, I think. That is, I made a new .qxd while in OS10 and saved on desktop - no problem saving or opening it - I could also read other quark docs on my hard drive(s) in OS10 - however, every quark doc on the NT server showed up as the UNIX thing...not to mention every other document that did not have an extention - as most mac files do not (like tifs or pagemaker or whatever)...
Of course, I am back to running OS9.2 and everything is as it was before - I just had to erase my h/d to get this far (bummer) - so looks like Quark is the problem. The permissions thing has got to be the problem.
the problem definately is Quark, but I don't think it's all their fault for 1 reason.
I still have an NT server, which is, of course, dead in the water---so here's the kicker...
IF I upgrade the server to Windows Server 2003 (I will have to buy new Hardware AND all the windows licenses and crap -- probably around $4,000)will the OS10 probelem be resolved or am I still going to have the permissions problem???
so now, that is the question I think
DICK
ericl - Apr 25, 2005 - 2:32 pm
I think that as long as you make files on a Windows host available to your Mac via a Windows "share" you will have this problem - Quark has a hairball with any file that has executable permissions turned-on, AND Windows is totally incapable of turning-off executable permissions. That's one BIG reason Windows is so darn insecure; you can't just remove the execute permission, so people hide executable code in files that a reasonable person would think should not contain executable code.
Now, there are other alternative ways to use a Windows host to behave as a file server for other operating systems.
The method you are currently using is Microsoft's proprietary CIFS (Common Internet File System).
The other method is the Open systems (every other computer but Microsoft) NFS (Network File System). This was developed by Sun Microsystems and is tha "standard" way for doing file sharing.
Microsoft offers a few different ways to make their O/S run NFS. The free way is to download SFU (Services For UNIX from Microsoft. The other good thing about SFU is that it runs on XP Pro, a tad bid cheaper than Server 2003.
If it were my computer system, I would only run Windows where I had to (No workaround).
Your best solution probably hinges on why you are storing files used on your Mac on Windows.
If you care to share this, I am a storage consultant & can help.
Dick, you did a great job of answering my questions, thanks.
Eric Lilleness
--------
dick_simpson - Apr 25, 2005 - 3:41 pm
hmmm - I have done this for quite a few years and this is the first thing I couldn't work around myself
btw - I avoid windows like the plague - unfortunately, our office software is all windows, so I have to use mac and win
the server we have hosts all our files for both the mac and win
ok, mostly mac files - the company books and other software is probably about 10-15% of the total gigs used
I suppose the fair thing to say is that when the computer people (local) I hired to wire up the newtork and such partitioned the server and said there was no problem having both mac an win files on the same drive, I should have known better
Hindsight - besides they LOVED NT!
DS
ericl - Apr 26, 2005 - 10:20 am
Hi Dick. You may also be able to pursue a remedy via Quarck, and like I have said, the root cause of your problem is all "Expert Opinion" until proven by test. The test requires runung a few UNIX commands in a terminal window on OSX.
Let me know what you want to do
--------