SIMPLE FIX for XP SP2 Installs

Greetings. I'll cut to the chase and won't explain here in detail what's really going on with this fix, but it has now successfully cleared a range of installation problems for iTunes 5.0, 5.01, and QuickTime 7, on two unrelated XP SP2 systems. Feel free to contact me if you want more info, but you may definitely want to give this a try if you're running XP SP2 and have been having iTunes install problems (be sure that you are logged in with Administrator privileges):
- Click Start
- Click Run
- Enter in the "Open:" field: "services.msc" (without the quotes)
- Click OK
- Scroll down to "Remote Procedure Call (RPC)"
[ NOT "Remote Procedure Call (RPC) Locator" ]
- Double click on this item
- Click the "Log On" tab
- If the "Local System Account" selection is already
selected, this fix won't help you. If the "Local System
Account" selection is NOT selected, SELECT it now.
[ make sure that "Allow service to interact with desktop
is not checked ]
- Click OK
- Close the Services window
- Reboot
- Try reinstall the 5.0 or 5.01 iTunes+QuickTime package
This may also fix a number of other odd XP SP2 behaviors. Good luck!
--Lauren--
Lauren Weinstein
[email protected] or [email protected] or [email protected]
www.pfir.org/lauren
Co-Founder, PFIR
- People For Internet Responsibility - www.pfir.org
Co-Founder, EEPI
- Electronic Entertainment Policy Initiative - www.eepi.org
Moderator, PRIVACY Forum - www.vortex.com
Member, ACM Committee on Computers and Public Policy
Lauren's Blog: lauren.vortex.com
DayThink: daythink.vortex.com

Over time I saw a range of different install problems as I continued trying to find a procedure to get iTunes 5 and/or QuickTime 7 installed on two completely different XP SP2 systems, neither of which initially had an iTunes installation (but both of which had QuickTime 6 installations).
The initial attempt at the (then 5.0) iTunes install resulted in the infamous "vanishing installation" -- the process appeared to proceed normally, but at the end no files had been installed, and the iTunes icon had only appeared for a few seconds. I eventually determined that the installer was failing silently and deleting all of the files it had installed at that point. No error messages were associated with this failure mode -- the installer's failure to be more verbose made this a much more difficult problem to attack (turning on installer logging gave more information, but was not as much help as might have been expected).
Unfortunately, the installer by that time had also mucked around with various QuickTime files and settings, leaving the original QuickTime 6 installation broken as well.
I then found it was impossible to even install the QuickTime 7 standalone, nor could QuickTime 6 be reinstalled. In all cases (even after manual attempts at uninstalling and cleaning up the partial installs, registry cleanups, etc.) the installers would abort ("interrupted") near the very end of their process, and as usual delete their new files.
iTunes 4.9 installs would also fail in much the same manners. However, I ultimately found a way to trick the system into a working 4.9 (except for CDDB support on one of the machines), using a technique that I documented on this forum some days ago.
As I dug through the various logs and errors, I became convinced that a privilege issue was at the heart of the matter -- this also fit with the sorts of changes that SP2 imposed on the system, and later MS security "fixes" that made even more changes.
This led to my researching the sorts of problems that could relate in that area, until I found discussions of a variety of problems caused by RPC-related privilege configuration errors, that can trigger many bizarre XP SP2 behaviors, including installer failures.
The procedure that I noted in the original message of this thread instantly fixed all iTunes and QuickTime installation problems on these systems. Both 5.0 and 5.0.1 installs proceeded perfectly after the change -- I did not test the change with 4.9.
This situation is the fault of both MS and Apple. MS -- for a whole bunch of SP2-related complexities and problems that were unnecessarily introduced, and Apple for apparently not noting the known issues in this area, and failing to take them into account in their installers. Apple also gets low marks in this situation for installer error reporting, and for how they've handled the situation publicly since the problems became known.
--Lauren--

Similar Messages

[svn:fx-trunk] 11642: Simple fix for non-integer translations by first multiplying to twips before casting to int .

Revision: 11642
Author:   [email protected]
Date:     2009-11-10 19:40:31 -0800 (Tue, 10 Nov 2009)
Log Message:
Simple fix for non-integer translations by first multiplying to twips before casting to int.
QE notes: Please test non-integer translations in FXG.
Doc notes: N/A
Bugs:
SDK-24110 - Drawing of compiled FXG items is off by half a pixel
Reviewer: Peter DeHaan
Tests run: Checkintests, Bug test case
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24110
Modified Paths:
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/types/FXGMatrix.java

