Unexpected error using PICED

Hello to all. I'm facing a problem with my PICED software. I started PICED application, with a new blank project in order to work with my PAC. I clicked "Edit Logic" and then when the window appeared i went directly to help.

So far so good! When i open the help content i wanted then to close everything and leave the help opened in order to take some notes of my own.

As soon as i did it, PICED application had closed and i cant run it. There is the following error message:

Exception 'EAccessViolation' in module PICED.exe at 0050CD67
Access violation at address 0090DD67 in module 'PICED.exe'. Read of address 00000778

Module: LogicEntryFrm, Source: LogicEntryFrm.pas, Line 4245
Procedure: TLogicEntryForm.SetLogicState

I uninstalled PICED, download it again and install it but the problem is the same. I uninstalled it again, used registry cleaning software and install it again. The error message doesn't leave.

Any suggestions?



P.S. I have already pressed "Send" in order to send the error message to Clipsal.

 

I believe that the cause of this problem will be solved with the next release of PICED which is due very, very soon.

 

Do you know approximately when it will be available??

 

Tuesday

 

will it have the backlight not turning off issue on older black and white touchscreens fixed?

 

Yes

 

i have downloaded and install PICED v4.4.0 but the problem seems to be the same!!

So, when i'm lauching PICED i get "PICED.exe has encountered a problem and needs to close". I pressed "click here" for more info and i get the following:

AppName: piced.exe
AppVer: 4.4.0.0
ModNane: kernel32.dll (WTF???)
ModVer: 5.1.2600.5512
Offset: 00012aeb

I press "Close" and then PICED Application is moving on to "Project Detals Wizard". Whatever i do there i get "Unexpected error occur"

Then i press "Cancel" to close PICED and i get the following error on messagebox:


"Error on call Winsock2 library function 'shutdown'. Either the application has not called WSAStartup, or WSAStartup failed"


Any ideas???

 

If you are running Vista you will need to run the application with administrator privileges. See this thread http://www.cbusforums.com/forums/showthread.php?t=4488

 

The error messages appear to be different to what you were getting previously.

Do you get a form with the "Send" button on it ? If so, can you click on it so we get the full details.

If not, can you do a screen grab of the error messages (use Ctrl + Print Screen) and post it ?

From your previous error messages which you sent in, one says you are running Windows 98 and the other says Windows XP SP3. Which one are you using now ?

 

TO RICHO:
Friend i'm using WinXP SP3 and i'm not planning to move to Vista!

TO DARREN:
The error messages are the same as in the first post but this time i gave you some more details in order to get an idea of this problem. Of course, i have sent many time the error messages to Clipsal.
As for the Win98 friend, for me this version of windows is dead

Here are all the screenshots for this problem (i have uploaded a ZIP file)

 

Looks like the error is happening early in the startup of Piced, prior to Delphi's exception mechanism loading.

If it's not too much trouble could you do a test for me.

Download the software http://www.dependencywalker.com/depends22_x86.zip from this website http://www.dependencywalker.com

It is a simple "debugger" that may capture useful information about what is happening during loading of Piced.

A) Extract the files form the zip and run the application "depends.exe".

B) Select File|Open from the menu and browse to and select the Tica executable file. c:\clipsal\piced\piced.exe (guessing on path here)

C) Select the menu options Profile|Start profiling

D) Check all the checkboxes on the dialog, EXCEPT "Automatically open and profile child processes"

E) press OK.

Now the program will try and run Piced. Once the error has occurred, close Piced.

A) Select File|Save As ... browse to a folder on you computer that you can find again, enter enter the name Piced.dwi and press save.

Now post this file to the forums, or send to tech support with a note to pass onto Darren.

(Darren: you will be able to open this file in depends.exe and will give you a good idea of what is happening)

 

Richo i did want exactly what you told me!

As soon as i press Profile-->Start Profiling the debugger started to log everything BUT the PICED application didn't start!!

Here is the log file file as you asked... (i made it zip in order to reduce the size of it)

 

Thanks for that. I talk to Darren about the results.

 

In the screen captures 2.jpg shows the debug info of the first exception. In that dialog there is the link "To view technical information about the error report, click here", does that provide a link to a dump file? This might contain a stack trace which would be really useful.

Otherwise may need to setup Dr.Watson (Microsofts crash data gathering tool), although I think Windows does that automatically nowadays.

 

Richo, here is the dump file of that error that you need to proceed...!

Please inform me what can we do about there problems...

 

Hello Ashleigh.

I'm running WinXP 32-Bit with SP3.

As for the "ACAPTUSER32.DLL" i have installed on my system Adobe 9 (Distiller, Reader, Photophop, Acrobat Pro, ImageReady and LifeCycle Designer).

I believe you that it might cause a problem but PICED was working perfectly before, even with these programs installed on my system and the whole thing happend as described in my first post....!

 

Ashleigh i've tried all of the above but the problem it is the same...! Nothing new happend!

The good thing is that everything in my house working perfectly because i already programmed them months ago.

The bad thing is that i bought something new and i can't make it work the way i want (i will tell you more details some other time what i have done here).