Ultra 4: Getting off on the wrong foot

Mdgm, thanks for the thought, but I am positive the zip was correct. I may not have explained it on this thread clearly, but the zip going back to the NAS was the same as it came from it, but only the netatalk file had different contents. I suspect the reason the new zip didn't take is probably the same reason the OS Reinstall didn't help.

However, good news. I said to heck with it and installed the Root SSH add on. Then I renamed the file (mv /etc/default/netatalk /etc/default/netatalk.original), then did an OS Reinstall via the boot menu, and hurray, the netatalk file NOW looks correct (included below). Time Machine is now plugging away happily. I was able to mount my Media share via AFP too. However, I am still at 10.6.8 and just got the message "Message from server "netgear" Something wrong with the volume's CNID DB, using temporary CNID DB instead. Check server messages for details. Switching to read-only mode."

Oh boy, this is fun! Does it get better? :-(
I will go searching the forum for this next problem.

netgear:/etc/default# cat netatalk
# Appletalk configuration
# Change this to increase the maximum number of clients that can connect:
AFPD_MAX_CLIENTS=50

# Change this to set the machine's atalk name and zone.
# NOTE: if your zone has spaces in it, you're better off specifying
#       it in afpd.conf
#ATALK_ZONE=@zone
ATALK_NAME=`awk -F. '{ print $1 }' /proc/sys/kernel/hostname`

# specify this if you don't want guest, clrtxt, and dhx
# available options: uams_guest.so, uams_clrtxt.so, uams_dhx.so, 
# 		     uams_randnum.so
AFPD_UAMLIST="-U uams_dhx.so,uams_dhx2.so,uams_guest.so"

# Change this to set the id of the guest user
AFPD_GUEST=nobody

# Set which daemons to run (papd is dependent upon atalkd):
ATALKD_RUN=yes
PAPD_RUN=no
AFPD_RUN=yes
TIMELORD_RUN=no
CNID_METAD_RUN=yes

# Control whether the daemons are started in the background
ATALK_BGROUND=yes