Some scripts are not running with 6.2 upgrade. How do we check/upgrade .net to 3.5. Thanks.

QUOTE:
Some scripts are not running with 6.2 upgrade.

Be specific, please.

QUOTE:
How do we check/upgrade .net to 3.5.

Microsoft site, Windows Update, Google.

Thank you. I will get back on specifics. Not sure how to post here. Also how can we go back to 6.1?

Why downgrade?

application is freezing and especially when try to close the application. Have to force quit mostly. May be there are many bugs in 6.2

There are probably less bugs in 6.2 than in 6.1 due to continuing bug fixing (User Guide ... What's Changed). Anyway, again it's too vague.

If they are public scripts, what are the names of the scripts that are not running?

Notes!
1. Kagi, Renko, and LineBreak Basic scripts are not supposed to run in 6.2 and each has a Rev A. upgrade that you may download.

2. If you test Futures, the Symbol Info Manager symbol entries may require changes due to the RegEx enhancement.

Could you give me more info on "......each has a Rev A. upgrade that you may download.........
Thank you.

Choose "File->Open Strategy..."
Click the button "Download..."
Check the box "Download Public Strategies".
Click "Begin Download".

You will see "Renko Basic [Rev A]" in the list, as well as a couple of other "[Rev A]" strategies.

Choose this strategy after you "Close" the "Download Strategies" dialog box.

Regards,
--Mike

Mike, Thank you very much.

I don't like the 6.2. It is taking for ever to load the bars on the new chart with new symbol entered. Please suggest to go back to 6.1.

This must be a local issue as nobody else have reported. A report would be helpful if there were more details provided than that.

Since loading new symbol assumes data on demand enabled, then which symbol(s) you're having trouble with? specific? or any? which data provider is this? and if it's Fidelity, have you already contacted them, and what was their resolution?

Maybe you're hitting a bad server? Or the network connection has a temporary glitch? Have you made a traceroute to the data provider's server farm?

Tracking Down Network Problems

I talked to Electronic channel support and they ref to this forum. I will get back. Thanks for the prompt replies.

I repeated. Looks for me server as of now for slow bars loading issue.

For example hershy 5 from published is giving error. Still having intermittent bars loading on various time frames. Very random.

Re: Hershey 5. I doubt that this strategy was ever published, that must be a WSTL translation. These have never been supported but you might like to paste the code for us to check and make sure we're actually not overlooking a new bug.

Thank you. Here is the link.
see DrKoch 1/9/2009 9:18 AM
Last changed: 1/9/2009 9:32 AM by DrKoch

The converted script works fine in 6.2.

Unfortunately, with all our mind readers going on vacation, it's not possible to troubleshoot problems not backed up by detailed error report. ;)

If your experience is different from mine, please follow this checklist from now on to report your findings with enough details:

How to report a Problem?

Could you paste the script the one you said works in 6.2
This could make life lot easier. Thanks.

The code from your link works without modification.

Here is the error message that I am getting when I ran the script.

Here is the link for the screen shot. (see below in Eugene's note)

Here's how you do it using the IMG tag:


The DrawImage method of WSTL internally looks for local Wealth-Lab 3/4 installation directory and requests the image (here: DownArrowMagenta.bmp) from there. If it wasn't found -- for example, when the WL3/4 directory has been removed during uninstall -- WSTL will alert about a missing file.

As you can see, the subject has nothing to do with 6.2. I'm moving the discussion to the WealthScript Translation forum.

p.s. For Fidelity data issues, if they persist, please open a new thread.

Thank you. Now how do I fix this issue. Unless I didn't get it from your message.

It's up to you, and there are different ways ranging from removing the DrawImage call in the translated script and to copying a bitmap file to the location on your screenshot (to make WSTL find the file you removed when deinstalling WL4).

why can not we have all the needed files in the 6.0 or greater installations. why it should look some where else for the files. is there anyway that i can get these files from wiki and plan them in the proper folder. need step by step help. as you know many of us are end users. Also why 6.2 upgrade removes the existing files from wl3/4 directory. Something is seriously missing here.

QUOTE:
why can not we have all the needed files in the 6.0 or greater installations.

1. First and foremost, Version 5/6 never relied on any of these files to work. They are not needed.
2. That was the WSTL's 3rd party developer (Dr. Koch) design decision to make the feature function exactly like this i.e. rely on installed WLP4 to display the DrawImage bitmaps.*
3. WSTL has never been officially supported. The WL6 team really doesn't have to care about how the unsupported 3rd party utility works internally.

QUOTE:
Also why 6.2 upgrade removes the existing files from wl3/4 directory.

Are you sure that you haven't removed it? If you're sure that was not your action, please call your Fidelity rep and ask. It was their decision to remove the WSTL download link too, and we're a 3rd party company not involved in creating the WLP installation package/script.

QUOTE:
is there anyway that i can get these files from wiki

For sure, we won't extract graphic bitmaps of Version 4 to distribute them in the Wiki or elsewhere. :) This makes zero sense. But if it really was the WLP 6.2 installer that has removed the leftover WLP 4 files, then legacy version have been decommissioned by Fidelity quite long ago.

Edit

*On a second thought, Dr.Koch is not to blame here at all, absolutely. As I already said, the solution is up to you. It's your script that is making the call to the inexistent bitmap. Although I provided two suggestions, nothing is stopping you from creating the folder at the exact location above and placing there any BMP (bitmap) images of your choice to serve as the up/down arrows (or whatever) because with DrawImage it's possible to plot a custom bitmap. The syntax: DrawImage. You can find a custom replacement image by searching the web.

I would not blame anyone. All I would like to use the ones working and worked before and I always admire your prompt replies.

QUOTE:
Also why 6.2 upgrade removes the existing files from wl3/4 directory.

I'm quite sure this is not the case. It seems likely that you made a mistake and uninstalled WLP4. Did you?

As Eugene says, the solution for the bitmaps is simple. Just recreate the directory structure required and insert the bitmaps. Right Click here and save the target for your zipped copy of the bitmaps.

Caveat: if the legacy version's registry hive has also been deleted during TrendCatcher's accidental removal of the Wealth-Lab Pro 4's leftover files (it could be a 3rd party system cleanup utility removing orphan files), placing the bitmaps back will not help.

Following the upgrade to 6.2, the script did not run/work. Then Fidelity tech support made me to uninstall the both the WLP's existing in 'add remove programs' and made me to re-install the 6.2 or current version. Then also did not work. 1. script did not work following upgrade. 2. Looks they made me uninstall wlp 4.0 or generic set up application too?? I am trying my best to explain what happened. All together I almost crippled my activities. Fidelity is losing with me. Learned lesson. Next time I will not accept the upgrade unless it is mandatory.

I worked around some scripts that generate the signals but no alerts generated. Frequently the signals are shown after the fact (usually not much of use). This is one of them. At this time, I feel that I lost the tool that I always liked.

Cone, you get a coffee. Eugene, you too. It worked. Worked for real. Beautiful. I see butterflies every where. :) :) :)
Hope it continues to work.

P.S. Let's rename the topic's misleading title "Some strategies are not running with 6.2 upgrade" to a more appropriate one: "Some WSTL scripts are not running after WL4 removal".