LLXX

Look in the ShellNew directory under your Windows directory.

Backup your data NOW. Your drive is going to die very soon.This is the infamous 'Click of Death', and it means the end is near.

That is definitely a leak... if by 'network manager' you mean the utility that sets the configuration of the wireless adapter, you don't need it. Windows XP has its own wireless configuration utility, which works perfectly fine. Fix the pagefile's size (I prefer 1024/1024) after a defrag and you will notice better performance as it fills up, since it doesn't have to resize and possibly fragment.

That's not Russian... Character encoding was probably changed. If I were you I'd stay with A-Za-z0-9 and nothing else.

How much is yours using? Mine is at 25Mb and that seems reasonable...

I doubt they would be using XPH on many PCs (seemingly office environment)... XPP VLK more likely.

Try starting explorer.exe from the task manager Run menu item. Sometimes a corrupted explorer.exe or missing Shell= key in the registry can cause this.

M$ decided not to continue with WGA? Either that or it was installed automatically without your permission, check to see if WgaTray.exe and WgaLogon.dll are present on your system for verification.

Exception C0000017 is Out of Memory.

If I remember correctly HP used cartridges with an integrated printhead and water-based ink. There is probably still ink in the cartridge, but the print head nozzles are clogged with dried ink. As the ink is water-based, it will easily dissolve in water. Heat a pot of water just below its boiling point and submerge the printhead of the cartridge for a few minutes or until ink starts to flow freely (like a nib pen) when the printhead is wiped with paper towel. A few "head cleaning" cycles in the printer will exercise the nozzles further and help to remove the last few clogs. Doing that between 2-minute soaks in hot water seems to work best. I've done my own printer service (and other's printers) for a few years, this is from experience B) Epsons and other printers with separate (not easily replaceable) printheads are cleaned in much the same manner, although with their alcohol-based inks an overnight soak in ethanol works much better to clear clogs. To lessen the chance of plugged printheads in the future, you can use diluted ink which is thinner and less likely to dry out and become viscous (it's also cheaper than using 100% ink ). Black can usually be diluted to 10% by volume with no quality loss, beyond that it becomes dark grey but still legible... (good for draft printing or high-volume low-quality) as for the colors, only the cyan and magenta can be diluted quite a bit, the yellow is already faint so 50% is probably as low as I'd go without noticeable color loss.

Perhaps you should be more careful when you type? I see spell-checking can be useful for long documents, but...

What's the BIOS version and date? You should try using a newer version of Free FDISK, or the Windows ME FDISK that can be found somewhere in this thread.

I have heard this but I use Sourcer for almost 20 years already.... I even tried to use IDA many years ago but it looked very strange and confusing to me. Do you know about good tutorial how to use it? Petr I learned IDA by just exploring the different menus and key combinations... I know the documentation is rather terse but it's really not of much help at all. Supposedly the newer versions have a better Windows GUI but I've always stayed with v3.6...

Nod32.

I know the newer defraggers can defrag in the background, but that is NOT good both in terms of data safety and solving the fragmentation problem. The best results are obtained by defragging during a minimum boot and leaving it alone to complete. Perhaps all those background defrags have caused this fragmentation.

If M$ doesn't know about it...

A download manager is mandatory for this. Right-click and Save Target As just doesn't work.

Actually, only a small amount of all calculations that are normally done by programs can be parallelised. Otherwise, 79/80 of those cores are going to be idle since the program can only run on one. Better one ultrafast core than many small ones, unless your main focus is on parallel computation/distributed computing.

I think that's just your partition table messed up, or you used a different version of the PDR than the one you originally had. Use the Free FDISK instead.

You couldn't be more wrong. VxDs can contain both 16-bit realmode *and* 32-bit protmode code in different sections. Disassemble a driver like the ESDI_506 I patched for Enable48BitLBA and you'll see what I mean....and Petr, have you tried IDA? It's *much* better than Sourcer.

What type of 'recovery CD' is it exactly? Is it one which contains an OEM-customised Windows, or just a direct dump of files to be copied to the hard drive?

I like to use a formatter called 'Fint13', it can do many different and even nonstandard formats (like 1.8M on a 1.44 floppy)

ROFL... reminds me of this

There is probably a patch you can do to restore the original run-on-load functionality. I prefer click-to-run, it's actually more secure and you don't have to look at all the Flash ad crap (which should've been blocked by HOSTS anyway...)

This is a forum not a realtime chatroom. Do not bump threads. Edit: Just realised I bumped it