1. ememcopy.e
- Posted by me <fork at UNIX.TAMU.EDU>
Sep 13, 1998
-
Last edited Sep 14, 1998
Hawke,
I haven't had a chance to implement your code just yet, however I did
find this:
Setting width to 640 and heighth to 480, and running mode 257 results in
no errors. I write to the last row and column, without errors using
this method. It is only running mode 261 at 1024 x 768 that seems to do
it.
Running in mode 261 w/ 1024x768 results in a Windows Error:
Ex
This program has performed an illegal operation and will be terminated.
Quit all programs, and then restart your computer.
Blah, blah, blah, you get the point
Not a causeway error (which I get through incorrect use of se_mem_copy).
This sounds more like an OS problem rather than Euphoria.
thanks
noah
2. Re: ememcopy.e
- Posted by Hawke <mdeland at NWINFO.NET>
Sep 13, 1998
-
Last edited Sep 14, 1998
noah wrote:
>Setting width to 640 and heighth to 480, and running
>mode 257 results in no errors. I write to the last
>row and column, without errors using this method.
>It's only running mode 261-1024 x 768 that seems to do it.
this is a whole different story...
>This sounds more like an OS problem rather than Euphoria.
actually, to me, that sounds not like an OS problem, nor
(as you thought) an euphoria problem. To me, it sounds
like a problem in the library... the routine itself.
If I were going to debug this, I would look at the banking
and indexing within the routine itself...
(that is how i found a really tricky, most nasty error
in the truecolr.e file from chris street... exhibited
similar behavior, but wasn't actually crashing...
it would display parts of an image in strange ways...)
if it wasn't for typos, none of us would get any
programming oversights in their proper places.
:) Hawke'
