|
HAY,
I HAVE ONE HARD DRIVE.
IT HAVE CAPACITY 160GB.
I WAS USING IT IN MY NEW COMPUTER (MANUFACTURED AROUND 2008.), AND IT WAS WORKING FINE. I WAS USING WINDOWS XP SP3.
THAN, I MOVED IT TO ANOTHER COMPUTER. THIS ONE IS OLDER (MANUFACTURED AROUND 2000.). AND I DID NOT MADE ANY CHANGES ON IT, OR ON DATA ON IT. EVERYTHING ON THE HARD DRIVE IS THE SAME LIKE IN THE NEW COMPUTER. JUST THIS COMPUTER IS OLDER. AND, BEFORE THAT I WAS USING HARD DRIVE WITH 14 GB CAPACITY AND WINDOWS XP SP3 ON THAT OLD COMPUTER WITHOUT ANY PROBLEMS.
BUT, NOW, WHEN I ATTACH THAT BIG HARD DRIVE IN OLDER COMPUTER, IT DOES NOT WORK CORRECTLY.
WHAT IS INTERESTING IS THAT BIOS (BASIC INPUT/OUTPUT SYSTEM) RECOGNIZES IT, AND SUCCESSFULLY REGISTER. SO, IN BIOS, I SEE THAT THIS HARD DRIVE IS CONNECTED AND THAT IT HAVE CAPACITY OF 160 GB.
BUT, THIS DRIVE CAN NOT BE USED EITHER AS PRIMARY OR SECONDARY DRIVE. WHEN I USE IT AS PRIMARY HARD DRIVE, IT DOES NOT BOOT UP SYSTEM. BIOS JUST SKIP IT, AND SEARCH THE NEXT BOOT DEVICE LISTED IN BIOS'S BOOT DEVICE PRIORITY LIST RIGHT AFTER HARD DRIVE. SO, IT CAN NOT BOOT.
BUT, I ALSO TRIED TO USE IT AS SECONDARY HARD DRIVE. I RECONNECTED MY OLD HARD DRIVE (14GB), AND BOOT WINDOWS XP SUCCESSFULLY, AND IN WINDOWS XP, THIS DRIVE IS NOT RECOGNIZED. WINDOWS XP REPORTS THAT ONLY ONE DRIVE IS CONNECTED AND THAT IS THE SMALLER ONE.
BY THE WAY, WINDOWS XP SUPPORTS HARD DRIVE OF 160 GB, BECAUSE ON NEWER COMPUTER IT WORKES ON IT.
BUT ONE VERY VERY INTERESTING THING HAPPENS WHEN I CONNECT THIS NEW HARD DRIVE ON OLDER COMPUTER, AND BOOT WINDOWS FROM OTHER HARD DRIVE, SO THAT I CAN USE THIS 160 GB HARD DRIVE AS A SECONDARY.
WHAT HAPPENS IS THIS: THIS OLDER HARD DRIVE WITH CAPACITY OF 14 GB IS COMPLETELY FORMATTED. AND THERE IS NO UNALLOCATED SPACE. I FORMATTED IT ON THAT WAY. AND THIS IS WHAT I SEE WHEN I USE JUST THE SMALLER ONE HARD DRIVE, WHEN BIGGER ONE IS NOT ATTACHED. BUT, WHEN I CONNECT BIGGER ONE THIS CHANGE. I USE WINDOWS DISK MANAGER TO MONITOR WHAT IS CONNECTED AND WHAT NOT. AND THERE I CAN SEE THAT MY SMALLER ONE HARD DRIVE IS COMPLETELY FORMATTED. BUT WHEN I CONNECT THE BIGGER HARD DRIVE AS A SECONDARY HARD DISK. DISK MANAGER DOES NOT SHOW IT. BUT, SUDDENLY, HOLE OF 9 MB APPEARS AT THE SMALLER ONE HARD DRIVE. WINDOWS DISK MANAGER REPORTS THAT SMALLER ONE HARD DRIVE HAVE 9 MB OF UNALLOCATED SPACE. BUT WHEN I REMOVE BIGGER ONE HARD DRIVE THIS DISAPPEAR. AND SMALLER ONE IS COMPLETELY FORMATTED AGAIN.
SO, IT IS CLEAR THAT THIS HARD DRIVE IS INCOMPATIBLE IN WINDOWS.
I HAVE ALSO TRIED TO USE WINDOWS BOOT DISK TO REPAIR INSTALLATION OF WINDOWS, SINCE WINDOWS MOSTLY DOES NOT SUPPORT MANY HARDWARE TYPES, ONCE INSTALLED. DURING SETUP, IT CONFIGURES ITSELF TO WORK UNDER SOME TYPE OF HARDWARE. SO, WHEN YOU JUST SIMPLY MOVE HARD DRIVE FROM ONE COMPUTER TO ANOTHER, WINDOWS DOES NOT BOOT UP SUCCESSFULLY UNTILL YOU RESTART SETUP SO THAT WINDOWS CAN MAKE CONFIGURATION CHANGES THAT WILL ALLOW IT TO BOOT ON OTHER COMPUTER.
SO, I TRIED TO USE SETUP BOOT DISK (CD) TO ACCESS HARD DRIVE ON THAT WAY. BUT, SETUP SIMPLY FREEZE, BEFORE IT EVEN STARTS EVERY TIME THIS HARD DRIVE IS CONNECTED. WHEN IS NOT, SETUP LOADS JUST FINE. BY THE WAY, THIS SETUP PROGRAM FOR WINDOWS INSTALLATION WAS ABLE TO START AND FINISH COMPLETELY WHEN I STARTED IT ON THE NEW COMPUTER.
SO, BIOS SEAS MY HARD DRIVE, AND IDENTIFIES IT CORRECTLY. WINDOWS DOES NOT. WINDOWS CAN NOT BOOT FROM IT, CAN NOT READ FROM IT, AND CREATES SOME STRANGE UNALLOCATED HOLE AT MY PRIMARY HARD DRIVE WHEN SECONDARY IS ATTACHED. SETUP FREEZES.
SO, MY HARD DRIVE IS INCOMPATIBLE WITH OLDER COMPUTER, BECAUSE ON NEWER IT WORKED VERY GREAT.
SO, MY QUESTION IS, WHAT CAN BE THE POSSIBLE REASON FOR THIS INCOMPATIBILITY I DESCRIBED DETAILY HERE?
YBY
_________________
YBY
|
FAQ
Search
Login
Register
HDDGURU FILES
