Re: Computer crash on OpenDialog D4 App Win2000
- From: Jamie <jamie_ka1lpa_not_valid_after_ka1lpa_@xxxxxxxxxxx>
- Date: Fri, 25 May 2007 22:22:37 -0400
Paul E. Schoen wrote:
"Tom de Neef" <tdeneef@xxxxxxxx> wrote in message news:4657523c$0$334$e4fe514c@xxxxxxxxxxxxxxxxxIf his PC with W2k is totally locking up, that is, no control of other
"Paul E. Schoen" <pstech@xxxxxxxxx> schreef in bericht news:46573aaf$0$7115$ecde5a14@xxxxxxxxxxxxxxxxxxx
I wrote a fairly simple application which selects and opens a text file
from an OpenDialog, and then loads the file into a Memo for processing.
It has worked fine for me on my computer (except for nomal debugging errors during development), and I posted it on my website for people to use.
I got an email from someone who said: "When I tried to go to directory where ASCII files was saved, program hangout. And I need to restart computer." He was using: "SYSTEM: Microsoft windows 2000 running on DELL WORKSTATION PWS360, Intel Pentium4 cpu 4GHz, at/at compatible, 1Gig RAM."
I had a friend recompile it using D2006, which made an exe 120kB larger, but he found no problems with the original version. I have made apps using D4 with the same OpenDialog component with no problems on Win95, Win98, WinMe, and WinXP.
I could possibly understand a problem once the file is opened and processed, but I tried that on various binary files and at worst the Memo just showed some garbage. Yet the user reports a complete computer lockup requiring restart before any files are even loaded?
It may not have to do with W2000. Could it be that your user has locked the files in some way? Can he/she reproduce the error and does it occur when trying to open other ascii files?
Tom
I have not heard back from him since he was going to try the newer compiled version. I even tried running the program from the compressed folder and it was OK. It did not sound like the crash occured upon opening the file, but rather just while browsing. He said he tried it several times with the same result. It would be disturbing to find such a serious crash could occur in a simple common component. I don't know much about W2000. Does the component use the Windows Explorer program to browse for files? Or is that in a DLL for standard Windows VCL functions? It looks like the DoExecute function is written in Delphi and not just a wrapper for a MS Windows function, so I would assume the code is within the executable.
It's only a freely offered utility, not a commercial product, but I also have other programs I am selling, and would like to know if there are bugs in D4 or compatibility issues with W2000. We specify WIN XP, however, so they would run on W2000 at their own risk.
Paul
programs etc.. I would say the problem is on their end.
The OpenFileDialog uses the old standby "GetOpenFileName" which
simply pops up a dialog you see.
from there, it is integrated into the OS with Explorer, its not
anything you can directly control.
Now the question is, do they have problems when selecting a file and
then it gets past to your code?
--
"I'm never wrong, once i thought i was, but was mistaken"
Real Programmers Do things like this.
http://webpages.charter.net/jamie_5
.
- References:
- Computer crash on OpenDialog D4 App Win2000
- From: Paul E. Schoen
- Re: Computer crash on OpenDialog D4 App Win2000
- From: Tom de Neef
- Re: Computer crash on OpenDialog D4 App Win2000
- From: Paul E. Schoen
- Computer crash on OpenDialog D4 App Win2000
- Prev by Date: Re: Computer crash on OpenDialog D4 App Win2000
- Next by Date: Re: A Delphi application and Vista.Problems
- Previous by thread: Re: Computer crash on OpenDialog D4 App Win2000
- Index(es):
Relevant Pages
|
|