Please help test eject code for iPod Agent

[Shadow]

This is a call for help. I've had a number of requests to add an "eject" button to iPod Agent. So, I've been working on the code to do this and I think I've got it. However, I haven't been able to test on too many systems so I'm now calling on you guys to help me out. I'd like to test this on as many systems as possible before I add the code to iPod Agent.

I've created a little stand-alone EXE that runs the code to eject the iPod. What I'd like people to do is download this little EXE and run it while their iPod is in "do not disconnect" mode. It won't display anything. Just run it and it should eject your iPod. If you are running XP, it should display the little "safe to disconnect" message bubble.

I've tested it so far on two XP systems. One connected via a USB 2.0 and one connected via firewire. Both work great. So, if you guys could try it on any setups you have available, that'd be great. Please let me know the following:

* What version of Windows was it on?
* Was the iPod connected via USB or Firewire?
* Did it successfully eject the iPod?
* What version of iPod software are you running (2.01, 2.1?)
* What generation of iPod did you test (1G, 2G, 3G)

You can download the little test app here (44 kb).

Thanks!

[enjoilax]

*bump*

Shadow i need you to resend me the Admin info.

[Shadow]

enjoilax, you've got PM

[enjoilax]

Shadow you got PM.

Sorry dog, BTW it works,

Sys: Win XP Pro Sp1
Connection: Firewire 4 pin
No extras.

[Shadow]

enjoilax, what gen iPod you got? And, what software version is it running?

[enjoilax]

3rd gen, S: 2.1

[Callused]

XP home (don't know service pack)
Firewire
It worked
2.1
3G

[jahwork328]

XP pro
USB 2.0
2.1
3g
Worked perfectly..

Eric

[noogabooga]

WinXP SP1
Firewire
iPod firmware 2.1
3G iPod

successful erect... er.. I mean ejection

[Shadow]

stark23x, that makes sense. Currently, the eject code just ejects the first iPod it finds. I haven't figured out how to tell which iPod it actually is if there are more than one. I could easily ejec them all. Ideally, I'd like to be able to just eject the one that is currently in use by iPod Agent. I'm working on that now but it is turning out to be difficult for me to figure out. It's a lot of C++ code and I'm quite the novice at C++. I figure most people just will have one iPod connected at a time so it shouldn't be that big of a deal.

Since I don't have two iPods to test with, could you answer a couple questions?

• In iTunes, when you connect multiple iPods, do they both show up in the Sources list?
• In iTunes, if multiple iPods connected and you click eject, what happens?

[noogabooga]

pretty soon, multiple iPods will become the norm lol just like TV and computers

[MOCKBA]

Works like a charm, XP, USB

[Phezult]

Did not eject.

Windows 2000, SP4
3rd gen
version 2.1
6pin firewire


This is not the only item plugged into the firewire card, though the Nikon Coolscan is currently off, so that shouldn't make a difference.

If you want hardware specs I can get back to you a a couple of days. Posting and then leaving town with the shiny new ipod.

If you get it to work, cool. If not, well, I gues moving the mouse isn't going to kill me...

J

[enjoilax]

Can you try it w/o the Coolscan in please?

Every little detail helps. If you want better software, then you got to be willing to help us out.

[Shadow]

I just uploaded a new iPodEject test program that will now create a log file on your harddrive. Anyone that tests this for me and has it fail, please email me the log file as it will greatly help me try to figure out how to get it to work with your setup.

Please download the new test iPodEject here.

The log file will be placed in the root of your C: drive. It will be named ipodeject.log. To find it, open Windows Explorer and navigate to your C: drive. It will be at C:\ipodagent.log. If you keep running iPodEject, the log file will keep getting larger. Feel free to delete the log at any time. This log will not be created in the final version.

Email it to me at ipodeject@mersjr.com.

Thanks