Access Your Computer From Anywhere
Control a PC from a Mac over the Internet  


MacWindows: the Web Site for Macintosh-Windows Integration
Click for MacWindows home

MacWindows

Mac OS X Cross-Platform Report

v10.0 to 10.1.5

Last updated May 29, 2003


On this page:

For issues with Mac OS X Server and Windows Clients, see the MacWindows Mac OS X Server Cross-platform Issues page.

For Mac OS X 10.2, see our Jaguar Cross-platform Report page.

Introduction

Mac OS X was released on March 24, 2001&emdash;exactly two years and a day after OS 9.0. Mac OS X is the result of nearly 10 years of research, planning, engineering, and strategy revisions in an effort to create a new generation of operating system for Macintosh. These efforts include Pink, Taligent, Copland, and Rhapsody. (Apple also briefly considered buying BeOS before bout NeXT and OpenStep.) In the end, Apple decided to go with the open source BSD Unix as the core of Mac OS X, running on a Mach kernel. Apple calls this first version an "early adopters" version. It is very stable and a good start, but is not quite finished. (See the John Rizzo's review at CNET.)

Steve Jobs predicted that by they end of the year 2001, Mac OS X would be largest Unix distribution in terms of volume, as well as the largest Java 2 distribution. We asked Jobs about the extent of BSD Unix that is available to the user OS X user. He described OS X as a robust and complete Unix environment. BSD in OS X provides uses with an FTP server and an Apache web server which can be turned on in the Sharing pane of the System Preferences window. The Terminal application, which provides a command line shell, is installed in the Applications/Utilities/ directory. Avie Tevanian, Apple's Senior Vice President of Software Engineering, said that most Linux software should run unaltered on OS X after a recompile. A server based on Mac OS X 10.1 shipped in September.

Though there is little new in the way of Windows integration in OS X 10.0. Cross-platform compatibility suffered in the short term, but bodes well for the long term. It suffers short-term because much of the most popular cross-platform software for the Mac does not yet run on Mac OS X, even under the Classic mode. We should see most of these products ported to OS X by the end of the year.Mac OS X 10.1 improved cross-platform compatibility (see Version history below).

Version History (from 10.0 to 10.1.5)

Mac OS X 10.2. August 24, 2002 -- see our Jaguar Cross-platform Report.

Security Update 2002-08-02. August 5, 2002 -- Security Update 2002-08-02 works for Mac OS X client as well as Mac OS X Server. Apple describes the update:

Security Update 2002-08-02 includes the following updated components which provide increased security to prevent unauthorized access to applications, servers, and the operating system. Apache v1.3.26 OpenSSH v3.4p1 OpenSSL v0.9.6e SunRPC mod_ssl v2.8.10

Version 10.1.5. June 5, 2002 -- The Mac OS X 10.1.5 upgrade includes general enhancements, bug fixes, and new peripherals supported, and several improvements in cross-platform and networking abilities. These include:

Version 10.1.4. April 19, 2002 -- On April 17, Apple made the Mac OS X 10.1.4 upgrade available through the OS X Software Update mechanism. Two readers wrote to say that the upgrade fixes problems with accessing Windows servers that we've reported. Simon Buchanan says that 10.1.4 fixes the SMB window update problem. Apple says this about the upgrade:

Networking Improvements: Dial-up connections over PPP are more reliable and system responsiveness has been improved. Significant improvement to file searching on local and remote volumes. Apple Filing Protocol (AFP) services can be browsed on networks with 3Com routers.

Version 10.1.3. February 20, 2002 -- Available through the Software Update mechanism. In addition to a number of multimedia improvements, the new version of the operating system includes some networking features, including login authentication support of Microsoft's Active Directory service and LDAP. MacWindows readers may remember that we have a discussion of how to authenticate using Active Directory, which is now on our Active Directory Reports page.

WebDAV (used by iDisk) can now authenticate using Digest, be we aren't familiar with what this is. The Mail program now supports SSL encryption as well.

Version.10.1.3 does not fix the Finder crashing problem with Windows servers SFM seen with v10.1.x, or some of the other cross-platform networking problems we've reported.

Versions 10.1.1, 10.1.2. Made available through the Software Update mechanism in System Preferences, there were mostly maintanence releases, without new features or major improvements.

Version 10.1.

September 26, 2001 -- Version 10.1 was a major revision. Apple's Ken Bereskin told MacWindows that every part of the operating system, including the BSD Unix core, was upgraded in this version. There are several important cross-platform enhancements:

A lot of networking software written for Mac OS X 10.0.x will not run on Mac OS X 10.1. This is becuase the kernel was rewritten. Apple sent us a technical explaination, which you can read below.

At the same time, Apple shipped Mac OS X Server v.10.1 (starting at US $499 for 10 clients; upgrade $19.95). Improvements in this version include system -wide performance enhancements, faster file transfer times, and increased reliability. Mac OS X Server v.10.1 includes the SAMBA file server to support Windows clients. Bereskin told MacWindows that it will keep selling its OS 9-based server, AppleShare IP, for the time being for the benefit of Apple's education customers. However, Apple plans to phase out AppleShare IP.

Versions 10.0.2, 10.0.3. These were bug fix updates released in April and May, 2001. 10.0.3 adds support for burning CD-R and CD-RW. Like 10.0.1, these updates were avaible through the Software Update mechanism in System Preferences.

First Mac OS X update, 10.0.1. April 15, 2001 -- Apple made Mac OS X version 10.0.1 available through the Software Update feature in System Preferences. Among the improvements, Apple lists "overall application stability as well as support for the popular Secure Shell service."

Version 10.0. The first version of OS X, released March 24.

Although it included file sharing using the AppleShare IP-compatible Apple Filing Protocol (AFP), it file sharing is not supported over AppleTalk, neither as a client or a server. All AFP file sharing is over TCP/IP. AppleTalk is included for use in printing to network Postscript printers.

OS X includes an FTP server, a Web server, and supports NFS file sharing.

Top of page

Notes of Interest

Disk Note

Unlike OS 9 and earlier, OS X does not support disks formatted in FAT, the PC standard for magnetic media. Rumors on the Internet say that support for FAT16 and FAT32 are scheduled to be added, but Apple would not comment. However, Apple has said that support for new file systems can be added to OS X.

Mac OS X uses MS Windows font formats. March 26, 2001 -- Apple Tech Info Library article 25251 describes OS X using Windows fonts:

Mac OS X also works with font formats used by Microsoft Windows. These fonts have all their data in the data fork and do not have the additional resources found in Macintosh fonts. Mac OS X works with these font formats:
  • TrueType fonts (with the extension .ttf)
  • TrueType collections (with the extension .ttc)
  • OpenType fonts (with the extension .otf)

Top of page
Reader reports:

TIP: Outlook 2001 Beta on OS X

April 5, 2001
Michael Llaneza

I found a glitch that may be affecting a number of people. I had Outlook freezing up if I switched away for any length of time. While I was troubleshooting Classic prefs, I discovered that Classic was set to sleep after 5 minutes. I changed this to 'never' and Outlook hasn't frozen or crashed once since.

For more on OS X issues with Outlook 2001, see our Outlook 2001 Beta special report page.

Top of page

OS X Mail and Exchange Server

See our Outlook 2001 Beta special report page.

Top of page

Sharity for OS X, file size reporting problem

April 26, 2001
Douglas Bergere ran into this problem with using Sharity, a SMB/CIFS file sharing client for Mac OS X for accessing Windows networks.

I am using the free 1 to 1 version. It's a bit pricey but seems to work fine. I have noticed that it reports all files as being 1 MB on a Samba server so the Finder complains that it does not have enough disk space if you try to copy many files at once. Clicking continue lets it copy anyway.

Configuration: Sharity on Mac OS X (4K78) connecting to HP/UX 11 server running HP's SMB implementation. There are too many variables to blame OS X or Sharity. I am looking for confirmation by another user using Sharity.

If you're using Sharity, please let us know if you've seen this problem.

May 29, 2001
Kevin Stevens

I don't have this problem accessing shares on a Win 98 box. File sizes all report accurately. Configuration: Sharity 2.4 1to1, OS X 10.0.3.

Top of page

Citrix Java client on MacOS X setup

April 27, 2001 -- Jonathan Mergy describes how to get the Citrix Java client running on Mac OS X on our Macs and Citrix Application Servers special report page.

Top of page

OS X Classic can't see some directories on Win2K SFM volume from Classic apps

April 30, 2001
Andrew Cunningham reported a problem with Mac OS X Classic as a client to Windows 2000 Services for Macintosh:

I have an odd situation where I have mounted Win2K server SP1 SFM volumes in OS X 10.0.1

The OS X Finder (and native Carbon and Cocoa applications) can see all files and folders on these volumes as it should.

However, when I go to any Classic application, and try and open a file through the standard file dialog, certain ( not all) folders on the SFM volumes are just missing from the standard file dialog. These missing folders do not have long names or anything special about them

If I reboot back into "real" OS 9.1 then all these folders are visible as they should.

May 1, 2001
Roland Miller

The thing that I have noticed is that OS X will not display folders on Win2k servers that you don't have permissions for. While OS 9 puts the "strap" across the folder to indicate that you can't open it, OS X seems to not display the folder at all.

May 1, 2001
Thomas Koons

I have not tried this but I have a similar problem and probably related. When I mount an ASIP server on my OS X system and try to save a file from a classic app to the mounted disk, I get an error message that either said it can't do it or end of file was reached? I don't remember that part but it won't save it. If I save it to the desktop and then drag and drop it on the mounted disk, it copies fine.

I don't think Classic is allowed to talk directly to the mounted disks so it cannot perform certain tasks?

May 3, 2001
Andrew Cunningham

I can add some more on this issue based on others comments:
  • The "missing" folders have full r/w permission, so there is no reason for anyone to hide them
  • If classic can see the folders, then Classic works great on this network volumes.

One of the problems I have having with OS X, that might be related, is as follows

  • Classic is set to mount AFP volumes at startup
  • I already have these AFP volumes mounted in OS X
  • And I then start Classic

I find that some or all of the volumes are unmounted from my OS X desktop after Classic starts, and I need to remount them.

As a side note, I have had a lot of luck with Samba 2.2 (so Windows machines can see my OSX volumes) and Sharity (so I can mount non AFP Windows volumes).

Reader sees similar problem with sharity

May 14, 2001
Gerard Sandoz reports a similar problem with Sharity, an SMB/CIFS client for Mac OS X:

I'm using Sharity onto MacOSX, and I can't open files from the mounted volume with a Classic app (ex: Word). It seems that Classic environment doesn't recognize the SMB volume from a NT 4 server.

Top of page

RedHat Linux 7.0/7.1 failure on VPC 4.0/4.02

May 8, 2001 -- Doron Eren told Connectix that he could not install RedHat Linux 7.0/7.1 on Virtual PC 4.0.2. Connectix replied that it was a known problem. Here is Eren's description of the problem:

I have tried several times to install RedHat Linux 7.1 (and 7.0) on my VPC. At the end of the installation, when the installer tries to write the system loader to the "hard disk" I get a fatal error every time, reporting that there is no such device as /etc/hda. attempts to create a boot floppy to a floppy read/write image also fail. This happens on Linux native partitions & DOS partitions, fixed and expandable. Am I missing something?

Eren said that Connectix replied with this:

Thank you for contacting Connectix Corporation. Unfortunately there are several known issues with Red Hat Linux 7.X. We are looking into the issues. Sorry for the inconvenience.

Top of page

TIP: Citrix client on Mac OS X: Java client runs best

May 26, 2001 -- Charles Soto sent us a report on how to get the Citrix thin/client Mac client to run under Mac OS X. (The Citrix applications server runs on Windows servers.) Soto said version 6.0, build 66 runs fine in Mac OS 9.1, but is slow in OS X Classic. He also tried the Java ICA client in OS X, which is still slower than the Mac client in OS 9.1, but faster than the Mac client running in OS X Classic.

Soto sent us the details of how to get the Java ICA Client running in OS X. He had to use Terminal application to create to shell scripts with Unix commands. You can read it on our Macs and Citrix Application Servers special report page.

Top of page

DHCP problem

We've had numerous reports of DHCP problems with Mac OS 9.2. Some readers also report DHCP problems with Mac OS X 10.0.x:

September 13, 2001
Graeme Bennett (Editor of the Mac Buyers Guide):

We have also been experiencing this DHCP problem. Strangely, we noticed it Sept. 8 and only affects our Mac OS X installation. We're wondering if it could possibly be related to the Unix clock rollover.

We've been reading a growing number of reports of problems accessing DHCP information from within Mac OS X and the problem has suddenly begun affecting our (ADSL) Internet connection in Mac OS X. Mac OS 9.1 on the same machine works fine, and the settings are identical under OS X. For some reason, though, Mac OS X can't seem to negotiate DHCP settings successfully, and can't access external domain names. (Our internal intranet hosts still work.) iDisk volumes still mount, and we can still ping hosts, so we know that TCP/IP is still working. As noted in your report, our Windows machines on the same hub all work fine. It's all quite mysterious.

September 19, 2001
Craig D Sutherland

I also have experienced the DHCP problems you and others described. These started at the time I installed 9.2.1.

Hardware: 733 MHz Tower 768M RAM 10.0.4, 3 partitions- 10.0.4 & 9.2.1, 9.2.1, data. Dual 800 1G MHz 10.0.4/9.2.1

Problem with DHCP in OS X in both machines. No problem with when booted from 9.2.1 or from other Macs on the LAN running 9.1

SWBell DSL line routed through IPNetRouter in a 7100 running 8.6.1. Dual Ethernet card setup. Original config was a static route DHCP setup- one I had been using for a year without a problem. IP Forwarding and DNS forwarding both are on in IPNetRouter.

Was able to ping, get e-mail, Timbuktu- but no DNS/Web access in OS X. Reconfigured IPNetrouter. Port 80 was not "working".

Checked the Routes in IPNetrouter- then established a new static route from the internal LAN side 192.168.x.x to the nameserver for SWBell.

Setup up the Domain Name Servers box in Network Prefs in OS X clients to include both the LAN server address and the SWBell nameserver address.

Seems to be stable now, but thought I was crazy for a while (still may be?).

Suggestions for workaround: some Unix commands

September 19, 2001
Timothy Dove

I have encountered what I can only assume is a DHCP issue. I use an ADSL connection, and from time to time, I can no longer surf. I have only experienced this with OS X though. The fastest fix I've found is to go into the terminal, and type:
sudo ipconfig set en0 BOOTP <return>
sudo ipconfig set en0 DHCP <return>

In my experience, this allows you to execute the command without having to log in as root. It will ask you for your password (must be done by an admin user). After this, I always regain my connection.

Top of page

Explanation from Apple: why Cisco VPN client and other net software doesn't work with OS X 10.1

October 8, 2001 -- Apple has responded to our reports of the Cisco VPN 5000 client not working in Mac OS X 10.1 with this technical explanation:

The Cisco IPsec VPN product on Mac OS X is written as a NKE (Network Kernel Extension). NKEs allow developers to extend the kernel based networking stacks shipped with the OS without recompiling the kernel (as is the case with most if not all BSD based Unix derivatives). This is roughly analogous in functionality to a STREAMS module in Classic Mac OS.

The current Cisco client doesn't work with 10.1 (10.1 has an entirely different kernel from 10.0.x and thus any software running in the kernel using kernel memory structures will need to be revised). Cisco is aware of the problem and is working to get a new build out to address the issue. I can not however comment on their release schedule.

Thomas Weyer
Network & Communications Technology Manager
Apple World Wide Developer Relations

Presumably, the new kernel in 10.1 is why DAVE for 10.0.4, Virtual PC for OS X Test Drive, and other networking products don't run in Mac OS X.

Top of page

Classic applications can't access SMB volumes in Mac OS X 10.1

October 8, 2001
Tim Moore reports this problem with accessing Windows servers from Mac OS X 10.1:

After a bit of testing using OS X 10.1, it looks like you can't open from a Classic application a file which is located on an SMB mounted file server (you are prompted to log into the file server a second time). Strangely, you can mount the same SMB server multiple times (which is what ends up happening in this scenario).

It's easily tested - mount an SMB share, then drag an .gif or .jpg onto it. Try opening it with Picture Viewer from Classic ...

October 10, 2001
Thomas Ekdahl said "I can verify that this happens on my machine too. Annoying."

October 10, 2001
Brad Spachman

I can verify the following report. Not only am I unable to double-click a document on an SMB volume and have it launch or open in a Classic application, I am unable to navigate to the SMB volume from the Classic application to access files. The only way to open a file from a SMB volume that I've found is to copy it to the OS X partition, use the Classic application, then copy it back--hardly the most user-friendly method.

October 10, 2001
Steve Crossman:

I can verify that Classic apps cannot see the SMB mounted shares in OS X 10.1 Classic can only see shares mounted using afp://server_name protocol

October 10, 2001
Philip Saunders

I can confirm Tim Moore's experience exactly. We have a Win2K server volume holding a library of PowerPoint 97 and 2000 presentations. (No SFM.) Easily mount the share on the X.1 desktop. Double-clicking a file on the share launches PowerPoint 98 or 2001 (whichever is installed) in Classic, but the file does not open; instead another logon screen appears, and if you go through it a second instance of the SMB share appears on the X.1 desktop. Same thing if you drag a file onto the PowerPoint icon in the Dock, or if you give the File:Open command from within PowerPoint.

Top of page

TIP: DAVE for OS X 10.0.4 inhibits OS X 10.1 SMB client: How to remove it

Please see our DAVE special report page for this tip.

Mac OS X 10.1: SMB/CIFS (Windows) file sharing doesn't work over AirPort

Please note that this is not a case of readers not using the correct syntax typing in the file servers name. Many readers report being able to access the same Windows (SMB) volumes over Ethernet.

October 12, 2001 -- Douglas Mclaughlin reports that while OS X 10.1 SMB file sharing works over Ethernet, it does not over AirPort:

I usually bring my own, personal iBook to work and I am now running Mac OS X 10.1. I was interested to hear that I would be able to connect to our Windows 2000 server. It took me quite a while to figure out the exact format of the address to put in the "Connect to Server" dialog and I did eventually get it to work... BUT, it only works through the Ethernet. I cannot connect when I try to use my AirPort card and our WaveLAN Access Point. I can connect just fine through Mac OS 9 and the Chooser using both Ethernet and AirPort. But the AirPort just won't connect through Mac OS X 10.1.

So, I was just wondering if anyone else has been able to connect through SMB with Mac OS X 10.1 and an AirPort network. Maybe it's just our Access Point and we need a real AirPort Base Station? I have encountered other problems with that Access Point.

October 15, 2001 -- Douglas McLaughlin, who first reported the problem, adds this information:

In addition, if I create an alias to the server volume after connecting through Ethernet double-clicking on the alias with the AirPort networking opens a window showing the root level of my system partition. Very strange. No error message, it just opens my hard drive!

October 15, 2001 -- Alex Dearden is another reader who can access SMB volumes over Ethernet but not AirPort:

I will confirm that I cannot mount any SMB volumes through my AirPort. I can use Ethernet with no problems, but not the Airport. Apple (or MacFixIt, can't remember now) has a warning saying that the server you're trying to connect to should respond to the airport base IP address and not the host IP address if I remember correctly. Which should be OK since the Airport Base is doing NAT. But I can't get the Mac to see anything on the Windows machine.

October 15, 2001
Scott Johnson:

I am experiencing the same problems Douglas Mclaughlin is regarding SMB over AirPort. I have a D-Link DWL-1000 access point and am able to access my Windows 2000 server through AppleTalk services over Airport, but am unable to connect via SMB. When wired directly to the hub via Ethernet and using the correct syntax, I am not experiencing any problems.

October 15, 2001
Carlos Soledade can use SMB over AirPort, but notes another issue:

We have an apple PB G4 running 10.1 at work. I have found that with an airport card in the PB G4 and several WaveLan access points there is no problem accessing WIN2K server shares over SMB. I use the following method per the Apple TIL:

smb://fileservername/sharename/

I then fill in domain username and password information in the std dialog that pops up. 

Curiously though, if the WIN2K machine is sharing a volume over SMB and over Apple File Services (WIN2K file sharing over AppleTalk), I cannot access the shares over SMB. Instead I have to use AppleTalk. Somehow sharing the volumes using both methods screws up SMB access.

We have many more messages from readers who are not seeing this problem on our Mac OS X Special Report page. Some are using Apple Base Stations, some are use other access points.

Top of page

Readers who don't have the problem with AirPort

October 15, 2001
A reader called J. A. C.

I can connect to the network using SMB with no problem at all. I'm using an Apple AirPort card and connecting to a Linksys access point.

October 15, 2001
Matt:

I'm using 10.1 exclusively now and I'm able to connect to Windows 2000 networks shares, a NetApps Filer sharing CIFS and a Quantum Snap Server SMB shares all through both Ethernet and airport.

I'm not using an Apple Base Station but a Nortel Networks Baystack 660. Hardware is a PowerBook 2000 G3/400 (Pismo).

I had some connection problems but it required a little bit of experimentation in how to structure SMB URLs for the Connect To dialog. Adding in the Win NT domain was the tricky bit.  

October 15, 2001
Jeff Hokit:

I have had success connecting through SMB to a Windows 2000 server and an XP workstation via airport in a couple of environments. In both cases I have a real Apple Airport Base Station.

October 15, 2001
Chad

Works fine for me, I'm just using a simple AirPort card and Base Station, using Apple's suggested form: smb://workgroup;server/share

October 15, 2001
Luciano K

At home I have a Cube and an Acer Travelmate 517 connected via Ethernet to a Netopia NetLINE wireless gateway. With my Pismo 500 with AirPort card I can surf the web as well as mount on the desktop the Acer shared folder via SMB.

October 15, 2001
David Goetzka

The new SMB integration into 10.1 works great for me at work on our NT network via Ethernet and at home via AirPort. I get a join error on my PowerBook, but everything still works.

At home I use a D-Link 713-P connected to my @home cable modem. I just set up a Win98SE machine on my home network and connected first try, 

My Win98SE machine connects to the D-Link via Ethernet. TCP/IP settings are set for DHCP with the gateway set to the D-Links LAN IP of 192.168.0.1. On the Identification tab, I named it Win 98 and the workgroup Mynet. Of course I turn on file sharing. After restarting, I create a new folder called Myfiles and share it. I set myself up as a user in the Users control panel. I don't use a password, but sure I could if I wanted. 

On my PBG4 in the Finder I go the the GO menu and Connect to Server. I type in smb://Mynet;Win 98/Myfiles. I type in Mynet and my name in the dialog box. Myfiles mounts on my desktop. So far, it all works great.  

Top of page

Fix for AFP disconnects in OS X 10.1

October 23, 2001 -- Dan O'Donnell agrees with a report last week that AFP connection disconnect problem also occurs with Mac OS X 10.1.

I just read your note that you haven't previously heard of the connection drop problem on OS X 10.1 and its (potential) fix with Apple's Ethernet update 2.0. I assure you it has been present, and the dropped connection is one of the biggest problems in the very large K-12 education community that is running OS X 10.1 with Macintosh Manager.

Rick Zeman also sees the problem, and offers a fix:

A workaround is to open a terminal window and add the following to the end of /etc/rc (using vi or whatever) as the root user: sysctl -w net.link.ether.inet.apple_hwcksum_rx=0

BEFORE the exit value. Reboot and and it'll take effect.

This allowed 10.1 (using the built-in Gigabit Ethernet) to work with a 5.1 SP3 server running the AFPTCP nlm from the Native File Access Pack. I've noticed a few file handle locking problems, but I don't know if it's 10.1 (though that's my guess), or NFA.

Top of page

Tips for accessing Mac OS X Server from Windows 2k client

This item moved to the Mac OS X Server Cross-platform Issues page.

Top of page

Quark hangs in Mac OS X 10.1 with AFP over AppleTalk connections

November 5, 2001
Adrain Fry reports that QuarkXPress hangs in Mac OS X 10.1 when he accesses files on AFP (Apple File Protocol) servers:

I manage a network with several Macs and many PC's connected to Windows NT 4 Server, running Services For Macintosh, and have just upgraded one of the Macs to 10.1.

Having lost the ability in 10.0.4 to connect to the SFM drive (had to use DAVE), I was pleased to see the ability to connect via AFP in 10.1. Classic apps' like Photoshop work fine, but QuarkXPress 4.1 hangs every time I even navigate to the mounted volume on the desktop. Oh yes, I have installed the Apple Ethernet Update 2.0; this seems, after some experimentation, to be a Quark thing.

We would only note that Apple Ethernet Update 2.0 is software for Mac OS 9.2.1, and should not affect Mac OS X.

November 19, 2001
Adrian Fry

[After installing 10.1.1] I have had time to play around with Quark a bit, and it seems that bug HAS been squashed - I had some hard drive errors to fix with fsck-y!

Top of page

Can't delete NT SFM files from OS X: OS X leaves invisible files on servers

November 9, 2001
Steve Crossman

When trying to delete files from our NT 4 SP5 file server from my OS X.1 cube, I get the message that the files or folder are in use and cannot be deleted.

They are not in use, and can be deleted from any OS 9 Mac or PC. Sometimes, I can delete all of the files, but not the folder. At other times, I can delete all the files in the folder and then delete the folder, this where trying to delete the folder without deleting the files will fail. Showing privileges on the folder indicated I have full read-write on all items.

Also, X.1 places several files beginning with a period, such as .Trashes .DS Store, that are visible to Macs OS 9 and PC users. I cannot see them from the X.1 Mac.

I've tried holding the Option key when emptying the Trash. File Sharing is not on and the w-drive shown below is on our NT 4 server, not on my OS X Mac.

Bottom line is, for me, that on an NT 4 file server using AFP with the 3 OS X Macs I have, there are many folders that cannot be deleted, that can easily be deleted from a OS 9 Mac, or PC.

November 15, 2001
Jason Froikin

MacOS X is right, the folder *IS* in use. The problem is that MacOS X creates hidden files (.DS_Store, .Trashes, etc.) within the shared folder, and then leaves them open. So technically, the folder *IS* in use. One possible workaround might be to unmount the drive, mount it again, and then toss the folder without opening it. Hopefully, Apple will fix this soon.

In case you're wondering, .DS_Store is where MacOS X stores information which used to be in the Desktop and AppleShare PDS files in Classic MacOS. .Trashes should be fairly self-explanatory.

November 19, 2001
Rick Zeman

This also happens with X connecting to a Netware 5.1 SP3 server running the AFPTCP.NLM. I suspect that this fix (Mac OS X 10.1.1) may cure it:

* Fixed problem with AFP attributes corrupting 1024 byte zones.

On another note, there is an acknowledged problem with X and network-based Trashcans not working (all files must be deleted immediately). No mention of any fix for that in the notes unless it's covered by one of the other AFP fixes.

February 1, 2002
Alan Pedersen-Giles points out another problem:

Others have noted that OS X 10.1.2 leaves files/folders (e.g., .DS_share and .Trashes) that are invisible to OS X on shared volumes. Unfortunately, these files are quite visible to other OS's (e.g., Windows clients on an NT server). Apple's highly touted networking seems somewhat useless if we, as browsers, hack other users off by leaving a bunch of files in our wake.

I have not, as of yet, seen a solution/workaround, and was wondering if anyone had ideas. It has been suggested to remove ".____" files via a (periodically run) shell script. I would prefer, of course, that these files not be written in the first place when browsing a volume by SMB. I suppose the second-best solution would be an automatic script that removes these files as they are generated, or upon removal of the shared volume.

These invisible files may have some affect on access from Classic. If you'd care to comment, please do.

February 5, 2002
Yann Bouckaert

Witnessed this problem too. Example: create a folder on the mounted volume, drag something in it, and try to delete the folder. A message appears that the folder is in use. BUT! When you do this on a volume that is mounted via SMB, you can delete the folder.

Top of page

OS X SMB leaving "duplicate" "dot underscore" files on servers.

NOTE: there is also a discussion of this problem with AFP file servers on our Jaguar Reports page.

January 14, 2002
Larry Martin Martin

I have also found that I am creating "duplicates" of many of my files that are small in size and begin with "._." on the NT Server.

February 27, 2002
Vanessa Schwab

I'm having the same problems. I use Sharity to connect to a Solaris server. When I save a file, say 'test.cfm', automatically, '._test.cfm' appears. Then, refreshing the browser will produce a 404 Object Not Found error. Currently, I have to go to a Mac running OS 9, delete the ._file, drag the good file to the Desktop, then replace it back onto the server. Refreshing brings up the page fine.

March 6, 2002
Neil Snape sees the problem with Sharity:

For each file I copied to the XP Pro PC from Mac OS X 10.1.3 with Sharity there was a second file with this strange prefix. Always a small<1K file. Could it be the resource file from ds.store?

March 6, 2002
Colin Smith send us an "unofficial response" from Apple:

Sure enough I have the same duplicate file problem described below. I always get duplicate files with a "._" prefix when I transfer to my home Windows 2000 server via SMB or Dave 3.1 and also when I use my IBM MicroDrive and mount it on my ThinkPad or when I transfer at the office to the Windows 2000 server. NOTE:These files do not show up when mounted under Linux.

Apple's unofficial response.

In Terminal type '/Developer/Tools/GetFileInfo <path to an image file>'

You should get something like:

file: "/Users/pat/Documents/Extension editing.rtf"
type: "????"
creator: "????"
attributes: avbstclinmed
created: 05/28/2001 00:12:05
modified: 07/24/2001 03:09:22

If the type and creator part is not ????, then he has metadata and that is causing the ._ files when transferred with Mac OS X.

I tried the Terminal script above and did not get the ???? Type and Creator described therefore all the files I transfer have metadata. But I'm not sure how to create files without metadata as the files I'm transferring are standard docs, images and PDF's??

March 6, 2002
Curran Riley

I'm seeing this too. I recently started storing things on a Windows 2000 share (I had been using NetWare 4.12 servers, but they were causing me lots of grief with lock ups in OS X).

Now, when making changes to files on the Windows 2000 share, I end up with the extra files with "._" on the front of the name. The files are smaller and don't have much info in them. For instance, one that was a .htm file that I'd edited in BBEdit had some font names listed in it, but the rest was gibberish.

March 6, 2002
Andreas Kampe-Wennborg

I also have this problem.

Connecting to a Windows share (doesn't matter if it is Win XP box or Win 2K Server) via SMB, whenever I create a file I get a duplicate ._ file. I cannot see the file(s) from the Mac only Windows.

In the root folder of the share I always get a ._Trash file.

Annoying - but really no big problem for me - I'm the admin for the network, so I set the rules/policy what is allowed or not. And guess what? ._ just got allowed.....

March 6, 2002
Steve Crossman

I have seen the ._. duplicate files on our server too, but I think it occurred to me when I was using SMB to copy files. Since SMB was much slower than AFP/IP, I stopped using it. I haven't tried SMB in 10.1.3 yet and I read that someone claimed speed has improved in the latest X release.

March 6, 2002
Jin Kim

This problem may not be a problem with OS X but rather the way the server's setup, especially if they are Web servers.

The use of "._" is a way to create sort of a token that effectively locks a specific version of a file for the server to use (perhaps cached to RAM). That's why simply replacing the file without "._" doesn't work. You have to remove the locking file (the "._" file) in order for the server to see the new version at which time it will create another "._" file to lock the new version.

March 6, 2002
J. L. Williams

I am seeing this too, John. I either have to fire up Virtual PC or OS 9 to delete these (or go to a PC to do it). Without diving into this, I don't know the source...could it have something to do resource/data forks? (I'm just guessing here.)

March 6, 2002
Greg Mulhauser

I experience exactly the same thing connecting to a Quantum Snapserver 1000 NAS box using 10.1.3 and SMB. It's very annoying to be leaving these duplicate files sitting around, which are plainly visible to Windows users as well as via the web interface to the NAS box. The NAS box is running relatively recent software, although not the just-released 3.4 -- however, if this is occurring on other platforms, I suspect the problem is with 10.1.3.

March 6, 2002
Nathan Margason

This problem also occurs when writing to PC formatted Zip disks. I'm the only Mac user in a PC office. Often I need to write files to Zip since we are just beginning to network the office. Unfortunately, OS X writes a duplicate with ".-" prefix for each file.

With regard to networks Dave 3.1 supposedly prevents this by adhering to the MS protocols whereas Sharity and Apple SMB implementations do not.

March 6, 2002
Sergio Najera

I have this problem too, which I belive is some sort of X's version of what OS9 left behind on Servers and Windows formatted disks and drives (hidden resource files?) . I haven't had any real problems with it other than getting very annoyed with the "trash" being left everywhere on the Servers. At least it's not as bad as OS 9's. But would like to find a way to stop it. At least on non-OS X disks and drives.

March 6, 2002
Michael Kuntscher

from Inside Mac OS X : System Overview:

Copy and Move Operations

When the Finder copies or moves a file, it uses the richest model available, given the formats of the source and destination volumes. The formats that are most significant in these kinds of operations are HFS+ (or HFS) and UFS. These operations particularly affect the representation of the HFS and HFS+ resource fork and the Finder attributes, especially the type and creator codes.

As one might expect, the Finder preserves the resource fork and Finder attributes of an HFS+ file "as is" when it copies the file to an HFS+ (or HFS) volume. The more interesting case, however, is when it copies an HFS+ file to a UFS volume. When this happens, the Finder splits out the information that is not in the data fork (particularly the type and creator codes) and writes this information to a hidden file in the same directory location as the copied file. This hidden file has the same name as the UFS file, except that it has a "dot-underscore" prefix. Thus, if you have an HFS+ file named MyMug.jpeg, when you copy it to a UFS volume, there will be a file named ._MyMug.jpeg in the same location. (my emphasis)

When the Finder copies a UFS file to an HFS or HFS+ volume, it looks for the hidden "dot-underscore" file. If one exists, it creates an HFS+ (or HFS) file reintegrating the information in the hidden file into the file's resource fork and Finder attributes. If the hidden file does not exist, the copied file has no resource fork.

Note that the Finder accomplishes these operations through the Carbon APIs on which it is based.

March 6, 2002
Rob Fernandez

I believe that what you are seeing is the resource fork of these files. I was told that this is how the Mac saves them on non-Mac file systems. Since they start with a . They are supposed to be invisible in Unix and Mac OS X. It is probably a bug that lets them be shown.

March 6, 2002
Rod Kirkpatrick

I have an OS X box 10.1.3 connecting to a Win2K box. I get duplicates of all files transferred via SMB. Folders that I have transferred appear not to be affected. Folders created by the OS are.

Example

.FBCLockFolder which is autocreated has a duplicate as does .Trashes B6_2 Folder (one of mine) does not have a duplicate I only just started using this functionality so have only just noticed it. Have not had much time to debug but trials indicate that its pretty universal.

March 6, 2002
Guy Teague

I experienced just this issue, nearly every file duplicated with a leading '_', when copying files from my ~Documents folder to a secure digital flash memory card mounted via the go! flash USB reader.

I didn't actually check to see if the files were exact duplicates, I just noticed the filenames. at the time I chalked it up to the new 10.1.3 update maybe not being quite compatible with the drivers for this device.

March 6, 2002
Brett Rockwood

I too have the "._filename" duplicates appearing on NT4 servers. (They aren't exactly duplicates as they contain no useful information for Windows as far as I can tell. Whenever I copy a file from OS X to an SMB NT server it places a file with the same name but prefixed by "._" In fact, I've told co-workers to just delete any file that begin with "._" and have experienced no problems. There is also an odd file named ".DS_Store" that appears. I haven't tried to track its origins down but routinely delete it to no bad effect. You can't see either the "._filename" files or the ".DS_Store" file from OS X though it is visible from OS9 and of course Windows. Would really like to stop annoying all the non OS X people with these worthless files...

Top of page

Problems with SMB support in Mac OS X 10.1

November 21, 2001
Peter Thompson

SMB connection is a welcome additional to Mac OS X but it does have problems (even in 10.1.1). The main one being it's loose connection between the real file and it's hidden file providing Mac OS specific info. For example, I created a ZIP file with DropZip, before DropZip had finished, I renamed the file. The Mac OS correctly reported that the file was still in use and the file name wouldn't change. However the hidden file had been renamed! So after DropZip finished, I tried to rename the file again, to which the OS replied that "a file with that name already existed." Now I have the invisible file with the new name and the actual file with the old name. Since Mac OS X will not show me the invisible file, I had to delete/rename the invisible on a Windows box so that Mac OS X could get back in sync.

On a separate occasion, the OS pulled me out of a file rename in such a way that the file was rendered useless. Even Windows NT utilities could not access the file, though it was listed on disk. It seems like the SMB implementation could have done with some more testing before release.

Top of page

More OS X file sharing problems: SMB and AFP

November 27, 2001 -- Hanz Makmur also reports on problems with Mac OS X file sharing with the Apple File Protocol (AFP), as well as another problem with SMB (accessing Windows PCs).

I notice other problems with SMB and AppleShare (AFP) on MacOS X 10.1.1 too.

SMB.

December 6, 2001
Steve Jones

I read with interest Hanz Makmur's comments - I have experienced similar problems with files & folders in mounted volumes dissapearing when selected. Only unmounting/remounting makes the files re-appear.

I have not tried the built in Apple support for SMB - these problems have occurred using DAVE.

Suggestions

December 10, 2001
Tony Kalf

I noticed the mentioned problems, but it's really not a DAVE problem. The point is that there is still trouble with file, directory and drive(share) naming and translation, despite the improvement for SMB within OS X 10.1.1. Long names are not fully supported !

Also when Dave is installed before the update 10.1.1 or installing Samba X 2.2.2 those problems appear too.

Some solutions :

Top of page

Bug v10.1.0-to-10.1.4 and NT Server SFM: Finder crashes

Numerous readers have reported problems with accessing NT Server with the 10.1.0-through-10.1.4 versions of Mac OS X. (Readers have also reported being unable to delete files on NT servers with earlier versions of OS X, posted above.) The problem only occurs when access Services for Macintosh (the AFP file server). Accessing the server using OS X's SMB client (via the Go menu) does not cause the problem.Some suggested workarounds are posted below.

Mac OS X 10.1.5 fixes the problem, as reported below.

 

January 3, 2002
Ken Kling reports Finder crashes when browsing mounted shares:

OS X 10.1.2 Finder still crashes with NT Server 4 SP6a; when browsing shares the Finder still crashes. The problem occurs when mounting the shares via AppleTalk. The latest time it produced this console.log entry (edited to remove local network info):
FSMakeFSSpec=-43
userSelectedURL is afp:/at/<server>:<domain>
*** malloc[293]: error for object 0x29c4910: Incorrect check sum for freed object - object was probably modified after beeing freed; break

at szone_error

Jan 2 16:54:45 <localhost> /usr/libexec/CrashReporter: Succeeded writing crash report: /Users/<user>/Library/Logs/Finder.crash.log

I don't think it does not occur when mounting the same shares via SMB but SMB mounting confuses many Mac apps.

January 4, 2002
Andreas Norén

We have that exact problem at work.

January 14, 2002
Larry Martin

With AppleShare on, logging on to Mac volumes on an NT 4 SP5 server, I get crashes in the Mac OS X 10.1.2 Finder when opening specific folders. Not all folders and no logic (yet) to how the folders that crash are different. But I can repeat it on certain folders.

Interestingly, logging on to the main Windows NT server using samba yields no such problems. I have had no crashes whatsoever. Unfortunately, I also have to sift through dozens of folders and invisible (to windows) files to get where I'm going. I have also found that I am creating "duplicates" of many of my files that are small in size and begin with "._." on the NT Server.

Also, I have yet to figure out how to automatically logon to the Windows server when I log in to OS X.

January 14, 2002
David Schlosser

We experience an OS X Finder crash when trying to browse Win NT shares via AppleTalk if a file or folder has been named with a space as the first character. Removing the space clears it up. Unfortunately, some users (most work on OS 9.1) like to do this to get their file/folder to the top of the list.

January 17, 2002
Mike Deme

Same problem here. I can mount the NT server fine. However, when I actually try to use it, the Finder crashes. Very disappointing. I can't switch our organizations Mac users over to X until this issue is dealt with.

January 17, 2002
Larry Groebe

I can confirm and reproduce this, too. Boy, can I reproduce this! I just wish I could stop it. It's nothing so simple as blank space in front of the file - I wish.

Because of problems like this, we only have one Mac currently running OS X, much as I would like to have more.

For instance, I just spent half-an-hour playing with one guilty directory on our NT server. Navigate to it in the Finder and you're guaranteed a quick crash. If I move all the dozen or so files in this directory into a subdirectory, the crash stops. Move a few files back, the crash still doesn't happen. Move a few more files back, the crash happens again. MOVE THOSE SAME FILES BACK OUT AGAIN, THE CRASH CONTINUES(!). Move *all* files out again, the crash stops.

That's a clue, but I'm not a smart enough detective.

January 17, 2002
Ralf Schmidt

We have still the same problems. It seems to be a problem with the filenames.

January 17, 2002
Dan Schwartz of the Mac-NT Mailing List told us that his readers are also reporting the problem.

January 21, 2002
Nicholas Macias points to file names:

I actually can't see how this got out the door at Apple; it seems to be that any filename that uses non-alphanumeric characters sends the Finder down in flames. We're running NT 4.0 with the latest service packs.

January 21, 2002
Michael Curtis has better luck in icon view:

I do have the Finder crash when connection to NT 4 and 2000 servers. It seems much better is I leave it in icon view. List is not too bad, but column is terrible. I haven't had time to investigate too much as yet.

January 21, 2002
Patrick Renner crashes when scrolling:

We're experiencing the same problem. I can log into the server all right but when I try to scroll down in the directory, the Finder crashes.

January 21, 2002
Brian Frobisher sees other symptoms:

I have been testing OS X 10.1.2 with our NT server using NT 4.0 SP6 an SFM.

When I mount a volume from the server it mounts fine, it is only when I start clicking "Open" arrows on folders to look in them that the volume window closes, the Finder kind of flashes and you end up with the volume still mounted, but the window is closed etc. Very frustrating.

P.S. I also had the Finder crashing while trying to view a .PDF that I d/l from APPLE yesterday. I installed Adobe Reader and it reported font problems with the .pdf in question, but the built-in PDF viewer was crashing the Finder.

January 21, 2002
Nicholas Sorensen crashes when he copies or opens a file:

Yes, I can report this same problem. I can mount the server, most of the time even navigate to the folder I need, but as soon as I attempt to copy or open any of the documents I get an immediate Finder crash.

Very annoying - I need to boot into 9 to grab the documents I need, reboot into X to work on them, boot back into 9 to copy them back, and reboot once again into X to continue working. Very tedious.

Sorensen also notes that the problem does not occur when accessing the Server via SMB.

January 21, 2002
Bailey Kessing

I also have this problem with one Volume on an NT Server. I had assumed that it was the server's problem since this only happened when I was navigating this one volume on a particular NT server.

January 21, 2002
Mark Cole

The OS X finder crash when accessing NT servers is a big problem for me.

February 4, 2002
Don Begley

I'm not suffering a Finder crash with my NT server but my OS X 10.1.2 machines do disconnect from the network after about 15 minutes of inactivity. Same machines on OS 9 run all day long. I wonder if these aren't related problems. My configuration: NT2000 Small Biz Edn w/2 G4s and many Win machines of various OS flavors.

Another quirk is that NT2000 is very sensitive to the time on its client machines. (I understand it's used to establish machine identity.) If an XP client in particular does not have it's time synchronized to the server, the server cannot access the client. I wonder if there could be a time-related issue going on between NT2000 and the Macs, too.

May 6, 2002
Luke Andrews

I too suffer from the Finder crashing problem while connected to an NT server using AFP.

My crashes don't seem to be random however. They only occur when I open or look at certain directories. The only thing funny I can see about those directories is that the files in them are old OS 9 files which have icons that OS X doesn't like. If I copy the directory to my local computer, I can open it and see the files, and none of them show any icons (though they show them in OS 9). Other than that, they seem unremarkable. No funny characters that NT might not like.

Workarounds

January 23, 2002
Dan Buchan writes that the problem does not occur using Mac OS X 10.1's built-in SMB client. (Log in via the Go menu's Connect to Server command, type smb://workgroup;username@servername/volume). Bucan says "I can now browse the entire server without the Finder crashes."

January 23, 2002
Andrew Cunningham

Connecting to Windows 2000 Server via SFM (TCP/IP) works perfectly with 10.1.2 for me. Fast and reliable. Is used heavily.

January 23, 2002
Reid Lewis of Group Logic reports that the problem does not occur when OS X access's ExtremeZ-IP running on the NT Server instead of NT Services for Macintosh. He writes:

We believe the crash is caused by the AppleShare on AppleTalk feature that was just added to OS X. While SFM on NT requires this, ExtremeZ-IP does not. Hence, we believe ExtremeZ-IP will solve the problem.

Group Logic offers a free trial version of ExtremeZ-IP. If your are having this problem, and can verify that ExtremeZ-IP doesn't have the problem, please let us know.

January 23, 2002
Greg Byerly reports of a method to lesson the Finder crashes:

I can connect to our Windows 2000 and NT server okay, but at random times to Finder will crash. Though this is not a fix, I've had good success with the following:

1. Log in to the NT or Windows 2000 server
2. View in icon mode (seems to be the most stable)
3. Do not scroll, instead, type in the first few letters of the folder you want in the Finder window to make the folder appear.
4. Click on the folder icon once and choose "Add to Favorites" from the Finder's File menu.

From that point on try not to access the server's root shared directory. Click on the Finder's "Favorites" button--the heart--and then click on one of the folder shortcuts in your "Favorites" menu. I've been using this method successfully for a week to access my shared folders on our NT and Windows 2000 servers. The Finder has not crashed once since I started access the server through this method--knock on wood!

If you have any helpful hints on the subject, please let us know.

10.1.4 doesn't fix the problem

April 22, 2002
Anthony Trumbo first reported that the Mac OS X 10.1.4 upgrade fixes the problem:

I have been using OS X 10.1.4 for a day and have been able to connect to our NT 4 SFM volumes without the Finder crashing as it did in previous versions.

Then he recanted:

April 26, 2002
Anthony Trumbo

Your readers are correct. After two days of smooth sailing, my finder began crashing again when browsing our AFP volumes on NT.

A large number of readers say that the Mac OS X 10.1.4 upgrade does not fix the proble. We received over a dozen responses. This one from a reader named Rafer is typical:

I have updated to 10.1.4 and still have the problem of the Finder crashing while browsing NT 4.0 SP6a servers, as do many people on Apple's forums under OS X > Networking and the web: "Finder crash while browsing NT." The person reporting it is fixed fix should give it some time, the crashes may return.

Elliott Hill points out the crashes are random:

I have updated my system to 10.1.4, I still have the Finder crash/relaunch issue. All I can say about the guy who said 10.1.4 fixed this issue is that this problem is random, it doesn't always happen when you

open a share from an NT server. You could open a share, then go a few levels of folders before it will relaunch the Finder for you. Or you could just open to the root level of the share and, bam, relaunch. Or you could scroll down to a certain spot and then crash. This has been the same since 10.1.

John DeMillion uses a replacement for the Finder to get around the problem:

We very successfully use SNAX to navigate our NT volumes and copy files/launch programs under Mac OS X. That and many other useful features make it an invaluable utility and a viable Finder replacement when needed.

However, Rafer says that he also sees the problem with SNAX:

I've tried SNAX many times and it crashes just as frequently - unless I turn off icons - then it is less frequent.

OS X 10.1.5 fixes Finder crash with Win NT.

May 6, 2002 -- Several readers have indicated that the upcoming Mac OS X 10.1.5, now in beta testing, fixes the problem of the Finder crashing when accessing Windows NT volumes. We have not word on when the new version will be released.

June 7, 2002
Marc Klureza

Mac OS X 10.1.5 seems to have finally fixed the bug of Finder crashes when accessing some NT 4 shares. Now I can think about rolling out OS X to our users.

June 10, 2002 -- A number of readers have verified last Friday's report that Mac OS X 10.1.5 does indeed fix the OS X problem of Finder crashes when accessing Win NT server volumes. For instance, John DeMillion reports:

Per your report from Marc Klureza, 10.1.5 does indeed fix the Finder-crashing problem with NT Server AFP shares. We haven't had a Finder crash here since 10.1.5 was released, and we're now using the Finder to access all of our NT AFP shares. The 10.1.5 ReadMe calls this "Better networking via AFP when accessing multilevel directories on Windows NT file servers", and I guess I'd have to agree that "not crashing" is better!

Don Rainwater sees an extra feature:

10.1.5 has fixed the problem with the Finder crashing while connecting to NT servers via AppleTalk on my machine (G4 400).

Also, I think it has also added icon previews instead displaying generic icons for everything. I don't remember them being there before.

Craig R. Arko confirms the fix with two versions of NT

Near as I can tell, 10.1.5 fixes the Finder problem with NT Server 4 and 3.51 as well.

Regular readers know that this has been a major topic, as reported on the our MacWindows Mac OS X Reports page. Justin Beek (who as confirms that 10.1.5 fixes the bug) sent us the link for the reports at Apple's Discussion forums.

Elliott Hill sums up most readers' feelings: "This 10.1.5 update has finally done it! YAY!!"

Top of page

Error Code -43 with Win Servers (NT and others)

Below, a readers blames an old problem--illegal characters in Mac file names.

January 3, 2002
Jon Buckley is receiving an Error Code -43 with Mac OS X 10.1.2 on a dual 800 MHz Power Mac G4 (640 MB RAM).

"The operation cannot be completed because one of more required items cannot be found. (Error Code -43)"

Message when trying to copy a folder full of files from NT Server to OSX Macintosh. The same file copies perfectly from NT Server to OS 9.

I can copy files but not folders using AppleShare over TCP/IP. I can copy everything if connected via samba but the performance is too slow to be productive. Using Dave from Thursby lets me copy folders but my Classic apps don't see volumes mounted by Dave.

Strangely I didn't have any of these problems with 10.0.4.

If you've seen this problem, please let us know.

January 15, 2002
Jon Buckley

Interesting tidbit... going to MacHelp in OS X and asking "What is Error Code -43?" pops up a list of options, and one possibility... that it could be a damaged RAID Drive. Now as I stated, I am not having this file transfer problem in OS 9, but perhaps it offers a tantalizing clue as to the culprit. Apple still has not replied to this issue on their message boards.

January 28, 2002
Kack Stoller reports seeing the -43 Error code when accessing MacServer IP:

Running Windows 2000 with MacServerIP 7.x (latest version) installed (the reason is another story entirely).

Some folders when copied (in either direction) between my local disk and the server result in the folder being created on the destination, then the -43 error appears. If I go to the source folder, select all the files, and copy them to the (newly created) destination folder, they copy without incident.

I don't know if the -43 problem is recursive if the source folder itself contains folders because I don't have any such situations in my work.

February 1, 2002
Steve Crossman

I can report the same thing happens with MacServerIP v7 and v8 with Win2K as reported by Jack Stoller. This does not happen with Win NT 4 sp5 or greater. I have not seen much improvement in MSIP v8 over 7. Win2K SFM beats either version when copying a lot of small <2mb files to or from the server. MSIP excels with large files>10mb and easily beats SFM by a factor of 2-3 times the performance.

I tried using SMB as an alternative to the above, and performance is, well ' terrible ' !

February 5, 2002
Yann Bouckaert

I too have seen this problem with Mac OS X workstations connected to Windows NT 4.0 Server with Macserver IP 7. On two file server configurations it works without errors: Windows 2000 Advanced Server with native AFP over TCP/IP, and on Windows NT 4.0 Workstation with PC Maclan (also AFP over TCP/IP). Also, the 'server' with PC Maclan seems to be the only configuration which is listed under 'local network', in the 'Connect to server' dialog box, as Macs that share their files over TCP/IP.

Suggested fixes

April 5, 2002
Carl Blesius

I am having the same problem that is mentioned on the MacWindows Mac OS X page concerning -43 errors in the middle of a large copy to my Win XP server. It seems to be related to specific files because once I find the last folder/file copied and try it again from there it happens again.

I am connecting to the XP machine using smb:// and doing it over a hub. Maybe this helps.

I think I figured it out in my case (it is so simple it is embarrassing)... file names that are supported in Mac OS X but not on windows machines.

Files with " in the name or / (e.g. the Rip function of iTunes pulls CDDBnames and uses them without regard for "proper" file names)

Once I found the files, changed the names and tried again everything worked fine.

December 16, 2002
Harry Werkman

I've been reading about peoples problems with accessing/moving/copying files. I also had the 'Error -43' problem with external media (such as FireWire drives formatted with FAT32) and resolved it by ensuring that the file name did not contain open square bracket '[' or close square bracket ']'.

This has fixed all my existing problems related to Error -43.

Top of page

TIP: How to configure hosts files in Mac OS X

Hosts files are useful for resolving DNS address and are often useful for getting Macs to connect to Microsoft Exchange Servers using Outlook.

There are two different approaches you can use: the Unix command line and the NetInfo Manager utility. (We have a description how to create a hosts file for Mac OS 9. Microsoft also has Knowledge Base article ID Q189906, also for OS 9 and earlier.)

October 31, 2001
Robert sends us the Unix command line method:

I'm using a standard unix-type /etc/hosts on my machine; to get it working, I _think_ (I've installed it once, and has been working perfectly so no reason to remember how I got there ;) I did the following (all from the Terminal app):

- create a directory /etc/lookupd (if it doesn't already exist)

- in that directory, create a file named 'hosts', containing the following line:

LookupOrder FFAgent DNSAgent NIAgent

This tells lookupd to use the FFAgent (the Flat File agent) over DNS and NetInfo for resolving hostnames. After the change, either reboot or restart lookupd by sending it a SIGUSR1 signal:

sudo kill -USR1 $(cat /var/run/loopupd.pid)

Check out the manual-page for lookupd for more information.

October 31, 2001
Laszlo Kardos explains how to use the NetInfo Manager:

Mac OS X doesn't actually have a host file in the same sense as Mac OS 9.x. How to add host machines to Mac OS X:
  1. Open NetInfo Manager (Applications/Utilities/NetInfo Manager)
  2. From Domain menu select Open
  3. Domain / . . . OK. This should bring up the local host
  4. From the Directory browser select machines
  5. From Directory menu add new subdirectory
  6. This will create a machines/new_directory
  7. In Directory:machines window below the directory browser will appear
  8. a listing of property and value(s)
  9. Double click on the 'new_directory' under the Value(s) column. This
  10. should allow you to change the value to yourhost.company.com
  11. From Directory menu select Add New Property
  12. Double click in the 'new_prpoerty' under the Property column.
  13. Change to 'ip_address'
  14. Double click on the 'new_directory' under the Value(s) column.
  15. Enter the xxx.xxx.xxx.xxx ip address the the machine yourhost.company.com
  16. Save changes
  17. You can add as many machines/servers on your intranet as you need.

    This has worked for me. I originally found this solution at MacWindows, however I don't have the original link/story anymore.

December 13, 2001 -- Adrian Spiegel points us to a page at MacWrite.com that describes how to set up a hosts file in Mac OS X.

Top of page

TIPS: Authenticating using Active Directory via Kerberos and LDAP, and Novell eDirectory

This discussion has been moved to the MacWindows Active Directory Reports page.

Integrating Mac OS X and Novell eDirectory

May 24, 2002 -- The Higher Education Mac OS X Labs Deployment Initiative web site has information on Integrating Mac OS X and Novell eDirectory. Richard Glaser of the University of Utah describes the site:

This document describes how you can use information stored in Novell's eDirectory to authenticate Macintosh users, provide file services and home directories for them, from a NetWare 6 server. It also includes example LDIF files to extend the eDirectory schema, updating users, and adding a mount organizational unit and mount object class.

Top of page

Network packet errors with OS X.

March 7, 2002
Jerry Chan

I have been plagued with network problems running my OS X 10 (w/Dave 3.1) on my PowerBook G3 (bronze) -- (-43 errors in the middle of a large copy to our Windows NT 4.0 SP6a server). Other Mac systems on the network did not have this problem.

Digging further, I checked the error statistics on our Compaq intelligent switch (SW3322) and noted that I was getting an enormous number of network errors with an equivalent number of dropped packets (up to 30% packet loss on OS X 10.1.2). The total amount of data involved in my test folder is approx. 180M.

Here's where it gets interesting:

a. The same PowerBook G3 on the same network connection runs ERROR-FREE copying the very same test folder under OS 9.2.1. That would rule out broken Ethernet hardware on my PowerBook G3.

b. Upgrading to OS X 10.1.3 this morning now allows me to copy the test folder completely to the server, albeit much more slowly (as dropped packets are presumably being resent). The error rate for 10.1.3 had dropped substantially to under 10%.

c. All errors reported by the switch are CRC ERRORS (no collisions, under/oversized frames, fragments, jabbers).

d. Changing port settings to 10BaseT actually allows the transfer to go quicker than 100BaseT. Error rates are under 10%, but no packets are being dropped (ALL ERROR PACKETS appear to be dropped under 100BaseT). Duplex / flow control settings do not appear to have any effect on the results.

MY BEST GUESS

Now I am not a network engineer, but something somewhere has to generate the CRC for each packet (OS X drivers?), and apparently it isn't being done properly or is getting clobbered prior to being transmitted. AND there is no problem when running OS 9.X on the same hardware (unlikely to be broken hardware). This looks to me like a BUG, perhaps tied to certain Ethernet hardware configurations

It might be interesting to check error stats on others who are having similar problems to see what the rates / type of error are.

If you've seen this problem, let us know.

March 11, 2002
Gregory Welch

I might be experiencing this also. I have been plagued with similar symptoms between my Ti G4 PowerBook and my dual 800 MHz mini tower, both on the same 100 Mbs hub. Our department network manager and I have been trying for a long time (a year?) to figure out the problem. At some point I had to drop back to a 10 Mbs hub, which seemed to work. Recently I tried the 100 Mbs hub and it seems to work "OK." I'm not sure why. Could be something updated in 10.1.2 or 10.1.3. But I still think there is a problem because the performance seems poor when compared to a similar setup I have at home (see below).

The symptom was that when I would try and copy files (large) between the two machines, the transfer would slow to a crawl, and eventually stop, eventually with the AppleShare connection dropping. I saw similar w/ ftp and http connections. I also did several OS 9/OS X comparisons, and the OS 9 copy seemed to fly, while the OS X copy would crawl or die. If I disconnected the *uplink* cable for the hub, things seemed to unclog. This led us to lean toward collisions near the switch my office is connected to. In any case it appeared that the problem was a snowballing of packet errors. Our network manager currently believes it was/is related to a duplex problem in the drivers, but we weren't sure. We never actually used a sniffer to look at the packets.

Strangely, I have a similar setup at home, and it FLYS in OS X. It is the same hub, my same PowerBook, but my home machine is a beige G3 mini tower with an Asante 100 Mbs card (and their OS X driver). The uplink is through a software router (IPNetRouter) and an ISDN line to our building.

A duplex problem is not out of line here. A problem with mismatch duplex settings between Windows servers and hubs can cause similar problems. Our Windows Server Tips page describes the problem and the fix, which is to turn off autosense in the server. However, at the point, we know of know way to configure duplex settings in Mac OS X. --Ed.

March 11, 2002
Jonathan Greenberg

I am seeing a tremendous loss of networking speed under 10.1.3 -- I use a Mac G4/500 and a laptop with Windows XP connected to a Linksys 4-port router, which used to give me pretty good transfer speeds (nearly the full 100 mbps via sftp). Now I am getting MAX 10mbps with sftp, 7 Mbps with SAMBA. I've sent bug reports to Apple and posted stuff to various message boards to no avail. I await a bug fix soon!

Top of page

Problem with saving Illustrator 10 files to NT Server fixed with Illustrator 10.0.1

The problem:

December 19, 2001
Michael White

After extensive testing using G4 systems running Mac OS 9.1, 9.21 and 9.22 connected to a Windows NT 4.0 file server we have discovered a MAJOR problem with Illustrator 10. When saving an EPS (formatted for Illustrator 10, 9 or 8) it saves an AI temp file to the same folder as the file (not to the scratch disk). The temp file is the same size as the visible saved file. This is a problem for anyone that doesn't have unlimited disk storage space (all of us). But the problem doesn't stop there. It assigns permissions granting administrator full control and everyone else special (no delete) access (even though. This results in the inability to save the document without renaming it (which created a new temp file). It also will not be able to be saved without renaming. This test was done by launching Illustrator 10, creating a NEW document, simply typing some text, saving as Illustrator EPS to the NT server in a new folder, typing in additional text and attempting to save (either apple+s or save as the same filename. This returns a file busy or locked error. NOTE: This does NOT happen when saving to the Mac desktop, HD or remote Mac HD. It does not create a temp file on an NT server when saving as an AI document either. Adobe was supposedly NOT AWARE OF THE PROBLEM.

We have also tested this saving an Illustrator 10 EPS to a Win2K server using MacOS 9.21 and OS X (and the same methodology as above) had the same problem occur at our affiliate in San Francisco. This problem will prevent us from implementing Illustrator X at this time.

March 12, 2002
Richard Hubley

We have experienced the same problem with saving Illustrator EPS files to and NT 4.0 server using Mac OS 9.2.2. Every time you want to save, you must save as a new file.

We had a different twist as well. I tried Illustrator 10 with Mac OS X 1.0.2 and not only did I need to create a new file every time I saved, but the files were invisible after they were saved. No Mac on the network could see them, but they were accessible on the server. Checking properties on the server showed that they were "hidden". Unchecking the "hidden" box allowed Mac access. I have not tried it with the OS X 1.0.3 upgrade as I don't have a lot of time to waste beta testing Adobe software.

We are at this time only using Illustrator 10 to save customer files down to version 9.

The fix:

March 18, 2002
Darryl Zurn

I noticed that you had a description of the problem of Illustrator 10 files being saved on a Windows NT server. The Illustrator 10.0.1 update from about a week ago fixes this problem.

The problem is supposedly with the Mac OS X in terms of permissions for intermediate temp files that Illustrator used. Adobe claims it was Apple's problem but they fixed it in any event. (The "twist" mentioned above is not really a twist, that's the source and the result of the problem, not just "need to resave the file")

Top of page

SMB connection problems with long server names

March 14, 2002
Todd Miller

I have found that if the server is named a name with 15 characters (the maximum allowed by Windows) you cannot connect via MAC OS X. For instance SMB://REALLYLONGSERVR/SHARE will not connect, but SMB://LONGSERVR/SHARE will connect fine.

To test this theory, I took a machine named M12345 and did an SMB://M12345/C$. This worked great. Then, I changed the name of the computer to MEDICINE-TODDST and tried to connect again. This time failure. I get the opportunity to put in a user/pass/domain but after that I get the "No file services are available at the URL smb://..." error message. I then renamed the machine to BEANIE, and tried to connect. Again, successful.

March 21, 2002
Brad Judy sent an explanation :

SMB service naming is based upon NetBIOS naming as defined in RFCs 1001 and 1002 (see section 5.2 of RFC 1001 for mention of the character limit). RFCs 1001 and 1002 define the NetBIOS service upon which SMB was designed to run. There is a recent Internet draft regarding the formatting of SMB URLs that is probably of interest to those relying on SMB for file sharing.

Microsoft dealt with this issue by assigning a separate NetBIOS name when giving a computer a name. If the given name is too long, the NetBIOS name is a truncated version of the name by default. Perhaps Apple should address this issue in a similar fashion if SMB is to be a natively supported protocol.

Top of page

SMB peer-to-peer File sharing problem with OS X 10.1.3: files don't show up (refresh problem)

March 26, 2002
Al Tucker reports a problem with OS X's SMB file sharing that occurs only when he access PC workstations (not servers):

Here's the problem:

1. Make a shared folder on the W2K PC.

2. Connect to it from the Mac with the smb://<IP address>/<share name> URL and mount that share.

3. Put files into the share on the PC.

4. On the Mac, files do not show up. Window remains blank.

5. Now, if on the Mac, you put a file into the mounted share, it seems to "jump start" the window refresh process and THEN suddenly ALL files are visible. But every time you add a new file on the PC, the Mac does not see it until you add a file to the share on the Mac side.

I do this all the time sharing between my OS X 10.1.3 Mac and my Win NT Server PC and never see the problem. Only when sharing between an OS X Mac and my coworker's Win 2K PC does this pop up.

March 29, 2002
Eric Cooper

I have noticed the same problem. Basically, OS X is not refreshing the window. You can also get files to show up by moving (downloading) one of the files you CAN see.

March 29, 2002
Darren Trokhan

I have seen the same problem between my Mac running OS X 10.1.3 and a Samba server running on an SGI. I can add files from the SGI, but I have to drop files into the folder from my Mac before the list is refreshed.

An easier way to update:

April 16, 2002
Joel Shoemaker

Regarding the issue of Mac OS X not showing newly added PC files placed within a PC share mounted on a Mac (without unmounting and remounting the share): rather than having to remount a volume or actually copy a file to the PC share window in order to have the contents refresh within OS X, all I have to do is change the view for that window and any newly added files are displayed. For example, if the window view I have for the PC share is list and I want it to be refreshed, I just switch to icons (at which time the PC files available are updated), then back to list. Doesn't get much easier/quicker than that (except auto-updating, which hopefully will be implemented in a future revision of OS X). FYI: my computers are a Dell w/ Windows XP Pro. and a B/W G3/400 w/ Mac OS X 10.1.3 connected via Ethernet over a 10/100 router/hub.

Reader says 10.1.4 fixes the problem

April 19, 2002
Simon Buchanan says that 10.1.4 fixes the SMB window update problem:

Just to let you know that 10.1.4 fixes the SMB folder/file refresh bug. At least with a RedHat Linux 7.2/Samba combo.

Top of page

File copying: disparity in performance between Mac-to-PC and PC-to-Mac

April 16, 2002
Joel Shoemaker reports that copying a file from Windows to OS X is significantly faster than going the other way:

After recently purchasing a PC, I began copying files back and forth between it (a Dell w/ Windows XP Pro.) and my Mac (B/W G3/400 w/ Mac OS X 10.1.3) via my Xsense (Macsense) XRouter Pro. The method by which I copy the files is via Windows file sharing: basically I've turned on file sharing in XP, shared a particular folder on my C: drive, then I connect to the PC from my Mac by accessing the Go menu->Connect to server... within OS X, and then I type in "smb://Dell/SharedDocs", login in my XP user name and password, and the shared folder mounts as a volume on my Mac Desktop.

I've had essentially no problems with this file sharing scheme, except for the vastly different speed at which files copy from one computer to another, depending on which direction the files are being copied.

For instance, if I have some files I'd like to copy from the PC to my Mac, I place them in the shared folder on the PC, then go to my Mac, mount the shared volume, then select the files and drag them over to my OS X hard drive. When I follow that procedure (PC-to-Mac), a 9.9 MB file (for example) copies to my Mac in less than five seconds, obviously fully utilizing the 100-Mbit function built-in to my 10/100-capable XRouter Pro.

On the other hand, if I mount the shared volume on my Mac, then copy files from my OS X hard drive to the shared volume on my PC, the same 9.9 MB file take 2 minutes, 15 seconds to copy (from Mac-to-PC). At best that is 10-BaseT speed, though probably not even that fast.

Any ideas as to what I can do to speed up the Mac-to-PC file copying to the same speed as when I copy from PC-to-Mac? Both computers connect to the router/hub at 100Base-T, the status/settings for both network cards show active 100-Mbit connections, and about the only option I can even find to play around with is the Flow Control properties for the 3COM 10/100 NIC on the PC (latest drivers installed), but whether it's set to 100-BaseT full-duplex or AutoSelect, the copying speeds remain the same.

April 17, 2002
Steve Maser

Is nothing really new. It's always faster to "pull" files from a mounted network device than to "push" them. Why? You got me. But it's always been there in the Mac OS (and probably Windows.)

Example: I "pulled" Applications/Utilities from my computer to my test computer. Took 2:15 I "pushed" the folder back from the test computer to a different location on my hard disk. It took 3:42.

However, the author of yesterday's report saw a much bigger disparity: 5 seconds in one direction and 2 minutes, 15 seconds in the other.

May 7, 2002
Joel Shoemaker

I noticed you posted a comment from Steve Maser concerning a possible explanation for the difference in copying speeds Mac-to-PC and PC-to-Mac. While I hadn't considered his explanation, I have to say that my own further testing conflicts with his suggestion and his own tests.

Via the same router that connects my Dell PC and Mac OS X-based B/W G3, I tried copying files to and from a couple of other Macs I have connected, this time using AppleTalk/File Sharing. The results were very different from those I previously noted when using SMB file sharing:

First test: I turned on AppleTalk and File Sharing on my B/W G3 (w/ Mac OS X 10.1.4; by the way, the just-released 10.1.4 update made no difference in the aforementioned SMB file copying speed) and connected to it via 100-BaseT Ethernet with an iMac SE w/ Mac OS 9.2.2 installed. Copying ("pulling") a 21.3 MB file from the B/W G3 to the iMac took 4 seconds. While still sitting at the iMac, copying ("pushing") that same file back to my B/W G3 (to a different spot on its hard drive) took the same amount of time, 4 seconds.

Second test: AppleTalk and File Sharing made active on a Power Mac 7500 (w/ G3/400 processor upgrade) w/ Mac OS 9.1 installed. I connected to that computer using the same iMac SE w/ Mac OS 9.2.2 (only this time using a 10-BaseT Ethernet connection). Pulling a 9 MB file from the PM 7500 took 15 seconds; pushing that same 9 MB file back to the PM 7500 (into a different folder on the hard drive) again took 15 seconds. 

Third test: Connected to the same PM 7500 via AppleTalk with my OS X- based B/W G3 (using 10-BaseT Ethernet) and copied an 8.9 MB file both to and from the PM 7500 in about 17 seconds.

So, it seems like there is no difference speed-wise when copying (pushing or pulling) files to or from one Mac to another, whether Mac OS X or Mac OS 9.x is installed on either computer, and whether the connection is 10 or 100-BaseT Ethernet.

That points to there being an individual problem when sharing files between Macs and PC's, specifically (at least in my case) when a PC share is mounted via SMB on my Mac w/ OS X and I copy files to the PC's hard drive. That being the case, unless someone has run across this particular issue before (though I've been unable to find it documented anywhere), or has a similar setup to mine where they can test the file copying procedure/speeds, I may be stuck with this problem for awhile.

(Maybe someone could check to see if this is a SMB or AppleTalk issue when dealing with Mac and PC file sharing by testing the mounting of AppleTalk-based volumes on their PC (say, via PC MacLAN) to see if there is any noticeable difference between copying files from that Mac volume to their PC and vice-versa. Just a thought.)

May 31, 2002
Joe Clunis

When we initially setup a new network using NT4 I noticed a similar problem. 2 NT4 boxes, both SP6a. Both ran SFM. The Primary domain controller was also the Exchange (5.5 SP4) server. The secondary was the file server. The file server operated just fine.

The primary, however, exhibited the "sorting" problem. I never really noticed if the sorting stopped eventually. The biggest problem was that copying a large number of files or just one large (150 MB, one of the test files) file caused a memory dump. The server goes offline, I run to the server room only to see the blue screen of NT rebooting. 

Because this was a big problem and we could work around having our Macs not connected to that server, we disabled SFM just so nobody could inadvertently reboot the PDC/Mail server. When nimda hit, the PDC ate it (running IIS also... yeah). So during the recovery SP6a was reapplied and it seems to have solved the problem.  

The server was never "re-service packed" because the admin didn't want to risk killing this server. One of the consultants who helped with the nimda recovery mentioned that deleting/messing with the "Microsoft UAM" Mac share can cause corruption of SFM that could conceivably lead to such problems. He recommended not touching it or just disabling the sharing. Who wants their users to connect to "Microsoft UAM" anyway? And of course he noted that the network share for Windows or Mac (identical in our case) should be a directory rather than the root of the volume.

I'm not sure why the secondary server did not exhibit this problem since they were both setup at the same time by the same person. The "sorting" and crash-during-copy may not necessarily be related in all cases, but they certainly seemed to be connected here.

July 15, 2002
Lachlan Stewart reports having the same disparity in performance between Mac-to-PC and PC-to-Mac file copies with Mac OS X and Windows servers that we report on our Mac OS X Special Report page:

I am having exactly the same problem as mentioned in Joel Shoemaker's tests. Copying files to my Win 2K server produces expected network performance (via my all too-hacked-together 100 Mbit network). Roughly I expect around 2-3 MB a sec, reasonable. However copying files from the Win 2K server I can only expect a max of around 600 KB/sec! Very annoying when transferring 600 MB CD images around! 

This has been tested via both Mac OS X SMB mounted shares, and DAVE 3.1 mounted shares. The problem has affected both my old G3 beige with 10/100 PC Ethernet, and my slightly newer B&W G3 10/100 Ethernet. Both with fresh installs of OS X 10.1.5. 

This is where it gets interesting though... If I am copying a file FROM the server - at a blistering 600 KB/s, and then initiate a file transfer TO the server, the incoming transfer moves up to around 2 MB/s, quite respectable from my wobbly old network indeed.

Since the problem only seems to occur with SMB mounts (DAVE or inbuilt SMB - I haven't used Sharity in sometime, but I seem to recall the same problem), and it's quite strange that potentially the file transfer can exceed the painful 600 KB/s I am pointing 'blaming finger' somewhere deep into the bowels of OS X for this one. Maybe network settings need tweaking somewhere deep in there? 

Do other people with similar configurations have these issues? Joel is the first person I have heard mention it and I have been living with this annoying problem since OS X's birth.

Top of page

Mac OS X -to -PCL printing

September 30, 2002
Jeff Fishbein

With some help, I have been able to achieve success printing from OS X (10.1.5, not Jaguar) to my HP LaserJet 5L, a rather common printer among PC users because it was one of the first inexpensive ($399-$499) 600 dpi models. I presume this method would work with ANY printer that uses PCL.

The part I can't explain is the part I'm not tech savvy enough to do on my own -- set up an Intel box running Linux (currently using Red Hat 7.3). Make sure that the LPD service is installed, and it is configured to use a "filter" to convert Postscript (using Ghostscript). The filter that worked best for me was the "ljet4" filter; the "omni" filter skewed the margins badly. Give the printer queue a name you will remember. Connect the PCL printer to the parallel port on that machine.

On the Mac:

Using the Print Center (in Applications/Utilities), add your new printer. After the "Add" dialog appears, make sure that the printer type (top) is "LPR printer using IP." Enter the IP address of the machine that hosts the printer (I do not use DHCP, and cannot say how it would work under that scenario). Deselect the "default queue" option, and enter the queue name you created above. Using the dropdown, select "LaserWriter 4_600" as the printer (others may work; this is the one my outside expert felt would lead to the least number of problems).

Although I can not describe how it might be done, the expert who helped me with the above believes that the printer could be connected to a network print server device, and that the Ghostscript rendering could be performed on the Mac.

I have not test printed from more than a couple apps, so I'm not sure how the quality holds in every circumstance. From Acrobat Reader for example, the photos were apparently scaled in far less than 256 colors, and it shows.

I hope this helps some of your readers who do not want to spend the money on a PS printer, or have a PCL printer already. While CUPS in 10.2 will make a lot of this irrelevant, I suspect a lot of folks, like me, are in no hurry to move to an OS that will break half their applications.

For Mac OS X 10.2 issues, see our Jaguar Cross-platform report page.


| Top of this Mac OS X Special Report Page |

Other MacWindows Departments

| Solutions | Tutorials | Tips | News Archives | Site Map |
|
MacWindows Home |


This site created and maintained by John Rizzo
Copyright 2001-2003 John Rizzo. All rights reserved.