>> >Emerald error 52: Bad File Name or Number
>I've seen this when the file-system that you are exporting the information
>to is not mounted, or that the file your are trying to write to is Write
>Protected or something silly like that.
No such beast -- it's a LOCAL hard drive, Win95.
>In our environment, we mount a UNIX machine via Samba, and if the user
>isn't logged into that resource, Emerald complains about it. Mounting that
>particular drive where the file is located solves the problem.
What drive are you talking about here? The Temp directory? Which
location is it "exporting" to, if not the local temp directory?