1. Edita not working in Vista
Extreme bummer. After using the latest version of Edita for several weeks
with no problem, it suddenly does not work at all, and I've tried many things:
I have re-installed it, I have installed earlier versions, even tried the
source version where I'm double clicking on Edita.exw. No luck. Edita
shows up in the Task Manager, but in no other way, including in the Alt-Tab
list of programs.
The last time it was working, and while I was in another window, it
spontaneously died, leaving a console error window, which I didn't understand
and closed. I am assuming it is some Microsoft weirdness, some update,
whatever... I did nothing funky with the system as far as I know.
I have checked Windows security settings, but can find no issue there. I do
have an err file, but see nothing in it to suggest why Edita no longer works.
Any ideas?
--Quark
2. Re: Edita not working in Vista
I'd like to know more about this err file.
Don Cole
3. Re: Edita not working in Vista
don cole wrote:
>
>
> I'd like to know more about this err file.
>
> Don Cole
OK, here are the first and last lines of this hughe ex.err file:
C:\EUPHORIA\AAA\EDALL\edita.exe:18645 in function mainHandler()
variable hB has not been assigned a value
hI = 59';'
hJ = 15
hK = 184621241
hL = {0,0,0,0}
... called from C:\EUPHORIA\AAA\EDALL\edita.exe:6266 in function WndProc()
Lt = 6295412
Lu = 15
Lv = 0
Lw = 0
Lx = 59';'
userHandler = <no value>
Ly = 15
Lz = <no value>
MB = <no value>
MC = <no value>
nCode = <no value>
stack = <no value>
MD = {0,0,0,0}
ME = 0
MF = <no value>
MG = 746288
MH = 184621241
^^^ call-back from Windows
... called from C:\EUPHORIA\AAA\EDALL\edita.exe:6537 in function pumpMessage()
MM = 22747464
MN = 0
... called from C:\EUPHORIA\AAA\EDALL\edita.exe:6585 in procedure WinMain()
MT = 1
sw_style = 3
MU = 22747464
... called from C:\EUPHORIA\AAA\EDALL\edita.exe:29836
and the last lines are:
Traced lines leading up to the failure:
C:\EUPHORIA\AAA\EDALL\edita.exe:12660 if visVVV!=isVisible(VVV)then
setVisible(VVV,visVVV)end if
C:\EUPHORIA\AAA\EDALL\edita.exe:12661 if isVisible(SB)then
C:\EUPHORIA\AAA\EDALL\edita.exe:12662 XK=CursorY+1
C:\EUPHORIA\AAA\EDALL\edita.exe:12663 XM=length(filetext[currfile])
C:\EUPHORIA\AAA\EDALL\edita.exe:12664 setText(SB1,sprintf(xl("Line %d of %d
Column %d"),{XK,XM,CursorX+1}))
C:\EUPHORIA\AAA\EDALL\edita.exe:12665 if insertMode then
C:\EUPHORIA\AAA\EDALL\edita.exe:12666 setText(SB2,xl("INS"))
C:\EUPHORIA\AAA\EDALL\edita.exe:12670 if XK>XM then
C:\EUPHORIA\AAA\EDALL\edita.exe:12673 XN=filetext[currfile][XK]
C:\EUPHORIA\AAA\EDALL\edita.exe:12674 XL=MapToByte(XN,CursorX)
C:\EUPHORIA\AAA\EDALL\edita.exe:12676 if XL then
C:\EUPHORIA\AAA\EDALL\edita.exe:12679 setText(SB3,"")
C:\EUPHORIA\AAA\EDALL\edita.exe:12681 XM=c_func(xGetDateFormat,{#400,2,NULL,NULL,NULL,0})
C:\EUPHORIA\AAA\EDALL\edita.exe:12682 XQ=allocate_TextSpace(XM)
C:\EUPHORIA\AAA\EDALL\edita.exe:12683 if
c_func(xGetDateFormat,{#400,2,NULL,NULL,XQ,XM})then
C:\EUPHORIA\AAA\EDALL\edita.exe:12684 XN=peek_string(XQ)
C:\EUPHORIA\AAA\EDALL\edita.exe:12688 setText(SB4,XN)
C:\EUPHORIA\AAA\EDALL\edita.exe:12689 XM=c_func(xGetTimeFormat,{#400,2,NULL,NULL,NULL,0})
C:\EUPHORIA\AAA\EDALL\edita.exe:12690 XQ=allocate_TextSpace(XM)
C:\EUPHORIA\AAA\EDALL\edita.exe:12691 if
c_func(xGetTimeFormat,{#400,2,NULL,NULL,XQ,XM})then
C:\EUPHORIA\AAA\EDALL\edita.exe:12692 XN=peek_string(XQ)
C:\EUPHORIA\AAA\EDALL\edita.exe:12696 setText(SB5,XN)
C:\EUPHORIA\AAA\EDALL\edita.exe:12701 end procedure
C:\EUPHORIA\AAA\EDALL\edita.exe:12707 if currfile and
sequence(routines[currfile])then
C:\EUPHORIA\AAA\EDALL\edita.exe:12723 end procedure
However, I am beginning to wonder about my recent install of Notepad++ and
the files I ran to get it to do Eu syntax coloring and another one from
the Eu site having to do with Notepad++. This last one I need to research
and will have to do it later. Will report anything interesting. This may
be a dead end, so still would like other ideas.
--Quark
4. Re: Edita not working in Vista
Sorry Quark,
That last post got sent prematurely.
Did that err. file show ERROR information on a file that you had
previously been working on (Back when Edita worked)
or
did that err. file show ERROR information on Edita (that you are trying to
run now)?
Don Cole
5. Re: Edita not working in Vista
DB James wrote:
>
> don cole wrote:
> >
> >
> > I'd like to know more about this err file.
> >
> > Don Cole
>
> OK, here are the first and last lines of this hughe ex.err file:
> C:\EUPHORIA\AAA\EDALL\edita.exe:18645 in function mainHandler()
> variable hB has not been assigned a value
> hI = 59';'
> hJ = 15
> hK = 184621241
> hL = {0,0,0,0}
>
> ... called from C:\EUPHORIA\AAA\EDALL\edita.exe:6266 in function WndProc()
>
> Lt = 6295412
> Lu = 15
> Lv = 0
> Lw = 0
> Lx = 59';'
> userHandler = <no value>
> Ly = 15
> Lz = <no value>
> MB = <no value>
> MC = <no value>
> nCode = <no value>
> stack = <no value>
> MD = {0,0,0,0}
> ME = 0
> MF = <no value>
> MG = 746288
> MH = 184621241
>
> ^^^ call-back from Windows
>
> ... called from C:\EUPHORIA\AAA\EDALL\edita.exe:6537 in function pumpMessage()
>
> MM = 22747464
> MN = 0
>
> ... called from C:\EUPHORIA\AAA\EDALL\edita.exe:6585 in procedure WinMain()
>
> MT = 1
> sw_style = 3
> MU = 22747464
>
> ... called from C:\EUPHORIA\AAA\EDALL\edita.exe:29836
>
> and the last lines are:
>
> Traced lines leading up to the failure:
>
> C:\EUPHORIA\AAA\EDALL\edita.exe:12660 if visVVV!=isVisible(VVV)then
> setVisible(VVV,visVVV)end
> if
> C:\EUPHORIA\AAA\EDALL\edita.exe:12661 if isVisible(SB)then
> C:\EUPHORIA\AAA\EDALL\edita.exe:12662 XK=CursorY+1
> C:\EUPHORIA\AAA\EDALL\edita.exe:12663 XM=length(filetext[currfile])
> C:\EUPHORIA\AAA\EDALL\edita.exe:12664 setText(SB1,sprintf(xl("Line %d of %d
> Column %d"),{XK,XM,CursorX+1}))
> C:\EUPHORIA\AAA\EDALL\edita.exe:12665 if insertMode then
> C:\EUPHORIA\AAA\EDALL\edita.exe:12666 setText(SB2,xl("INS"))
> C:\EUPHORIA\AAA\EDALL\edita.exe:12670 if XK>XM then
> C:\EUPHORIA\AAA\EDALL\edita.exe:12673 XN=filetext[currfile][XK]
> C:\EUPHORIA\AAA\EDALL\edita.exe:12674 XL=MapToByte(XN,CursorX)
> C:\EUPHORIA\AAA\EDALL\edita.exe:12676 if XL then
> C:\EUPHORIA\AAA\EDALL\edita.exe:12679 setText(SB3,"")
>
> C:\EUPHORIA\AAA\EDALL\edita.exe:12681 XM=c_func(xGetDateFormat,{#400,2,NULL,NULL,NULL,0})
> C:\EUPHORIA\AAA\EDALL\edita.exe:12682 XQ=allocate_TextSpace(XM)
> C:\EUPHORIA\AAA\EDALL\edita.exe:12683 if
> c_func(xGetDateFormat,{#400,2,NULL,NULL,XQ,XM})then
> C:\EUPHORIA\AAA\EDALL\edita.exe:12684 XN=peek_string(XQ)
> C:\EUPHORIA\AAA\EDALL\edita.exe:12688 setText(SB4,XN)
>
> C:\EUPHORIA\AAA\EDALL\edita.exe:12689 XM=c_func(xGetTimeFormat,{#400,2,NULL,NULL,NULL,0})
> C:\EUPHORIA\AAA\EDALL\edita.exe:12690 XQ=allocate_TextSpace(XM)
> C:\EUPHORIA\AAA\EDALL\edita.exe:12691 if
> c_func(xGetTimeFormat,{#400,2,NULL,NULL,XQ,XM})then
> C:\EUPHORIA\AAA\EDALL\edita.exe:12692 XN=peek_string(XQ)
> C:\EUPHORIA\AAA\EDALL\edita.exe:12696 setText(SB5,XN)
> C:\EUPHORIA\AAA\EDALL\edita.exe:12701 end procedure
> C:\EUPHORIA\AAA\EDALL\edita.exe:12707 if currfile and
> sequence(routines[currfile])then
> C:\EUPHORIA\AAA\EDALL\edita.exe:12723 end procedure
>
> However, I am beginning to wonder about my recent install of Notepad++ and
> the files I ran to get it to do Eu syntax coloring and another one from
> the Eu site having to do with Notepad++. This last one I need to research
> and will have to do it later. Will report anything interesting. This may
> be a dead end, so still would like other ideas.
>
> --Quark
Hello Quark,
I that case it seems to crash in Edita. An err. file from runnning Edita.exw
rather than Edita.exe would be more usefull. As far as Notepad++, never used it,
can't help there.
Don Cole
6. Re: Edita not working in Vista
DB James wrote:
>
> C:\EUPHORIA\AAA\EDALL\edita.exe:18645 in function mainHandler()
> variable hB has not been assigned a value
> hI = 59';'
> hJ = 15
> hK = 184621241
> hL = {0,0,0,0}
>
I have tracked that down to the first red herring: atom icon in bind.ew is not
being initialised. However for this to occur it means that the bind window is
getting a WM_PAINT message at startup, which means there is something wrong with
the main window. The most likely cause of this is something in your edita.ini
file.
1) rename edita.ini to say Xedita.ini
2) start edita as normal
3) examine edita.ini and Xedita.ini and see if you can "fix" the settings eg
Window Position = 149, 4
Window Size = 708, 558
Window Maximized = 1
(let me know what you find please)
4) quit, delete the new edita.ini and rename Xedita.ini back
If this does not solve the problem, try renaming edita.edb
Regards,
Pete
7. Re: Edita not working in Vista
Pete Lomax wrote:
>
> DB James wrote:
> >
> > C:\EUPHORIA\AAA\EDALL\edita.exe:18645 in function mainHandler()
> > variable hB has not been assigned a value
> > hI = 59';'
> > hJ = 15
> > hK = 184621241
> > hL = {0,0,0,0}
> >
> I have tracked that down to the first red herring: atom icon in bind.ew is not
> being initialised. However for this to occur it means that the bind window is
> getting a WM_PAINT message at startup, which means there is something wrong
> with the main window. The most likely cause of this is something in your
> edita.ini
> file.
> 1) rename edita.ini to say Xedita.ini
> 2) start edita as normal
> 3) examine edita.ini and Xedita.ini and see if you can "fix" the settings
> eg Window Position = 149, 4
> Window Size = 708, 558
> Window Maximized = 1
> (let me know what you find please)
> 4) quit, delete the new edita.ini and rename Xedita.ini back
> If this does not solve the problem, try renaming edita.edb
>
> Regards,
> Pete
Hi Pete,
This problem is surreal. I did try your ideas and no luck. The current
version of Edita I'm trying is the non-compiled version. It had no edita.ini
file, but I renamed the edita.edb file and tried running edita.exw. As with
all other attempts, there was a program running in task manager (EXW.exe in
this case), but nothing in a Window. However, a new edita.edb was created
which was identical to the renamed one.
While brooding on the task manager listings, I noticed Nexus radio there and
I had not seen that program visibly for several days though it is set to run
automatically. I decided to uninstall it.
Now for the strange part: in the midst of uninstalling Nexus radio, Edita
popped up! More later when I get back to the computer.
And thanks to Don for his responses.
--Quark
8. Re: Edita not working in Vista
Pete,
Edita is now working normally. Getting rid of the Nexus Radio which was
not running properly (running in memory, but no window or button on the task
bar) caused Edita to return to visibility and has full functionality as far as
I now know.
Don't understand what was happening, but Nexus is an Eu application.
--Quark
9. Re: Edita not working in Vista
- Posted by Pete Lomax <petelomax at blue?onder.?o.uk>
Sep 19, 2007
-
Last edited Sep 20, 2007
DB James wrote:
>
> Pete,
>
> Edita is now working normally. Getting rid of the Nexus Radio which was
> not running properly (running in memory, but no window or button on the
> task bar) caused Edita to return to visibility and has full functionality
> as far as I now know.
>
> Don't understand what was happening, but Nexus is an Eu application.
I can take a guess at what happened. At startup easinst.ew enumerates all
windows and sends them WM_GETTEXTLENGTH and WM_GETTEXT messages, looking for
window titles beginning with "Edita". If the process is dead then Edita locks up.
There may be a trick here to use SendMessageTimeout rather than the current plain
SendMessage, never tried that. Should be pretty easy to write a test window that
plays dead for say 30 seconds, something else I have never deliberately done. 
Regards,
Pete
10. Re: Edita not working in Vista
Pete Lomax wrote:
>
> DB James wrote:
> >
> > Pete,
> >
> > Edita is now working normally. Getting rid of the Nexus Radio which was
> > not running properly (running in memory, but no window or button on the
> > task bar) caused Edita to return to visibility and has full functionality
> > as far as I now know.
> >
> > Don't understand what was happening, but Nexus is an Eu application.
>
> I can take a guess at what happened. At startup easinst.ew enumerates all
> windows and
> sends them WM_GETTEXTLENGTH and WM_GETTEXT messages, looking for window titles
> beginning
> with "Edita". If the process is dead then Edita locks up. There may be a trick
> here
> to use SendMessageTimeout rather than the current plain SendMessage, never
> tried that.
> Should be pretty easy to write a test window that plays dead for say 30
> seconds, something
> else I have never deliberately done.
>
Why use SendMessage() at all?
Since you expect Edita main windows to be top level and of some window class you
may invent for this purpose (don't you?), use FindWindow(lpEditaClassName,NULL).
No need to deal with window text, which ANSI/Unicode issues might make more
confuse. And the process being dead is not a problem, since it is not queried at
all.
CChris
> Regards,
> Pete
