First, I just retried it an other time with a fresh VMware machine. After fdisk, reboot, black screen. I change boot order with F2 in virtual BIOS, then if I choose boot hard disk, a message tells me it boot local hard disk... and get just blinking cursor.
---- Le Fri, 17 Jan 2025 06:42:45 -0500 Bernd Böckmann via Freedos-devel a écrit ---- > > > Am 17.01.2025 um 10:46 schrieb Paul Dufresne via Freedos-devel > > freedos-devel@lists.sourceforge.net>: > > > > Ok, turns out that from there, I could press F2, to access virtual BIOS, > > change boot order to boot from CDROM, then continue installation. > > I guess it could means that in 1.3, the partition was not marked as active > > and now it is? > > The boot loader should have printed a "partition signature != 55AA" message > in that case. However, it did not do this because of a regression in > bootnorm.asm: Fdisk does not add a valid partition signature when creating a partition? (and I realize you are talking of partition signature which is different than MBR signature). You means that is the job of format to add the partition signature? I am confused why VMWare does not load and execute the MBR at the first boot, but after doing fdisk, it thinks that it shoud load and execute it. But thinking about it, I realize that before fdisk, there were no valid MBR signature... after fdisk there is one, so it is indeed BIOS job to launch MBR. Still... I don't see why 1.3 would not write "partition signature != 55AA" after fdisk reboot... and rather boot with CDROM menu. I retested... and after fdisk reboot, Virtual BIOS is configure to boot with Hard Disk before CDROM... but boot CDROM, even if I stop the VM and restart it. 1.3 Does what we want... but as a BIOS why does it not launch valid MBR if present? _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
