🚀 go-pugleaf

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:

>DOSLOGO - SET EDITOR=<myeditor> is just ignored !

Works fine for me edlin, DOS 5.0 edit or emacs.
Note that it really should be termed as "edit command".
What ever you put there will be executed as a dos command.
For example if I say "edit foobar" in dos to edit a file,
then my set command would be, SET EDITOR=edit. If my edit command
was "C:\emacs\bin\emacs foobar" from dos then my set command would
be set EDITOR=c:\emacs\bin\emacs" (NOT set EDITOR=emacs). 
Also in logo to edit a file you say *edit "myprog (that's one
double quote and no extention).

>        - new files all end up in the \LOGO directory,
>          rather than in \LOGO\WORK - how do I tell the
>          program where to put them ?

DOS logo uses only the current working directory that you started
logo from.

>        - (presumably related) a message on start-up reports
>          (correctly) that there is no LOGO.INI file -
>          what do I put in this ?

I should explained this. But if your "scroll" area is working correctly
then ignore it. It basically allows you to send "Borland graphics codes"
directly to the borland graphics library in case I messed up on some
monitors. It was needed in early versions for VGA work but it now does the
right thing for CGA/EGA/VGA.

>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 keep having to reach for the rodent to reactivate
>          the command entry cursor in the "Commander" -
>          is there something I am missing, or is this just
>          the way this system works ?

I do need to clean this up a bit. As someone suggested up/down arrow
keys would make it so that you don't have to leave the input box so
often in the first place (and less need for mouse). I have to be careful
about having the command window "pull" the focus in to strongly or
I'll get opposite complaints.

>        - Once a "Status" window has been displayed, how can 
>          I get rid of it again (other than just dragging it
>          offscreen) ?

Oh come on, try looking at the status button once the status window
is poped up.

>Kym Thompson - s911190@yallara.cs.rmit.oz.au
>Computer Studies, Nth. Metro College of TAFE, Melbourne, Australia

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.


-- 
________________________________________________________________________________
                        |     The views expressed herein do not     |    Fear
 Victor-charles Scafati |   necessarily represent the views of the  |     no 
 scafati@mr.med.ge.com  |  author, let alone his employer or client |    Art!
________________________________________________________________________________

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.