Posted by Neil Smith [MVP Digital Media] on 12/22/07 18:16

On Fri, 21 Dec 2007 19:43:48 +0000, Spex <No.spam@ta.com> wrote:

>Richard Crowley wrote:
>> "Spex" wrote ...
>>> Richard Crowley wrote:
>>>> "Spex" wrote ...
>>>>> Richard,
>>>>> The default iTunes mode is for the general simpleton who has to have
>>>>> iTunes sync everything automatically. Turning off sync everything
>>>>> clears the iPod ready for manually updating.
>>>>
>>>> Yeah, people keep saying that, but I've spent only an hour
>>>> trying to discover how to "turn off" this "feature". The UI
>>>> design drove me so crazy that I gave up after an hour.
>>>>
>>>> If this is really possible, surely someone has published a web
>>>> page that shows how to remove the fangs from iTunes.
>>>
>>> When you connect you iPod to the computer iTunes will open at the iPod
>>> summary page....
>>
>> IME, it immediately starts doing *something* (which it doesn't
>> reveal) and won't let you interrupt until *it* thinks it is done.
>> There still appears to be no way of neutralizing it before you
>> risk attaching your iPod. That is "user-visious" in my book.
>
>I've never encountered that. Mac or PC or have you seen this on both
>platforms?
>
>I only have a small part of my music collection in iTunes which only
>amounts to 1500 tracks so far but it loads instantaneously. Perhaps the
>*doing something* is a corruption of the itunes database and it's being
>rebuilt. Just guessing.
>
>I have a PC here with iTunes on it and it takes ages to load because it
>is looking for a dll that it never finds. Both iTunes and QT look for
>this dll and give an error when they don't find it. I click OK the
>programs load with no noticeable problems. I've never spent the time to
>fix this as this PC has only one function to run combustion now and
>again. Could the problem you've encountered be similar? Dunno.


I know of at least one dll which causes problems at install and
upgrade, that's the vbscript.dll

I don't know if it'll help because you didn't mention which dll is
failing, but here's a shot : Go to Start -> Run, type in CMD

At the comand line, type

regsvr32 vbscript.dll

Press enter, and (expect) a message popup 'register server in
vbscript.dll succeeded'. If you're missing that file somehow (regsvr
fails or can't find the dll), run

sfc /scannow

To scan system files and see if it can be found in the installer cache
If it's repaired (other repairs might be made as well), rerun the
regsvr32 command to make sure programs are aware of it.

HTH
Cheers - Neil
------------------------------------------------
Digital Media MVP : 2004-2007
http://mvp.support.microsoft.com/mvpfaqs

[Back to original message]