-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Chase,,

Thanks for checking checking this out. See comments below:

On 2/7/2014 16:20, Charles Yahrling wrote:
> Greg et al,
> 
> Here's what I found:
> 
> 1) chrome users need to disable malware and fishing protection
> before doing your download else it's flagged as malicious and
> stops

I also got grief from gmail about the attachment, but Norton and AVG
both say my Win box is bug free.

> 2)  unzip of the first file creates ..\Downloads\wsjt-doc\wsjt-doc
> with wsjt-setup.bat inside.
> 
> 3) on the first try, download of cygwin 64 landed in c:\cygwin.
> after launching that I got many popups asking what source server to
> use, what files I wanted, LibUSB-Win32 driver was missing but I
> could get it from sourceforge, and that I needed the win native
> version of Bonjour.

I'll update the instructions so they don't point to the .EXE directly,
then use the Right-Click, Save Too option can be used.

> 4)  I deleted it all and started over, being careful to put cygwin
> in ..\Downloads\wsjt-docs\wsjt-docs. setup batch file then ran as
> advertised.
> 
> 5) running wsjt-doc-setup ran to completion with no errors seen
> 
> 6) wsjt-doc.bat terminated with "/usr/bin/svn.exe: error while
> loading shared libraries cannot open shared object file: no such
> file or directory" ( I used both the corrected svn
> path..../wsjt/doc and the corrected-corrected path .../branches/doc
> ) with same result

I'm a little confused on this one. wsjtx-doc.bat should simplly open
up / run a Cygwin Terminal, then you issue the svn checkout command to
pull the ../branch/doc

subversion is the 3rd element in the set PACKAGES variable, I am not
sure if svn did not install or what the deal is there, but the
wsjt-doc.bat should not be looking for subversion* at all.

When you say you used corrected paths, can you explain that a bit
more? There should be no path correction needed.

> 
> 7)    reboot didn't help
> 
> 8) I have a very fast cable modem connection so i don't think
> timeouts were an issue
> 
> When I earlier queried Joe about the wsjt-x installer defaulting
> to c:\wsjtx his explanation was that versions of windows later than
> XP might not grant appropriate rights to make install go smoothly.
> Could this be related?  If so a rework of the batch files to make
> sure everything lands in c:\wsjt would be a good idea.

Yes, this probably the best approach, c:\wsjtc-doc \ d:\wsjt-doc and
stay well clear of the User Authentication stuff.

> Also, if you make and corrections to your instructions would you
> start over with a new post that goes step by step?   It's too easy
> to make a mistake flipping back and forth between diffs.

I'll write up an updated version for this later today, as Im

> hope this is of some use, chuck
> 
> 
> 
> _______________________________________________ Wsjt-devel mailing
> list [email protected] 
> https://lists.berlios.de/mailman/listinfo/wsjt-devel
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS9Q5zAAoJEAmfcyeKlj0xNf4H/00jMmKCKXIwedIXFMVcy/vp
H9Nsn23Gw+aZ0gSy88ztBYsFSzhrldvU+aMkjalEfJZ4n/EcX4eByUIsjWPXJ8BF
R++966jk6Cfhl/UthL2YuuIWRVU0JTb0PNUDGmOlWNC85WpPMOagV0vbKYijgRMS
ndn/jLFS39dx4A3p4BSc21XXcwqgXxhyD3gZLoAhk6Jp1XpN3p5NURTUBwWNPlbb
GrzjuvI3J7mZgKbBiJ0vMEE9cc1moEcsBMFRrAWzkXcCvX4Fa1GxMiqkXOd20z6i
SN5DkgCAd/rMXS9hVA1ErQiAlyPdNZZS/snY1mB97jq2CChzQD61mIR0pzGG5vc=
=erbs
-----END PGP SIGNATURE-----
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel

Reply via email to