I recently installed 32bit Vista Business on my work computer (company orders).
After that I decided to give scilab-5.0.3 a try since I've been using scilab-4.1.2 for
some time now. I downloaded the binary and installed it, everything was fine thus far.
However, when I try to start scilab-5.0.3 the system just locks up. The scilab splash-screen
comes up, then the scilab main window appears behind it but it's all white and I can't do anything.
Not even CTRL+ALT+DELETE works.
Okay, I thought and reinstalled scilab-4.1.2 (which works flawlessly in Vista I might add)
Today I decided to try a nightly build to see if there was any difference. Now the scilab splash
comes up, then the scilab window appears behind it but it's still all white and I can't do anything.
However, now CTRL+ALT+DELETE works. So if I press CTRL+ALT+DELETE while scilab 5.1 is
loading and then just press 'cancel', the scilab window appears and I can use the computer and
I've gone through the newsgroup and the bug reports looking for some similar problem but I
haven't found any.
Has anyone had troubles like these? I can't think of any reason for this to happen.
Can you launch scilab 5.x with “Console mode” (icon) (scilex.exe) and type
[a,b] = getdebuginfo()
And do a bug report @ http://bugzilla.scilab.org
You can have many versions of scilab on your pc, if you install in a separate directory.
Example: on my pc , I have 8 versions without any problems
In reply to this post by Emanuel Birge
There, I added a bug and supplied the debuginfo. The bug number is 4115.
On Wed, Feb 11, 2009 at 5:07 PM, Allan CORNET <[hidden email]> wrote:
In reply to this post by Allan CORNET
s = scanf("%s");
r = eval(s);
Jacco Kramer said on 11/11/2008 15:52:
> Hi, I just tried to use the �input� function in scilab 5.0.3 on Win XP.
> When used on the commandline it works fine, but if I run it from scipad
> I get errors. I couldn�t copy it: the only way to get the error was to
> press enter and make a quick screenshot just before scilab shut
> (itself?) down. So, I attached the screenshot to this mail.
This is one of the most often reported bug.
... and many others
Today is however special: it has been reported twice.
The opteam said they "have been working on it [...but...] these bugs
are not trivial to fix". Not idea about the plan for fixing it, if any.
|Free forum by Nabble||Edit this page|