Page 1 of 1

"Common Dialog" error?

Posted: Wed Aug 14, 2002 4:49 pm
by Ian Cabell
I contacted TextPad support about this error, but they say that it's just a Windows thing. Anyone have more information? A way to fix the problem?

The issue happens when I've been using TextPad for a while, though I've known it to happen after just a couple minutes. When I try to save or open a document, I get the message:

"A common dialog box returned error 0xffff
Please notify support@textpad.com.
Try restarting first TextPad, then Windows."

Restarting TextPad does clean things up, but the error sometimes occurs several times in a row. I suppose restarting Windows helps too, but sometimes it doesn't help much.

Thanks for your help,
--Ian

Re: "Common Dialog" error?

Posted: Wed Aug 14, 2002 6:00 pm
by just a friend
One way to isolate the problem is to uninstall Textpad then reinstall. If the problem persists, the problem is most likely Windows. If the problem goes away, then great!

HTH...

Re: "Common Dialog" error?

Posted: Sat Aug 17, 2002 11:12 am
by CyberBrain
Have you tried cleaning your system of ad/spy-ware? I had a problem with once where it sometimes gave me a wierd error-dialog when loading too many files in a workspace. I ofcause can't know if this is it, but it would be very interesting to know.

To clean as/spyware from windows use "Ad-aware" from http://www.lavasoftusa.com

If this was it, please write it here.

Re: "Common Dialog" error?

Posted: Mon Aug 19, 2002 2:44 pm
by Ian Cabell
Thanks for the helpful suggestions!

The problem might be Windows-related, since it's remained after re-installing TextPad. But if TextPad isn't programmed to interact with Windows efficiently, that isn't Windows' fault. Not that I'm an avid Windows supporter...

I haven't tried ad-aware. I'm on a corporate network, so I suspect there are some background IT programs, but I would hope they aren't trying to interrupt my use of TextPad =) I'll take a look and let you know.

Thanks,
--Ian

Re: "Common Dialog" error?

Posted: Mon Aug 19, 2002 4:06 pm
by Ed
This post is not going to help you...

I had this problem on a corporate network, too (not Nortel even though I used to be there). I never did resolve it. Other people running same/similar set ups had no problem. I'd be interested if anyone has an answer to it.