Tweet
Oh GOD NO. iPods are the bane of our existence in managed services.
*RING* "My machine won't boot..."
"Is your iPod plugged in?"
"Yes...?"
ARGH!
*RING* "My machine won't boot..."
"Is your iPod plugged in?"
"Yes...?"
ARGH!
-
The Internet - where men are men, women are men, and teenage girls are FBI agents!
I'm the least you could do
If only life were as easy as you
I'm the least you could do, oh yeah
If only life were as easy as you
I would still get screwed -
Can't say I've ever that problem... oh wait...
I knew this was an issue when the BIOS boot sequence attempted to boot from a removable (Firewire, USB) or external startup disk before the primary hard disk.
The mapped network drive problem has nothing to do with "H:" specifically. I've seen it happen on one mapped to "E:" as well. In most cases the iPod is being mapped to the drive letter that follows any physical drives - or at least the system thinks it is.
Pain in the arse for sure, but iPod's are not the only problem devices. There are of course solutions available for this problem (which by the way is a problem with Windows' Mount Manager). Sadly the solutions are less than ideal. The actual core to this problem was partially worked around in Windows XP, as it should start from "Z" and move back as it assigns for mapped network drives.Last edited by Jessterw; 25 May 2007, 12:21.“And, remember: there's no 'I' in 'irony'†~ Merlin MannComment
-
Originally posted by Gurm View Post
And then they wonder why the backup tape is full...
Edit: This is a small company mixed with a family home...large quotas etc etc. I just exclude all media folders from the backup schedule.FT.Comment
-
@Jesse: sure its not just H:, but that's the setup I inherited with that business. Changing would be a whole lot more difficult than putting a large sticker on the ipod that says "bring this near a work machine again and I'll rip you a new docking port"
FT.Comment
-
Hehe. Oh I totally understand. I only know the problem because we had it at my old job, except with some other devices under Windows 2000. Would have users calling me up saying they kept copying files to the device and they weren't showing up on it later.
Sadly, MS didn't have any support documentation on the problem at the time, so it took me a little time to work out the exact problem.“And, remember: there's no 'I' in 'irony'†~ Merlin MannComment
-
It used the first available driveletter (but ignored that I reserved it for another drive, but this could be Windows).
Still having the movie issue though: the xvid plugin I found is for MacOS, divx doesn't change anything.
JörgComment
Comment