Wind River has no FIRST tab

[TheChosen1]

Ok, so I have installed WindRiver with no evident problems during the installation, but after I apply the 2013 workbench update, and proceed to run WindRiver for the first time, I have no FIRST tab from which I may deploy or undeploy code. This is obviously a major problem for our team and I was wondering if anyone else has experienced this and/or knows how to fix it. I have found a few similar threads on the forums but none of them seemed to have helped me in my predicament. The tutorial that I followed may be found here: http://wpilib.screenstepslive.com/s/...s#!prettyPhoto

I am running WindRiver 3.3.1, if it helps.

[BradAMiller]

Originally Posted by TheChosen1

Ok, so I have installed WindRiver with no evident problems during the installation, but after I apply the 2013 workbench update, and proceed to run WindRiver for the first time, I have no FIRST tab from which I may deploy or undeploy code.

Just to be sure, are you saying there is no FIRST item in the menubar in Workbench after installing the update? Also, can you confirm that you've installed Workbench into C:\WindRiver? The update assumes that installation path.

Brad

[TheChosen1]

Sorry about the late reply, in any case, I actually managed to fix it and the fix is an odd one, in my case I could only get the FIRST tab to appear when I installed WindRiver without the second install disc, the reason why this is so odd is because I am, in fact, using a 64 bit machine on windows 7, which is what the second install disc is for.

[nightpool]

Originally Posted by TheChosen1

Sorry about the late reply, in any case, I actually managed to fix it and the fix is an odd one, in my case I could only get the FIRST tab to appear when I installed WindRiver without the second install disc, the reason why this is so odd is because I am, in fact, using a 64 bit machine on windows 7, which is what the second install disc is for.

Are you sure? I installed WindRiver on a 64-bit Windows 8, and I used the second disk. It all seems fine... Did you run the patch AFTER the second disk?

[TheChosen1]

I'm sure I did, I know it's very weird, but what can I say, at least it is fixed.