WinAVR deleted the contents of my PATH environment variable

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

The installation of WinAVR has removed the original contents of my PATH environment variable and replaced it with:

C:\WinAVR-20100110\bin;C:\WinAVR-20100110\utils\bin

The original PATH was quite long but any installation software must never overwrite it.

This is not a new issue as I have already seen this raised in posts from 2010.

I am very surprised that it has not been fixed, and I am now having to spend a couple of hours adding back the paths and dealing with the error messages from missing libraries.

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

This just a note to ay that while this is a problem, it likely will not be fixed. WinAVR is no longer maintaned. There has been no update of the WinAVR package since 20100110.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

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

AFAIR the WinAVR installer presents a checkbox so that the user can select whether or not he wants PATH to be changed or not.

If you don't want the change, don't select that check box.

avrfreaks does not support Opera. Profile inactive.

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

SprinterSB wrote:
AFAIR the WinAVR installer presents a checkbox so that the user can select whether or not he wants PATH to be changed or not.

If you don't want the change, don't select that check box.

That is certainly not a helpful response. A "change" to the path does not mean "deleting all other entries".

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

Nevertheless..

1) Unchecking the check-box seems to be the closest you can come to a good behavior, and
2) This will not be fixed - WinAVR is a dead, no longer maintained, project.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

Last Edited: Thu. Sep 26, 2013 - 08:18 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

CliveGregory wrote:
The installation of WinAVR has removed the original contents of my PATH environment variable and replaced it with:

C:\WinAVR-20100110\bin;C:\WinAVR-20100110\utils\bin

IIRC, WinAVR just adds these two strings in front of PATH. If it would not be so, there would be quite a loud response here on this already - mind, that there are hundreds if not thousands of people who have installed WinAVR20100110, many of them right after it came out, and many of them are regular or irregular here.

So, whatever happened at your installation, was unintended.

JW

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

Quote:

IIRC, WinAVR just adds these two strings in front of PATH. If it would not be so, there would be quite a loud response here on this already

This has always been my experience but I think it was found that if the addition of the two PATH entries overflows the environment string allocation then the fault reported here occurs. I guess that's why only about 3 people amongst the 100's or 1000's who have installed WinAVR have seen this issue. Anyway as Johan says:
Quote:

WinAVR is a dead, no longer maintained, project.

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

clawson wrote:
Quote:

IIRC, WinAVR just adds these two strings in front of PATH. If it would not be so, there would be quite a loud response here on this already

This has always been my experience but I think it was found that if the addition of the two PATH entries overflows the environment string allocation then the fault reported here occurs.
Ah, I see. Thanks for the clarification.

Every day something new to learn...

JW

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

This just happened to me too. Whole system is broken now. There need to be huge warnings anywhere anyone ever talks about installing Winavr.

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

I know it sucks, but you can of-course get the old PATH back by looking in your system backups. :evil:

And again: WinAVR is a dead project. There will be NO maintgenance, and this includes any documentation changes/additions.

Just throw WinAVR out and use the current AVR Toolchain from Atmel instead.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

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

i ran into the same problem tonight, thats really really BAD even if its old and unsuported.

 

but if you happen to have the same problem AND

1. have no actual backup of your system and

2. had an space issue on the system disk, which leads to deleted restore points ;)

AND

3. had not rebooted the system more than twice

 

there is at least hope and a possible solution

 

you can recover your path from the copy windows keeps in the registry

 

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Environment

OR

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Session Manager\Environment

 

here you find a key named "path" which is... well your path variable

 

a good day to anyone with the same problem

Last Edited: Sun. Jun 14, 2015 - 02:06 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Re post #1 above.. also, can one use Windows' restore points to get the path reinstated?

 

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

yes one can,

but as long that you don´t rebooted more than twice

its easier to get it back from the registry backups windows keeps on each successful reboot as i described before.

 

but to your question, if you have a restore point where your path exists

 

1. you create a new restore point

2. then you go to the restore point where your path is complete

    - by booting into it and copy your correct path it to a file or whatever

3. return to your newest restore point and restore the path from what you have copied

 

OR

you could restore the registry file of that restore point from shadowvolume and open it in regedit

that can be done easily with a tool like http://www.shadowexplorer.com where you select the date of the restorepoint

the file is in C:\Windows\System32\config\system

 

OR you open the old file with regedit by selecting the HKEY_LOCAL_Machine and the go to "File" -> "open HIVE" in other languages this might be called "open structure"

then you can select the little arrow thingy right to the open button and select "show previous versions"

there you open the version of "C:\Windows\System32\config\system" which should have your path

 

there are more detailed instructions

http://superuser.com/questions/587404/recover-accidentally-deleted-path-environment-variable

http://superuser.com/questions/265532/how-to-extract-environment-variables-from-system-restore-point-windows-7-64-bit/265575#265575

 

 

i hope that helps

 

 

Last Edited: Sun. Jun 14, 2015 - 02:43 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Welcome to 2015 folks. Why would you be using a 2009 compiler in 2015?

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

SprinterSB wrote:
AFAIR the WinAVR installer presents a checkbox so that the user can select whether or not he wants PATH to be changed or not. If you don't want the change, don't select that check box.

 

Those of us lacking your psychic abilities will have to make the same mistake.

 

FWIW: I found a hint on using SysInternals procexp to restore my PATH.   That worked for me but until I found it I was referencing the WinAVR authors using colorful metaphors.

NOTE: This is where you put your personal "signature". If you don't change it people will know you're a clueless frunobulator.

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

This is 2017  - why is anyone using WinAVR at this stage anyway - it's the best part of an 8 year old compiler!

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

clawson wrote:

This is 2017  - why is anyone using WinAVR at this stage anyway - it's the best part of an 8 year old compiler!

 

For Teensy.  From: https://www.pjrc.com/teensy/

Software Development Tools

WinAVR C compiler.

Teensyduino, add-on for Arduino IDE.

Simplified USB Examples or Dean Camera's LUFA library.

 

NOTE: This is where you put your personal "signature". If you don't change it people will know you're a clueless frunobulator.

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

Yup, the downside of the internet is that there is nothing to expire old and out of date pages that have been written years ago. If you are lucky the author will have had the foresight to put a date on pages that may act as a warning that you are looking at old rubbish.
.
In 2017 it is Atmel themselves (mainly) who build the Windows based version of avr-gcc for us. Google "atmel toolchain for Windows" or just get AS7