• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About mundy5

  1. dude, that's awesome; sometimes the older electronics are more stable and longer lasting than today's cheaper component driven systems.
  2. keep the good news flowing. Congrats bigleg!
  3. Salami, we're glad that you found this post. I believe that there were reports of bad CA-42 cables but it does not look like that was the cable you purchased. The CA-42 cables from China are usually made with the prolific board. I believe 2303 is the most common. Have you also installed a driver for your 2303HX chip? That might be part of the problem. Anyway, if you can get a hold of a CA-42 cable, we can try to help or make sure that you have installed a driver for your particular cable. They do not work out of the box.
  4. I don't own an original or clone CA-42 cable myself, but it is widely known that the clones don't respond the same as original cables do. Apparently your clone-cable really needs to see a phone attached for it to function or get initialized/seen by the system. You could try to use another USB-port (not on a hub), preferably one that is directly attached to the motherboard (at the back) like Mundy suggests or maybe even on another system, but it's just a long shot. If you can get your hands on a computer with a real on-board COM-port you could use the MAX232 option. If that's not an option you get yourself one of the other USB->TTL-RS232 solutions around. Greetz, Peter. I'm not so sure about the problems reported on the clone CA-42 cables. I have a clone made in China that worked fine. I think there might be "human error" involved. Anyway, I am one who used a Chinese made CA-42 cable with success.
  5. If my memory serves me correctly, my computer recognizes the CA-42 cable when the USB is plugged in even when nothing is on the other end once the driver has been properly installed. I think on my desktop, I was able to install the driver first and then the computer connected the driver to the CA-42 cable. On my laptop, I had to first connect the CA-42 to the usb port and then it prompted me for the driver. Either way, I do not believe the CA-42 cable was connected to my hdd. Are you saying that your computer does not recognize it at all? Try a different USB port that has a direct connection, some USB ports are part of hubs that are internal to the computer. Do you have the driver, not the Nokia suite, for your CA-42 cable?
  6. As you can tell from this image you uploaded, it does not have the SD15 firmware but some IBM version of it. I'd recommend that you contact IBM to see if they have a solution. Of course, you could try a CA-42 cable or a RS232-TTL converter, but I'd call IBM first or go to their support website. I have not seen anyone else with your particular drive on this thread. It might be worth starting a new one. As I said in an earlier post, different firmware, all bets are off since we cannot test it from our end.
  7. Your error codes are not what we have seen here. what is the firmware on your hdd? it should say SD15 otherwise, all bets are off on this solution.
  8. All, I wanted to encourage all new members to read carefully the first post of this thread. I think we are now observing a phenomenon that is unfortunate. People with different versions of the firmware or with slightly different symptoms are coming to this site and trying the fix and when it doesn't work, they are posting for a solution. I am not technically capable enough to help folks with different HDDs and different firmware. I can only speak of my own experience in successfully trying this fix. I would encourage you all to try this solution if you have the bad SD15 firmware and the correct 7200.11 HDD from Seagate. I feel for you that your HDD is not working properly but I'm not sure we can be of much help if yours does not fall into the correct specs.
  9. yes, you will have to remove the drive. You should see a separate PCB attached to the HDD once you remove it from the enclosure. The board that is visible should be LaCie's. Of course, you will not know until you actually disassemble the enclosure.
  10. yes, that is exactly how I did it. I didn't even have any electrical tape on them. but to be safe you should.
  11. always good to read a success story!
  12. good. that's right. but I had the BSY problem which made the hdd not recognizable at all. I'd try the solution. You really have nothing to lose unless you want to pay the 700 Euros.
  13. Thank you for confirming what I suspected. I think i365 (Netherlands) have just done the same to me. I sent them a 7200.11 500GB drive with BSY failure and they told me to pay 775€ to recover the data (then less than 500€ if I was not in a hurry). I asked them to return it to me. Now I have a drive with something like the LBA0 problem. I'm new here and I have one question: Does the LBA0 problem show the correct model number in BIOS? My drive now shows itself as "IDE Hard Disk" when booting, and 0GB size in BIOS (it spins and I can hear the heads moving). Is this the typical behaviour? Should it be as easy to fix as you are talking here? Thank you very much! XPG, I'm sorry to hear of your experience. Your evaluation of the situation makes me hesitate in giving you any firm answers. In most cases, I believe those with the LBA0 problem had no issues with the drive being recognized properly by the BIOS. The only problem they had was that it was recognized as a null sized HDD which means, not useable. In your case, since it is not even being recognized by BIOS properly, I am not certain. Have you verified that you have the problem firmware using the serial number checker on the seagate website? I think I have a link a few posts earlier. If so, then I think you should be able to go through the LBA0 fix to see if that corrects anything for you. The HDD will spin up like normal and should not have any funny sounds associated with it. If it has other sounds, then you are most likely also dealing with other problems. As it was in my case which is why I returned it after backing up all the data ASAP. Keep us updated on this.
  14. If your PC has the faulty model and firmware, then yes, you will also have this problem. You can take the serial number of your seagate hdd and go to the seagate website and type in the serial number. go here and choose #2 "click here to use the serial number check utility" it will tell you if it is one of the affected models. that is the sure way to know if it is this problem. btw, it doesn't matter the brand of your pc, if they used the faulty seagate hdd, then you will have this problem.
  15. You're the 2nd person in recent days to say the exact same thing. I have 2 questions. 1. How are you powering your sata hdd? Using your old computer? 2. Are you making sure that it is sharing the same ground? When I did it, I was using a the desktop with a different hdd and the CA-42 cable. They were sharing the same ground.