Re: question about shared memory in the cygwin daemon

On Aug 4 14:53, Clarke, Trevor wrote: We currently run on 32bit windows and 32/64but solaris with near future plans to run on 64bit windows. The product is for a specific client so we can assume 4gb or more of physical ram. You can't access more than 2GB (or 3GB with the appropriate kernel

Re: question about shared memory in the cygwin daemon

: Dave Korn [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 04, 2004 1:37 PM To: [EMAIL PROTECTED] Subject: RE: question about shared memory in the cygwin daemon -Original Message- From: cygwin-owner On Behalf Of Clarke, Trevor Sent: 04 August 2004 17:54 I'm currently developing image

question about shared memory in the cygwin daemon

I'm currently developing image processing software which will use matlab as a plugin for interactive processing. The problem is, matlab, when called from another program, spawns a separate matlab engine process. The data we are working with can get very large (4gb+) so we can't pass copies of it

RE: question about shared memory in the cygwin daemon

-Original Message- From: cygwin-owner On Behalf Of Clarke, Trevor Sent: 04 August 2004 17:54 I'm currently developing image processing software which will use matlab as a plugin for interactive processing. The problem is, matlab, when called from another program, spawns a separate

RE: question about shared memory in the cygwin daemon

directly on disk. -- Trevor R.H. Clarke [EMAIL PROTECTED] Ball Aerospace Technologies Corp -Original Message- From: Dave Korn [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 04, 2004 1:37 PM To: [EMAIL PROTECTED] Subject: RE: question about shared memory