thisThis is my first post, forgive me if I am in the wrong place or if my post is considered inappropriate.
I have borrowed the idea from numerous Mac user forums, after I added a SSD disk to my Sony VAIO VPCW12J1E, 32bit, dual booting Debian Sid / Windows 7 Starter on standard MBR - no GPT, no EFI, no UEFI.
The netbook is equipped with a heavily mutilated Phoenix BIOS, which lacks the option to set the chipset in AHCI mode (see my post here for example).
With Debian already installed in IDE mode, and initramfs-tools package, it's all quite simple:
With Windows is another story, the previous magic string does not suffice alone and indeed, it prevents the system from seeing the SSD disk - so it does not boot. But I believe the SATA settings mentioned in the official datasheet can be translated into other setpci strings, tailored to a standard PC (as are specifically dedicated the strings and the other solutions spreaded on the WWW and already applied to Macs, I have already tried them on my netbook but to no avail). I can provide whole PCI configuration space of my ICH7-M in IDE and AHCI mode to get a diff (see attachment #2) but I would need a lot of help translating the differences into the right strings.
edit
Following for example post #7 here, I tried with grub4dos, from an MS-DOS floppy (I think I need to set at leasthave a USB floppy drive) with a setpci compiled with DJGPP from here - tracing the SCRAE bit plus enable some ABARs on irq 24various values of the offsets from the linux lspci dump of the ICH7-M put first in IDE mode and so on,then in AHCI mode, but still to no avail:
setpci changes the end passingoffset values as I would like, but not even grub4dos can identify the stringsSSD:
after a few minutes from loading, it ends in the right sequence fromgrub>
console, and then ls (hd0,0)
just hangs (while grub2grub4dos floppy alone with controller stuck in IDE just boots Windows as expected).
PleaseHere is a picture of the diff IDE - AHCI, anyone can help me?and the autoexec commands I issued from DOS.
I move into uncharted territory, and if I have not made mistakes in my attempt, I begin to think that my BIOS mutilations are not workable this way.