I like that ideagyro wrote:.
2. Non-uefi boots now use grub4dos to chainload Grub2, rather than directly booting Grub2.
Installing the mbr for grub4dos is a lot simpler than installing the mbr for Grub2.
I'm going to have to look to see how you did it.This is the 'menu.lst':s243a wrote:I like that ideagyro wrote:2. Non-uefi boots now use grub4dos to chainload Grub2, rather than directly booting Grub2.
Installing the mbr for grub4dos is a lot simpler than installing the mbr for Grub2.
Code: Select all
timeout 0
default 0
title grub2
kernel /boot/grub/i386-pc/core.img
You're welcome.01micko wrote:Tested out stickpup and f2stickpup and both seem to work fine in a dev version of slacko I built.
At first they wouldn't boot so I tried to do a debugsave and kept getting errors which was a bit perplexing. It turns out that there is a bug in that script that fails to save the variable $mount_point so the files were copied to '/' which I manually copied over to a drive. That allowed me to debug my issue.. simply unplugging my powered usb hdd fixed that, but I dare say wait4usb needs some attention as I could proceed with boot to functional desktop running ./init manually.
I fixed the debugsave file in woof. See commit 01bae0f so an indirect thanks must go to you for that fix! Thanks
I created a wikka entry for FrugalPup with a very brief explanation and links to your index page and the first page of this thread. Let me know if want anything in that wikka page changed.gyro wrote:I have uploaded "FrugalPup" help pages to http://www.fishprogs.software/puppy/fru ... index.html.
"MOK manager" help page can be viewed at http://www.fishprogs.software/puppy/fru ... p-mok.html.
gyro
I can live with it.01micko wrote:I created a wikka entry for FrugalPup with a very brief explanation and links to your index page and the first page of this thread. Let me know if want anything in that wikka page changed.
I told him about Frugalpup Installer, to make a boot-able USB stick, to run on their UEFI Windows 10 laptops.I am part of a team (20 people as I write -the test/sample bunch- but will become larger if I am successful) of engineers dealing with commissioning and service various systems in the maritime industry. Our company (a big one) manufactures and deilvers all sorts of marine equipment: propulsion, prime movers, generators, switchboards, towing systems, steering machinery, etc. etc.
Together with that kind of hardware we also deliver their relative control systems, nowadays tipically networks of controllers.
The company gives us laptops (state of the art ones actually) as a part of our tools and paraphernalia. On these computre we quite a chunk of SW (proprietary and not) developed originally in Windows environments.
Beside the dedicated SW tools to deal with our "actual" job (we are field engineers after all) we also have the bureucratic crap that the company considers mandatory (backoffice stuff, all rigorously windows based... no sh**t!!). And since nowadays everybody is paranoid, all our laptops HDs are ecnrypted and we are not allowed to have a separate partition with, say... linux for instance.
As it comes, all our new generations of controllers are running on linux (no sh**t... again...), so we found ourselves in a bit of a quandary
Sorry, I'm not sure that I understand exactly what you are getting at.01micko wrote:If I may, I would like to make a suggestion concerning f2stickpup and multiboot support. What if by default, or as an option, the 'puppy' files were installed 2 dirs deep? Without much modification, I'm sure then the 'boot' facility could easily detect whatever pups are installed and modify the appropriate boot files accordingly.
