Windows XP

That''s what you get for renaming system files.

Seriously though, I dunno. Make sure it''s not a hardware problem - memory is my first suspect when I see a blue screen(one of my chips went bad on me).

Good, free memory test program

Sorry to hi-jack the thread a little, but you left the topic wide open ("windows xp"). (by the way cool program link)

I''m still having problems with my XP, it freezes up often when right clicking on certain files, and sometimes when just opening certain folders/selecting certain files, then unfreezes after about ~5 minutes, and does whatever I told it to do origionally (select file, or right click).

Anyone know of a fix, or even a cause, for/to this problem? .sen

Forgive me if this is a dumb question, but if your RAM is kaputt, how in the heck are you meant to run a diagnostic program to check it?? So far as I'm aware, computers with faulty RAM will not boot at all generally.

*Edit* I guess RAM can be faulty in several ways or something... just a guess.

[edited by - mephs on May 4, 2003 6:44:15 AM]

Mephs:

Computers with faulty RAM WILL boot, however, once you end up using the actual memory range that is faulty, the data you are trying to use is corrupted and usually results in a crash.

What you CAN do, and what these programs most likely do, is boot a very light OS-thingy. Then it will try to write data to memory and read it again. If it gets back different data then it wrote back, you have a faulty memory range. Off course, if your complete RAM bank is dead, you computer won''t boot, but hey :D Same with Scandisk for your HD. It will see if sectors are bad. If your complete HD is dead, you can''t run Scandisk either, can you?

---

Senses:

Hrm. I think your HD might be slightly fried, or your disk is TERRIBLY fragmented. Or your filesystem is kaput. In any case, it can''t really retrieve the data it wants. And won''t continue until it gets the data.

---

Wavarian:

Pop in your installation disk, and boot from that one. Select "repair" at the first screen. This will put you in a dos-like console (after punching in your Admin password), and you can simply go to \windows\system or \windows\system32, depending on where the file is. Then simply do ''ren whateveryoucalledit.file crss.exe''. Have fun!!!

Computers defragmented (I do it often), and the problem is somewhat new. Is there anything I can do? I heard also it might be one of the WinXP patches I have D/L''ed causing the problem. .sen

quote:

---

Original post by Senses777
Sorry to hi-jack the thread a little, but you left the topic wide open ("windows xp"). (by the way cool program link)

I''m still having problems with my XP, it freezes up often when right clicking on certain files, and sometimes when just opening certain folders/selecting certain files, then unfreezes after about ~5 minutes, and does whatever I told it to do origionally (select file, or right click).

Anyone know of a fix, or even a cause, for/to this problem? .sen

---

XP likes to scan files & folders to give you the handy-dandy info panel on the side of windows. Unfortunatly i found that with certain types of file (very large .zip files mainly) XP takes *ages* to scan it. See if you can isolate it down to a particular file/directory and go from there..

Oh, and turning off the zip file intergration and using winzip or something may help if this is the actual problem.

WinXP, Win2000, and WinNT come with a recovery console. USE IT!!! . It WILL save your a$$ more often than not.

I thought system files on XP were protected...

R

/*//*//*//*//*//*//*//*//*//*//*//*//*//*//*//*//*//*//*//*///

Resist:Temptation 1.18

/*//*//*//*//*//*//*//*//*//*//*//*//*//*//*//*//*//*//*//*///

quote:

---

Original post by Senses777
Sorry to hi-jack the thread a little, but you left the topic wide open ("windows xp"). (by the way cool program link)

I''m still having problems with my XP, it freezes up often when right clicking on certain files, and sometimes when just opening certain folders/selecting certain files, then unfreezes after about ~5 minutes, and does whatever I told it to do origionally (select file, or right click).

Anyone know of a fix, or even a cause, for/to this problem? .sen

---

This isn''t necessarily correct, but that''s what happened just before I lost my laptop hard drive.

thanks pouyacat, that helped. Turns out winxp did something good in copying a backup copy to its original filename, so all I had to do was restore a previous registry backup =)

Firing up a DOS shell (command.com in your primary master drive root) and navigating that way is a great weapon for fighting the file lag.

---------------------------------------------
How many nukes could a fat duck duck if a fat duck could duck nukes?

quote:

---

Original post by Senses777
I''m still having problems with my XP, it freezes up often when right clicking on certain files, and sometimes when just opening certain folders/selecting certain files, then unfreezes after about ~5 minutes, and does whatever I told it to do origionally (select file, or right click).

---

Not sure, but I think your system is broken/inconsistent. When you right-click on a file, Explorer creates a context menu. It is possible for programs to "hook" into this context menu. If had such program and uninstalled it, and the "hook" was left, it may cause what you describe. A coworker of mine has a seriously broken Windows XP installation, and it regulary freezes, but I suspect that is because of broken network associations. If it takes 5 minutes for it to come around, it might be network related, as most network operations timeout after 6 minutes.

a good way to rename the file back would be to use an oem pre-installation cd. those are bootable and they will get you into a console that you could rename the file with. my copy of win xp home came with one.

Sen:

I think CWizard has the closest answer - it''s gonna be to do with the shell. What else does Windows need to do when you right-click a file? Were it not for the shell-hooking system, it would just be displaying a simple menu each time, and we know how easy that is to do.

The shell-hooking info is stored in the registry (HKEY_CLASSES, IIRC), so it''s possible that the registry is corrupt. The only suggestion I''ve got is to remove all your file type associations (or at least, all the ones that cause you problems). It should only be certain types of file - is there a common program that works with those files? (If WinZip were causing the problem, you''d get it with *any* file)...

Superpig
- saving pigs from untimely fates, and when he''s not doing that, runs The Binary Refinery.

quote:

---

Original post by Cestps

---------------------------------------------
How many nukes could a fat duck duck if a fat duck could duck nukes?

---

i like that

------------------------------------------------------------
I really need to update this signature...

Hmm, thanks for all the help. It seems to be only with zip files as far as I can tell (though I remembered it being with other things too). And it only happens with very large ones (>100MB, but generally only with >500mb). Explorer is doing it right now actually, but since its only explorer that is effected and I had the browser open I can still use this without problems, I just cant do anything with my desktop etc for ~5 minutes. I highly doubt it is a network problem, because the computer is thinking so hard during the whole thing, its not like its just waiting or something.

It is indeed HKEY_CLASSES [wait, there it went, the right click context menue popped up just now over Mozilla, hehe] that holds the extention info, but how would I go about fixing this problem if it were in the right click context menu? .sen

Try to uninstall WinZip or WinRar, and see if it is better. Then reinstall them and hope it still works.