CaspianSage
Member
Why do programmers get confused between Halloween and Christmas - OCT31 = DEC25
Steve
Goodness I say you are doing pretty well, I can't get past October 12 ;-)
Why do programmers get confused between Halloween and Christmas - OCT31 = DEC25
Steve
James Mcquade said:In my opinion...
OkiePC said:My advice is to contact Rockwell with your serial numbers and get them converted to Factory Talk activations.
CaspianSage said:...I hate dongles...
EngDave said:...I found out that just by having the USB key plugged in Logix 500 WILL see the keys and run just fine! So for Windows 10 just having a USB key with the master disk on it will allow legacy software to run!...
EngDave said:...Good learning experience though as this is the hand Rockwell has handed us.
EngDave said:Not all of us have time to sort through AB's knowledge base. If I have an issue I check Google first which 99% of the time takes me here where others like me have taken the time to figure out a working solution. So I apologize for the "look at me." I did this for myself and my team and figured I'd share these findings with everyone. I will keep future findings to myself. Thank you for the warm welcome.
A_G said:...We ended up using this method to move activations to USB thumb drives as a precaution in case the original floppies failed.
So just to repeat that with reboots to verify, Logix 500 will work just fine with the USB plugged in.
On a small side note I did do an evmovecf from my USB drive to the C drive on windows 10 and that DID work. I did a run as admin and it added the files just fine, did a few reboots to verify, and even moved them back without loosing anything.
Aabeck said:...What I have done is remove the Win10 hard drive and connect it as an external drive to a XP or Win7 computer and EVMove the activation to the Win10 drive.
Then reinstall the drive & boot up WIn10. RSLogix will boot and see the license.
Not all of us have time to sort through AB's knowledge base. If I have an issue I check Google first which 99% of the time takes me here where others like me have taken the time to figure out a working solution. So I apologize for the "look at me." I did this for myself and my team and figured I'd share these findings with everyone. I will keep future findings to myself. Thank you for the warm welcome.
That's all good and should work no problem as you've described. That would be done using the original EVMOVEW application. But you shouldn't really need to be removing hard disk drives to do this, which can expose users to other potential issues. We are usually very careful doing the likes of this but you just never know.
EVMOVE options...
The original method involved using EVMOVEW to transfer the Activation from the Master Disk in the floppy disk drive to the local hard disk drive. Then, once it was required to move the Activation to the hard disk drive on another machine, you would use EVMOVEW to first transfer the Activation back to the Master Disk and then again to transfer it to the hard disk drive on the other machine.
This was all fine for years as a 3.5 floppy disk drive was a de facto standard on workstation machines. As the floppy disk drive slowly began to disappear, users often now had no way to transfer Master Disk Activations to a hard disk drive on a machine without a floppy disk drive.
As a result of this, and the fact that other removable media such as CompactFlash were now readily available on modern machines; Rockwell released a newer version of the application, namely EVMOVECF. This version then supported the transfer of existing Activations on hard disk drives to CompactFlash cards so as to transfer to the hard disk drive on another machine that also had the now common CF drive. You use EVMOVECF to first transfer from the hard disk drive to the CF card and then you use EVMOVEW on the other machine to transfer from the CF card to the new hard disk drive, similar to how you would have from the Master Disk floppy.
Later, as USB removable media overlapped, and eventually took over from the likes of CF, the EVMOVECF application could still be used to achieve the same transfer using a USB flash drive instead of the CF drive.
Using EVMOVECF and a USB flash drive is the simplest way to transfer these older EVRSI Activations around on the latest machines, Windows 10 included. There really should be no need to remove hard disk drives to carry this transfer out.
Whether some of the older versions of Rockwell software that support EVRSI will work sufficiently under newer operating systems is another potential hurdle and is being discussed here on the Forum quite a bit in recent times.
Regards,
George
Geospark said:...Using EVMOVECF and a USB flash drive is the simplest way to transfer these older EVRSI Activations around on the latest machines, Windows 10 included...
CaspianSage said:I think you may be mistaken here. Any attempt to move a key using any version of Emove on a win 10 machine no matter how you do it has always resulted in loosing the key when I have tried. If you have been successful I would like to know how you did it, The process you described below did not work for me. So I would appreciate it if you have some additional info to enlighten me...
EngDave said:...On a small side note I did do an evmovecf from my USB drive to the C drive on windows 10 and that DID work. I did a run as admin and it added the files just fine, did a few reboots to verify, and even moved them back without loosing anything. Granted this is an enterprise VM...
...I'll try it on my Windows 10 Pro box and report back...
CaspianSage said:...I like this forum a lot, even when asking something I should know or forgot or may seem like an ignorant dumb question, I get help from someone really fast....