hcvv:
From working Leap 15.6 on another computer, using SUSE Studio ImageWriter.
I hope that is correct and done correctly.
I have no idea about all these tools, GUI or not) that seem to be able to do it correct when you use the correct options, buttons, etc. Again, it might be correct.
I know that using dd from the file to the device (note: NOT a partition) is correct in any case.
Thus when some tool can do the same thing, it is correct.
What @GrandDixence2 eluded too… Maybe a BIOS update will add features?
@rmatov900 I would suggest sticking with the gpt setup as it offers protected MBR.
I know what that is. I have multiple installations of 16.0 on GPT disks in UEFI PCs. I want to know why malcolmlewis wrote “Then it’s Tumbleweed or Slowroll…” and “No UEFI capabilities”, implying OP cannot install 16.0 because his laptop does not support UEFI, thus, not 16.0, in response to my questions.
@mrmazda for the moment it still supports Legacy grub… A some point it won’t be supported, if the system BIOS upgrade to the 2020 version can be done via DRDOS, that may offer some additional life. Don’t know how graphics performance will be?
Leap 16 support is expected to be as long as SLE 16, 7 or so years give or take, like Leap 15 has been, thus, likely longer than the expected remaining life of a currently “older” laptop. So those statements were, and are, future-proofing wisdom, not requirement.
I feel that my major error was disk cleanup from all partitions and then clean install of openSUSE Leap. Maybe we would not have this discussion if I removed only old operating system partition which was the biggest anyway. I’ll take that as lesson. Laptop is not picky what is on disk as long as it can read partition table, ditto, 15.6 USB stick with msdos works, 16.0 with gpt not.
Now that malcolmlewis mentioned DRDOS, I’ll see what can be done with that, or any free dos I can find. Fingers crossed that small msdos partition with generic MBR code in it will do the trick.
I’ll try Tumbleweed, but I’m out of suitable USB drives at the moment. My workflow was one USB drive is the latest, like 16.0 and another is current version, like 15.6. Now that I looked for 3rd, it came out that the biggest is 2GB ;)))
As mrmazda correctly noticed, idea behind Leap 16.0 was to install system that will last as long as laptop with no maintenance. There are people that can profit from that machine, but are just computer users, not geeks, so 15.6 with short lifespan will not do the job.
@mrmazda could it go during the Leap 16.0 release series… I don’t have a crystal ball 
My reference for future proofing was related to a UEFI capable system, since the OP does not appear to have that capability, it’s all moot. Aside from a potential MBR mitigation by continuing to use a GPT disk rather than a DOS type is the only thing I’d suggest.
Conclusion: My error was deleting everything on hard disk. I should clear only Windows partition.
I installed FreeDOS using their CD. Two partitions: one system the other data. After it was booting on its own (without CD) I ran Leap 15.6 installer. Besides Disk section it was uneventful, boring installation.
In Disk configuration installer complained about not enough space on hard disk start. It showed message that warned me it is unsupported configuration and system may not boot. It asked for at least 256kB, which I did not agree to.
I went trough Guided menu, changed btrfs to ext4, in hope that disk and boot configuration files will be something I can read when I have to. I asked for bigger swap to allow hibernation. I went with full KDE installation which went 2 previous times without glitch, so I took lunch break. Back from lunch I found installed KDE. It was time to check what unsupported installation did. USB drive out, ask KDE to Shutdown computer.
And now suspense 
Luckily, Dell makes firmware (BIOS) run short, and I got GRUB menu on the screen. Check that USB drive did not return to port, just to tease me -no. It booted from hard disk.
This fdisk -l result. It looks strange, but it works.
Disk /dev/sda: 698.64 GiB, 750156374016 bytes, 1465149168 sectors
Disk model: WDC WD7500BPKT-7
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x56d06930
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 63 1024127 1024065 500M 6 FAT16
/dev/sda2 1024128 2048255 1024128 500.1M f W95 Ext'd (LBA)
/dev/sda3 2050048 1449056255 1447006208 690G 83 Linux
/dev/sda4 1449056256 1465149167 16092912 7.7G 82 Linux swap / Solaris
/dev/sda5 1024191 2048255 1024065 500M e W95 FAT16 (LBA)
Partition 1 does not start on physical sector boundary.
Partition 5 does not start on physical sector boundary.
Partition table entries are not in disk order.
As this solved problem I need another one to play with
What that would be?
Thanks everyone for guidance and patience with me.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.