Currently Being ModeratedMar 24, 2013 8:35 PM (in response to thered2001)
Are you running just the one iWeb site? Because, iWeb does run under Mountain Lion. And, you should be able to copy the iWeb Application over to your new machine along with the iWeb domain file.
If you need help doing so, you could drop me an email at firstname.lastname@example.org & I would be happy to walk you through this. But, it is pretty straight forward
Currently Being ModeratedMar 25, 2013 2:16 AM (in response to thered2001)
So to summarize, iWeb does not display well with Apple Remote Desktop.
Why not show a picture of the remote screen. Saves a lot of typing.
BTW, I have a 12 year old iMac upstairs. I use Chicken of the VNC on my current iMac and Mocha VNC on my iPad.
The iMac upstairs has iWeb 2.0.4. iWeb 3.0 does not run with the installed OS.
And although it is very slow, I can use iWeb from both devices. (It's easier to go upstairs and do the editing there.)
Never had to change settings. Simply started Apple Remote Desktop. That's it.
Perhaps it's better to install iWeb on your new Mac. Use filesharing (same system preference window) and copy everything you need.
Currently Being ModeratedMar 26, 2013 9:09 AM (in response to thered2001)
Solved the problem, sort of.
Because I needed to get work done in iWeb, I plugged in a spare monitor to the Mini. As expected, everything displayed fine locally. I did my work and left the monitor in place and powered on.
After reading some other posts regarding Screen Sharing and artifacts, I had another try at Screen Sharing...
Now that the Mini is no longer "headless" everything displays just fine via Screen Sharing! Pleasing, but not a long-term solution. I had envisioned keeping my seldom-used apps on the Mini and running it headless via Screen Sharing.
So, now on to looking into this line of troubleshooting. And, as mentioned above, this is not the correct forum for further discussion of this problem.