I redownloaded the Etano zip on June 11, deleted the addon domain in my cpanel account that I had it on before, then reuploaded and reinstalled. Instead of deleting the mysql database, I had truncated the user profiles table using phpmyadmin, but there appeared to be a slight bug with the admin after the reinstall. So...
I then deleted the domain again as well as the database, and started over (I did also delete the domain's folder in File Manager both times). After reuploading and reinstalling Etano again, unfortunately it is now partially d.o.a.

I was definitely liking the script in starting to get to know it a bit, despite not <hint> having any more skins yet </hint>

, and I must admit to being puzzled about why this would be happening now.
Here's what's happening:
1. When I sign up as a test user, the email doesn't come, and it doesn't come for anything else like lost password recovery, too
2. I set up the cron job (*/5****), but it sent me this message: ": Sorry, a critical error has occured. If you are the site administrator please check out the error log to see the actual error."
3. The error log in the Etano admin panel keeps getting two errors every hour at 55 min. after the hour:
"mysql_result():
supplied argument is not a valid MySQL result resource
<br /><pre>Array
(
(
[function] => general_error
[args] => Array" ...more
"
Undefined variable: res
<br /><pre>Array
(
(
[file] => /home/[PrivateName]/public_html/[DomainFolderName]/tools/cron/jobs/60/1clean_errors.php
[line] => 11" ...more
Interesting - I just noticed in the admin that these errors now fill only one page going back to June 15, but there were pages and pages before. I guess they get deleted after a while?
My previous install was from a May 24 download which is the same size as the June 11 one (8,242 KB). That one was sending user emails prior to installing the June 11 copy, although at first it had looked as if it wasn't going to. It also looked as if the second one wasn't going to show my added profile field, too, but it did.
Should I just try another domain perhaps? That's ok for this test domain, but it would not be good if this happened for a "real" domain intended for going live.
There's probably a really simple answer...Could it be having deleted and recreated the addon domain so many times (probably up to four times total)?