Where can I find the module some::module? It seems not available in PPM.
I downloaded and installed all other requirements, but it seems that the rendering script is not referenced. I expect something like tiles.pl for running. Where is this file? There is only Geo-OSM-Tiles package available, but I don't want to calculate tile numbers, I want to render...
Is it really necessary to install 2 of the ActiveState Perl Version 5.10 modules from command line and 5 others via GUI? Instead of Ctrl-Enter menu File/Run marked actions seems to be fine as well.
Error installing tah_light
Installed it and entered username and password but just get: Processing... Completed!
Each time i click "Start TAH"
Also the TAH shortcut on the start menu doesn't work due to a space in the folder name: "C:\Program Files\TilesAtHome\perl\bin\perl.exe" C:\Program Files\TilesAtHome\tah.pl should be: "C:\Program Files\TilesAtHome\perl\bin\perl.exe" "C:\Program Files\TilesAtHome\tah.pl"
--tommg 19:24, 27 August 2008 (UTC)
path with spaces
The problem are spaces in pathnames. I would suggest installing to a path without spaces. I discovered the following places needing patches:
33: my $cmdout =`\"$dircur\\svn\\bin\\svn.exe\" help >NUL`; 371: my $cmd = "\"".$dirperl."\\bin\\perl.exe\" ".$main->BCB->GetLBText($item); 452: my $cmd = "\"$dirsvn\\bin\\svn.exe\" up";
--Stephankn 10:57, 31 August 2008 (UTC)
Installation on Windows Vista 64-bit Ultimate edition
In case this helps anyone else...
I used the Windows installation package available from the wiki link to install it. Once it had installed I cut and pasted the folder from underneath "Program Files (x86)" to somewhere underneath "Documents", and updated the start menu shortcut to reflect this change (adding quotes as per Tommg's comment above). While modifying properties I also set Windows XP compatibility and run as administrator, though I'm not sure these were really required. It seems to be working, anyway - I've now got stats for tiles rendered and kb uploaded on the User\show page.
--EdLoach 14:32, 31 August 2008 (UTC)
Suddenly perl refused to use the temp-dir. It failed detecting tmp being not writeable. Solution was to remove complete tmp directory. The next run recreated the directory structure. In case of a tile associated to your client think about backing up client id.
--Stephankn 20:30, 1 February 2009 (UTC)
Error Downloading Parts of T@H, MD5-Errors
Now there is a similar problem: the version of apache xerces the installer is looking for is no longer at the location it is looking for it. Apache has updated the version (2.10.0 to 2.11.0 I believe). Also downloading the old version from apache's archives doesn't help, because it has a different checksum. I guess, the installer needs to be updated. --JoRi 21:18, 15 December 2010 (UTC)
- Thank you for reporting this. A fixed version 184.108.40.206 is now available. --Stephankn 21:49, 16 December 2010 (UTC)
If Win@home doesn't run after a re-installation, it is recommended to uninstall win@home using the uninstaller located in the TilesAtHome directory, and install it again with the installer. It takes some times btu may unblock an issue with SVN (Subversion).
Possible to install in another partition?
The installer warns against installing on anything else but C:\TilesAtHome but as I'm really low on space on that partition it would be very useful to install in D:\TilesAtHome
What would I need to hand-tune after an installation to that location? apapadop 16:24, 15 April 2011 (BST)
- I remember issues with hard-coded folders in the tah source in the context of classpath. You could grep the source for the foldername to find matching locations. If you create a patch I can apply it. But tah itself is no longer actively developed. Nothing I can do from installer side. So best would be to try and see what happens. --Stephankn 12:02, 10 July 2011 (BST)
Vulnerable version of SVN installed
Subversion 1.6.6 (released 2009) installed with the package, with current version being 1.6.16
Please consider including the latest SVN in the package (or downloading it on demand) - http://subversion.apache.org/security/ indicates there are good reasons to update. apapadop 16:40, 15 April 2011 (BST)
- these issues all affect the server side, not the command line client used by Windows@home. The current version of the installer (220.127.116.11) includes svn 1.6.17. --Stephankn 11:53, 10 July 2011 (BST)