i need expert in hardware

First of all technically this is not a hardware issue. This is a software issue related to memory buffer when allocating i/o data structure. Now I am taking you are using Windows as this is the only platform who is effected by this kind of stupidity, mostly on 2k3, 2k8 and vista now. Microsoft already has patch for this so google for it, this is due to your busy process working simotanously at once.

For anything to be copied for example a data sector in local disk it has to be first allocated on the memory buffer which is now done directly and is not passed over ext bus. After that the data can be removed or remapped, depending on the type of task you are doing and number of process accessing the bridge on your computer will be effected.

PS: This is not a problem in any other platform other than WinBLOW, your hardware is fine its the inferior implemantion of poor memory management in WinBLOW to emulate Unix like platform that causing this problem. Hence linux is ALWAYS superior when it comes to memory?

If it's a Sata drive check your IDE ATA/ATAPI Controller Settings in Device Manager in Windows XP.

Start>Control>System>Device Manger>IDE ATA/ATAPI Controller. right click on your Primary or Secondary IDE and click on advanced setting tab. Does your sata drive show transfer mode PIO? if it does unistall all your primary and secondary ide drivers then do a reboot that should solve your problem. If everything says DMA if available in the transfer mode box or ultra dma 1,2,3,4, then it's another problem. Or it could be a memory buffer problem.

I had the same problem awhile back. Hope that helps.

http://sniptools.com/tipstricks/gett...-in-windows-xp

If thats not the issue then pay close attention to HyperNodes Post.

thank you grimms i checked it out and i found its DMA

thank you grimms i checked it out and i found its DMA

thank you grimms i checked it out and i found its DMA

Quote:

---

Originally Posted by HyperNode

First of all technically this is not a hardware issue. This is a software issue related to memory buffer when allocating i/o data structure. Now I am taking you are using Windows as this is the only platform who is effected by this kind of stupidity, mostly on 2k3, 2k8 and vista now. Microsoft already has patch for this so google for it, this is due to your busy process working simotanously at once.

For anything to be copied for example a data sector in local disk it has to be first allocated on the memory buffer which is now done directly and is not passed over ext bus. After that the data can be removed or remapped, depending on the type of task you are doing and number of process accessing the bridge on your computer will be effected.

PS: This is not a problem in any other platform other than WinBLOW, your hardware is fine its the inferior implemantion of poor memory management in WinBLOW to emulate Unix like platform that causing this problem. Hence linux is ALWAYS superior when it comes to memory?

---

can u give me the link of this microsoft patch plz

Quote:

---

Originally Posted by HyperNode

Microsoft already has patch for this so google for it, this is due to your busy process working simotanously at once.

---

Yeah, a link would be nice as well as the definition of the "busy process".

Well to be honest unless you understand how harddrive works when it access data to read/write, relocate, remove then you will only get confused if you haven't seen memory map of a file yet. As you have to understand the concept of cluster and status of given field. Keep in mind we are not using DMA any more it was after ATA-4 that it was changed to Ultra-DMA for HDD's primary way to communicate with other device. Now depending on the task you are doing and number of process accessing the disk each of the duration of task itself will be affected.

For example let say you are accessing hda now it has 2 volume 0 and 1. Now you are reading file from hda0 while in hda1 you are allocating a selected group of data cluster and removing it (not same as Windows method of delete as it will just remove the file and rename it unless completely erased secure way). At the same time you open and copy a iso9660 and saving it in hda0. Now all three of this process is accessing the same HD so the duration of each task would be effected. Once again you have to know how a harddrive works to hardware level to understand how the arm, head moves on each platter even when they are doing it simotanously at once.

But any ways here is the link from M$> http://support.microsoft.com/default.aspx/kb/931770 <

PS: As windows try to emulate more and more like UNIX platform wannabe. Some of the poor memory handling methods has yet to be tested by them let alone trying to multi task. If anyone of you are interested or like to know me then just drop me a PM ill be happy to explain it.

I don't see how your explanation of how a HDD works and that MS hotfix have anything to do with each other- maybe I'm just dense.

Quote:

---

Originally Posted by clocker

I don't see how your explanation of how a HDD works and that MS hotfix have anything to do with each other- maybe I'm just dense.

---

Unless you understand how HD works you won't understand the problem let alone the fix itself. Its all connected and not magic how it works. Don't try to google any of this unless you have background in IT or understand hardware basic levels it would be pointless.

Clocker, you are such a noob. :rolleyes: