You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
It still gives out errors.
Click on the atapi error in the list to read the error description below, and show a screenshot again.
I had an error like this a long time ago due to a bad contact on the stub that connects the hard drive to the motherboard.
This is the area of interest in the atapi error log:
Install on D and run MT (and ME) in portable mode. To do this, add /portable to the shortcut properties for MT and ME.
... And get a lot of headaches in working in the pendulum
I'm just an old-timer. I am doing fine with 3-5 terminals without a key, I used to have up to 10 or more, and I don't feel any inconvenience.
But I often see on forums how the "key people" have this one that doesn't work, and this one that glitches.
Click on the atapi error in the list to read the error description below, and show a screenshot again.
I had an error like this a long time ago due to a bad contact on the stub that connects the hard drive to the motherboard.
This is the area of interest in the atapi error log:
I'm just an old-timer. I am doing fine with 3-5 terminals without a key, I used to have up to 10 or more, and I don't feel any inconvenience.
But I often see on forums how the "key people" have this one that doesn't work, and this one that glitches.
Pull out the cable that connects the hard drive to the motherboard and check its contacts. If it looks OK, with no damage or deformation, plug it in again, gently and as far as it will go. If the contacts are in doubt, then try a new stub.
If that doesn't help, I'd first try another hard disk and check the BIOS settings.
Pull out the cable that connects the hard drive to the motherboard and check its contacts. If it looks OK, with no damage or deformation, plug it in again, gently and as far as it will go. If the contacts are in doubt, try a new stub.
If that doesn't help, I'd first try another hard drive and check the BIOS settings.
Got it. I'll pull it out now.
What about the hard drive? If, for example, a part is damaged, you could isolate it, i.e. you could rewrite it to another part of the drive...
I don't have another drive, so I can't just check...
I guess I'd have to call in a handyman then?
Pull out the cable that connects the hard drive to the motherboard and check its contacts. If it looks OK, with no damage or deformation, plug it in again, gently and as far as it will go. If the contacts are in doubt, then try a new stub.
If that doesn't help, I'd first try another hard drive and check BIOS settings.
Cleaned it. Visually there are no problems.
Switched it on at 16.57. Doesn't seem to give any errors...