i dont know why you are so mean i just asked which
wrongs i had wrong
anyway im done with thoseSo, the questions have 4 alternative answers. We tell you which questions you got wrong. This eleminates one of
the alternatives, leaving 3 choices. Usually in most mutlichoice questions 1 choice is obviously incorrect,
leaving 2 choices. One of those you have probably already discarded when you initially made your incorrect chocie
thus leaving 1 alternative. Congratulations you just 100% on your test. I don't think so. Go read your book or notes or
whatever you have because all the answers will be in there. The teacher will not ask you a question on a subject
you have no prior knowledge of.

[svn:fx-trunk] 7824: Simple fix for SDK-21480 - Batik reports that the * selector has a null name so we handle this as a special case .

Revision: 7824
Author:   [email protected]
Date:     2009-06-13 11:46:34 -0700 (Sat, 13 Jun 2009)
Log Message:
Simple fix for SDK-21480 - Batik reports that the * selector has a null name so we handle this as a special case.
QE: Yes, this was really a compile time issue rather than a runtime issue.
Doc: No
Checkintests: Pass
Bugs:
SDK-21480 - Universal selector not applied
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21480
    http://bugs.adobe.com/jira/browse/SDK-21480
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StyleModule.java

Try the following changes to the JS file
Lines 103 and 104 change the values
this.showDelay = 100; // was 250
this.hideDelay = 200; // was 600
Comment out line 286
Spry.Widget.MenuBar.prototype.bubbledTextEvent = function()
//    return Spry.is.safari && (event.target == event.relatedTarget.parentNode || (event.eventPhase == 3 && event.target.parentNode == event.relatedTarget));
Comment out line 366 and add new lines 366 and 367
var self = this;
this.addEventListener(listitem, 'click', function(e){self.Click(listitem, e);}, false);
this.addEventListener(listitem, 'click', function(e){self.mouseOver(listitem, e);}, false);
// this.addEventListener(listitem, 'mouseover', function(e){self.mouseOver(listitem, e);}, false);
this.addEventListener(listitem, 'mouseout', function(e){if (self.enableKeyboardNavigation) self.clearSelection(); self.mouseOut(listitem, e);}, false);
I have not tested the above changes ontouch screens; they do seem to work Ok on desktops.
NOTE: Line numbers could be different because of the difference in our versions.

Is there any fix for the flashplayer installer not working on a windows 7, 64-bit, using firefox?

I Hit the download link, get the permission windows, and the flashplayer installer window comes up, but doesn't do anything. i left it up all day when i went to work, come home 12 hours later and it was still just sitting there not installing. Is there a fix for this? i have looked everywhere and nothing that i have found has worked. even the suggestions on the adobe help page doesn't work..

And you used the offline installers from the link that Andy posted:
Flash Player for Internet Exporer - ActiveX
Flash Player for Firefox - NPAPI
If yes, please post the contents of the FlashInstall.log file in C:\Windows\system32\Macromed\Flash

HT1222 What's the fix for the Flashback Installer virus?

I am infected with the fake Flashback Adobe installer. I deleted everything associated with it, ran my Intego Virus Barrier 6, installed the authentic Adobe Flashback and changed my email password in my Mac mail and in the mail program from my ISP but the viral emails keep on coming.
When will there be a fix for this?

Helpful Links Regarding Flashback Trojan and Virus Protection
An excellent link to read is Tom Reed's Mac Malware Guide.
A link to a great User Tip about the trojan: Flashback Trojan User Tip.
To check for the trojan: Anti Flashback Trojan 2.0.4.
A Google search can reveal a variety of alternatives on how the remove the trojan should your computer get infected. This can get you started. Or the preferred method is to use Apple's protection tool: Flashback Malware Removal Tool 1.0.
Or, open Software Update. If you do not have the Apple protection software installed it will download and install it via Software Update. If no update appears that means you either already have it installed or it isn't needed for your system. The software is only available for Leopard, Snow Leopard, and Lion versions of OS X.
Also see Apple's article About Flashback malware.
For general anti-virus protection I only recommend using ClamXav.

Here's the FIX for one quicktime installation error

