Wow thats a new problem symptom. And possibly something never tested for. And yes one would hope the IDE would only reset the selected channel. I would think that it might be a PC driver issue rather then an IDE caused problem and it might be best first to try and determine if this symptom is seen on all three platforms, windows, mac, linux.
If you have two you might simply have to (re)start both of them separately and not use File -> New from the menu. There was another thread lately with a similar error.
I have also had this issue a few times. I have one board connected that I am not actively using but is playing music etc (normally playing music), then I upload and the one playing music will reset and go back to the start of the folder of music it is playing through.
Never had a major problem with it, it's just rather annoying.
Well I would call it a bug if a single instance of the IDE reset comm ports other then the single select comm port selected.
That's what it does. I have one sketch open fiddling with one board.
The other board is connected but not being used by any instances of the IDE.
Not sure if it always does this or just on occasion but I think it always does it.
Today it seemed to 'half reset' my board too. The music was still playing from where it was (will only stop when arduino is restarted - as long as the rMP3 has power it will keep playing) but the LCD displaying the visualiser froze. I had to reset the board to get the LCD to start working again.
I will look into it more when I get the chance (and I remember :P)
The only short term fix I can suggest would be for you to defeat the auto-reset function on the board(s). Just wire a 150 ohm resistor between the +5 volt pin and the reset pin. Remove the resistor when you want to upload to it.
Right. Windows 7 ultimate, two different ports (neither on hubs, one connected to a mobo port and one to the front case port (from mobo plug) so they are not even on the same internal hub.
One Arduino Duemilanove and one rDuino LEDHead.
I will get off my laptop and go try some more stuff in a bit.
An explination may be that the IDE communicates with the arduino USB chip and not a virtual serial port established by the USB chip. If the USB chips have the same identifier, both may be treated as one.
An explination may be that the IDE communicates with the arduino USB chip and not a virtual serial port established by the USB chip. If the USB chips have the same identifier, both may be treated as one.
That sounds like a promising path to consider. Tell FTDI to get their driver s#$% together.