msvcr90-ruby191.dll error

[sal]

Hi,
i have installed flowstone 2 demo on different folder than v1 professional, but after doing that, i get the attached popup with exe exported on v1.
Even adding the msvcr90-ruby191.dll to the same folder where the exe is located the popup appears and only reinstalling flowstone v1 solved the issue.

[AnthonyTower]

Sal,
what version of Windows did you install the exe on?

I test FlowStone2 exes on numerous computers and have reproduced the exact same error as you on a machine running an older version of Windows XP SP3.
After debugging this issue though, I came to the conclusion I had a faulty RAM DIMM in that particular computer.
I also updated that computer's SP3 with the very latest updates.
Everything is okay now.

Let us know.

Cheers

[sal]

hi,
i'm on windows 7 64 bit and it's not a ram problem, it's related to a conflict between flowstone v1 and the ruby functionality of flowstone v2.

[AnthonyTower]

hi,
i'm on windows 7 64 bit and it's not a ram problem, it's related to a conflict between flowstone v1 and the ruby functionality of flowstone v2.

How did you find this out ?
I'm led to believe then, by de-installing FS1 the problem goes away ?
I had that same error message on a 'virgin' Windows XP SP3 install.... before I troubleshooted it to be a RAM issue.

Cheers

[AnthonyTower]

I forgot to add that out of the half dozen computers I test FS2 compiled exes on, half of them are loaded with Windows 7 Home Premium SP 1.

You can always post your problematic compiled exe here and I'll be glad to test it out on my various computers, than give you the results.

Cheers

[sal]

hi Anthony,
maybe my first post is not clear.
I have flowstone v1 professional and i wanted to try flowstone v2 free version on the same system.
After the installation of flowstone v2, the msvcr90-ruby191.dll error is related to exes compiled on flowstone v1.
So it's clear there is something in windows registry that points flowstone to compile the exe including the ruby dll which is only available in v2 and i don't see any relationship with bad ram modules.
After reinstalling flowstone v1 the problem disappeared, so i just wanted to let other people know what i have done to solve it.

[AnthonyTower]

... the msvcr90-ruby191.dll error is related to exes compiled on flowstone v1.
So it's clear there is something in windows registry that points flowstone to compile the exe including the ruby dll which is only available in v2 and i don't see any relationship with bad ram modules.
After reinstalling flowstone v1 the problem disappeared, so i just wanted to let other people know what i have done to solve it.

I wonder if writing an ahead-of-time compiler for Ruby instead of running the Ruby scripts in a run-time environment (and without resorting to a JIT compiler) would solve issues like this one...

Cheers

[DSP]

So basically what you are saying is, only install one copy of FlowStone on your PC.

V2 works perfectly

V1 Works Perfectly

But installing both in separate folders will cause a conflict in the registry.

Makes sense

[csdsp]

hi,
New problem (sorry for my english)

I work with win7 64bits

I've make a very simple software with just a ruby custom ticker and all is basic: time and math component. After i install the exe on 5 computers: 1 with win 7 64 bits (no problem) and 4 with xp sp3 exactly the same, hard and soft, the system is cloned (ssd drive) new system, all checked. 2 works fine and 2 have msvcr90 problem. i don't understand.

Thanks for your help.

Regards

-i've only flowstone 3.02 installed

[trogluddite]

Hi, there,

You're not the only one to have had this problem - but a coupe of other people have managed to fix it on their systems. These are both quite long threads, so you may have to read down a bit to find the suggested fixes...

http://www.dsprobotics.com/support/viewtopic.php?f=2&t=1259&p=4229&hilit=flowstone+crashes#p4212
http://www.dsprobotics.com/support/viewtopic.php?f=2&t=586&hilit=crashes+load

Seems that the error message is sometimes misleading - the .dll you mention in turn calls other .dlls which are part of the Windows installation, and sometimes it is these that are the ones it can't find/

Hope that helps get you fixed up.