Can't believe this isn't mentioned in here anywhere or in any of the threads on the Web. I got help from the Ubergeeks on the Well, where I should have started in the first place.
If you can't install because Quicktime won't install (error -3, error 1402 etc.) and you can't get permissions to enter the registry keys...
Run: regedit
navigate to the folder mentioned in the error message. For me it was HKEYLocalMachine\Software\Microsoft\Windows\CurrentVersion\Uninstall\Quicktime
This seems to be the most often-cited culprit.
Right-click on the Quicktime folder. Select Permissions. Hit Advanced. Click the "Owner" tab. Click on yourself in the lower window. Hit OK.
Install your software and enjoy.
This may not fix everyone's problems, but I bet it fixes the vast majority of those that are similar to the one I had, which I spend hours and hours trying to fix before I simply asked someone who knew what they were doing.
Maybe if the folks at Apple see this, they can, you know, add it to their troubleshooting guide. It's a very common problem.

In case anyone is reading this thread, I found a fix for this problem. In another discussion thread, a nice person referenced an article at http://docs.info.apple.com/article.html?artnum=93865 that explains what to do with these kinds of permission errors (1402 and 1406). I followed the instructions and also made the changes to the specific line item I had a problem with. Installation ran successfully although there were a couple of error messages about not being able to unregister a couple of .dlls, which apparently is not fatal to the installation.

Simple Fix for "Sticky Upper Optical Door" Problem

I've seen quite a few threads popping up in here with regard to the fact that a great many brand-new Mac Pros suffer from a problem where the door/cover for the upper optical drive does not spring shut after the drive is closed.
Our new Mac Pro suffered from this problem, and with a bit of investigation, I believe I've found a very safe, simple, and completely reliable fix for the issue, so I thought I'd post my solution here in the hopes it will help others.
No bending, pushing, or mangling of any sort is required for this fix; it's really incredibly simple:
• open the case and remove the optical drive caddy. Do this by pulling it straight toward you. A small amount of force might be needed if this is the first time you've done it, but eventually the entire aluminium enclosure which holds the drives should slide out.
• with the drives removed, you'll be able to see the door/cover assembly. Just inside the opening of the case near the opening for the top drive, you'll see a Phillips (star) screw. Loosen this screw just a bit - in my case, all that was needed was about 1/8 of a turn.
• verify that this fixes the sticking problem with the drive door/cover by manually wiggling it up and down.
• tighten the screw to the point where you're not worried it might work itself loose on its own, but not so tight that it causes the door/cover to begin sticking again.
• replace the drive enclosure, close the case up, and you're done!!
I'm guessing they use a powered screw-driver when assembling that part of the case, and that the screw just gets over-tightened in the process, but then again.. who cares how it happens, so long as it can be fixed!?
Hope this helps..

It's nice to know there's a community out there. I bought my Mac pro refurbished and was starting to think the sticking door was why I got it cheaper. Thanks for posting your solution.

Simple fix for Included Mail Script

This may have been mentioned elsewhere, but for those that have tried to use the "Display All Accounts And Preferences" AppleScript that Apple includes with Mail 2.x & discovered it doesn't work, the fix is simple:
Open the script in Script Editor & use its search & replace for the line that reads:
set theRulesPlist to (homeDir & "Library:Mail:MessageSorting.plist") as alias
Replacing it with:
set theRulesPlist to (homeDir & "Library:Mail:MessageRules.plist") as alias
Save the script & it will now work without error.
This script generates a new email message with tons of info about your accounts, preferences, & even the permissions of the folders Mail uses. This email item can be very useful for copying details about your account into Discussions posts. It doesn't actually address or sent the email, & you should be careful about sending it to anyone since it could reveal details about your accounts you don't want others to see.
The same goes for any post here, of course.

looking at Apple's example scripts is often enlightening.
Actually, this is the only use I make of AppleScript.
BTW, you can open rather than execute any script available
in the app's Script Menu by holding down the option key when
you select it.
Again, thanks for the tip. I wasn't aware of that either.

Simple fix for non-ejecting CDs/DVDs

