PDA

View Full Version : Problems with 2.0 build 905


Partha
01-03-2003, 02:13 PM
I tried to connect to my own site, and suddenly got this problem :

WinSock 2.0
Connecting to xxxxxxx
Connection failed (Connection timed out)
Delaying for 63 seconds before reconnect attempt #1
An internal error has occurred.
Access violation at address 028F824A. Read of address 028F824A
An internal error has occurred.
Access violation at address 028F824A. Read of address 028F824A
Retry attempt Aborted


I am NOT using a cracked version of FlashFXP but a legit version downloaded from www.flashfxp.com and since I am NOT a registered user of FlashFXP, using it as a shareware with increased delays at startup.

Note : this above problem happened 2 times . But in the 3rd happened, FlashFXP did connect properly and did it's job efficiently. But I would love to know what went wrong above :) .

MxxCon
01-03-2003, 03:53 PM
what's your os?
how often does this error happen?
anything in errorlog.txt?

Partha
01-04-2003, 12:26 PM
1) My Os is windows XP Professional.
2) Happened only twice , both times yesterday. I started FlashFXP twice and each time the error occured twice. But when I started FlashFXP thrice, eveything went on smmoth like nothing has happened before !!
3) There is this thing in errorlog.txt. I am pasting below :


04/01/2003 12:33:39 AM
Version: 2.0 (build 905)
Compiled on: Nov 5, 2002
Object class: TApplication
Object Name:
Access violation at address 028F824A. Read of address 028F824A

04/01/2003 12:33:45 AM
Version: 2.0 (build 905)
Compiled on: Nov 5, 2002
Object class: TApplication
Object Name:
Access violation at address 028F824A. Read of address 028F824A

04/01/2003 12:34:02 AM
Version: 2.0 (build 905)
Compiled on: Nov 5, 2002
Object class: TFrmMain
Object Name: FrmMain
Access violation at address 028F824A. Read of address 028F824A

04/01/2003 12:34:45 AM
Version: 2.0 (build 905)
Compiled on: Nov 5, 2002
Object class: TApplication
Object Name:
Access violation at address 028F824A. Read of address 028F824A

bigstar
01-04-2003, 01:01 PM
You need to upgrade to v2.0 build 906

Partha
01-04-2003, 01:05 PM
Hmmm, so is this a known bug for 2.0 build 905 bigstar ??

bigstar
01-04-2003, 02:51 PM
905 had some code that should of never made it into a public release. Upgrade and see if the problem goes away.