Flowstone & the Paradox Machine

[JB_AU]

How is or in which way is Flowstone Virtualised?

I tried my best to understand nubeat7 messagebox & fileopen example & see why it wasn't working.
I used a little asm to force an infinite loop but separate the shared memory access.
Flowstone crashed, flowstone continuously crashed, removing the schematic, killing the process, removing flowstone , it's components / registry entries & pagefile, not even a restart/shutdown to be sure helped.

I reinstalled flowstone, it still crashed , so out came my books, notes & cd's of tools n gadgets from 80's glory box
Surprisingly tools designed on win95 still work in win7 , cut a long tedious story short.

In C:\Windows\System32 there was a hidden stream with a broken/locked msvcr90-ruby191.dll .
I expunged msvcr90-ruby191.dll & flowstone returned to normal

I like & understand the need to protect or enhance the software to make it more private or more compatible.

I do not need a crystal ball to see the future, surely every time traveler understands the paradox effect, where two of the same object from two separate timelines can not occupy the same space at the same time or everything crashes.

[JB_AU]

I'm bumping this on purpose;
bump
bump

If you go to C:\Windows\System32 & look for msvcr90-ruby191.dll with windows explorer it's not there right???

If you use Flowstone to explore C:\Windows\System32 & look for msvcr90-ruby191.dll with *.* it's there!

If you actually take a deeper look there are many more files.

bump
bump