1. Pathing problems.
------=_NextPart_000_000B_01BFAD94.C239DBC0
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi all (or at least anyone like me with no life and nothing worthwhile =
to do at Easter!)
I have been attempting to help a new user of Morfit for Euphoria. The =
user has been
unable to get our include to even open the Morfit dll. No matter what =
pathing=20
arrangement we try, the handle returned by open_dll is always zero.
I have not encountered and have not received any other reports of this.
If anyone has had a similar failure with Morfit EU or any other problems =
with it I
would be grateful to hear them.
Does anyone have any suggestions? Would attempting to run this from a =
DOS
based editor (such as ee) cause this (eg problem with directories with =
spaces?)
I'm really stumped. Any help would be greatly appreciated!
Thanks
Mark=20
------=_NextPart_000_000B_01BFAD94.C239DBC0
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Hi all (or at least anyone like me with no life and =
nothing=20
worthwhile to do at Easter!)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>I have been attempting to help a new user of Morfit =
for=20
Euphoria. The user has been</FONT></DIV>
<DIV><FONT size=3D2>unable to get our include to even open the Morfit =
dll. No=20
matter what pathing </FONT></DIV>
<DIV><FONT size=3D2>arrangement we try, the handle returned by open_dll =
is always=20
zero.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>I have not encountered and have not received any =
other reports=20
of this.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>If anyone has had a similar failure with Morfit =
EU or any=20
other problems with it I</FONT></DIV>
<DIV><FONT size=3D2>would be grateful to hear them.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>Does anyone have any suggestions? Would attempting =
to run this=20
from a DOS</FONT></DIV>
<DIV><FONT size=3D2>based editor (such as ee) cause this (eg problem =
with=20
directories with spaces?)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>I'm really stumped. Any help would be greatly=20
appreciated!</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>Thanks</FONT></DIV>
<DIV> </DIV>
------=_NextPart_000_000B_01BFAD94.C239DBC0--
2. Re: Pathing problems.
On Mon, 24 Apr 2000 02:28:21 +0930, Mark Brown <mabrown at SENET.COM.AU> wrote:
>Does anyone have any suggestions? Would attempting to run this from a DOS
>based editor (such as ee) cause this (eg problem with directories with
spaces?)
>
>I'm really stumped. Any help would be greatly appreciated!
>
Mark:
I would suggest that you write a single line simple exw program like:
include dll.e
? open_dll("morfit.dll")
-- pause to read
if getc(0) then
end if
If this doesn't work put the DLL in the same directory as exw. Usally
windows expect a dll to be in the windows directory.
Then the dll maybe corrupted or maybe set for read-only ( I don't know
if that would be a problem though )
Then try loading another DLL if that works then you need your user to get
another copy of the dll from a different source.
hope this helps
Bernie
3. Re: Pathing problems.
Thanks to everyone who has replied to my post. I'm going to deal with each
suggestion one at a time so you know what I've tried
> Directories with spaces ??? ...use quotes... !!!
> eg:
> cd c:\program files
> ...won't work, but:
> cd "c:\program files"
> ...will.
The line that is failing reads as follows so no go I'm afraid
m3d_dll = open_dll("morfit.dll")
Note, we have tried absolute paths like
m3d_dll = open_dll("c:\\Program Files\\morfit.dll")
or whatever and still no go.
>That the user is running the program from a DOS editor could be
>a problem. Have u seen the code? Maybe some typing error, or the
>directory where morfit.dll is?
I thought that too as I had trouble with an early MEdit but that involved
finding the directory in which the models were held. Because the dll
was in the same directory as the include it had no problem in locating
the dll. The code itself is my own MorfitEU.ew include and Todd's
"LoadWorld.exw" example. MorfitEU spits the dummy because it
can't get a handle for the dll.
>I would suggest that you write a single line simple exw program like:
> include dll.e
> ? open_dll("morfit.dll")
> -- pause to read
> if getc(0) then
> end if
The user has tried something similar with the result that he can get a
handle on other dll's but not Morfit (arggghhhhh).
>If this doesn't work put the DLL in the same directory as exw. Usally
>windows expect a dll to be in the windows directory.
Haven't tried the dll in with exw......will suggest that to him
>Then the dll maybe corrupted or maybe set for read-only ( I don't know
>if that would be a problem though )
>Then try loading another DLL if that works then you need your user to get
>another copy of the dll from a different source.
Hadn't thought of that but I don't think so. The bound Euphoria exe of
"Light_3DCard" actually doesn't have a problem with getting the handle
The Morfit "loading world" box comes up.
(is there a clue in that? That was bound on Todd's machine)
The problem seems to exist only when running "raw code"
Many thanks again for the help. If you have any more ideas I'd really
appreciate them (and sorry for the long post)
Mark
4. Re: Pathing problems.
At 02:28 AM 04/24/2000 +0930, you wrote:
>Hi all (or at least anyone like me with no life and nothing worthwhile to
>do at Easter!)
>
>I have been attempting to help a new user of Morfit for Euphoria. The user
>has been
>unable to get our include to even open the Morfit dll. No matter what pathing
>arrangement we try, the handle returned by open_dll is always zero.
>
>I have not encountered and have not received any other reports of this.
>
>If anyone has had a similar failure with Morfit EU or any other problems
>with it I
>would be grateful to hear them.
>
>Does anyone have any suggestions? Would attempting to run this from a DOS
>based editor (such as ee) cause this (eg problem with directories with
>spaces?)
When I ran into this my solution was to use the windows function that
returns short filenames, then run with short filename only. I couldn't
figure out any way to make certain functions work if the path name had a
space in it anywhere. People have assured me that there is a way to make
those long pathnames with spaces work, but I haven't been able to find
it. Converting everything to short (i.e., DOS) filenames works quite
beautifully.
--Brent
++++++++++++ Brent Hugh / bhugh at griffon.mwsc.edu ++++++++++++++
+ Missouri Western St College Dept of Music, St. Joseph, MO +
+ Piano Home Page: http://www.mwsc.edu/~bhugh +
+ Internet Piano Concert: http://www.mwsc.edu/~bhugh/recit +
++++ Classical Piano MP3s: http://www.mp3.com/brent_d_hugh ++++
