I suspect my question may have been overtaken by events. Last night I was trying to implement the lin'n'win system and I seem to have screwed up the disk. GParted now reports the entire SolidState drive as "unallocated"I have now fixed this with a program called gdisk.

In case it is any help I did not see any sign that your Installer made any changes to the BCD file. The command bcdedit /v produced the same result before and after.

I have made progress with the lin'n'win instructions and have got menu options but it is not completely working yet with grub.

In case it is any help I did not see any sign that your Installer made any changes to the BCD file

To confirm, this was after the ISO was installed, not lick itself, correct? (you can have the same effect by going to "file" > "install/uninstall bootloader")

The lin'n'win method doesn't yet actually support UEFI - you probably get an error similar to this.

Anyway, here is the UEFI-compatible instructions that lick more or less performs. You can go through them and see what parts don't work:

Quote:

# disable fast boot in an admin command prompt
powercfg -h off
# mount your UEFI partition as the z:/ drive (note this won't show up in windows explorer, but you can run `Z:` to go to the Z drive):
mountvol z: /S

# Next, open up (or create the text file) C:/lickgrub.cfg, and paste in the contents here.

Now try to reboot, and you should see different screen when you boot (the only thing in it will be Windows, but we can add puppy to it later). If you run into any issues in the process, please post whatever errors you get. If you get through everything and it still doesn't work, post the output of running

Your image seems to be the exact error I was getting with another approach to dual boot. I have tried 4 different ones today so I am a bit confused. With LICK I did not see any menu to allow me to select anything - Win10 just booted as if I had never tried LICK

Yes, I was talking about the absence of changes to the BCD file after the ISO was installed.

I am a bit wary of your suggestion "mount your UEFI partition" - and a bit confused. Win10 itself seems to use 3 partitions and I have added 3 more for Linux. Which partition do you mean? and if it is one of the Win10 partitions will it cause trouble.

Earlier today I came across this Blog entry for UEFI boot
http://blog.puppylinux.com/?viewDetailed=00009
and it seems very simple and nearly works with TahrPup64 (there is a problem with graphics even though the same TahrPup works fine with legacy boot and syslinux). If I can get the graphics working I suspect it would fit well with BCD - now that I think I know how to use BCD Edit.

I will think more about your suggested solution tomorrow - time for bed now.

Thanks again

...RLast edited by Robin2 on Fri 29 Apr 2016, 18:41; edited 1 time in total

Robin2 posted, " With LICK I did not see any menu to allow me to select anything - Win10 just booted as if I had never tried LICK."

Are you aware that when you turn off a Window's 10 computer with its default settings, it doesn't shut-down? Rather, they are factory set to "hibernate" so that they will boot to desktop faster. Ergo, you never get a boot menu.

If you try to legacy boot from a USB stick with it turned on it is very obvious - Puppy reports that it can't mount the Windows partitions.

Thanks again. I will spend more time on this today.

I reckon if I have not figured it out before I go to bed toning I will probably just wipe Win10 completely. But its an interesting excercise and I would like to figure it out.

What I like about the Lin'n'Win system is that the instructions are very transparent. It would be great if there was a similar explanation of what LICK is trying to do. If I understood that I could also review/verify the "output" it produces.

Just a bit of advice. Before you wipe Windows 10 --which works (sort of)-- from your computer, make certain you can run something else. Anything else. If not a Puppy, try Zorin -- a more or less tamed Ubuntu.

As your problem is being able to boot Puppy, being able to boot anything is better than owning a large paper-weight.

I believe any puppy made using woof/woof2/woof-ce will work (as long as there hasn't been major changes to the boot process).

Precise is compatible.

I haven't tried DebianDog, but it may need some manual tweaking - it appears as though there are multiple initrds, while Lick takes a random one. You may need to swap the one with another one, to your liking. Additionally, you might need to modify lickgrub.conf (in the root of C: after installing)

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum