Can I insall Studio 7 and keep Studio 6 on the drive.

Go To Last Post
8 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi all,

 

I've been away from programing for awhile but I'm ready to start up again.

I have Studio 6 Version 6.2.1548 Service Pack 2 currently installed on my C:Drive.

I have lots of code that was created with it.

But, I'd like to create my new code with the latest tool...Studio 7.

And I don't want to uninstall Studio 6 and have issues.

 

Is there any reason I can't install Studio 7 side by side with Studio 6?

It's a major version change...so they should both work...right???

 

I could install Studio 7 on a different drive (volume) if that would help.

My primary drive is split up into multiple volumes C: E: F: G: and H:

Right now all my software is installed on C: but I suppose I could install Studio 7 on the E: drive if that was allowed.

 

Also...how is the stability of Studio 7? 

 

Thoughts?

 

 

 

 

 

This topic has a solution.
Last Edited: Mon. Feb 5, 2018 - 04:30 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I think they changed USB support between 6 and 7 so while the two IDEs can happily live side by side they are going to try to share USB support (presumably using that of the last one installed). This could be a problem.
.
You could try Virtualbox to isolate one from another (but to do that you will need Windows installation media)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have both, and simply switch drivers in device manager as needed. I have a thread on this in the studio forum

Jim

If you want a career with a known path - become an undertaker. Dead people don't sue! - Kartman

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB user

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks Clowson and Jim

 

I can't remember where I saw it, but somewhere it mentioned Studio 7 used and updated Jungo Driver that was incompatible with older Studio versions.

That's no biggie.

 

If I need to build old stuff with Studio 6, I can just fire up Studio 7 and use it only to flash the newly created hex file, as well as set fuses.

Since I have two screens on my PC it should be easy.

 

I'm not keen on going back and fourth with drivers on Device Manager.

I would also assume that the new driver may flash new firmware in my AVRISP MKII???

That may be one more headache to address in trying to switch drivers back and forth.

 

My next question is, can I install Studio 7 on my Volume E: drive rather than in C:\Program Files (x86)

Would the Install of Studio 7 on the E: share Atmel system files that reside on C:\Program Files (x86)\Atmel?

 

My C: drive is getting crowded...but I don't want to create headaches or break anything by installing on E:

I want to be sure that my E: Studio Install has everything self-contained...with no cross dependencies to Atmel Studio 6 files residing on C:.

 

Thanks again guys for any info you can provide...

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

jrkirk wrote:
My next question is, can I install Studio 7 on my Volume E: drive rather than in C:\Program Files (x86) Would the Install of Studio 7 on the E: share Atmel system files that reside on C:\Program Files (x86)\Atmel?

If teh E:\ drive is local to your PC then its not a problem, you point the installer to where you want it to go.  If the E:\ is a network drive, Studio will run like crap, and you risk losing your work if you have a network failure.

 

JIm

If you want a career with a known path - become an undertaker. Dead people don't sue! - Kartman

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB user

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

My PC has 2 physical drives.

The first drive is partitioned into C, E, F, G, H, and I.

So I think I'll shoot for E:

 

Thanks again...

This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

OK...I downloaded the Studio 7 local install EXE file and installed Studio 7 on my Primary Disk E: Drive Volume.

During the install process, the installer prompted to load a number of new drivers.

I always answered yes to the new driver installs.

The install went flawlessly.

 

When I brought up Studio 7 for the first time it loaded fine.

 

I started Windows 7 Device Manager and watched as I plugged in my AVRISP MKII programmer.

It recognizes the device and adds a Atmel directory to the top of the device chain.

Expanding the directory shows the active AVRISP MKII driver and the Properties Window says the device is working properly.

No longer is it recognized as a Jungo Driver.

 

So I tried to use Studio 7 device programming function to connect to one of my ATmega32u2 boards.

Unfortunately, Studio 7 was unable to recognize the chip on the board.

 

So I shut down Studio 7 and did a cold boot of the computer...restarted...and reloaded Studio 7.

 

On this reload of Studio 7 instead of the Startup Screen...a different screen came up...a screen saying Studio 7 needed to repair itself.

I responded to continue with the repair.

It went through the repair process fine.

 

So then I shut down Studio 7...cold booted...restarted...and reloaded Studio 7.

I again tried to hook up my AVRISP MK2 to my board.

This time...SUCCESS...the chip was recognized and I looked at the fuses...

 

So things went fairly seamlessly.

 

Then I fired up Studio 6 and tried to go into device programming.

I confirmed it does not work.

My AVRISP MKII device is now loading a driver that is only recognizable by Studio 7.

 

But as I said, I will use Studio 7 to do all my device programming for Hex files generated by either Studio 6 or Studio 7.

 

Thanks for everyone's help!!!

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

CHEERIO!

 

Jim

If you want a career with a known path - become an undertaker. Dead people don't sue! - Kartman

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB user