🚀 go-pugleaf

In article <tfiske.725743115@qualcom> tfiske@qualcom.qualcomm.com (T.J. Fiske) writes:


   With the upcomming release of Windows Socket Standard, is anybody
   working on converting one of the Windows WAIS clients over to this
   standard?  This would allow one client to work for everybody!  No
   matter what network software they were running under Windows.

   If anyone has any ideas please let me know, we are using PC/TCP and
   therefore cant run and any of the PC Clients, and since we have 400
   PC users, this is a bit a problem? :)

Actually, if you use the generic ethernet version of PC/TCP over
packet drivers, you can run PCWais simply by wrapping a batch file
around it to inet unload beforehand and ethdrv after; alternatively,
and perhaps more simply, you could wrap batch files around your PC/TCP
commands to ethdrv before and inet unload after.  That's what we used
to do, before we decided PC/TCP wasn't worth the bother.

As for ideas for a port, you can find the source code for Faiez
Hindi's version of PCWais at hilbert.wharton.upenn.edu in
pub/tcpip/pcwais.zip; source is for Borland C++ 3.0 with Application
Frameworks, though it should be easy to move the WAIS engine stuff to
other environments, it was a fairly straight port of the Unix 8-b4
code.  In fact, I believe I have a version of the command line waisq
program port to DOS that Faeiz did, which might make a better starting
point; that is in fact how we did PCWais in the first place, port the
command line version then wrap a user interface around the WAIS
engine.  We never bothered to release the command line version, but if
folks are interested let me know and I will have a look when I get
back to the office next week.

Note that neither of these Penn versions with source code have Jim
Fullton's enhancements of relevance feedback, buffer size negotiation
and others; Jim's version is in pcdist.zip at hilbert and at UNC.  I
don't think his version comes with source, though I haven't looked in
a while.  Oh, and there is at least one known bug with both versions
having to do with queries returning no matches that would have to be
found and fixed.


- Tony
  catone@dmark.wharton.upenn.edu

In article <CATONE.92Dec31001034@sovereign-gw.dmark.wharton.upenn.edu> catone@dmark.wharton.upenn.edu (Tony Catone) writes:
>In article <tfiske.725743115@qualcom> tfiske@qualcom.qualcomm.com (T.J. Fiske) writes:
>
>
>   With the upcomming release of Windows Socket Standard, is anybody
>   working on converting one of the Windows WAIS clients over to this
>   standard?  This would allow one client to work for everybody!  No
>   matter what network software they were running under Windows.
>
>   If anyone has any ideas please let me know, we are using PC/TCP and
>   therefore cant run and any of the PC Clients, and since we have 400
>   PC users, this is a bit a problem? :)
>
>Actually, if you use the generic ethernet version of PC/TCP over
>packet drivers, you can run PCWais simply by wrapping a batch file
>around it to inet unload beforehand and ethdrv after; alternatively,
>and perhaps more simply, you could wrap batch files around your PC/TCP
>commands to ethdrv before and inet unload after.

If you need a sockets-based DOS client to start from, try ours.
It's available for anonymous ftp at:
oac.hsc.uth.tmc.edu:/public/dos/misc/oacwais.exe

This is a self-extracting archive.  Contact me for info about the source
code.

Steven E. Newton
Academic Computing

-- 
+      +      +      +      +      +      +    |snewton@oac.hsc.uth.tmc.edu
            I can hear you well,               |Nobody else speaks for me,
            George Orwell.                     |and I speak for no one else.
                                               |     +     +     +     +     +