The_Unbeliever said:
...When typing in a new document, or opening an existing one from mail, all is well. However, when you click on Save As, and try to browse to another directory, then it takes ages to do something, and the computer seems to be frozen up. After 1 to 3 minutes, you can browse again, until you double-click on another subdirectory, then then whole thing seems to "hang" again for a while...
We get this a lot when the domain server was buggering up.
So - if you logon to the pc using a specific domain - then that could be the problem.
Check the machine that is the domain server's event log for hard disk errors and other stuff.
What happens is that you request access to an object - the domain server is asked - well - whi is this person requesting access ? - the domain server is supposed to answer immediately and identify you - but for some reason it is delayed...find out what the delay is.
To proove this, log onto the local computer, and not the domain. i.e. Logon and set the domain to the computer name. If you can access directories and local stuff quick and easy, then it's the domain controller.
Otherwise - check your event log for wierd stuff - specifically hard disk errors.
DigitalSoldier said:
Ok sorry to hijack ur topic but i also need help and i hope its window related
Everytime i try to install something on my computer it will install like 5% and then i get an error i cant install and sometimes i get a blue screen with an error IRQ_NOT_LESS_NOR_EQUAL so i did a format windows copies the files and then when the actual installation starts i get the same error only 5 % and then a stop message...
Yup - test the ram - it's probablee something else though - ram usually crashes dead and then won't POST [Power On Self Test] beeping 4 or 5 times without actually booting and stuff.
IRC = Something to do with an Interrupt Request check that does not return properly - the catch is that all your PC's prepirials [sp] run on interrupt requests, so it could be any damn PCI Card / drive / mouse / keyboard / whatever .. not just the memory. Even the dang CPU.
If you've built the machine, try to work a methodology that makes it crash [like run install - yours seems to crash at 5%] then remove all the cards from it [unless you have a screen card - keep that - otherwise there's nothing to see], unplug the mouse, and run it on one memory chip and see if it is stable.
Then add one device at a time until the problem returns. If the problem does not return then it could have been a bad connection.
I had this with a faulty ethernet network card.
Good wuck

!