I haven't so far been ble to reproduce this behaviour, either with the new
executable from the Bath site, or from my own build using VC++ 5. Since we
are not dealing with a variable in memory, but an argument to a function,
one's first thought, of some memory overwrite, would not seem to apply.
Is there any sign that the behaviour is associated with a particular
score+orc?

Richard Dobson

pete moss wrote:

> nope, restarting didnt work.
> hey, jpff, is this function with the weird flag one by you or one put in
> one of the msvcrt40.dll files?  just curious, as i can see no reason why
> something hardcoded would suddenly change its code...unless it was
> written by microsoft.
> or perhpas i really shouldnt have read that email entitled good times
> because it has really infected my computer with a nonexistant virus that
> causes csound to change file attributes as if by random.
> or maybe not.
>