Move from one computer to another

[jandrew]

I run Cumulus (with a WH1090) on an old laptop dedicated to that purpose.
I now want to change the operating system on that laptop.
I do this by moving Cumulus and all its data to a second laptop (in order to keep real time updating) then format and install the OS on Computer 1; catch up on all upgrades; load my anti-virus software; set the system not to hibernate; etc - a few hours to do this and double check.. Then reverse the process.
I have performed the following steps :

• Exit Cumulus on Laptop 1;
  Disconnect the WH1090;
  Copy the whole of the Cumulus folder (which is on the C drive) to a memory stick;
  
  Copy the memory stick to the C drive of Laptop 2;
  Connect the WH1090 to Laptop 2;
  Start Cumulus.

I have done this before and it worked perfectly (I think).
But today, things are going wrong :

• I have followed the procedure above;
  But when I start Cumuls on Laptop 2 it appears to spend time downloading all the data from the WH1090 (all 4000+ data items);
  Then it spends an absolute age (20 minutes or so) updating;
  When I look at the data files, the last 2 weeks (about) are double entered - (every minute up to the time when I first disconnected and every 5 minutes [the WH1090 save period] for the overlapping period).

Luckily, I have not formatted Laptop 1. So I can reattach the WH1090 to that laptop and restart Cumulus. Only the most recent data is downloaded from the WH1090 and there is no overlap. So I am OK.

But what am I now doing wrong - I really need to change the OS.
When I have changed computers before (using the above method) everyything went perfectly

?????
jandrew

[mcrossley]

Date and time formats exactly the same on each 'puter? List separators? Read the link at the top of this page about Win7 (if relevant)?

[jandrew]

Ah !! Thanks.

I have re-read that note (having seen it over a month ago) and it certainly seems that this would cause my problem. Laptop 1 is using Windows XP, Laptop 2 is using Windows 7.

However, I'm sure that I used the circumvention on the windows 7 machine when I first read about the problem. BUT, now I'm not so sure. (I have two Windows 7 machines, so did I do it on only one of them ????)

Now that I think about it. When I used my process to change machines before, it was from a Windows 7 desk-top to a Windows 7 laptop.

I have time tomorrow lunch time to try again. I will report back - so watch this space.

jandrew

[steve]

In theory, the Windows 7 issue should no longer be an issue, as I put a circumvention into Cumulus some time ago. But the problem must be something to do with date formats, for it to be downloading the entire logger. If you zip up the diags folder and attach it, I'll take a look. It's probably worth attaching the diags folders from both machines.

[jandrew]

Thanks Steve.

I got up early this morning - all excited - to try again.
Having run the Win7 routine suggested above - still a failure.

I have now run out of time, so I will have another go after lunch and send both diags if another failure.

jandrew

[jandrew]

Hi, here I am again.

I am trying to move my Cumulus processing to another computer.

Let's set the scene, in case it is important:

• I am using 2 laptops.
  "XLLT" is a dedicated machine for running Cumulus and updating my website. It runs the WinXL OS.
  "Win7LT" is the laptop that I use for everyday purposes. It runs the Win7 OS.
  I am using Version 1.9.3 build 1041 of cumulus.
  I have run the procedure below four times - about 4.00pm and 7.00pm on 4 October and at about 9.00am and 1.00pm on 5 October.
  After the second run yesterday I followed the circumvention set out in the note about Windows 7 in the Forum heading above.
  All four runs failed in that they downloaded the whole of the logger data (about 6 minutes) and then "processed data" for about 25 minutes leaving me with corrupted data files.
  That corruption was that all the data for the last 14 days was double loaded and the graph for rainfall which is set to cover 31 days, only covered the last 14 days.

The procedure that I have followed is

• 1. Exit Cumulus on XLLT.
  2. Detach the WH1090 from XLLT.
  3. Copy the whole Cumulus folder from the C drive to a memory stick.
  4. Copy the memory stick to the C drive on Win7LT.
  5. Attach the WH1090 to Win7LT
  6. Start Cumulus on Win7LT
  After the failure explained above:
  7. Exit Cumulus on Win7LT
  8. Detach the WH1090 froom Win7LT
  9. Attach WH1090 to XPLT.
  10. Start Cumulus

The XLLT took a few seconds to download the latest data from the WH1090, processed that data and then worked perfectly.

I attach zipped copies of the Diags folders :

• From the XLLT immediately after step 10 above (whilst Cumulus was still running).
  From Win7LP immediately after step 8 above

I can't work out what I am doing wrong. Help, please.

jandrew

[mcrossley]

Windows 7:
Locale = 2057 ENG: United Kingdom (English (United Kingdom))
List separator=, Decimal separator=. Date separator=/ Time separator=:
Short date format: 05/10/2012
Long date format: 05 October 2012

Windows XP:
Locale = 1033 ENU: United States (English (United States))
List separator=, Decimal separator=. Date separator=/ Time separator=:
Short date format: 10/5/2012
Long date format: Friday, October 05, 2012

[jandrew]

AAARRRrrrggg. I learn something every day.

The data files have each line starting with dd/mm/yy.

Can I just change the XP machine to : Locale = 2057 ENG: United Kingdom (English (United Kingdom))
so that the short date format is dd/mm/yy.

Would I need to exit Cumulus before I did that?
When I restart Cumulus, won't it fall into the same problem and corrupt the date files?

After 6 weeks data on file, will such a change upset my past data ?

I can see that I shall need to tread very carefully. All the more reason to get on with updating the OS on the XP machine.

jandrew

[steve]

The data logs will be OK, but you will need to edit any dates in today.ini to UK format before you can use it on a machine with UK settings. You will probably also need to edit all the other .ini files, e.g. the all-time records in alltime.ini, etc.