1. BindW not working still
Thanks Rob and Al.
But still,
Running from the interperter (the Edita green light) everything works right.
Which I interpet as, the interpeter is working properly and the enviromental
varibles being set correctly.
I only have trouble binding.
I get :
Fatal run-time error:
BAD IL OPCODE: i is 58, word is 195, len is 3171
This happens from the command line bindw.
And Rob just for the heck of it re-installed (in drive C:) euphoria using
e25setup.exe. Afterwords I tried bindw and I got "Need full version" I then
dragged your secret files to c:\euphoria\bin.
And same problem again.
Any ideas,
Don Cole
2. Re: BindW not working still
don cole wrote:
> Thanks Rob and Al.
>
> But still,
>
> Running from the interperter (the Edita green light) everything works right.
>
> Which I interpet as, the interpeter is working properly and the enviromental
> varibles being set correctly.
>
> I only have trouble binding.
>
> I get :
>
> Fatal run-time error:
> BAD IL OPCODE: i is 58, word is 195, len is 3171
>
> This happens from the command line bindw.
>
> And Rob just for the heck of it re-installed (in drive C:) euphoria using
> e25setup.exe.
> Afterwords I tried bindw and I got "Need full version" I then dragged your
> secret
> files to c:\euphoria\bin.
> And same problem again.
>
> Any ideas,
"BAD IL OPCODE" makes me think that your euphoria\bin\bind.ex
is not from the exact same version of Euphoria as your backendw.exe.
One might be 2.5 alpha or beta, and the other is 2.5 official, for example.
Changes were made to the IL format between 2.5 alpha, beta and official.
Another, not too likely possibility is that your bound .exe file
got corrupted somehow, maybe because your disk or O/S or memory is flaky.
If that's not the case, then send me the necessary source files,
and I'll try to bind them on my machine. There's always a chance
it could be a Euphoria binder bug, but I thought you were binding
successfully before your system crash.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: BindW not working still
Robert Craig wrote:
>
> don cole wrote:
> > Thanks Rob and Al.
> >
> > But still,
> >
> > Running from the interperter (the Edita green light) everything works right.
> >
> > Which I interpet as, the interpeter is working properly and the enviromental
> > varibles being set correctly.
> >
> > I only have trouble binding.
> >
> > I get :
> >
> > Fatal run-time error:
> > BAD IL OPCODE: i is 58, word is 195, len is 3171
> >
> > This happens from the command line bindw.
> >
> > And Rob just for the heck of it re-installed (in drive C:) euphoria using
> > e25setup.exe.
> > Afterwords I tried bindw and I got "Need full version" I then dragged your
> > secret
> > files to c:\euphoria\bin.
> > And same problem again.
> >
> > Any ideas,
>
> "BAD IL OPCODE" makes me think that your euphoria\bin\bind.ex
> is not from the exact same version of Euphoria as your backendw.exe.
> One might be 2.5 alpha or beta, and the other is 2.5 official, for example.
> Changes were made to the IL format between 2.5 alpha, beta and official.
If its any help My euphoria\bin\bind.ex is Feb 6, 2002
and my backendw.exe is Mar 7,2005.
Maybe the 2.5 upgrage files got lost in the crash. I'll see if I can find the
zip somewhere. But that's another problem I lost my My Downloads folder in the
crash.
The more I think about I think you've got the problem nailed down.
Because I re-intalled the binder stuff you sent me but not the 2.5 up grade.
Does this stuff have to be in c: or can it all be in d:?
Thanks for the help,
Don Cole
Thanks for the help
4. Re: BindW not working still
don cole wrote:
> Robert Craig wrote:
> > don cole wrote:
> > > Thanks Rob and Al.
> > >
> > > But still,
> > >
> > > Running from the interperter (the Edita green light) everything works
> > > right.
> > >
> > > Which I interpet as, the interpeter is working properly and the
> > > enviromental
> > > varibles being set correctly.
> > >
> > > I only have trouble binding.
> > >
> > > I get :
> > >
> > > Fatal run-time error:
> > > BAD IL OPCODE: i is 58, word is 195, len is 3171
> > >
> > > This happens from the command line bindw.
> > >
> > > And Rob just for the heck of it re-installed (in drive C:) euphoria using
> > > e25setup.exe.
> > > Afterwords I tried bindw and I got "Need full version" I then dragged your
> > > secret
> > > files to c:\euphoria\bin.
> > > And same problem again.
> > >
> > > Any ideas,
> >
> > "BAD IL OPCODE" makes me think that your euphoria\bin\bind.ex
> > is not from the exact same version of Euphoria as your backendw.exe.
> > One might be 2.5 alpha or beta, and the other is 2.5 official, for example.
> > Changes were made to the IL format between 2.5 alpha, beta and official.
>
> If its any help My euphoria\bin\bind.ex is Feb 6, 2002
That's an old 2.3 bind.ex that's obsolete.
It won't work with 2.5.
You've since upgraded to the 2.5 bind.ex.
Use that one.
In case you need it, I've just sent you the
2.5 Binder instructions again.
> and my backendw.exe is Mar 7,2005.
That's the latest one, for 2.5.
> Maybe the 2.5 upgrage files got lost in the crash. I'll see if I can find the
> zip somewhere. But that's another problem I lost my My Downloads folder in the
> crash.
>
> The more I think about I think you've got the problem nailed down.
>
> Because I re-intalled the binder stuff you sent me but not the 2.5 up grade.
There is no "2.5 upgrade". There is just the full 2.5 official package,
with setup installer from:
http://www.rapideuphoria.com/v20.htm
which is Public Domain. Then there's the 2.5 Binder, which you paid for.
It's a small collecton of files in a .zip, and includes bind.ex.
You just have to add these files to your euphoria\bin directory.
> Does this stuff have to be in c: or can it all be in d:?
It can be in either, but you need the installer to set it up,
or you have to do things manually, by setting your
PATH and your EUDIR environment variables to point to the right place.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
5. Re: BindW not working still
Robert Craig wrote:
> That's an old 2.3 bind.ex that's obsolete.
> It won't work with 2.5.
> You've since upgraded to the 2.5 bind.ex.
> Use that one.
Actually, there is no longer a "bind.ex".
It was replaced in 2.5 by "bind.il", which is
referenced in bind.bat and bindw.bat.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
