I used BuildSV to create a self-viewing flic a few years back. It has always
played without any special handling (memory managers, and the like), but now
I get a Runtime Error #200 [memory_address] message whenever I attempt to
run *any* of my old flics (self-viewing).

Does anyone have any ideas?

Grim

Post a reply to this message

GrimDude <gri### [at] wfecanet> wrote:
: Does anyone have any ideas?

  It's most probably because your computer is too fast. The error usually
happens when the program tries to time the speed of the computer and in
a computer which is too fast the counter overflows.

  Yes, as funny as it may sound, computers can be too fast sometimes ;)

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message

GrimDude wrote:
> 
> I get a Runtime Error #200 [memory_address] message whenever I attempt to
> run *any* of my old flics (self-viewing).

It also happens with a lot of old PC games (1991-1994).

-- 
Adrien Beau - adr### [at] freefr - http://adrien.beau.free.fr
 Mes propos n'engagent que moi et en aucun cas mes employeurs

Post a reply to this message

Well, Warp, is there a way to slow a system down to get this thing to work?

Grim

Post a reply to this message

GrimDude <gri### [at] wfecanet> wrote:
: Well, Warp, is there a way to slow a system down to get this thing to work?

  There might be programs out there which slow down the system (by making
idle loops), but I don't know how well they work (specially for DOS programs).

  You could also try slowing the computer by disabling external cache,
internal cache or both. (If you do this, you'd better boot directly to DOS,
as the computer will become slower than a 486 and running Windows in this
mode is quite a pain.)

  Some BIOSes allow you to underclock the CPU, but I'm not sure if they allow
to underclock it so much that it will make a difference with respect to the
DOS program.

  I don't think there's a perfect solution (except fixing the program itself,
which can be quite difficult).


-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message

GrimDude wrote in message <3b5743fe$1@news.povray.org>...
>I used BuildSV to create a self-viewing flic a few years back. It has
always
>played without any special handling (memory managers, and the like), but
now
>I get a Runtime Error #200 [memory_address] message whenever I attempt to
>run *any* of my old flics (self-viewing).


This sounds similar to a problem with all programs compiled using old
versions of Borland C++ when running on any computer with a 500MHz or faster
processor.  I think there's a fix for it out there somewhere.

--
Mark

Post a reply to this message

> Well, Warp, is there a way to slow a system down to get this thing
to work?

Hi Grim!

 On my old P2 300 W98 I can start some Dos-Boxes with a selfprgrammed
simple counter, and that does the trick. But I think I'm on the
too-fast-border: sometimes those runtime-error-200-programmes start
well, sometimes they don't. Running some dosboxes with that
counterprogeramm help.
 Using an old dta version to produce fli-files, I wrote a batch-loop
that starts dta over and over untill "out.fli" exists, then, running
that batchfile, I hold down space till my pc beeps - that seems to
slow down enough to prevent runtime-error-200.
I know it's dirty, but it works for me.

cukk

Post a reply to this message

Can't you just convert into an avi or other?

Andy

"GrimDude" <gri### [at] wfecanet> wrote in message
news:3b5862a4$1@news.povray.org...
> Well, Warp, is there a way to slow a system down to get this thing to
work?
>
> Grim
>
>

Post a reply to this message

Once it's built into a self-executable I don't know how to handle it
anymore. There may be a way to clip off the unwanted portion, but I would be
working blind in that procedure.

Grim

Post a reply to this message

"Mark Wagner" <mar### [at] gtenet> wrote in message
news:3b591b43@news.povray.org...
> GrimDude wrote in message <3b5743fe$1@news.povray.org>...
> >I used BuildSV to create a self-viewing flic a few years back. It has
> always
> >played without any special handling (memory managers, and the like), but
> now
> >I get a Runtime Error #200 [memory_address] message whenever I attempt to
> >run *any* of my old flics (self-viewing).
>
>
> This sounds similar to a problem with all programs compiled using old
> versions of Borland C++ when running on any computer with a 500MHz or
faster
> processor.  I think there's a fix for it out there somewhere.
This might work, but I'd recommend backing up any file that you want to keep
before doing this:
http://alpha.qmw.ac.uk/~ugah006/gotools/tppatch.html
>
> --
> Mark
>
>
>

Post a reply to this message