[Bug 26744] Matlab 2009a: "Manage Licenses" doesn't work

wine-bugs at winehq.org wine-bugs at winehq.org
Sun Aug 3 17:21:04 CDT 2014


http://bugs.winehq.org/show_bug.cgi?id=26744

--- Comment #6 from Anastasius Focht <focht at gmx.net> ---
Hello folks,

still cannot confirm, works fine here.

Prerequisite: 'winetricks -q mfc42 vb6run'

You also need 'winetricks -q vcrun2005' to work around msvcr80 insufficiency
(bug 37026).

The installer complains about missing .NET Framework during installation of
some component (if one doesn't have Mono by default), but that's rather
harmless.

The error window is by design (Windows vs. Linux/Wine address space layout) and
doesn't affect the actual activation process/license management.

The app does something stupid: it reserves a hard-coded contiguous range of
virtual memory. Upon failure it falls back to 'noshield'.

Also documented here:

http://www.mathworks.de/de/help/matlab/ref/matlabwindows.html

--- quote ---
matlab shieldOption provides the specified level of protection of the address
space used by MATLAB during startup on Windows 32–bit platforms. It attempts to
help ensure the largest contiguous block of memory available after startup,
which is useful for processing large data sets. The shieldOption does this by
ensuring resources such as DLLs, are loaded into locations that will not
fragment the address space. With shieldOption set to a value other than none,
address space is protected up to or after the processing of matlabrc. Use
higher levels of protection to secure larger initial blocks of contiguous
memory, however a higher level might not always provide a larger size block and
might cause startup problems. Therefore, start with a lower level of
protection, and if successful, try the next higher level. You can use the
memory function after startup to see the size of the largest contiguous block
of memory; this helps you determine the actual effect of the shieldOption
setting you used. If your matlabrc (or startup.m) requires significant memory,
a higher level of protection for shieldOption might cause startup to fail; in
that event try a lower level. Values for shieldOption can be any one of the
keywords shown in the table below.

Option

Description

-shield minimum

This is the default setting. It protects the range 0x50000000 to 0x70000000
during MATLAB startup until just before startup processes matlabrc. It ensures
there is at least approximately 500 MB of contiguous memory up to this point.

Start with this, the default value. To use the default, do not specify a shield
option upon startup.

If MATLAB fails to start successfully using the default option, -shield
minimum, instead use -shield none.

If MATLAB starts successfully with the default value for shieldOption and you
want to try to ensure an even larger contiguous block after startup, try using
the -shield medium option.

-shield medium

This protects the same range as for minimum, 0x50000000 to 0x70000000, but
protects the range until just after startup processes matlabrc. It ensures
there is at least approximately 500 MB of contiguous memory up to this point.

If MATLAB fails to start successfully with the -shield medium option, instead
use the default option (-shield minimum).

If MATLAB starts successfully with the -shield medium option and you want to
try to ensure an even larger contiguous block after startup, try using the
-shield maximum option.

-shield maximum

This protects the maximum possible range, which can be up to approximately 1.5
GB, until just after startup processes matlabrc.

If MATLAB fails to start successfully with the -shield maximum option, instead
use the -shield medium option.

-shield none

This completely disables address shielding. Use this if MATLAB fails to start
successfully with the default (-shield minimum) option.
--- quote ---

Again: the activation/managing of licenses works fine here.

If it still crashes after applying the winetricks recipes attach a new
backtrace with Wine 1.7.23 otherwise resolve the bug.

Just stating "still an issue" isn't very useful if the symptoms changed, that's
basically recycling the bug for different issues.

Regards

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.


More information about the wine-bugs mailing list