If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
First, you need to ascertain whether this is a WinMe issue or - more
likely - a hardware issue. Confirm that you can 'see' both physical HDD's in your BIOS. If not, check cabling AND Master/Slave links correctly set. Have you acknowledged (detected and set) a second drive in the BIOS? If OK in BIOS, boot with your WinMe Startup (floppy) disk and confirm that you can 'see' both disks AND their partitions in Real Mode DOS. If so, can you read AND write (in DOS) to all partitions. Confirm the above then worry about WinMe. BTW - What letter(s) is/are assigned to your CD-ROM(s) - if fitted? Mart "Nigel Andrews" wrote in message ... I am having problems with Windows ME when adding in a working old hard disk. After going into 'safe mode' (because I switched off the PC) I get a blue screen 'Windows protection error'. This happens whenever a replacement second harddisk is connected. If I remove it then Windows starts cleanly. I have checked that the cable is connected correctly (any other connection gets a worse result i.e., No O/S!) I have treid this with two old harddisks that should be OK. I also had it with the orginal harddisk which is why I am trying to replace it. Any ideas please? Thanks Nigel |
#12
|
|||
|
|||
Mart,
Thanks for the quick response. I have the slave set to Auto in the BIOS (and of course the jumpers set to Slave on both the replacement) But booting with the ME start-up disk, with one of my replacement old disks installed, it doesn't finish booting (or boots to an A: prompt but says C:, D: etc don't exists!). With the other connected I get to a Minimal Boot, and can start FDISK but it says it can't access disk 2!. I thought both these were working, tho' years ago, and they are similar drives tho' much lower capacity than what they are replacing. Both the drives 'come alive' during the boot sequences (spinning up and heads chattering). Is this showing that they are faulty or is it the format on the disks themselves which is causing the boot problems? Thanks again Nigel "Mart" wrote in message ... First, you need to ascertain whether this is a WinMe issue or - more likely - a hardware issue. Confirm that you can 'see' both physical HDD's in your BIOS. If not, check cabling AND Master/Slave links correctly set. Have you acknowledged (detected and set) a second drive in the BIOS? If OK in BIOS, boot with your WinMe Startup (floppy) disk and confirm that you can 'see' both disks AND their partitions in Real Mode DOS. If so, can you read AND write (in DOS) to all partitions. Confirm the above then worry about WinMe. BTW - What letter(s) is/are assigned to your CD-ROM(s) - if fitted? Mart "Nigel Andrews" wrote in message ... I am having problems with Windows ME when adding in a working old hard disk. After going into 'safe mode' (because I switched off the PC) I get a blue screen 'Windows protection error'. This happens whenever a replacement second harddisk is connected. If I remove it then Windows starts cleanly. I have checked that the cable is connected correctly (any other connection gets a worse result i.e., No O/S!) I have treid this with two old harddisks that should be OK. I also had it with the orginal harddisk which is why I am trying to replace it. Any ideas please? Thanks Nigel |
#13
|
|||
|
|||
Well Nigel, you certainly seem to have proved that WinMe isn't the cause!!
Under the circumstances - and that may depend both on how urgently you want/need to replace your D: with a 'good' one and how full your wallet feels - you could cut your losses and buy a new HDD. However, if you want to 'see it through' then examine each of your 'old' drives in turn - by temporarily throwing-off your existing 'good' C: drive. Keep things simple! Make each of your old drives (individually) the C: (master) and FDSK /STATUS each one to ascertain their state - Fdisking and re-formatting if necessary - followed by a Real Mode DOS Scandisk. Then, when you've proved that they are still serviceable - and all is back to normal with your 'original' C: back in place - re-introduce them, one at a time as the D: BTW - Auto *may* not be enough - You *might* have to re-detect them first in the BIOS (there should be 'detect' option available - refer to the User Manual (if you have one!!) Is this showing that they are faulty or is it the format on the disks themselves which is causing the boot problems? Depends upon the results from above tests, but they sure sound 'suspicious' Mart "Nigel Andrews" wrote in message ... Mart, Thanks for the quick response. I have the slave set to Auto in the BIOS (and of course the jumpers set to Slave on both the replacement) But booting with the ME start-up disk, with one of my replacement old disks installed, it doesn't finish booting (or boots to an A: prompt but says C:, D: etc don't exists!). With the other connected I get to a Minimal Boot, and can start FDISK but it says it can't access disk 2!. I thought both these were working, tho' years ago, and they are similar drives tho' much lower capacity than what they are replacing. Both the drives 'come alive' during the boot sequences (spinning up and heads chattering). Is this showing that they are faulty or is it the format on the disks themselves which is causing the boot problems? Thanks again Nigel "Mart" wrote in message ... First, you need to ascertain whether this is a WinMe issue or - more likely - a hardware issue. Confirm that you can 'see' both physical HDD's in your BIOS. If not, check cabling AND Master/Slave links correctly set. Have you acknowledged (detected and set) a second drive in the BIOS? If OK in BIOS, boot with your WinMe Startup (floppy) disk and confirm that you can 'see' both disks AND their partitions in Real Mode DOS. If so, can you read AND write (in DOS) to all partitions. Confirm the above then worry about WinMe. BTW - What letter(s) is/are assigned to your CD-ROM(s) - if fitted? Mart "Nigel Andrews" wrote in message ... I am having problems with Windows ME when adding in a working old hard disk. After going into 'safe mode' (because I switched off the PC) I get a blue screen 'Windows protection error'. This happens whenever a replacement second harddisk is connected. If I remove it then Windows starts cleanly. I have checked that the cable is connected correctly (any other connection gets a worse result i.e., No O/S!) I have treid this with two old harddisks that should be OK. I also had it with the orginal harddisk which is why I am trying to replace it. Any ideas please? Thanks Nigel |
#14
|
|||
|
|||
Nigel Andrews wrote:
Mart, Thanks for the quick response. I have the slave set to Auto in the BIOS (and of course the jumpers set to Slave on both the replacement) But booting with the ME start-up disk, with one of my replacement old disks installed, it doesn't finish booting (or boots to an A: prompt but says C:, D: etc don't exists!). With the other connected I get to a Minimal Boot, and can start FDISK but it says it can't access disk 2!. I thought both these were working, tho' years ago, and they are similar drives tho' much lower capacity than what they are replacing. Both the drives 'come alive' during the boot sequences (spinning up and heads chattering). Is this showing that they are faulty or is it the format on the disks themselves which is causing the boot problems? Well, as Mart says, it's not WinME that's at fault (so far). Might want to check your cabling as well as the jumper setting on the (presumed) Master drive; bear in mind that if the original drive is CS then the cable is actually different from "normal" M/S IDE cables. Rick Thanks again Nigel "Mart" wrote in message ... First, you need to ascertain whether this is a WinMe issue or - more likely - a hardware issue. Confirm that you can 'see' both physical HDD's in your BIOS. If not, check cabling AND Master/Slave links correctly set. Have you acknowledged (detected and set) a second drive in the BIOS? If OK in BIOS, boot with your WinMe Startup (floppy) disk and confirm that you can 'see' both disks AND their partitions in Real Mode DOS. If so, can you read AND write (in DOS) to all partitions. Confirm the above then worry about WinMe. BTW - What letter(s) is/are assigned to your CD-ROM(s) - if fitted? Mart "Nigel Andrews" wrote in message ... I am having problems with Windows ME when adding in a working old hard disk. After going into 'safe mode' (because I switched off the PC) I get a blue screen 'Windows protection error'. This happens whenever a replacement second harddisk is connected. If I remove it then Windows starts cleanly. I have checked that the cable is connected correctly (any other connection gets a worse result i.e., No O/S!) I have treid this with two old harddisks that should be OK. I also had it with the orginal harddisk which is why I am trying to replace it. Any ideas please? Thanks Nigel |
#15
|
|||
|
|||
My suspicion falls on the size of the 'new' HD's - they may be bigger than
the BIOS of the system can cope with -- Noel Paton (MS-MVP 2002-2005, Windows) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm http://tinyurl.com/6oztj Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "Mart" wrote in message ... Well Nigel, you certainly seem to have proved that WinMe isn't the cause!! Under the circumstances - and that may depend both on how urgently you want/need to replace your D: with a 'good' one and how full your wallet feels - you could cut your losses and buy a new HDD. However, if you want to 'see it through' then examine each of your 'old' drives in turn - by temporarily throwing-off your existing 'good' C: drive. Keep things simple! Make each of your old drives (individually) the C: (master) and FDSK /STATUS each one to ascertain their state - Fdisking and re-formatting if necessary - followed by a Real Mode DOS Scandisk. Then, when you've proved that they are still serviceable - and all is back to normal with your 'original' C: back in place - re-introduce them, one at a time as the D: BTW - Auto *may* not be enough - You *might* have to re-detect them first in the BIOS (there should be 'detect' option available - refer to the User Manual (if you have one!!) Is this showing that they are faulty or is it the format on the disks themselves which is causing the boot problems? Depends upon the results from above tests, but they sure sound 'suspicious' Mart "Nigel Andrews" wrote in message ... Mart, Thanks for the quick response. I have the slave set to Auto in the BIOS (and of course the jumpers set to Slave on both the replacement) But booting with the ME start-up disk, with one of my replacement old disks installed, it doesn't finish booting (or boots to an A: prompt but says C:, D: etc don't exists!). With the other connected I get to a Minimal Boot, and can start FDISK but it says it can't access disk 2!. I thought both these were working, tho' years ago, and they are similar drives tho' much lower capacity than what they are replacing. Both the drives 'come alive' during the boot sequences (spinning up and heads chattering). Is this showing that they are faulty or is it the format on the disks themselves which is causing the boot problems? Thanks again Nigel "Mart" wrote in message ... First, you need to ascertain whether this is a WinMe issue or - more likely - a hardware issue. Confirm that you can 'see' both physical HDD's in your BIOS. If not, check cabling AND Master/Slave links correctly set. Have you acknowledged (detected and set) a second drive in the BIOS? If OK in BIOS, boot with your WinMe Startup (floppy) disk and confirm that you can 'see' both disks AND their partitions in Real Mode DOS. If so, can you read AND write (in DOS) to all partitions. Confirm the above then worry about WinMe. BTW - What letter(s) is/are assigned to your CD-ROM(s) - if fitted? Mart "Nigel Andrews" wrote in message ... I am having problems with Windows ME when adding in a working old hard disk. After going into 'safe mode' (because I switched off the PC) I get a blue screen 'Windows protection error'. This happens whenever a replacement second harddisk is connected. If I remove it then Windows starts cleanly. I have checked that the cable is connected correctly (any other connection gets a worse result i.e., No O/S!) I have treid this with two old harddisks that should be OK. I also had it with the orginal harddisk which is why I am trying to replace it. Any ideas please? Thanks Nigel |
#16
|
|||
|
|||
Mmm...
I thought both these were working, tho' years ago, and they are similar drives tho' **much lower capacity than what they are replacing**. Over to Nigel Mart "Noel Paton" wrote in message ... My suspicion falls on the size of the 'new' HD's - they may be bigger than the BIOS of the system can cope with -- Noel Paton (MS-MVP 2002-2005, Windows) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm http://tinyurl.com/6oztj Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "Mart" wrote in message ... Well Nigel, you certainly seem to have proved that WinMe isn't the cause!! Under the circumstances - and that may depend both on how urgently you want/need to replace your D: with a 'good' one and how full your wallet feels - you could cut your losses and buy a new HDD. However, if you want to 'see it through' then examine each of your 'old' drives in turn - by temporarily throwing-off your existing 'good' C: drive. Keep things simple! Make each of your old drives (individually) the C: (master) and FDSK /STATUS each one to ascertain their state - Fdisking and re-formatting if necessary - followed by a Real Mode DOS Scandisk. Then, when you've proved that they are still serviceable - and all is back to normal with your 'original' C: back in place - re-introduce them, one at a time as the D: BTW - Auto *may* not be enough - You *might* have to re-detect them first in the BIOS (there should be 'detect' option available - refer to the User Manual (if you have one!!) Is this showing that they are faulty or is it the format on the disks themselves which is causing the boot problems? Depends upon the results from above tests, but they sure sound 'suspicious' Mart "Nigel Andrews" wrote in message ... Mart, Thanks for the quick response. I have the slave set to Auto in the BIOS (and of course the jumpers set to Slave on both the replacement) But booting with the ME start-up disk, with one of my replacement old disks installed, it doesn't finish booting (or boots to an A: prompt but says C:, D: etc don't exists!). With the other connected I get to a Minimal Boot, and can start FDISK but it says it can't access disk 2!. I thought both these were working, tho' years ago, and they are similar drives tho' much lower capacity than what they are replacing. Both the drives 'come alive' during the boot sequences (spinning up and heads chattering). Is this showing that they are faulty or is it the format on the disks themselves which is causing the boot problems? Thanks again Nigel "Mart" wrote in message ... First, you need to ascertain whether this is a WinMe issue or - more likely - a hardware issue. Confirm that you can 'see' both physical HDD's in your BIOS. If not, check cabling AND Master/Slave links correctly set. Have you acknowledged (detected and set) a second drive in the BIOS? If OK in BIOS, boot with your WinMe Startup (floppy) disk and confirm that you can 'see' both disks AND their partitions in Real Mode DOS. If so, can you read AND write (in DOS) to all partitions. Confirm the above then worry about WinMe. BTW - What letter(s) is/are assigned to your CD-ROM(s) - if fitted? Mart "Nigel Andrews" wrote in message ... I am having problems with Windows ME when adding in a working old hard disk. After going into 'safe mode' (because I switched off the PC) I get a blue screen 'Windows protection error'. This happens whenever a replacement second harddisk is connected. If I remove it then Windows starts cleanly. I have checked that the cable is connected correctly (any other connection gets a worse result i.e., No O/S!) I have treid this with two old harddisks that should be OK. I also had it with the orginal harddisk which is why I am trying to replace it. Any ideas please? Thanks Nigel |
#17
|
|||
|
|||
Thanks again for all this good advice.
I think I will have to go for a new (small) drive. I didn't really want to as the PC is fairly old and has a few other problems. As this problem is that the programs on the partitions which are now not 'linked' because the drives all stepped down one by letter. I may look to reinstall those to the current drive letters. Although perhaps I should ask if there is any easy way to tell WindowsMe that a programme that was on E: is now on D:? I suspect reinstalling is easiest way. Nigel "Mart" wrote in message ... Mmm... I thought both these were working, tho' years ago, and they are similar drives tho' **much lower capacity than what they are replacing**. Over to Nigel Mart "Noel Paton" wrote in message ... My suspicion falls on the size of the 'new' HD's - they may be bigger than the BIOS of the system can cope with -- Noel Paton (MS-MVP 2002-2005, Windows) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm http://tinyurl.com/6oztj Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "Mart" wrote in message ... Well Nigel, you certainly seem to have proved that WinMe isn't the cause!! Under the circumstances - and that may depend both on how urgently you want/need to replace your D: with a 'good' one and how full your wallet feels - you could cut your losses and buy a new HDD. However, if you want to 'see it through' then examine each of your 'old' drives in turn - by temporarily throwing-off your existing 'good' C: drive. Keep things simple! Make each of your old drives (individually) the C: (master) and FDSK /STATUS each one to ascertain their state - Fdisking and re-formatting if necessary - followed by a Real Mode DOS Scandisk. Then, when you've proved that they are still serviceable - and all is back to normal with your 'original' C: back in place - re-introduce them, one at a time as the D: BTW - Auto *may* not be enough - You *might* have to re-detect them first in the BIOS (there should be 'detect' option available - refer to the User Manual (if you have one!!) Is this showing that they are faulty or is it the format on the disks themselves which is causing the boot problems? Depends upon the results from above tests, but they sure sound 'suspicious' Mart "Nigel Andrews" wrote in message ... Mart, Thanks for the quick response. I have the slave set to Auto in the BIOS (and of course the jumpers set to Slave on both the replacement) But booting with the ME start-up disk, with one of my replacement old disks installed, it doesn't finish booting (or boots to an A: prompt but says C:, D: etc don't exists!). With the other connected I get to a Minimal Boot, and can start FDISK but it says it can't access disk 2!. I thought both these were working, tho' years ago, and they are similar drives tho' much lower capacity than what they are replacing. Both the drives 'come alive' during the boot sequences (spinning up and heads chattering). Is this showing that they are faulty or is it the format on the disks themselves which is causing the boot problems? Thanks again Nigel "Mart" wrote in message ... First, you need to ascertain whether this is a WinMe issue or - more likely - a hardware issue. Confirm that you can 'see' both physical HDD's in your BIOS. If not, check cabling AND Master/Slave links correctly set. Have you acknowledged (detected and set) a second drive in the BIOS? If OK in BIOS, boot with your WinMe Startup (floppy) disk and confirm that you can 'see' both disks AND their partitions in Real Mode DOS. If so, can you read AND write (in DOS) to all partitions. Confirm the above then worry about WinMe. BTW - What letter(s) is/are assigned to your CD-ROM(s) - if fitted? Mart "Nigel Andrews" wrote in message ... I am having problems with Windows ME when adding in a working old hard disk. After going into 'safe mode' (because I switched off the PC) I get a blue screen 'Windows protection error'. This happens whenever a replacement second harddisk is connected. If I remove it then Windows starts cleanly. I have checked that the cable is connected correctly (any other connection gets a worse result i.e., No O/S!) I have treid this with two old harddisks that should be OK. I also had it with the orginal harddisk which is why I am trying to replace it. Any ideas please? Thanks Nigel |
#18
|
|||
|
|||
The newer Powerquest Partition Magic programs, ca. Ver 5 to 8, have a
utility, DriveMapper, which can achieve this rewriting of the registry to redirect the new volume information. Since Powerquest was purchasd by Symantec and no longer exists, these partition manager programs are now inexpensive on the third-party market, i.e., Amazon and eBay, among others. -- Jack E. Martinelli 2002-05 MS MVP for Shell/User / DTS Help us help you: http://www.dts-L.org/goodpost.htm http://www.microsoft.com/athome/secu...t/default.aspx In Memorium: Alex Nichol http://www.microsoft.com/windowsxp/e...ts/nichol.mspx Your cooperation is very appreciated. ------ "Nigel Andrews" wrote in message ... Thanks again for all this good advice. I think I will have to go for a new (small) drive. I didn't really want to as the PC is fairly old and has a few other problems. As this problem is that the programs on the partitions which are now not 'linked' because the drives all stepped down one by letter. I may look to reinstall those to the current drive letters. Although perhaps I should ask if there is any easy way to tell WindowsMe that a programme that was on E: is now on D:? I suspect reinstalling is easiest way. Nigel "Mart" wrote in message ... SNIP |
#19
|
|||
|
|||
Nigel, considering age and expense, you might want to fully explore your two
other old drives first - even if it means a complete FDISK/Format of one of them - anything to get it to be recognised as a 'new' D: drive. You should have sufficient information from all the contributors to this thread to at least try, before you are forced to give-up g You *may* be able to pick up a serviceable, second-hand HDD from your local 'Computer Fair' for next to nothing. However, I would agree with Jack's recent comments as well as his earlier ones at the beginning of the month, should you choose the re-mapping route. Good luck Mart "Jack E Martinelli" wrote in message ... The newer Powerquest Partition Magic programs, ca. Ver 5 to 8, have a utility, DriveMapper, which can achieve this rewriting of the registry to redirect the new volume information. Since Powerquest was purchasd by Symantec and no longer exists, these partition manager programs are now inexpensive on the third-party market, i.e., Amazon and eBay, among others. -- Jack E. Martinelli 2002-05 MS MVP for Shell/User / DTS Help us help you: http://www.dts-L.org/goodpost.htm http://www.microsoft.com/athome/secu...t/default.aspx In Memorium: Alex Nichol http://www.microsoft.com/windowsxp/e...ts/nichol.mspx Your cooperation is very appreciated. ------ "Nigel Andrews" wrote in message ... Thanks again for all this good advice. I think I will have to go for a new (small) drive. I didn't really want to as the PC is fairly old and has a few other problems. As this problem is that the programs on the partitions which are now not 'linked' because the drives all stepped down one by letter. I may look to reinstall those to the current drive letters. Although perhaps I should ask if there is any easy way to tell WindowsMe that a programme that was on E: is now on D:? I suspect reinstalling is easiest way. Nigel "Mart" wrote in message ... SNIP |
#20
|
|||
|
|||
I have taken the easy option - sorry guys!
Jack's suggestion to use PM to change the program and registry entries which referred to the drives, to the correct drives, was the simplest way. I don't have to get another drive and I am not investing anything in an old PC which might fail me in only a few months. Thank-you for ALL your help and advice. It helped me make a decision which I am happy with. Nigel "Mart" wrote in message ... Nigel, considering age and expense, you might want to fully explore your two other old drives first - even if it means a complete FDISK/Format of one of them - anything to get it to be recognised as a 'new' D: drive. You should have sufficient information from all the contributors to this thread to at least try, before you are forced to give-up g You *may* be able to pick up a serviceable, second-hand HDD from your local 'Computer Fair' for next to nothing. However, I would agree with Jack's recent comments as well as his earlier ones at the beginning of the month, should you choose the re-mapping route. Good luck Mart "Jack E Martinelli" wrote in message ... The newer Powerquest Partition Magic programs, ca. Ver 5 to 8, have a utility, DriveMapper, which can achieve this rewriting of the registry to redirect the new volume information. Since Powerquest was purchasd by Symantec and no longer exists, these partition manager programs are now inexpensive on the third-party market, i.e., Amazon and eBay, among others. -- Jack E. Martinelli 2002-05 MS MVP for Shell/User / DTS Help us help you: http://www.dts-L.org/goodpost.htm http://www.microsoft.com/athome/secu...t/default.aspx In Memorium: Alex Nichol http://www.microsoft.com/windowsxp/e...ts/nichol.mspx Your cooperation is very appreciated. ------ "Nigel Andrews" wrote in message ... Thanks again for all this good advice. I think I will have to go for a new (small) drive. I didn't really want to as the PC is fairly old and has a few other problems. As this problem is that the programs on the partitions which are now not 'linked' because the drives all stepped down one by letter. I may look to reinstall those to the current drive letters. Although perhaps I should ask if there is any easy way to tell WindowsMe that a programme that was on E: is now on D:? I suspect reinstalling is easiest way. Nigel "Mart" wrote in message ... SNIP |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Can't make up my mind . . | Ivan | General | 17 | March 31st 05 02:02 AM |
Phantom extra partition - how to cure? | SpamHog | Setup & Installation | 0 | November 15th 04 05:01 PM |
Fixing partition table in extended partition | Wiggy | General | 7 | August 29th 04 06:34 PM |
XP on Fat32x advice ...? | RJK | General | 6 | August 5th 04 02:24 AM |
Replacing the boot drive, w/o reinstalling Windows and the apps? | Bill in Co. | General | 50 | August 1st 04 08:30 PM |