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.

pete


Mark Wilkes wrote:

> I've had the same problem. Funny thing is that if you restart your
> machine it'll work normally again for a while.
>
> Mark
>
> >This is the version of winsound i am using:
> >MIT Csound: 3.477 (Mar 16 1998)
> >
> >when i compile files, they now come out as read-only.  today is the
> >first day that this has happened.  the files i compiled yesterday
> >are
> >not read-only.  the only difference is now i am using different
> >orc/sco
> >files.  i have never had problems with csound generating  read-only
> >files before.  it doesnt really bother me.  now i have another step
> >to
> >take care of before compiling another file with the same name.  i
> >have
> >just never known an exe file to randomly change its code for no
> >apparant
> >reason.
> >
> >thought id let you guys know
> >pete