Prev: remember pushbutton state of internal GUI
Next: remember pushbutton state of internal GUI
From: bob uvacek on 26 Jul 2010 14:20
Hi
it will destroy your previous working Simulink environments.
It will not be able to run your old Simulink models.
It will require to learn tons of internal simulation problem settings before even a simple model will work.
The old models will have errors in results if you make it work.

Ask me more if you want the complete story.
Bob
From: Scott Hirsch on 26 Jul 2010 14:37
Bob -

I'm so sorry to hear that you are apparently having lots of problems running Simulink on a 64-bit OS in R2010a and the R2010b prerelease. We certainly have lots of users who are successfully using these versions of Simulink on 64-bit OS, so it sounds like you have come across some specific issues.

A few thoughts/questions:
* Have you contacted tech support?
* Did you install a 64-bit version of MATLAB, or a 32-bit version?
** Running a 32-bit MATLAB on a 64-bit OS mostly works, but is not officially supported in R2010a: http://www.mathworks.com/support/solutions/en/data/1-1CAT7/?solution=1-1CAT7

- scott
From: bob uvacek on 27 Jul 2010 03:02
"Scott Hirsch" <shirsch.nospam(a)mathworks.com> wrote in message <i2kkl0$adb$1(a)fred.mathworks.com>...
> Bob -
>
> I'm so sorry to hear that you are apparently having lots of problems running Simulink on a 64-bit OS in R2010a and the R2010b prerelease. We certainly have lots of users who are successfully using these versions of Simulink on 64-bit OS, so it sounds like you have come across some specific issues.
>
> A few thoughts/questions:
> * Have you contacted tech support?
> * Did you install a 64-bit version of MATLAB, or a 32-bit version?
> ** Running a 32-bit MATLAB on a 64-bit OS mostly works, but is not officially supported in R2010a: http://www.mathworks.com/support/solutions/en/data/1-1CAT7/?solution=1-1CAT7
>
> - scott

Scott,
the aim here was to install 64bit Simulink on 64 bit OS. Since this 10b version is the first to have working fixed point option on 64bit OS.
How can we find out what got installed?

Do you say that other customers did not loose their old simulation environments?
Or that this is not what should have happened?
Do you say that other customers had their old models work without changing anything?

Or do you just claim that new customers without history can successfully run examples?
At this time I am very skeptical seeing the strong typing requirements and narrowed down use of symbols that is required to succeed.

Errors like "Error using ==> slfs at 120 Target Function Library 'Simulation target TFL IPP is missing or does not contain a valid TFL Table " are suddenly everywhere.
Bob
From: Scott Hirsch on 27 Jul 2010 07:18
Bob -

Thanks for the additional detail. We have been working with plenty of customers who are migrating from 32-bit to 64-bit MATLAB, and we run the same model tests on all of our supported platforms (32- and 64-bit), so it is generally expected that models built in a 32-bit environment should run on 64-bit (with the exception that s-functions would need to be recompiled, as with any platform change).

You should have received an email from the Simulink product manager yesterday. You can work with him on the issue, or get in touch with technical support directly (http://www.mathworks.com/support/contact_us/).

In the meantime, you may find this thread to be helpful:
http://www.mathworks.com/matlabcentral/newsreader/view_thread/279912

You can check which version of MATLAB you have installed by typing "computer" at the command line. The response will end with "64" if you installed the 64-bit version (e.g. PCWIN64 of GLNXA64).

Sorry again about the problems you have encountered, and I hope that we're able to help you get things running smoothly again.

- scott
 | 
Pages: 1
Prev: remember pushbutton state of internal GUI
Next: remember pushbutton state of internal GUI