Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Tomcat76

  • Birthday 01/16/1976

Contact Methods

  • Website URL

Profile Information

  • OS
    XP Pro x86
  • Country

Recent Profile Visitors

1,406 profile views
  1. The three hotfixes Destro mentioned in "Step 7" won't install if SP3 for the Compatibility Pack is not installed first. This seems logical, seeing those are post-SP3 fixes. What I did was: 1) install SP3 for the Compatibility Pack and verified that Microsoft Update was broken again 2) install the three hotfixes (KB3127894, KB3203438 and KB3191897) manually Now Microsoft Update is working fine. So I guess the conclusion is that SP3 for the Office 2007 Compatibility Pack exhibits the same problem IE is suffering from: you need to install the latest update(s) manually. Pfff... ;-P
  2. @mixit Just want to say that the instructions in the OP worked right away for me on a computer running Windows XP and Firefox 46.0.2. So I'll just have to find a way to install FF 46 or newer on my main computer. Thanks!
  3. I haven't finished my testing yet, but here are a few observations. Having the Office Compatibility Pack (fileformatconverters.exe) installed, approximately doubles the amount of time Microsoft Update needs to search for updates (about 2 minutes total), but it runs through. Installing SP3 for the Compatibility Pack borks Microsoft Update. Uninstalling SP3 fixes Microsoft Update again. I CANNOT confirm that uninstalling SP3 for the Compatibility Pack also removes the entry for the main Office Compatibility Pack in Control Panel>Software; the entry is still there as expected. Also, when visiting Microsoft Update after uninstalling SP3 for the Compatibility Pack, I do not get updates for the Compatibility Pack other than the SP3. The only other updates I'm offered are for Word Viewer, Excel Viewer and Powerpoint Viewer. I guess I'm not supposed to install these (to fix Microsoft Update), so I'll just move on to Step 7 in Destro's guidelines.
  4. Destro... You are on to something! Earlier today, I found out that on the problematic PC here, Windows Update was working fine but Microsoft Update still wasn't. It screwed up in the way I described in my initial post. After uninstalling the hotfixes for the Compatibility Pack (redundant step?), SP3 for the Compatibility Pack and the Compatibility Pack itself, Microsoft Update finally worked as expected! Tomorrow I will try to reinstall the Compatibility Pack per your instructions. I'll keep you posted.
  5. I have actually installed Windows Installer 4.5 from a downloaded redistributable yesterday. Installation dialogs from MSI installations had a blank title bar and blank buttons; only the description (text) was visible. Installing WI 4.5 seems to have fixed that, and Windows Update is still working for me. That computer has the Word and Excel Viewers installed plus the compatibility pack. It used to have Office 2003 running in the past but that's been replaced with OpenOffice.
  6. One problem: on attempting to install the May 2017 cumulative rollup for .Net Framework 3.0 SP2 that is offered, the PC reboots itself immediately. This causes the SoftwareDistribution folder to become corrupt once again. Luckily, the same fix (delete entire SoftwareDistribution folder) fixes it. According to an entry in Event Viewer, the update doesn't apply to my PC. But why would it have to trigger an automatic reboot?
  7. By observing the network icon in the system tray, nothing much is happening; it flashes briefly just once or twice every minute. I haven't used any special tool to monitor traffic, though. Incidentally, I seem to have fixed it on the PC at hand. I let Microsoft Update search for updates once again, and then inspected WindowsUpdate.log in the %WINDIR% folder. Then, I searched Google for some of the errors and warnings that appeared, and stumbled upon a site that suggested to remove/rename the entire SoftwareDistribution folder (after stopping wuauserv), instead of just the SoftwareDistribution\Download subfolder. After rebooting the machine, Microsoft Update gave me the list of updates to install in less than a minute. It's now installing update 57 of 78. :-)
  8. @jaclaz: That PC needs regular attention since it's a Prescott in a small enclosure (HP Microtower). I admit it's been a while since the last time. When cleaned up, the CPU runs at 72~75°C on full load. @Destro: I already tried those, but thanks anyway :-)
  9. This topic has been discussed to death, but since I wasn't able to solve it using the advise found around the Web, I was hoping to get ADDITIONAL possible solutions to this problem. If it doesn't lead us anywhere, I'm OK with it being closed or terminated. It concerns a computer (not my main rig) that is running XP 32-bit which is primarily used by my 3-year-old niece to watch YT videos. I wanted to test the POSReady 2009 registry edit on it before applying it to my main rig, which is also running XP 32-bit. The problematic computer has had Automatic Updates disabled ever since Microsoft ended extended support. The problems I have observed: 1) When enabling Automatic Updates or when going to Windows/Microsoft Update with Internet Explorer, an instance of svchost immediately reaches 50% of CPU usage (100% of one core) and both the CPU fan and rear exhaust fan are blowing away to lower the temp on the "PresHott" CPU which is at around 80°C then. This doesn't stop until I close IE or reboot the PC. 2) The search for updates using Windows or Microsoft Update never finishes. What I have done in an attempt to fix it: 1) Disabled anti-virus. No dice. 2) Manually renamed the catroot2 folder and deleted the SoftwareDistribution\Download in Safe Mode. No change. 3) Changed the startup type of the Background Transfer Intelligence Service (BITS) from Manual to Automatic. Didn't help. 4) Reset IE8 to default. No change. 5) Followed the instructions found here to install Windows Update Agent 3.0 (which was already installed), and to run a batch file that re-registers a whole bunch of system files and fixes the catroot2 and SoftwareDistribution folders (which didn't help either). I didn't download KB927891 because the link refers to an executable intended for XP 64-bit. 6) Created an updated WUA 3.0 installer using a batch script by MSFN.org members and installed it, but it complained it was already installed. The installed binaries are indeed the same. 7) Ran the command sc config wuauserv type= own to have Windows Update run in an svchost process of its own. No dice. 8) Deleted "Networkservice" under HKLM\Software\Microsoft\Windows NT\CurrentVersion\SvcHost after backing it up. Didn't help, so I restored it. 9) "Downgraded" from Microsoft Update to Windows Update. No dice. 10) Installed the latest cumulative update for IE8 for Windows XP 32-bit that I could find, which was the KB4018271 update from May 2017 (with binaries from April 2017). No dice. 11) Installed the latest cumulative update for IE8 for PosReady 2009, which appears to be the KB4025252 update from July 2017. It installed without a glitch, but it didn't help resolve the Windows Update problem. 12) Uninstalled IE8, rebooted, re-installed IE8 "with updates" and rebooted. No dice. Installed KB4025252 and rebooted. Still the same. 13) Just let Windows Update run. The CPU fan and rear exhaust fan are blowing away like there's no tomorrow and the CPU temp is over 80°C, which I don't like. I let it run for more than half a day and it was still searching, so I closed IE. So... What else is there to try? It could be that more updates than the latest cumulative update for IE8 are needed to satisfy Windows Update. A list of prerequisite updates like the ones for Windows Vista and Windows 7 might be of help. Ideas?
  10. Both the Flash and HTML5 player on that BBC test page are working for me, using FF 34.0.5 on XP x86. Dave-- I can confirm getting the odd error message using Opera 12.18 even though the Flash video is playing just fine. It's probably to do with how they detect the plugin. At least they aren't blocking the browser based on that false assumption.
  11. Firefox 34 is the most recent version that will work acceptably on my computer. It is still tamed down with Memory Fox and various other memory controlling about:config changes, which make a huge difference. It's still leaking, but I can at least browse a little longer. Some time ago, I did an extensive test with many different FF versions and the problems with FF35 and later are too big. I installed 52 ESR yesterday, but it took more than half a minute to start (each time) and browsing was exceptionally sluggish. 45 ESR, which I tried after that, was better in that respect. With my limited knowledge of obscure about:config settings, I doubt I will find a fix for Primetime CDM for older versions of Firefox. So I will run another major test with the latest versions of Firefox to see if I can make them work acceptably, and go from there.
  12. I'm using Firefox 34.0.5 on XP SP3 32-bit. For me, after manual setup, the Primetime CDM plugin doesn't even appear in the list of plugins. I have checked all about:config settings and the folder path for the plugin files multiple times but I can't find anything wrong. I too would like to know if there are older versions of the Primetime CDM plugin available that I can try out. I've been in this sinking life raft for the past couple of days after YT decided to pull the plug on Flash completely. I can't play most of the newly released videos now because YT won't make available the WEBM versions until much later, usually up to half a day (up to several days in extreme cases). I've tried tinkering with other settings per the instructions on various forums, but the only change I ever got out of it is green video. I need a break... :-)
  13. Various problems with latest eRightSoft SUPER

    Hi Allen. Thanks for the reply. I followed up on your suggestion to give avidemux a spin. Quite a crash dummy, and it gives me an error upon every launch (The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll), but otherwise it's a pretty decent app. It's actually the first "alternative" to SUPER of all that I've tried over the years which outputs files in a good (if not the same) quality. I still need to find out where to find the "slow motion" setting and how to create files larger than 9,000MB, the latter because Pinnacle Studio doesn't seem to recognize the audio track if the file is split up. Avidemux also doesn't support 32-bit ARGB for the video, the format I'm using when capturing from my capture card with VirtualDub (video preview is distorted/greenish/upside down). ASF files don't seem to be supported either (crash). Inspite of the problems, though, I intend to keep this because it has some really useful features. InstallRite... yes... How could I forget? I'll try this on one of the other computers here.
  14. Various problems with latest eRightSoft SUPER

    Yzöwl... Thanks for the re-welcome. I'm still alive. I've just been busy....
  15. Hello all -- long time no see I have been into video editing a lot lately, and frequently used eRightSoft's SUPER as one of the programs to help me with this task. I've been using version 2010 build 37 for a really long time before I decided to upgrade to the latest version a couple of days ago. The only real problem I had with the older version is that the FFmpeg encoder was unable to output widescreen 720p HD videos; 960x720 (4:3) worked, and so did 1080x720 (3:2) but only if the video lasted a few seconds. MEncoder *was* able to cope with 1280x720 and 1080x720 resolution vids just nicely. The only time I needed to use FFmpeg in this context was when I wanted to crop or pad the video, which MEncoder can't do (at least not in SUPER). Having to downsize the video to e.g. 1024x576 while cropping with FFmpeg and resize it back to 1280x720 with MEncoder is not a preference of mine. For completeness' sake, I'll mention that I usually output videos in an AVI container using "Raw Uncompressed" as the video codec and "WAV PCM 16 LE" as the audio codec. Framerate, resolution, sampling rate and number of audio channels obviously depends on the input file and what I want to do with it. Most input files are FLV or MP4 files from YouTube, and recorded online ASF stream files. After the upgrade to the latest version (2012 build 51) and having used it for several days, the following problems came to my attention: 1) After I click on the "Encode (Active Files)" button, there is a delay of about 30 seconds before processing actually begins. This delay is also present for every video file when multiple files are to be processed subsequently. 2) The function "Disable Audio" is broken. After clicking "Encode (Active Files)" and waiting for 30 seconds, the program reverts to normal and acts as if it has finished processing, yet no output file is created. No error message appears. 3) Similarly to problem #2, I am unable to create .WAV files from AVI files; no output file is created. 4) With older versions of SUPER, I noticed that it could only mux video and audio streams if the file containing the video stream did not contain an audio stream and if the file containing the audio stream did not contain a video stream. Seeing that I can't create either type with the new version of SUPER (see problems #2 and 3), I decided to just drop the two media files (identically formatted AVI files) into the program window and started the muxing process, but it failed with the message "Invalid!" for the first stream file. So much for muxing. (I need this functionality because sometimes video and audio streams in the input files are out of sync, oftentimes after converting ASF to AVI. I normally cut or add a few video frames to the AVI file using Pinnacle Studio and output that to a new AVI file, create a .WAV file from that with SUPER and then mux it with a silent version of the original AVI file, yielding a file that is hopefully in sync. This is indeed a hit or miss scenario, but that's what you get when using freeware applications. Luckily I'm usually spot on.) 5) When using a custom video scale size, it's very hard to enter values in "Do not encode the first" and "Encode only for a total duration of" boxes. After typing one character (eg, "1" in the "Do not encode the first" box), the focus is automatically changed to the Width box in the Video Scale Size section of the program's interface. If I want to type a "5" after the "1", I need to click inside the "Do not encode the first box", use the arrow-right key on my keyboard, and then type "5". Very annoying. This doesn't happen if one of the predefined resolutions is chosen in the Video Scale Size section. 6) When I switch between FFmpeg and MEncoder, the framerate always changes automatically to 29.97fps. Most videos I make have a framerate of 25fps. This is yet another thing to be added to the pile of things that you need to watch out for when using SUPER. 7) Every time I want to make a video greater than 640x480, I get a big warning message saying that large resolutions will create bigger files and more system resources are required to process them. This is when I get one of those well-duh-huh moments. Seeing that the message cannot be disabled, it makes SUPER feel like a program from the 1980s in this day and age of HD video. That's about it. I wish I could revert to the older version, but anyone who has ever tried that will know that it won't work. SUPER stores information about the most recent version having been installed in some hidden location, blocking operation of an older version. Any help is greatly appreciated, as I need to process more videos. If of help, I'm on Windows 2000 so there is no System Restore feature.