- May 19, 2011
- 20,130
- 14,626
- 136
Ivy Bridge gen board: H61M-USB3V
A customer wants a Windows 11 upgrade on this "unsupported" PC, and I felt that it was time to start using the 24H2 version as 23H2 is only supported until this October. During this upgrade attempt, four things were changed: The machine was configured to run in IDE mode so I switched it to AHCI and sorted out Windows to accept that, the Boot HDD was cloned and replaced with a SSD (so all my upgrade attempts were with the SSD), memory upgrade from 4GB to 8GB RAM (additional module added, memtest86 ran and passed 4 times no errors), and later during my attempts to do the Win11 upgrade I switched the system to UEFI (along with mbr2gpt on the SSD).
Win11 upgrade plans A, B, C and D all failed so I decided to unplug the PC and go back to a spare PC and try my latest idea on there. My latest idea worked, so I intended to start the process all over again on the customer's PC including a drive swap, re-clone the HDD, etc, with an overall plan to have that PC booting from BIOS as it always has done rather than UEFI (my logic being that if a computer has been reliable in a particular mode and there's no compelling reason to change it, and the change could cause problems down the road like I've experienced before with PCs made soon after the change to UEFI, and the change could be easily made later if need be, then if it ain't broke don't fix it).
So this morning I unplugged the SSD from that PC and reconnected the original HDD. I fully expected for it to throw a boot wobbly because MBR vs GPT, but what happened instead was that when the PC powered on, it beeped rapidly so many times that I wouldn't even bother to count it (20 beeps at least, the sort of rapid beep that is similar in tempo to the final beeps of a 'no graphics' beep sequence) then it auto powered down. I disconnected the HDD, switched it on again, it did the same beep sequence and temporarily showed a 'Dual BIOS' screen' I haven't seen before then auto powered off. I then removed the additional memory module and it either booted properly straight away or it did on the second attempt (I *think* it booted straight away, this happened first thing this morning and I wasn't expecting this drama). I then reconnected the HDD, switched from UEFI to BIOS mode and it booted Windows.
Since then I've added the extra memory module, done the clone, booted Windows from SSD, all is well. However, that beep sequence worries me. Any ideas? It's not running the latest BIOS, I *can* do that but I'm not a fan of BIOS updating unnecessarily plus to my knowledge this PC has never done this before so why now.
A customer wants a Windows 11 upgrade on this "unsupported" PC, and I felt that it was time to start using the 24H2 version as 23H2 is only supported until this October. During this upgrade attempt, four things were changed: The machine was configured to run in IDE mode so I switched it to AHCI and sorted out Windows to accept that, the Boot HDD was cloned and replaced with a SSD (so all my upgrade attempts were with the SSD), memory upgrade from 4GB to 8GB RAM (additional module added, memtest86 ran and passed 4 times no errors), and later during my attempts to do the Win11 upgrade I switched the system to UEFI (along with mbr2gpt on the SSD).
Win11 upgrade plans A, B, C and D all failed so I decided to unplug the PC and go back to a spare PC and try my latest idea on there. My latest idea worked, so I intended to start the process all over again on the customer's PC including a drive swap, re-clone the HDD, etc, with an overall plan to have that PC booting from BIOS as it always has done rather than UEFI (my logic being that if a computer has been reliable in a particular mode and there's no compelling reason to change it, and the change could cause problems down the road like I've experienced before with PCs made soon after the change to UEFI, and the change could be easily made later if need be, then if it ain't broke don't fix it).
So this morning I unplugged the SSD from that PC and reconnected the original HDD. I fully expected for it to throw a boot wobbly because MBR vs GPT, but what happened instead was that when the PC powered on, it beeped rapidly so many times that I wouldn't even bother to count it (20 beeps at least, the sort of rapid beep that is similar in tempo to the final beeps of a 'no graphics' beep sequence) then it auto powered down. I disconnected the HDD, switched it on again, it did the same beep sequence and temporarily showed a 'Dual BIOS' screen' I haven't seen before then auto powered off. I then removed the additional memory module and it either booted properly straight away or it did on the second attempt (I *think* it booted straight away, this happened first thing this morning and I wasn't expecting this drama). I then reconnected the HDD, switched from UEFI to BIOS mode and it booted Windows.
Since then I've added the extra memory module, done the clone, booted Windows from SSD, all is well. However, that beep sequence worries me. Any ideas? It's not running the latest BIOS, I *can* do that but I'm not a fan of BIOS updating unnecessarily plus to my knowledge this PC has never done this before so why now.
Facebook
Twitter