🚀 go-pugleaf

scafati@thor.med.ge.com (Victor-charles Scafati 4-6784 MR Srv) writes:

>In article <mills.718554712@dialup.athena.lkg.dec.com>, mills@athena.lkg.dec.com (George Mills) writes:
>|> s911190@yallara.cs.rmit.OZ.AU (Kym R Thompson) writes:
>|> 
>|> >I am having some problems setting up DOSLOGO and MSWLOGO 2.0.
>|> >They run, BUT:
>|> 

>|> 
>|> >MSWLOGO - The HELP command produces the message "Help file
>|> >          missing ...", even though it (LOGO.HLP) is there !
>|> 
>|> Note that it looks in the area the logo.exe is located.
>|> I've never heard anyone have this problem before. logo.exe
>|> and logo.hlp must be in the same directory.
>|> 

>I hate to correct the author of the software but...

>When I was fooling around with mswlogo, I had this problem, and I solved it by 
>adding "set logopath=e:\logo" (which was my logo directory) to my autoexec.bat.
>The README file told me to do that if my logo directory was anything but c:\logo.
>Why don't you try this Kym?  I think that it will help.

I have no problem being corrected. But I still claim that I'm right.
The only thing logopath is used for is the "lib" directory.
In fact I have logopath pointing at a place that does not have
.exe or .hlp and it works in 3.0 or 3.1 windows.

I can't seem to break it as long as .exe is in the same directory as .hlp.
The code looks up the path the .exe was executed from and uses that for the
.hlp. In fact I plan to get rid of logopath and use the same method for finding
the lib directory but I was lazy.

Now doslogo is another story. The hlp "directory" must be in the logo
directory and the logo directory must be in c:\logo or have logopath set
where ever it is.

Are we mixing up dos versus windows logo or perhaps lib versus hlp.