> 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

I've forwarded this to Dave.  Depending on how old your DTA is, it may
already be fixed.  He has a Win32 command line and Windowed version
posted somewhere...

Xander

GrimDude wrote:
> 
> 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

Alexander Enzmann wrote:
> 
> I've forwarded this to Dave.  Depending on how old your DTA is, it may
> already be fixed.  He has a Win32 command line and Windowed version
> posted somewhere...

It's hosted at povray.org of all places :)

ftp://ftp.povray.org/pub/povray/utilities/dta/ 

-- 
Ken Tyler

Post a reply to this message

At any rate, I found a program that will allow this to work. CPUGrabber at
the following site:

 http://www.doctorbinky.com/download.html

Thank you for forwarding that post Mr. Enzmann. Is there a snail mail
address for Mr. Mason? I don't use plastic, and I am going to register this
program, as it has suddenly become useful to me.

I'll research that in the docs I have, but it's always nce to know....

You might forward my new email to him, should you desire. gri### [at] wfecanet

Grim

Post a reply to this message

Ah, Ken. The problem is that the functionality of the newer version differs
greatly from earlier versions. Whereas I like bmp files, and avi too, I
liked putting together the old flc, flh, and flt files too.

Now, I am wondering how much it would take to get a peak at his source
files? 8O

Grim

Post a reply to this message

Ken, I sent you email and have not received a response. Are you indisposed?
:)

Grim

Post a reply to this message

GrimDude wrote:
> 
> Ken, I sent you email and have not received a response. Are you indisposed?

Burp. Incoming...

-- 
Ken Tyler

Post a reply to this message