I've had trouble getting discs to eject since I got my new Intel duo-core iMac a few weeks ago. I tried all the suggestions on this forum and those that the Apple support people suggested. Finally, a repair guy came to the house today to replace the superdrive.
I'm almost embarrassed at how simple the solution was. I have the iMac with the built-in iSite camera. There's a plastic case that fits over the screen. It detaches (with great difficulty) for repairs to the computer. The case is attached to the computer with "snaps" and state-of-the-art (supposedly) tape that is very difficult to remove. It should be tight. Well, mine wasn't. The upper left corner (NOT the corner next to the drive) wasn't snapped in all the way. It was loose by maybe 1/8 of an inch. That little bit of crookedness was just enough for the superdrive slot not to line up properly, and that's why the computer couldn't eject the discs. It was a purely mechanical problem.
The repair guy used the palms of his hands on each upper corner to squeeze the case and snap it on tight. Presto! Instant fix. The discs eject with ease now.
The only problem is that the tape doesn't seem to be very tight on that upper left-hand corner. So it might loosen again. If it does, I'll be calling Apple support again.
I was embarrassed that I hadn't noticed this problem before (you couldn't see it if you were looking straight at the computer, which is the only way I ever see it), but I was also relieved that the superdrive didn't have to be replaced.
So, if you're having problems ejecting discs, check to see if the case is snapped onto the computer tightly.

Just a follow-up. My case would not stayed snapped to the computer. I had to call service out again, and they replaced the case. Seems the clips that hold the case to the computer weren't designed very well. The new case has redesigned clips, and now everything is fitting tightly. No problem ejecting discs any longer.

Here's a simple fix for Mail constantly asking for account password

This one was driving me nuts, but now I have a fix...I think. Open up Keychain Access in Utiliites. Double click the entry in the login keychain, then check "Show Password." Give your login password and hit the "Allow" button. After the pword is shown, just close the box. That's it. No more need to redo all the pwords in Mail and Keychain. Works for me. Mail seems to need some hand holding from time to time.

My e-mail provider is Verizon. If I'm being asked for the password for the main account, I double-click on this in the login keychain shown below. But since I'm using Snow Leopard, this might appear differently for you, although I doubt it.

Fairly simple fix for dv6000 power button, microphone, internal speaker problems

