nikki605

Waiting for the slim version.

Shortly after making my post, I found a similar solution here: http://www.dslreports.com/forum/r28027601-Horrible-youtube-speeds It specified 2 ip address ranges to block: 173.194.55.0 - 173.194.55.255 206.111.0.0 - 206.111.0.255 I entered those 2 ranges in the router and it did seem to help reduce the buffering issue. I don't watch a lot of YouTube videos either but when I do I'd like them to be viewable.

I have noticed this as well on my WinXP desktop system (Speccy details for this PC are linked in my signature). I am using Defraggler version 2.15.742. I also notice a long delay after clicking the Analyze button before anything happens. Once the Analyze has completed, I normally click on the File List tab to select all the files for defragging, but there is again another long delay during which time the check box to select all files is greyed out. On my Win7 laptop, I see the NO DATA but that is immediately replaced by the drive map as soon as I click on the Analyze button. On this system, I do NOT get the other 2 delays that I get on the WinXP desktop system. (again, Speccy details for the Win7 laptop are linked in my signature).

I need to go get that... thanks!

We Verizon FiOS customers have long complained about poor YouTube performance. Good article, thanks for posting.

I'll go get it.

For devices like video & pointing devices,yes. Here are some examples from my laptop. Intel HD Graphics Device ID 8086-0046 Revision 3 Subvendor Lenovo (17AA) Current Performance Level Level 1 Driver version 8.15.10.2622 Count of performance levels : 1 Level 1 HID-compliant mouse Device Kind Mouse Device Name HID-compliant mouse Vendor Microsoft Location Bluetooth HID Device Driver Date 6-21-2006 Version 6.1.7600.16385 File C:\Windows\system32\DRIVERS\mouhid.sys File C:\Windows\system32\DRIVERS\mouclass.sys Click on any of the "Speccy" links in my signature below to see exactly what information is available.

Guess it's time for me to upgrade to v4.x

You & me both Dennis! I have an 8-year old WinXP desktop that is primarily used by my wife. Under the threat of death, I HAVE to keep it running. She's tried my Win7 laptop and still can't figure it out. Last fall, the HDD finally gave up the ghost, so I bought a new 500GB SATA drive for it and scratch loaded WinXP back on it. The scratch reload gave it quite a performance boost. Last month, I replaced the PSU (bad fan) and finally, the rear case fan and CPU cooler fan (both noisey) for maintence purposes. While I had it apart, I cleaned the CPU & heatsink and applied new AS5 thermal compound which dropped the temp about 2~3°C. Still love WinXP. It just works! Long live the desktop.

A buzzing sound could be a bad transformer or possibly capacitor in the PSU. The fan shouldn't be running until the PC is powered up & booting. It might also be a bad earth ground at the power outlet. Either way it could be a sign of a pending failure.

Men in Black? Sorry... couldn't resist. I'll stop now.

Of course it did... they build 'em to do that. If it were me, I would first disconnect the a/c power cord, open the case and disconnect all the PSU power connectors from all devices including the motherboard. Then reconnect the a/c power cord and listen for the noise. This would isolate it down to the PSU if it still makes the noise and would probably have to be replaced. If there is no noise, I would disconnect the a/c power cord again and reconnect the power connectors to the motherboard. Repeat the process with each device adding them back one at a time until you hear the noise.

Cool. Thanks MrG, I'll go get it now.

I know when it gets updated by reading about it here. Thanks for the timely info. I'll go get it now.

I just successfully downloaded & installed 3.28 slim build from piriform.com with no problem. Give it another try as Hazel posted.

The S.M.A.R.T. attributes are explained here: http://en.wikipedia.org/wiki/S.M.A.R.T. This parameter is considered informational by the most hardware vendors. Although degradation of this parameter can be an indicator of drive aging and/or potential electromechanical problems, it does not directly indicate imminent drive failure. Regular backup is recommended. Pay closer attention to other parameters and overall drive health. Do you have the laptop power management set to turn off the HDD after x amount of time? That may be why the start/stop count is so high. My laptop has more power-on hours (503d) than yours (127d), but fewer start/stops (1,600) than yours (110,513). I have my HDD set to not shut down.

That's one fast goose!

I have MSE installed in a WinXP VM and after this week's updates, the ver is 4.2.223.0 and the Engine ver is 1.1.9103.0 I did not get any further MS update notification of a newer version. KB2804527: http://support.micro....com/kb/2804527 It doesn't mention any specific OS (XP, Vista, 7, etc.)

I use Norton anti-virus and had no problem downloading or installing CCleaner 3.27.1900. It may be a false positive from your a/v program. Which a/v program are you using? Upload the file to https://www.virustotal.com/ and see what it says. I just uploaded the ccsetup327_slim.exe file and it reported as 0/44 detection ratio.

"linoleum?" You really ARE dating yourself. But that's OK. The house I grew up in also had a linoleum kitchen floor, so we're probably about the same age.

ASK seems to be bundled with a lot of freeware these days. Gotta pay the bills somehow, I guess.

BINGO! I didn't think to look at the Restore tab since I wasn't looking to do a restore. But I'm glad to see that there is a Verify capability while still booted into WinXP so that I don't have to boot the Rescue CD every time I perform a new image. Thanks Dennis! I also followed Alan's advice back on the 1st page and last night I created a small "test" partition on the C:\ drive. I copied a bunch of folders/files into it, made an image & verified it. I deleted everything from the "test" partition, booted the Rescue CD and restored the image. After booting back into WinXP, all the folders/files appeared to restore correctly. I'm going to buy the Standard version for the additional features. Thanks for the great recommendation!

Great info Alan & Keatah - thanks for that. I'm thinking I may just spend the bucks for the Standard version to get the incremental and differential capability as well as the Verify function after image creation without having to boot the Rescue CD. Like anyone who uses a disk backup/imaging program, I just want something that backs up and restores correctly, something my last product didn't do very well. Next will be setting up a backup schedule. I haven't even looked at that function yet.

Guess I needed to be clearer. I didn't mean verify the burning of the Rescue CD, I meant verify the disk image that is written on my external HDD from the internal C:\ drive. When I start an image job, after selecting the Destination, the next window displays an Imaging Summary. One of the entries is: Auto Verify - N I assumed, perhaps incorrectly, that there was a way to enable Auto Verify. Maybe that option only exists in the paid versions... maybe not. What I did was after creating the drive image, I booted the Rescue CD. There, I found a "Verify" function and clicked on it. It ran for several minutes and ended with a sucessful verification of the disk image. I was looking to save time by NOT having to boot the Rescue CD just to verify the disk image. I thought I could turn on Auto Verify during the disk image setup to avoid the extra step.

Ah, spammers... gotta love 'em. After a little trouble burning the Rescue disk (WinPE), I was able to boot it and verify the image I had made to the FireWire external HDD. Macrium's internal burning program didn't write anything to the CD. I ended up telling it to create an iso image and I used another burning program to burn that iso to CD - I made 2. I also saved the iso image as a file on another external HDD... just in case I need to burn another Rescue disk. Is the only way to verify the image by booting the Rescue CD? I looked for the verify option while setting up the image creation, but didn't find it. Am I missing something? It seems like a lot of steps: 1. Create the image from WinXP (~40 minutes in my case) 2. Shut down WinXP & boot the Macrium Rescue CD to verify the image 3. Reboot WinXP This morning I'm going to try creating a "test" partion with Gparted, put some data in it and actually try an image and then restore to see what happens.