Interprocess communication between a compiled .mdl and a compiled .m

I have a GUIDE script that provides a simple GUI to a model that sends UDP messages to an embedded controller. I'm using 2009b SP1 on a Windows 7 box. It works when run from Matlab. I need to move this to a network that is isolated from my office network, and it will be unable to reach its license servers.

I can't appear to compile both GUI.m and the backend.mdl into one executable file.

I attempted to use the deployment tool to compile GUI.m and real time workshop to compile backend.mdl, but this breaks the communication between GUI.m and backend.mdl.

When I run the compiled backend.mdl, it does not launch GUI.m as it does when running interpreted. When I then run the compiled GUI.m, it scrolls some errors and then exits.

??? Error using ==> run at 65 (next line: reference to a company tool box that is loaded by the interpreter but isn't referenced by my code)

??? Error using ==> evalin Undefined function or variable 'MdlName'.

Error in ==> GUI>GUI_OpeningFcn at 55.

Error in ==> gui_mainfcn at 221

Error in ==> GUI at 42

(various additional complaints about undefined functions, invisible figures at MCR termination, etc.)

What file to the line numbers reference?

Any suggestions on an approach that will work?

Any simple working examples?