NOTEbook file transfer problems (DRM maybe or file corruption maybe)
Maybe this should go in MC 6.0 feedback but it is here for now.
I just had a successful day with MC 6.0 Beta1 on the main machine (meaning no aborts all day and everything worked okay). The day before the replay was pretty good. Lots of nice features. Very happy.
Okay so here comes the big test of whether I roll back to MC 2.1.999.999 or not.
I install MC 6.0 in on the notebook following my procedure which was very well mastered after flipp flopping between MC 2.1.999.999 and MC 3.0 beta about 3 or 4 times. Okay so MC 6.0 is on the notebook. From experience I copy in the DLLs for ELcollections and the GV2.2 DLL as well and I compile absolutely all EL studies which I had exported on the main machine which were running fine all day (I know that if I open a workspace with an uncompiled study it removes it). Great that is all done - my notes are still applicable to MC 6.0 I find (just like yesterdays main machine install).
I copy the database files over as I would normally do as well as the workspaces (this is from main mahine to notebook). My standard daily procedure that works flawlessly with MC 2.1.999.999
That is the good news. Now the bad.
Okay so that is done and I notice in my notes that I have to set the defaults on my drawing tools. So I decide to go into the main machine and set the defaults so I do not loose them. But the main machiine thinks that I am running MC on the notebook (in actual fact all I had done was compile the studies on the notebook so I won't loose them when I open the workspaces). It comes up trys to run but dies. I try it a few times and it asks me if I want to terminate the session on the notebook (which of course is not there) but I decide to answer yes anyway. It goes off then I think it tries to run and just vanishes without a message of any sort. I repeat this about 5 times and it can't figure out that I have nothing running on the notebook.
Okay so I reboot both machines hoping something will clear. No cigar on that try. Exactly the same stuff happens.
Okay so lets try the notebook. (both machines are still connected to the internet at this point). It thinks I am running MC on the main machine. It is wrong but it can not figure that out.
So I decide to unplug the notebook from the internet to see what happens and I run MC on the notebook. It says that I am disconnected and it can not run real time data. That is fine because that is what I put in the checkbox anyway (I want offline data to review the days trading offsite - like I don't want to be in this house any longer MC6.0). Okay so it tries to work and does a little better in that it opens the workspaces and manages to get some of the data. Unfortunately it is still sitting there while I write this and has not put any bars on the charts yet.
Gee, I am one of the guys TSS can trust. I had part of my database program that I run each morning which reminds me to take down MC before I leave to review the charts in the morning (see code below - JW is my initials for my middle name). Since I put that in I don't think I have forgotten once to shut MC down in the morning at home so I can use it offsite. MC 2.1.999.999 is a great program such that shutting it down on the main machine for offsite use is not a big deal in that it comes back up without fail ever within 30 seconds when I get back (something that is mentioned in the case study as being a great feature). Sadly MC 6.0 is still trying to figure it out (20 minutes later). Hopefully MC 6.0 finally reaches the standard that MC 2.1.999.999 has set for excellence in reliablity.
So here is the plan. I go out of the house without the charts. Next morning I check my email and this thread. If I can't get it to run I go to my notes on MC2.1.999.999, fall back (takes about 1 hours if I remember) and I am gone until the official release comes out and I give it one more try at this. I practice the discipline of keeping my mind on trading every day and not thinking about MC 6.0.
Code: Select all
If funcJWYNSmallTalk("Did you bring Multi Charts down before leaving the house.") Then
'no action needed - it is just a reminder.