Help - Connecting to WindowsNT server - LOOK!

[srobert]

Ok. I'm a lonely Mac working in a all PC company.

I'm hooked on a windows NT server for emails and so that my files get backed-up every nights.

I always have trouble connecting to the server since I upgraded to 10.3.

Here is what I see when connecting with classic's chooser. (That's good by the way):

And here is what I get when I connect using Panthers Network Browser (and it's Wrong!:

You'll notice I can't see the icons of my files and My Quark application (4.1) won't even open them using the open command. You'll also notice that my color labels are gone.

Here is a zoomed view of the mysterious unrecognizable quark files:

http://homepage.mac.com/srobert/.Pictures/thumbnails/zoomed_icon.jpg

Also, when browsing around on the server using OSX, I often see mysterious icons called "Icon*" that I don't see using classic's chooser. My guess is that those files are normally invisible to the mac. But somehow, I can see those with panther. Here is a pic:

Can anyone help me with this?

Any help would be VERY appreciated.

Thanks in advance

 

[wrldwzrd89]

Ok. I'm a lonely Mac working in a all PC company.

I'm hooked on a windows NT server for emails and so that my files get backed-up every nights.

I always have trouble connecting to the server since I upgraded to 10.3.

Here is what I see when connecting with classic's chooser. (That's good by the way):

