jaclaz Posted December 28, 2016 Posted December 28, 2016 5 minutes ago, dencorso said: So: 8.1 to 10 cannot boot from MBR, while XP cannot usually use UEFI. Hmmm. Maybe you need to reword that. Possibly keeping BIOS as counterpart of UEFI and MBR as counterpart of GPT. Last time I checked Windows 8 and 8.1 (cannot say 10) booted from MBR really fine, whilst XP could definitely not boot in UEFI mode and not even from GPT disk on BIOS. jaclaz
dencorso Posted December 28, 2016 Posted December 28, 2016 Yes! And welcome to this thread, jaclaz! Let's say I meant to say: "8.1 to 10 do not install by default in BIOS mode, when UEFI is available, while XP cannot boot in UEFI mode." In fact I don't think I meant to say that, but that's what I should have meant to say, whatever I actually meant to say at that time.
Damnation Posted December 28, 2016 Author Posted December 28, 2016 I'm not sure it's an EFI problem, as the problem will also happen if I return to XP after booting my USB ubuntu, and I set up ubuntu in MBR mode when I installed it. I think I've skipped chainloading, each OS is on it's own drive, their bootloaders only boot themselves, they aren't aware of other OSes If I want to boot a different OS, I press F12 after POST and select the drive I want to boot
dencorso Posted December 28, 2016 Posted December 28, 2016 I see. But... was the 10 SSD physically connected when you installed XP to the other SSD?
Damnation Posted December 28, 2016 Author Posted December 28, 2016 I disconnected it whilst installing it, as it overwrote my win10 bootloader the 1st time i installed when i'd left it connected
Damnation Posted December 29, 2016 Author Posted December 29, 2016 Dibya, you mentioned earlier that you had a friend with the same motherboard as me that has XP installed, can you ask them how they did it?
Dibya Posted December 29, 2016 Posted December 29, 2016 7 hours ago, Damnation said: Dibya, you mentioned earlier that you had a friend with the same motherboard as me that has XP installed, can you ask them how they did it? I only installed it there for her with onepiece update pack and Ahci driver by Fernado.
Damnation Posted December 29, 2016 Author Posted December 29, 2016 1 hour ago, Dibya said: I only installed it there for her with onepiece update pack and Ahci driver by Fernado. OK Thanks, I'll try this out is nlite OK to integrate? or should i use something else?
Dibya Posted December 29, 2016 Posted December 29, 2016 37 minutes ago, Damnation said: OK Thanks, I'll try this out is nlite OK to integrate? or should i use something else? NLITE is okay . I use nlite only . I donot know what really happening with you . If it does not solve go for your f12 meth-ode. BEST OF LUCK Remember to test your iso made by nlite in vm before installation .
Damnation Posted December 31, 2016 Author Posted December 31, 2016 OK, I integrated the update pack and AHCI drivers into my install the install worked in a VM, but on my actual hardware it got stuck in a BSOD loop on the 3rd reboot, just after the EULA and the license key phase The BSODs disappear too quickly that I can't see the error code, any way I can make it not reboot on BSOD?
jaclaz Posted December 31, 2016 Posted December 31, 2016 24 minutes ago, Damnation said: OK, I integrated the update pack and AHCI drivers into my install the install worked in a VM, but on my actual hardware it got stuck in a BSOD loop on the 3rd reboot, just after the EULA and the license key phase The BSODs disappear too quickly that I can't see the error code, any way I can make it not reboot on BSOD? disable automatic rebooting via F8 when booting: jaclaz
Damnation Posted December 31, 2016 Author Posted December 31, 2016 It's a 7B, that's AHCI right? damnit, I thought I'd integrated the drivers correctly
jaclaz Posted December 31, 2016 Posted December 31, 2016 (edited) 1 hour ago, Damnation said: It's a 7B, that's AHCI right? damnit, I thought I'd integrated the drivers correctly Yep, it is "inaccessible boot device", in your case it does mean a mismatch between hardware and (SATA or AHCI) drivers or a "bad" installations of those drivers. But don't you have a "IDE compatibility mode" in your BIOS? (only to temporarily check if the rest is OK, then you may reinstall with the "right" drivers or manually add them) jaclaz Edited December 31, 2016 by jaclaz
Dibya Posted December 31, 2016 Posted December 31, 2016 2 hours ago, Damnation said: It's a 7B, that's AHCI right? damnit, I thought I'd integrated the drivers correctly If you are using fernados moded driver intrigate only the dev id listed in IN iDE/ATA section of device manager Best of LUcK. do you using pae patch for ram ? Then remember to replace hidparse.sys with server 2003 one.
Damnation Posted January 3, 2017 Author Posted January 3, 2017 Hi again, Some progress, Integrated onepiece update pack and intel AHCI driver no more 7B BSOD, but nothing is actually installed on next boot, no control panel or anything Do I need to make a modification to my XP CD for install off a USB CDROM drive?
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now