I have a dv6000 notebook computer, S/N CNF6380XM1, P/N EZ829AV.
Over time (I've had the computer for almost 4 years) the power button, internal speakers, and microphone became increasingly flaky and eventually stopped working altogether. Classic signs of a bad connection. I could still turn on the computer by touching the QuickPlay button to the right of the power button.
I used the Maintenance and Service Guide, HP Pavilion dv6000 Notebook PC, Document number 416618-003 (PDF can be found online from HP) to get the removal/replacement procedures for the switch cover (the piece of the case above the keyboard that has the power button, the Quick Play buttons, and the speakers) and the power button board. Remove three silver screws inside the battery compartment, pop loose some snaps along the top edge of the switch cover, and carefully fold the switch cover back over the keyboard. The power button board is pretty obvious other than knowing you need to slide the latch ears on the ZIF connector away from the connector body (towards the flex cable) in order to release the flat flex cable.
The power button board has flat flex cable that connects to the motherboard. In addition to having the power switch, this board is used as a breakout board for the microphone and the internal speakers. I looked at the contacts of the ZIF flat flex connector under a microscope and aha!, just as I suspected, they are gold plated. You might think this is a good thing, and it would be if the mating contacts on the flat flex cable were also gold plated. But alas they are tin plated. Gold + tin + vibration + time = bad connection. For those interested in the technical details of this, do a search for "fretting corrosion".
Since I'm pretty miserly and like to fix stuff, I decided to try simply cleaning the contacts. I cut a strip of carborundum paper (very fine abrasive coated paper) the same width as the flex cable, insert it into the ZIF connector, close the latch, and pull the paper out. I repeated this 3 times, then shot some compressed air into it to remove any gritty dust. I then rubbed the contacts of the flat flex cable with the carborundum paper and wiped them off with a clean static-free cloth.
After reassembly, everything is working again! Since this didn't address the root cause of the problem, it will probably eventually start acting up again, but maybe by that time I'll be ready for a new computer anyway. A proper fix would be to replace the ZIF connector with one that has tin contacts, and to replace the flat flex cable.
This is a design flaw on the power button board. A ZIF connector with tin contacts should have been used. Ironically, I learned about fretting corrosion over 20 years ago from an old HP reliability guru named Ed Aoki when I was an engineer in the HP medical electronics business.
After doing an internet search on "dv6000 power button", I saw that there seem to be quite a few frustrated people out there that are having similar problems with internal speakers and microphone. The troubleshooting flow chart in the service manual does not help to properly identify the problem component (the power button board and flat flex cable). Hopefully this info will be helpful.

No, its too expensive for HP to plate the zif connectors with something that doesn't corrode....rolleyes.
Thanks nice tutorial.
The DV 6000 series was plagued with motherboard issues
http://h10025.www1.hp.com/ewfrf/wc/document?lc=en&dlc=en&cc=ca&docname=c01087277

Possible simple fix for itunes store issues

Was having the same problem with my Macbook Pro and iPhone 3gs. Could not login/download app updates etc. despite having the same account for several years.
Here's what worked for me......
Go to the apple store (not iTunes store) and log in to your account as normal.
Click on change account information.
Change the email address to a different valid email address and click continue.
Click on change account information again.
Change the email address back to the original email address and click continue.
Hopefully, if you now try logging in to your iTunes account, all should be fine and dandy!!!
I hope this helps with Windows too

Unfortunately, this did NOT work for me. I am still stuck and have done everything. I lost my original user name and now have my long email address as my user ID... bummer. Also, I had a very simple password that I lost, too, because I was trying to reset things. Also, a big bummer!!'
This is day 4 for me now and I am still not able to use my credit card!!!

Possible simple fix for Yosemite freeze/high CPU etc

Short version: Update tom latest version of Dropbox client for OSX
Description:
Running OS X 10.10 on 2011 MBP w/ 840 EVO SSD
Everything was running great for a week or so, then started experiencing high CPU usage, and ultimately the system would stop responding. Lot's of strange error messages in syslog brought me to the forums, but no answers.
Initially, I thought the trouble was caused by 3rd party kext's loading since I had disabled signing and forcibly enable trim. In the end, I disabled trim and reset the driver signing to defaults and followed basic troubleshooting posted elsewhere here to regain control:
Boot safe mode
SMC reset
PRAM reset
After this, I enabled trim, etc but ran into trouble yet again. So I started looking at apps one at a time. I downloaded and installed the latest Dropbox client, and everything has been great since. I believe (in my case) the older version of Dropbox that had not been updated since Mavericks seemed to be the culprit. I wrongly assumed that this couldn't happen due to Sandboxing, but I'm not a software engineer.
Hope this helps.
BKå

Unfortunately, this did NOT work for me. I am still stuck and have done everything. I lost my original user name and now have my long email address as my user ID... bummer. Also, I had a very simple password that I lost, too, because I was trying to reset things. Also, a big bummer!!'
This is day 4 for me now and I am still not able to use my credit card!!!

Tip - Satellite L355-S7902 Simple fix for L355-S7902 any vibration from the hard drive

My Satellite L355-S7902 developed a very noticable vibration.
I soon found the source: the SATA hard drive was loose in the drive bay.
The simple and effective solution is to glue a small block (3/8in cube) of high density foam between the drive and the cover.

Thanks for your help, I have had a read around lots of sites, but am still confused, do I have to make up a special version of xp with the Toshiba drivers?
BELOW IS THE BLUE SCREEN OF DEATH TEXT:
A problem has been detected by windows has been shut down to prevent damage to your computer
If this is first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:
Check for viruses on your computer. Remove and newly installed hard drives or hard drive controllers. Check your hard drive to make sure it is properly configured and terminated.
Run CHKDSK / F to check for hard drive coruption, and then restart your computer.
Technical information
STOP: 0x0000007B )0xF78D2524, 0xC0000034, 0x00000000, 0x00000000

Possible Fix for 8i Patch installs (redhat)

After doing a couple of reinstalls and trying to get the
81501 patch to work, I decided to wipe the entire product
directory and start fresh. The patch then installed without
a single problem and everything relinked w/o errors.
I had noticed earlier, but ignored, that the uninstaller
doesn't really clean up after patching and other stray files.
I think this may have caused problems with subsequent
attempts.
Hope this helps someone.
Kev
null

Kevin (guest) wrote:
: After doing a couple of reinstalls and trying to get the
: 81501 patch to work, I decided to wipe the entire product
: directory and start fresh. The patch then installed without
: a single problem and everything relinked w/o errors.
: I had noticed earlier, but ignored, that the uninstaller
: doesn't really clean up after patching and other stray files.
: I think this may have caused problems with subsequent
: attempts.
: Hope this helps someone.
: Kev
That's not true ...if you read instructions carefully ...u
should open it up in a fresh folder ...because the patch checks
itself if it
has 37 files as it blows up...With the other subfolders or
files running around it adds up to the count and stops your
installation
null

SIMPLE FIX for XP SP2 Installs

Similar Messages

Maybe you are looking for