I ran create-client, edited the introducer.furl line in tahoe.cfg to point to the public grid.
Now trying to connect to testgrid, I get: c:\allmydata-tahoe-1.10.0>bin\tahoe.pyscript start STARTING 'C:\Users\mnation\.tahoe' 'C:\Users\mnation\.tahoe' does not look like a directory at all That directory doesn't exist. Sorry for the newb questions. -----Original Message----- From: tahoe-dev-boun...@tahoe-lafs.org [mailto:tahoe-dev-boun...@tahoe-lafs.org] On Behalf Of Mike Nation Sent: Thursday, June 27, 2013 4:51 PM To: Daira Hopwood; Tahoe-LAFS development Subject: Re: [tahoe-dev] Windows install trouble Thank you! I entered "bin\tahoe.pyscript" and that did the trick. Windows couldn't recognize the command "bin\tahoe" because of the other file in that directory named just "tahoe" which isn't an executable. -----Original Message----- From: Daira Hopwood [mailto:davidsa...@leastauthority.com] Sent: Thursday, June 27, 2013 4:24 PM To: Tahoe-LAFS development Cc: Mike Nation Subject: Re: [tahoe-dev] Windows install trouble On 27/06/13 21:42, Mike Nation wrote: > I’m following the instructions here: > https://tahoe-lafs.org/trac/tahoe-lafs/wiki/AdvancedInstall#point9.4 to > install. I > installed the Windows version of Python 2.7. When I complete the > “c:\python27\python > setup.py build” command, I get a 5 KB file named tahoe in the \bin\ > directory, but Windows > doesn’t recognize it as a command – it’s not an executable. bin\tahoe.pyscript should be an executable script, and entering "bin\tahoe" in a Command Prompt should run that script. If that doesn't work, please paste the output of "c:\python27\python setup.py scriptsetup". -- Daira Hopwood ⚥ _______________________________________________ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev _______________________________________________ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev