Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   C/C++ (http://www.chiefdelphi.com/forums/forumdisplay.php?f=183)
-   -   WindRiver "System Clock Has Been Set Back" (http://www.chiefdelphi.com/forums/showthread.php?t=130224)

iShah 22-08-2014 11:13

Re: WindRiver "System Clock Has Been Set Back"
 
Okay, I got the issue fixed. I don't know if this is the right way to do it, but this is what I did.

Step 1: Use windows file manager to find any files made after tomorrow. If not important, delete them. If important, open them up and save them again or copy into a new file to get the date fixed.

Step 2: Delete WindRiver. Use the uninstallers if you want, I don't see that they made a huge difference.

Step 3: Use regedit to find a Windriver folder in your registry. It should have about 2 files, both of which are registry related. Delete it. Continue to search your registry. You will find one registry entry clearly marked as the WindRiver license manager. Delete it.

Step 4(Don't know if this helps, but...): Clear your cache and then restart. You may be hit by some notes saying your registry is being repaired. That's okay.

Step 5: Reinstall WindRiver. Use default directories and don't restart after the 3.0 installation.

Step 7: PROFIT!

/thread

Alan Anderson 22-08-2014 13:23

Re: WindRiver "System Clock Has Been Set Back"
 
I'm sorry for not telling you to clean out the WindRiver stuff from Windows registry in the first place. That's one of the first places to look for persistent license data. I thought I read that you had done that already before I gave my first suggestion, but I must have imagined it.

Certified Nerd 23-08-2014 21:21

Re: WindRiver "System Clock Has Been Set Back"
 
What did you do for revenge?

iShah 24-08-2014 20:18

Re: WindRiver "System Clock Has Been Set Back"
 
Quote:

Originally Posted by Alan Anderson (Post 1397610)
I'm sorry for not telling you to clean out the WindRiver stuff from Windows registry in the first place. That's one of the first places to look for persistent license data. I thought I read that you had done that already before I gave my first suggestion, but I must have imagined it.

Yeah, no, its okay. I got it fixed in the end, and I have frc toolchain set up on my computer now so I have a backup solution regardless.

As to what I did for revenge, well... Our school uses iPads. So, during robotics, the two culprits who did this mysteriously had their iPads drained to empty... repeatedly. They weren't using them or anything, they just... died. Also, upon awakening, the iPads were found to be filled with 1000s of photos of a desk.

If you actually want to know what happened, I just set their brightness to max, bluetooth on, set them to constantly ping for Wi-Fi, and then placed it on a desk and repeatedly mashed the volume buttons within the camera app until the iPads died/utterly crashed. Believe me, we have used iPads with bad batteries, so it doesn't take long.

Tristan Lall 25-08-2014 01:09

Re: WindRiver "System Clock Has Been Set Back"
 
I find it interesting that people are inclined to take it out on your friends, rather than Wind River and Flexera.

The bug you encountered is likely a flailing attempt at prevent a user from circumventing the licence term by changing system dates. The FlexLM licence management software notices that the date has changed: "Shut. Down. Everything." You'd think that Flexera would be capable of a more nuanced response, such as the one Microsoft has been using in case of activation failures for what—15 years?

And although you got it for free, this is also commercial software that people depend on to get their work done. Doesn't it seem rather negligent to have such a simple thing force a customer to spend hours dealing with it? Wind River should have caught that in quality assurance, and leaned on Flexera to stop it from happening.

(I realize that there may be business decisions that drive them to operate this way, but that doesn't make it any less irresponsible.)

Certified Nerd 31-08-2014 11:09

Re: WindRiver "System Clock Has Been Set Back"
 
Quote:

Originally Posted by Tristan Lall (Post 1397890)
I find it interesting that people are inclined to take it out on your friends, rather than Wind River and Flexera.

The bug you encountered is likely a flailing attempt at prevent a user from circumventing the licence term by changing system dates. The FlexLM licence management software notices that the date has changed: "Shut. Down. Everything." You'd think that Flexera would be capable of a more nuanced response, such as the one Microsoft has been using in case of activation failures for what—15 years?

And although you got it for free, this is also commercial software that people depend on to get their work done. Doesn't it seem rather negligent to have such a simple thing force a customer to spend hours dealing with it? Wind River should have caught that in quality assurance, and leaned on Flexera to stop it from happening.

(I realize that there may be business decisions that drive them to operate this way, but that doesn't make it any less irresponsible.)

in his first post he said he knew who did it.


All times are GMT -5. The time now is 14:05.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi