standalone trouble

Oct 28, 2008 at 4:18am

standalone trouble

I am finding lots of stability issues with the applicaitons I buid that are not in my dev patches.

A. Send/receives not working
b. Buttons and comment will be there the first time I open the app, but then disapper the next time.
C. Apps fail on open

I am using max 5 on windows xp.

Is the standaolen exe the best way to put a max app on a coputer that doesn’t have max installed? Can I install max on multiple computers??

I didn’t have stability issues like this in PD…I am a bit flummoxed

Any help is appreciated

Thanks

#40536
Oct 28, 2008 at 9:57am

On 28 oct. 08, at 05:18, Jon Grant wrote:

>
> I am finding lots of stability issues with the applicaitons I buid
> that are not in my dev patches.
>
> A. Send/receives not working
> b. Buttons and comment will be there the first time I open the app,
> but then disapper the next time.
> C. Apps fail on open
>
> I am using max 5 on windows xp.
>
> Is the standaolen exe the best way to put a max app on a coputer
> that doesn’t have max installed? Can I install max on multiple
> computers??
>
> I didn’t have stability issues like this in PD…I am a bit flummoxed
>
> Any help is appreciated
>
> Thanks

Could you be a little bit more specific?patch, OS version, max
version, steps to reproduce… Otherwise we can only speculate.

Thanks,
ej

#143523
Oct 28, 2008 at 3:30pm

Max 5.0.2
Windows XP SP3

Ok, I did some more fiddling and found the following:

I am using two computers that are hooked into a LAN

I am using a network drive to create the max patch on. The dev machine opes the exe fine. The production machine opens the exe without Comment boxes, buttons, toggles etc below are the error messages. Also [clocker] doesn’t work in the built applications.

folderwatcher_beginproc: ReadDirectoryChangesW failed
folderwatcher_beginproc: ReadDirectoryChangesW failed
folderwatcher_beginproc: ReadDirectoryChangesW failed
folderwatcher_beginproc: ReadDirectoryChangesW failed
folderwatcher_beginproc: ReadDirectoryChangesW failed
Error 126 loading external dac~
gain~: gain~: no such object
ezdac~: ezdac~: no such object
flonum: flonum: no such object
comment: comment: no such object
toggle: toggle: no such object
comment: comment: no such object
message: message: no such object
button: button: no such object

#143524
Oct 28, 2008 at 3:39pm

It’s possible that windows max5 can’t create standalones on network drives.

2 things.
Update to 5.05

Create the standalone on your home drive.

Let us know how you go…

-A

#143525
Oct 28, 2008 at 4:57pm

some things:

I can build the exe fine, then I build the exe with the name Test.exe and I run into trouble.

Are there rules on how a standalone can be named? Also, if I make a standalone, the computer doesn’t need the runtime installed, right? Can there be trouble if the computer has a runtime installed other than from the standalone?

#143526
Oct 28, 2008 at 5:27pm

There were changes in the way we link to the MS C++ runtime in 5.04 I think.

Your standalone should work fine without the runtime installed as long as you created it with a version of max 5 >= 5.04.

As far as I know there are no limitations on names, outside of normal windows OS demands on chars in names.

Let us know more details if you are still having problems. Do you have 5.05 running? Are you building locally?

If it still doesn’t work, then let’s take this into support

support at cycling 74 dot com.

Please attach a copy of the standalone which doesn’t seem to work.

-A

#143527
Oct 28, 2008 at 5:55pm

Ok,

So 5.0.5 is working. Counter works, etc

Except when I name the application test.exe, oh well – not going to name it test anyway. Of course, that only happens when I run test.exe on another machine.

But what is the folderwatcher_beginproc: ReadDirectoryChangesW failed message that pops up?

Thanks again for your help

#143528
Oct 28, 2008 at 7:53pm

BTW, in the next incremental release, 5.06, we shall support multiple standalones being open at the same time.

-A

#143529
Oct 29, 2008 at 9:52pm

Thanks for pointing out the issues with using windows standalones on a network share. Max on windows wasn’t dealing with network filenames (i.e. \sharenamefolderfile.txt) which was causing problems (i.e. launching a standalone from a network share would crash). This will be fixed for Max 5.0.6.

Rob

#143530

You must be logged in to reply to this topic.