forum.vdsworld.com

CodeScript

I get this error frequently if VDS 5.x IDE is run for a long time.
Need not necessary use any externals or @LIB() function.
It causes PVDS/VDS 4.x not to load giving this Hard error message box on Win XP.
VDS 5.x itself gets into this trouble rarely although it troubles it's predecessors.
Is it just me or any one else has similar problems?

PGWARE · **Web Host** Joined: 29 Dec 2001 Posts: 1562

I've encountered messages only like that while debugging with dll's. I have noticed thought that sometimes when opening the vds 5 ide that sometimes it will freeze up and never open all the way. It appears only to happen when opening scripts. The only way to stop it was by doing END TASK on it several times.

FreezingFire · **Admin Team** Joined: 23 Jun 2002 Posts: 3508

Sometimes after using VDS 5 for awhile and I try to open VDS 4, or a
program created with VDS 4, it just gives a runtime error for the compiled
EXE and a Windows XP "This application has encountered a problem and will
now close" error report box. Confused

CodeScript · Posted: Sat Sep 20, 2003 3:35 am Post subject:

vdsalchemist · Posted: Sat Sep 20, 2003 11:29 am Post subject:

Hi All,
Just to let everyone know. PVDS 4.x is not the same product as VDS 4.5. PVDS is new and was released with VDS 5 so PVDS and VDS 5 prob. share some of the same code which could account for the errors being present in both.

FreezingFire · **Admin Team** Joined: 23 Jun 2002 Posts: 3508

Really I think that personal VDS 4 is probably VDS 4 with just the registration
and compilation coding taken out, with perhaps some code from Personal
VDS 2.x

That's just my guess but I don't think they added any new VDS 5 code to it.

vdsalchemist · Posted: Sat Sep 20, 2003 1:54 pm Post subject:

Well that could be true too not sure I will ask CR. I was guessing since Personal VDS came out at the same time as VDS 5 that they do share some of the same code Question

CodeScript · Posted: Sat Sep 20, 2003 2:14 pm Post subject:

This occurs with VDS 3.x/4.x too as I had tested. In fact PVDS is more immune than these and VDS 5.x has the best immunity - rarely succumbs to this.

vdsalchemist · Posted: Sun Sep 21, 2003 3:02 pm Post subject:

CodeScript,
That is strange. I don't think I have ever seen this error under VDS 3.x Question

Actually for the most part the only version of VDS I have really seen memory type exceptions is with VDS 5.

FreezingFire · **Admin Team** Joined: 23 Jun 2002 Posts: 3508

After trying to start VDS 4 after using VDS 5, I get this:

FreezingFire · **Admin Team** Joined: 23 Jun 2002 Posts: 3508

CodeScript · Posted: Mon Sep 29, 2003 1:52 am Post subject:

FreezingFire · **Admin Team** Joined: 23 Jun 2002 Posts: 3508

It's just as you've said, CodeScript. I had it open for a long time
then tried to launch VDS 4. Does the offset number in the error
dialog screenshot I posted help?

CodeScript · Posted: Tue Sep 30, 2003 4:49 am Post subject:

I think the offset number is dependent on other local factors which decide base address etc. but I used to get a given fixed offset per session atleast. I have not done a more closer observation for different window sessions though.