When is a 64-bit version going to be released for version 5 (5.1? 5.2?)
I have 2500 stocks, 30min bars, 4 years back.
32-bit XP pro cannot handle even half of it before crashing on OutOfMemoryException.
So I have a Xeon 64-bit and XP Pro 64-bit...Now I just need WL to be able to run on it.
ETA?
Thanks.
Size:
Color:
Should be ready for probably a December release - whatever version number that may be.
Size:
Color:
Wow, so far...
Is there a wrokaround to be able to work with so much data?
Why is it not able to run 64-bit? I thought that .Net programs are portable to whatever platform the .Net package is ported to.
Size:
Color:
It turned out that there was one component used by Wealth-Lab Version 5 (and 5.1) that was incompatible with 64-bit. That component will have to be replaced and a 64-bit installation created later this year.
Size:
Color:
Is this a core component, or just something visual/unessential?
If the later, maybe you could put a flag that will disable the use of it.
Size:
Color:
Thanks for the suggestion, but it's not a question about how to fix it. Fidelity will produce the 64-bit build late this year (I think).
Size:
Color:
Hmmm...but WL 5.1. will still work fine under WOW32 thing of 64-bit Vista,will it?
Size:
Color:
Your guess is as good as mine, but it's not been tested and we're not supporting that configuration. We've purposely disabled installations on 64-bit machines.
Size:
Color:
I got the same problem for a long time. Hope that Fidel can release new version run on 64-bit asap.
Also, do you think it will help to use 2 high-end video card 512mb-1gb GDDR3?
Size:
Color:
QUOTE:
Also, do you think it will help to use 2 high-end video card 512mb-1gb GDDR3?
No, because video memory is not related to this sort of work.
Size:
Color:
Bumping this one,
Any release-date set yet?
Size:
Color:
Size:
Color:
You can run wl5 on x64 using CorFlags.exe from the dotnet framework 2.0 sdk
The problem lies in that (at first glance)there appears to be some 32bit only assemblies and the executable asks for "any version" of dotNET at runtime - on a 64bit platform the os returns the 64bit dotNET, which is incompatibile with the 32bit assembly. Solution: Simply tell the executable to request "x86" dotNET instead.
Size:
Color:
A really good find, thank you.
Size:
Color:
It will run using Sun's VirtualBox, a free application like VmWare. However you will need to have a copy of Windows XP or Vista to create the OS. The setup instructions are clear.
Scott
Size:
Color:
Using Vista Business... have run several thosand symbols without a problem.
Size:
Color:
I heard from Fidel that WL5.3 which can run on 64 bits will be available Feb-Mar 09. In the meantime,
MarketPlaya or Whoever know how to make WL5.1 run on 64 bits XP please help, be a litle specific steps ... , thank a lot.
Size:
Color:
QUOTE:
MarketPlaya or Whoever know how to make WL5.1 run on 64 bits XP please help, be a litle specific steps ... , thank a lot.
It's already on the WL5 Wiki FAQ (thanks to MarketPlaya):
The CorFlags workaround
Size:
Color:
i've tried this procedure with corflags but i'm failing miserably, a brick wall stands in my path of .net knowledge.
would appreciate some futher assistance. i've downloaded the .net SDK and installed it, ran corflags from SDK command prompt
but keep erroring out with "error cf002 could not open file for reading"
from the sdk command or starting from c:\(full path to corflags) i type, corflags.exe c:\users\xxMExx\downloads\wealthlabpro5setup.exe/32bit+
error.
alternatively by adding a space between wealthlabpro5setup.exe and /32bit+ my error out message is "the specified file does not have a valid managed header"
Size:
Color:
Seems like you're trying to install
wealthlabpro5setup.exe with CorFlags, why the need? WLP/WLD installs correctly but won't run on a 64-bit OS. Try to launch WealthLabPro.exe from its main directory using CorFlags.
QUOTE:
alternatively by adding a space between wealthlabpro5setup.exe and /32bit+ my error out message is "the specified file does not have a valid managed header"
This explains it all. The installer you're trying to run is a non-managed app (i.e. not .NET). So, point CorFlags to the right file (WealthLabPro.exe).
Size:
Color:
Eugene, i can't generate a wealthlabpro.exe with version 5 the installer warns and quits.
Size:
Color:
Have you already tried XP SP2 compatibility mode?
Size:
Color:
i have
Size:
Color:
Maybe Fidelity modified the installer somehow, can't tell. Nonetheless, they should be releasing WLP 5.3 real soon.
Size:
Color:
that may be, i had not tried corflags till today though the above .jpg is the same result i got 6 months ago. thanks though.
Size:
Color:
To sweeten the pill, you may take a free trial of Developer 5.1 and apply the CorFlags workaround. At least on Win 7 x64, it runs stable and works fast.
Size:
Color:
This might have been answered somewhere else:
I see ppl writing about release 5.3. Is it released now and does it support vista 64bit?
Regards
Size:
Color:
Developer 5.1 is already 64-bit compatible but only when you apply this
very simple fix. It will run on Windows 7 x64 Ultimate (public beta) as well.
WLP 5.3 is released, Developer not ready yet. By the way, WLP 5.3 users can take a look at their WLP Home Page to find some news about a patch that will see the light soon.
Size:
Color:
Eugene,
Are you refering to the Fidelity Wealth lab page? I didn't see anything about a patch.
Thanks,
Scott
Size:
Color:
No, I was referring to the home page inside WLP 5.3.
Size:
Color:
thanks
Size:
Color:
What is the bottom line today?
Does Wealth Lab 5 support 64 bit Windows Vista?
Thanks,
Size:
Color:
Size:
Color: