spjallid.is

Sæl.

Þannig er mál með vexti að núna er harði diskurinn minn að keyra í PIO mode og er ég búin að reyna að fara eftir þessum hérna þræði til að laga það en það virðist ekki virka. Þannig að nú spyr ég, hvernig get ég losað diskinn úr PIO-Mode?

Er mikið í videovinnslu og þegar ég reyni að rendera eitthvað fer tölvan einfaldlega í fokk.

Hérna eru myndir af því hvernig þetta er þetta stillt hjá mér í device manager.

Primary IDE Channel
Secondary IDE Channel

Getur hugsanlega lagað þetta í BIOS

þetta hefur reynst mér vel í gegnum tíðina .. en enndilega að hafa í huga að pio mide errorar eru vísbending um að harði diskurinn sé mögulega að gefa sig, svo endilega vera duglegur að backa up :wink:

Kóði: Velja allt

Go to..

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1]

Notes:  These keys are called SCSI solely for historic reasons; SCSI Port 0 is actually IDE1 and SCSI Port 1 is IDE2.

 

Modify..

DMAEnabled = 1 (DWORD value)

Notes:  This is usually set to zero after a PIO failback.  Some systems may change your “1” to a “3” after a reboot - it seems to depend on how heavy your computer is already with DMA-enabled hardware.  One of my machines’ drives default to DMA3 and doesn’t seem to act any differently, but I can’t find a reference to this behaviour anywhere online.. shrug..  The machine in question is bristling with lots of tacked on hardware: 2 HDDs, CD, DVD, 3D video with TV-Out, wireless keyb/mouse, onboard sound, network, 4 USB devices.

 

Go to..

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0001]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002]

Notes:  0001 is the key for IDE2 and 0002 is the key for IDE1, go figure.  The string associated to MatchingDeviceId will tell you for sure what you’re looking at (ie: “primary_ide_channel” or “secondary_ide_channel”.  If you don’t know what those basic nuts & bolts terms are, I really really really think you should stop what you’re doing RIGHT NOW.)  Also, you don’t need to remember that entire long-winded numbered key, 4D36-etc… I just scan the fourth octet of the first dozen Class keys for “6A”  (as underlined in the blue text above).

 

Delete..

MasterIdDataCheckSum

SlaveIdDataCheckSum

Notes:  If you don’t see a checksums associated with a particular slot, then there’s no device detected.  If you can’t work out which slot goes with which drive, well, that gives me misgivings about you messing about in RegEdit, but it doesn’t matter if you simply delete all the checksums in the 0001 and 0002 keys (there can be a max of two devices for IDE1, two for IDE2).  At the next login, WinXP will notice something is up when the detected devices don’t match the checksum flags and the device’s capabilities will be re-examined.

 

Delete..

MasterDeviceDetectionTimeout

SlaveDeviceDetectionTimeout

Notes:  Delete these keys if present, if you have a device that is not detecting or doesn’t already have a checksum associated with it.  If there’s a timeout=1 flag, Windoze doesn’t bother detecting for a device in that slot at login.  Again, this is just a detection flag, so it doesn’t matter if you delete them willy-nilly; if there truly is no device there, the timeout key will simply be recreated at next login.  If you still have access to a hard drive that has a timeout flag like this, chances are it’s running in the crippled “Dos Compatibility Mode” where XP is basically fudging your connection to it in real time.  I think you are told this under Device Manager > Disk Drives > (appropriate device) > General Properties tab, and also with a warning message at login.  If it is a newly installed device, you may have also forgotten to assign a partition and/or drive letter to it using the Microsoft Management Console: Start > right-click My Computer > Manage > Storage folder > Disk Management console.  Not recommended for n00bs! Very dangerous!

 

Create..

ResetErrorCountersOnSuccess = 1 (DWORD value)

Notes:  If this flag is present, the running tally of device access failures is reset to zero after every successful access.  (I mentioned earlier that a transfer mode downgrade is triggered after a sixth cummulative failure.)  Hopefully, this will lengthen the time before your next PIO failback as you’ll need six consecutive failures to trigger it.

ADDENDUM – Microsoft finally released a "patch" for the failback behaviour.  However, after minimal scrutiny all this atapi.sys upgrade really does is change the trigger requirement of six cummulative fails to six consecutive, which is what we've been doing for ages with this reseterrorcounters flag anyway.  *sigh*  :o/

 

Reboot..

Notes: After you’ve rebooted, go back into the IDE settings and see if DMA is available now.  If the Current Transfer Mode is still PIO, then I wash my hands of you.  (splash splash)  See that? I’m washing my hands.

Finnst ólíklegt að harði diskurin sé að gefa sig, þetta er annar af 2 glænýjum diskum sem ég set windows á. Eg prófaði fyrst að setja winsows upp á 74GB Raptor og hann fór í PIO mode og þegar ég fór með hann í viðgerð sögðu þeir að hann væri gallaður. Núna er ég með winsows á glænýjum 500GB hörðum disk og þetta er samt svona

Inn í hvað fer ég til að geta breytt þessu Xyron.

dezeGno skrifaði:Inn í hvað fer ég til að geta breytt þessu Xyron.

Heldur windows takkanum á lyklaborðinu inni og ýtir á R. Þá kemur upp run glugginn og í hann skrifar þú regedit og ýtir á enter. Þá færð þú upp registryið og getur breytt að vild.

spjallid.is

PIO Mode

PIO Mode