VOGONS


First post, by murrayman

User metadata
Rank Member
Rank
Member

Somebody's gonna bust my chops for posting here and indirectly referencing Windows 7 as retro, but extended support ended a couple months ago, so here we go bby~

I have an AMD desktop circa 2010 that has a BIOS-based motherboard. I've had Windows 10 installed on it on a SSD for years, but I recently just added a second SSD and installed Windows 7 on it. As expected, it installed Windows Boot Manager, and while it works fine, it overrides any ability to use the BIOS boot selection screen - meaning if I try to boot directly to one drive or another using the BIOS (either defaults or F12 boot menu), it will jump into Windows Boot Manager regardless. I don't want this, as I'm planning to add a couple other drives with different OSs such as WinXP and Ubuntu, and I don't want any boot manager - not even grub. I just want to use the BIOS.

I've searched around online trying to find a way to literally delete Windows Boot Manager, rather than just hide it or have it default to an OS, but I can't find anything aside from UEFI solutions. Does anyone know how to get rid of this thing?

P3B-F 1.04, PIII 1k, 512MB PC133, GF DDR 32MB + DM3DII 12MB SLI, SB0100
P3B-F 1.03, PIII 700, 384MB PC100, V5 AGP, SB0160
CP 5170, PII 350, 256MB PC100, Rage LT 2MB, ESS 1869
PB M S610, PMMX 233, 128MB EDO66, DM3D 4MB, Aztech

Reply 1 of 3, by Jo22

User metadata
Rank l33t++
Rank
l33t++

Hi, may I ask which Windows you are using (Win 7/10, x86 or x86-64) ?
Also, was Windows installed in UEFI mode (64-Bit) using GPT, or traditionally in BIOS (CSM) mode using MBR ?

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 2 of 3, by murrayman

User metadata
Rank Member
Rank
Member
Jo22 wrote on 2020-04-10, 07:03:

Hi, may I ask which Windows you are using (Win 7/10, x86 or x86-64) ?
Also, was Windows installed in UEFI mode (64-Bit) using GPT, or traditionally in BIOS (CSM) mode using MBR ?

The first OS on the computer is Win10 64bit running on SATA-0. The second and most recent OS installation is Win7 64bit on SATA-1, which is the one that installed Windows Boot Manager. It was installed using MBR partition scheme for BIOS, as my motherboard just predates the widespread adoption of UEFI. I just added a third SSD to use WinXP, but can't access it or anything directly aside from Win7 while the Windows Boot Manager is still around and interfering with the BIOS' ability to direct boot to a drive.

System specs
- Corsair RM850x PSU
- Gigabyte GA-MA785GM-US2H (rev. 3.3)
- AMD Phenom II X6 1100T w/ AMD Wraith MAX
- 8gb (x4 2GB) g.skill F2-8500CL5-2GBPK DDR2 1066 (clock 800, 4-4-4-10 timing, memtest86+ stable @ 24hr)
- XFX Radeon HD 4890 1GB
- SSDs / HDDs (all AHCI)
> SATA-0: Samsung 840 EVO 120gb SSD (Win10 x64)
> SATA-1: Kingston SA400S37240G 240gb SSD(Win7 x64)
>SATA-2: Intel SSDSA2BW080G3H 80gb SSD (WinXP x86, TRIM occasionally)
> SATA-3: Hitachi HDS721010CLA630 1tb HDD (shared non-program files between OSs)
> SATA-4: HP DVD writer 1270t

P3B-F 1.04, PIII 1k, 512MB PC133, GF DDR 32MB + DM3DII 12MB SLI, SB0100
P3B-F 1.03, PIII 700, 384MB PC100, V5 AGP, SB0160
CP 5170, PII 350, 256MB PC100, Rage LT 2MB, ESS 1869
PB M S610, PMMX 233, 128MB EDO66, DM3D 4MB, Aztech

Reply 3 of 3, by murrayman

User metadata
Rank Member
Rank
Member

Was unable to figure it out online or on my own; went ahead and formatted / reinstalled each OS on each drive by having all other drives unplugged during the process. Working perfectly now

P3B-F 1.04, PIII 1k, 512MB PC133, GF DDR 32MB + DM3DII 12MB SLI, SB0100
P3B-F 1.03, PIII 700, 384MB PC100, V5 AGP, SB0160
CP 5170, PII 350, 256MB PC100, Rage LT 2MB, ESS 1869
PB M S610, PMMX 233, 128MB EDO66, DM3D 4MB, Aztech