And here is what I get when I connect using Panthers Network Browser (and it's Wrong!:

You'll notice I can't see the icons of my files and My Quark application (4.1) won't even open them using the open command. You'll also notice that my color labels are gone.

Here is a zoomed view of the mysterious unrecognizable quark files:

http://homepage.mac.com/srobert/.Pictures/thumbnails/zoomed_icon.jpg

Also, when browsing around on the server using OSX, I often see mysterious icons called "Icon*" that I don't see using classic's chooser. My guess is that those files are normally invisible to the mac. But somehow, I can see those with panther. Here is a pic:

Can anyone help me with this?

Thanks in advance

Any help would be VERY appreciated.
Those files have somehow lost their type and creator information, which Quark needs to recognize the files. Also, the labels are stored in the same place that the file type/creator is (the resource fork), so I suspect that something funny's happening with the resource fork in Panther of those files. One possibility is that the labels and file type/creator data is actually stored locally on your hard disk in a place that Classic knows about but Mac OS X doesn't. Someone may have changed the Mac compatibility settings on the Windows NT server, which could also be screwing things up.
<edit> I mistakenly put my reply inside the quote of your post. That's fixed now.</edit>

 

[srobert]

Someone may have changed the Mac compatibility settings on the Windows NT server, which could also be screwing things up.

What's starnge is that it works fine ic Classic but not in Panther. Those previous screenshots were taken from the same computer on the same hour.

 

[dudeami]

This seems to me like it my be an issue with Quark 4.1 running in classic mode when booted to 10.3.

Quark 6 is compatible, and will run natively in OS 10.3.

Are there difference when accessing the share from OS 9 and OS 10, like do you use appletalk in OS 9, but SMB in OS 10.

 

[srobert]

This seems to me like it my be an issue with Quark 4.1 running in classic mode when booted to 10.3.

Quark 6 is compatible, and will run natively in OS 10.3.

Are there difference when accessing the share from OS 9 and OS 10, like do you use appletalk in OS 9, but SMB in OS 10.

Quark? Hmmm... maybe. But it did work fine in 10.2.

Appletalk is on in panther.

 

[wrldwzrd89]

Quark? Hmmm... maybe. But it did work fine in 10.2.

Appletalk is on in panther.

This suggests that you are having crossed protocol issues when using Mac OS X. Mac OS 9 doesn't know about Samba, so it doesn't get confused. Mac OS X, on the other hand, does use Samba. With both Samba and AppleTalk active, Mac OS X might be getting confused about which protocol to use and might be using the wrong one (Samba instead of AppleTalk).

 

[srobert]

This suggests that you are having crossed protocol issues when using Mac OS X. Mac OS 9 doesn't know about Samba, so it doesn't get confused. Mac OS X, on the other hand, does use Samba. With both Samba and AppleTalk active, Mac OS X might be getting confused about which protocol to use and might be using the wrong one (Samba instead of AppleTalk).

Solution? ^_^

 

[dudeami]

Ok I didn't know you were using 10.2 originally.

Have you update the OS to 10.3.3? Those updates had some corrections to browsing and applications running in classic mode.

However, there is no application installed for OS X on your machine that can open those files. The application you have is an OS 9 version, so you might expect to see different icons when viewing the file with an OS that has the Application installed like OS 9 chooser, and when viewing it with an OS that doesn't haven't installed like OS 10.3. If you don't already have 10.3.3 installed, maybe this will help OS X associate the file with the OS 9 Application.

Also could you elaborate on the problem opening the files from the Quark 4.1 menu. Does it let you browse to the directory? Can you see the file when you have browsed to the directory in the open file window? Do you get a permissions error, or an application error? Do you only access Quark files on the mounted network drive? Can you save a New test quark file to the mounted network drive?

 

[wrldwzrd89]

Solution? ^_^

Try turning off SMB temporarily in Directory Access.

 

[dudeami]

Here is another thing to try.

When you are browsing the mounted network drive in OS 10.3.3, right click on one of the Quark files, or ctrl-click if you have a one button mouse and choose get info. Alternately you can highlight the file and hit open-apple-I.

In the get info window, pull down the Open with: box and choose the quark 4.1 application. you should see this application towards the bottom, there should be different sections in the drop down selection box. The first section should contain the current default application that OS X will try to use to open that file type, the next section should be a list of OS X applications that the OS thinks you can use to open that file type, the next section should be a list of OS 9 (Classic) applications that OS X thinks you can use to open that application. If you see Quark here choose it, if not go to the last section which is Other... section and browse to the quark 4.1 application and choose it. Now that you have selected Quark 4.1 to open this file, associate all files of this type with Quark by hitting the Change All button in the Open with: section of the Info window. Then close the Info window. You should see the Icon of those files change to the Quark looking icon that you see in Classic. Then try double-clicking the file to open. If OS 9 is not already running in emulation, then you should see both the OS 9 startup Icon and the Quark 4.1 icon opening in the dock.

Hope this helps.

 

[srobert]

Got an inyteresting explanation on an anothoher forum from a guy named John:

The problem you are seeing has to do with resource forks and how different versions of Mac OS access servers.

In Mac OS prior to OS X, the ability to access Windows servers using the native Windows protocol (SMB) was not part of the OS. Meaning that, you either needed to install a third party plug-in like DAVE on all of your clients, or you had to install Apple File Protocol support on your Windows Server. Judging by the screenshots above, I'd say that your company decided to go with the latter. This means that the NT Server is sharing out both SMB and AFP.

Starting with Mac OS X (10.1, technically), the Finder has had the ability to mount SMB shares natively. Meaning that a plug-in like DAVE is not required to access Windows Servers using the SMB protocol.

Why does all of this matter? Resource forks. AFP services (which is what your Classic's Chooser shows by default) are resource fork aware, while SMB services (which is what Mac OS X's Finder shows by default) are not resource fork aware. So when you attempt to access the files in Mac OS X, you are not getting critical parts of the file data. That's why your Quark files don't work properly. Part of their metadata is missing.

So... how do you fix it? Well, the problem is that you are accessing the NT server using SMB. Instead, use AFP. Manually mount the necessary share in the Finder by selecting Go -> Connect to Server. Then, enter afp://ntserveraddress/sharename and connect. Now when you look in the share, you'll see the Quark files will work properly.

Coincidentally, the other files you mentioned are along the same lines. The files you are talking about have an AFP "Hidden" attribute, which is not supported by SMB. So when you look at the share using SMB, you see the files. When you look at it with AFP, they are hidden properly.

I'll try it right now...

 

[7on]

adding an extension to those files should work

I icon file is normal. it is a custom icon for the folder it is in.

 

[wrldwzrd89]

Got an inyteresting explanation on an anothoher forum from a guy named John:



I'll try it right now...

That's what I suspected the problem was. I just didn't explain it very well.