According to Joe Cotroneo: > Thanks for mentioning that. The installation I used has a copy of sort.exe > in the c:\htdig\bin directory. There are references to /usr/bin/sort.exe > but I think having it in c:\htdig\bin\sort.exe will suffice. > > mv.exe is used by htfuzzy & htsearch and should also be located in the /bin > folder along with sh.exe. I use a custom script to handle the index > building, so that's why I may have overlooked the importance of mv.exe - I > never got any errors for mv.exe not being present.
The /bin/mv string may appear in the htsearch binary as a result of the EndingsDB module being linked it, but it's not used by htsearch. In the 3.1.6 code, I think only "htfuzzy endings" will make use of /bin/mv. In the 3.2.0b4 code, "htfuzzy synonyms" also uses mv. > -----Original Message----- > From: Gilles Detillieux [mailto:[EMAIL PROTECTED]] ... > According to Joe Cotroneo: > > I've recently installed HtDig under Win32 (Windows NT/2000), and like > > many other Win32 attempts had issues getting it all working. > > > > I have come up with some tips that may help anybody else out there > > wishing to use HtDig under Win32 - as I didn't see all of these posted > > anywhere. > > > > I downloaded the Win32 binary version of HtDig hoping for a quick & > > easy installation, and to get it working I had to do the following: > > - install it into c:\htdig - as the program files are hard coded to > > use c:\htdig\bin > > - put the latest copy of cygwin1.dll into c:\htdig\bin (this helped > > with some word sort failed errors) > > - ensure the TMP and TEMP environment variables point to a valid temp > > folder, and there is adequate free disk space > > > > The htmerge program requires \bin\sh.exe to be present, which is not a > > problem if cygwin is installed on the system. However, if cygwin is > > not installed then you need to put a copy of sh.exe into the \bin > > folder on the drive you wish to run it from. Having a copy of > > cygwin1.dll in the bin folder helps as well. > > > > eg, Say you have c:\htdig, but you have a script that runs from drive > > D:, you'll need to have another copy of sh.exe & cygwin1.dll in > > d:\bin\ .. You can skip this if your script changes to c:\htdig\bin > > when performing it's htmerge operation. > > > > With the above steps taken care of your HtDig installation should now > > be functional. > > You didn't mention anything about sort.exe and mv.exe. Don't these also > have to be in \bin for htmerge and htfuzzy to work? -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
