Bug in EditPad Lite

[ms]

EditPad Lite
Version 4.5.4 has a bug. I used Editpad Classic for 4 years, very happy
with it, then it started to do funny things on exit.

I tried Lite about a month ago. It was working fine for 2 weeks, then
started what I describe below, so stopped using it. The author does not
respond regarding the free version.

Started using it again 3 days ago as default text editor in W98SE. In
the past 3 days, opened and edited about 30 text files with no problem.

Yesterday, it started the problem again. I double click a text file
(#1), I see 3 tabs, one is the desired file, empty screen, the other 2
files are in the same folder, also empty screens.

I exit, try another text file, opens fine. There appears to be
absolutely nothing wrong or unusual about file #1. I opened it in
Editpad Classic, no problem.

On a file, it seems to suddenly malfunction, consistently on that
file. There was no event on my computer when this happened, just working
with text files. Cold boot this AM, again that particular file has that
problem. There are no viruses, worms, trojans, etc. on my home computer.

Has anyone else seen this behavior?

Is there a utility to look at a "normal" text file to see if something
else is going on?

And what to look for?

Mike Sa

 

[badgolferman]

EditPad Lite
Version 4.5.4 has a bug. I used Editpad Classic for 4 years, very
happy with it, then it started to do funny things on exit.

I tried Lite about a month ago. It was working fine for 2 weeks, then
started what I describe below, so stopped using it. The author does
not respond regarding the free version.

Started using it again 3 days ago as default text editor in W98SE. In
the past 3 days, opened and edited about 30 text files with no
problem.

Yesterday, it started the problem again. I double click a text file
(#1), I see 3 tabs, one is the desired file, empty screen, the other 2
files are in the same folder, also empty screens.

I exit, try another text file, opens fine. There appears to be
absolutely nothing wrong or unusual about file #1. I opened it in
Editpad Classic, no problem.

On a file, it seems to suddenly malfunction, consistently on that
file. There was no event on my computer when this happened, just
working with text files. Cold boot this AM, again that particular
file has that problem. There are no viruses, worms, trojans, etc. on
my home computer.

Has anyone else seen this behavior?

Is there a utility to look at a "normal" text file to see if something
else is going on?

And what to look for?

Mike Sa

I have used EditPad Lite for years also and have never experienced your
problem. You might consider upgrading your version though. It is at 5.2
now and perhaps the big has been fixed.

 

[MLC]

Il 03/gen/2004 _ms_ ha scritto:

Has anyone else seen this behavior?

It is my default text editor and I never saw that behaviour, even with the
old versions.
Meanwhile, follow the badgolferman's hint and upgrade your version!

 

[ms]

I have used EditPad Lite for years also and have never experienced your
problem. You might consider upgrading your version though. It is at 5.2
now and perhaps the big has been fixed.

Thanks to you and Maria.

I just installed the latest (5.2.0). Exactly the same results. BTW, with
some work, it can be changed to an executable instead of an install.
Even the author, won't provide as no install, but says you can move the
exe wherever you want. Of course, once you install, you have to
uninstall to use the exe, save preferences in ini file.

So I need a way to look at the problem text file, see what the problem
is.

Mike Sa

 

[Allen Day]

Thanks to you and Maria.

I just installed the latest (5.2.0). Exactly the same results. BTW, with
some work, it can be changed to an executable instead of an install.
Even the author, won't provide as no install, but says you can move the
exe wherever you want. Of course, once you install, you have to
uninstall to use the exe, save preferences in ini file.

The only files necessary to operate EditPad are the EditPad.exe and
EditPad.ini -- the rest of the files are documentation and, in the case of
EditPad Pro, spellcheck libraries, etc. So, technically, you could open the
install archive and manually extract the necessary files.

It seems unlikely that a plain text file would cause so much trouble, but
if it's not terribly private data, I'd be glad to take a look at it for you
-- just remove the .null from my email address. . .

That aside, I guess you could run a conversion on it to make sure that the
document is properly oem/ansi/unicode but . . . again, none of these things
should bother EditPad.

Have you tried opening the file by clicking file > open rather than just
clicking the file?


--
Allen http://theprawn.com
http://protempore.org/jarday

This is for the flowers, who have no appreciation for beauty;
And the sheer ugliness of it all will surely be lost on them.

 

[Gordon Darling]

On Sat, 03 Jan 2004 13:53:40 +0000, ms wrote:

Hi, there Mike. Hope you had a good Xmas and all the best to you and yours
in 2004.

EditPad Lite
Version 4.5.4 has a bug. I used Editpad Classic for 4 years, very happy
with it, then it started to do funny things on exit.

I tried Lite about a month ago. It was working fine for 2 weeks, then
started what I describe below, so stopped using it. The author does not
respond regarding the free version.

I've always found Jan Goyvaerts very responsive. He could be enjoying a
Xmas/New Year break. On the other hand he is unlikely to be interested in
bug fixing a very old version of

snip

I double click a text file
(#1), I see 3 tabs, one is the desired file, empty screen, the other 2
files are in the same folder, also empty screens.

I exit, try another text file, opens fine. There appears to be
absolutely nothing wrong or unusual about file #1. I opened it in
Editpad Classic, no problem.

On a file, it seems to suddenly malfunction, consistently on that
file. There was no event on my computer when this happened, just working
with text files. Cold boot this AM, again that particular file has that
problem. There are no viruses, worms, trojans, etc. on my home computer.

Has anyone else seen this behavior?

Absolutely, no problems here with any file I throw at EditPad either the
Windows or Linux Version.

Is there a utility to look at a "normal" text file to see if something
else is going on?

And what to look for?

You'll need to look at the problem file with a hex editor and sit with an
ASCII table and look for non-printing control characters embedded in the
file.

However you would be far better upgrading to the current version (5.2.0)
http://EditPadLite.com

Regards
Gordon

 

[dszady]

[...]
Have you tried opening the file by clicking file > open rather than just
clicking the file?

I had the same problem with Adobe 4. Couldn't click on the file to open
it, but took the same route you suggest Allen and it works fine even
with the newer files.

 

[ms]

The only files necessary to operate EditPad are the EditPad.exe and
EditPad.ini -- the rest of the files are documentation and, in the case of
EditPad Pro, spellcheck libraries, etc. So, technically, you could open the
install archive and manually extract the necessary files.

It seems unlikely that a plain text file would cause so much trouble, but
if it's not terribly private data, I'd be glad to take a look at it for you
-- just remove the .null from my email address. . .

That aside, I guess you could run a conversion on it to make sure that the
document is properly oem/ansi/unicode but . . . again, none of these things
should bother EditPad.

Have you tried opening the file by clicking file > open rather than just
clicking the file?


--
Allen http://theprawn.com
http://protempore.org/jarday

This is for the flowers, who have no appreciation for beauty;
And the sheer ugliness of it all will surely be lost on them.

Thanks, Allen.

you could open the install archive and manually extract the necessary >files.

How to open the install archive, it is a setup exe?

There is possibly something with that file. I am back to Editpad Classic
as default. When I rightclick, Open With- Editpad Classic, the file
opens fine. When I browse to the Editpad exe, then open and browse to
the file, it opens fine. But when I go to the file directly and
doubleclick to open, it shows a blank screen in Editpad Classic. At
least not multiple open files like Editpad Lite.

I looked in the file using frhed, a hex editor. I see no difference than
as another "normal" file I looked at in hex.

Thanks for the offer to look at the file (16.9K), I'll email it to you.

Mike Sa

 

[ms]

On Sat, 03 Jan 2004 13:53:40 +0000, ms wrote:

Hi, there Mike. Hope you had a good Xmas and all the best to you and yours
in 2004.

I've always found Jan Goyvaerts very responsive. He could be enjoying a
Xmas/New Year break. On the other hand he is unlikely to be interested in
bug fixing a very old version of

snip


Absolutely, no problems here with any file I throw at EditPad either the
Windows or Linux Version.


You'll need to look at the problem file with a hex editor and sit with an
ASCII table and look for non-printing control characters embedded in the
file.

However you would be far better upgrading to the current version (5.2.0)
http://EditPadLite.com

Regards
Gordon

Thanks, Gordon, and best wishes to you for the new year. You do a
valuable service on ACF with those program postings. Mostly stuff I
don't do, but the MS info is of interest.

I had upgraded to Editpad Lite 5.2, same results.
I posted the file status in a reply to Allen. I think I'm starting to
see the funnies that happen when it's been too long since a W98 install,
as John Corliss once said. Next time, I will get a computer where a
clean restart is easier.

Mike Sa

 

[Allen Day]

[...]
Have you tried opening the file by clicking file > open rather than just
clicking the file?

I had the same problem with Adobe 4. Couldn't click on the file to open
it, but took the same route you suggest Allen and it works fine even
with the newer files.

That's odd -- what it sounds like is, as I told [ms] over e-mail, a problem
with the parameters the system is using to open the file. It may be such a
thing as a bad command line operator in the string in the registry's
setting for that file . . . but, as I'm not having that problem and cannot
very well test, it's only a theory and a sketchy one, at that.

--
Allen http://theprawn.com
http://protempore.org/jarday

This is for the flowers, who have no appreciation for beauty; And the
sheer ugliness of it all will surely be lost on them.