No-format install for UEFI based machines Win8 & MacTel

Message

Ted Dog · #1 Post by **Ted Dog** » Sat 03 Jan 2015, 21:24

a complete package, rEFInd and grub2 ready to run inside zip. includes support security keys for linuxes in secure boot mode, and a txtfile config for standard Grub2 boots BOTH windows 8.1 hardware and Macs and fully configurable to replace grub4dos roll in newer hardware.
Preset for a few versions of puppylinux spins that can be loop booted. IE just a copy of ISO file as is, no disc to burn nor dd scary stuff.
Made to be copied by windows or MacOSX and booted using default EFI mode.

http://smokey01.com/software/utility/uefi.zip
Updated host location March2016 old datahost gave exe which is not right, its a zip file.

after opening, copy to base of a fat formatted usbdrive, then download iso files and copy to same area.

here is what the flashdrive must look like

Code: Select all

drivers
EFI
Fatdog64-631.iso
Fatdog64-700b2.iso
grub.cfg
keys
Shellx64.efi
unicorn-6.2.1.91.iso

=== included grub.cfg === linux formatted text (should/would) change to windows style cr/lf etc next round to allow editing from windows textfile editors..

Code: Select all

insmod png
background_image /fatdog.png
set timeout=10



menuentry "Start Fatdog64-631.iso" {
loopback loop0  (hd0,msdos1)/Fatdog64-631.iso
linux (loop0)/vmlinuz
initrd (loop0)/initrd
}
menuentry "Start Fatdog64-700b2.iso -BETA" {
loopback loop0  (hd0,msdos1)/Fatdog64-700b2.iso
linux (loop0)/vmlinuz
initrd (loop0)/initrd
}

menuentry "Start unicorn-6.2.1.91.iso -BETA VERY SLOW BOOT" {
loopback loop0  (hd0,msdos1)/unicorn-6.2.1.91.iso
linux (loop0)/vmlinuz

}

menuentry "---" { true; }
menuentry "Firmware configuration" {
	fwsetup
}
menuentry "Shutdown" {
	halt
}
menuentry "Reboot" {
	reboot
}

already like it better than non iso file method I have used for months, nicely clean since FatDog64 has same named files inside..[/url]

Ted Dog · #2 Post by **Ted Dog** » Sat 03 Jan 2015, 21:29

more info:

9b005a9187590ca36825f1303f58a25b uefi.zip

Windows formatted (actually used windows

to compress this)

size 2442K

Ted Dog · #3 Post by **Ted Dog** » Sat 03 Jan 2015, 21:32

if the drive does not have a MBR (some do not,) then cut (hd0,msdos1) from grub.cfg (can edit within GRUB2 booting but do it later to grub.cfg after boot, does not change file when done at boot-time)

Ted Dog · #4 Post by **Ted Dog** » Sat 03 Jan 2015, 21:38

Most Win8 boxes did not need any priority changes but if yours does the most common is F12 at earliest boot. other F keys are F2 and F1

MacTel always need to use Alt-M and wait a while it will showup as EFI and the right most harddrive icon. If you can bless it (mac people know what that is ) then it will start without Alt-M

This does support secure boot with FatDog64 keys.

cthisbear · #5 Post by **cthisbear** » Sat 03 Jan 2015, 23:45

With datafilehost always untick >>

>>> Use our download manager and get recommended downloads

Chris.

Ted Dog · #6 Post by **Ted Dog** » Sat 03 Jan 2015, 23:55

good point.. windows is easily spoofed forgot about those issues. linux has me so spoiled.

maybe a nice person with hosting space that would not need to use such a site.. or remember my dang password for my own..

cthisbear · #7 Post by **cthisbear** » Sun 04 Jan 2015, 00:21

datafilehost is still a good site....but that thing is an issue.

Could your download be used to boot another Puppy.

Even 32 bit....after amending the menu.

I see that Uncle Baz....our retired leader...ahem
is releasing a 64 bit ISO.

Quirky April 64-bit coming

http://bkhome.org/news/?viewDetailed=00151

Great to see how enthusiastic he has become reviving his
own creation.

http://bkhome.org/news/?viewDetailed=00149

103 new packages for T2

" My mammoth effort over the last few weeks has been to compile
every package used in Puppy and derivatives, such that a pup
can be built without any PETs except for 'noarch' PETs.

That is, built entirely from binary packages compiled in T2. "

Happy New Year to you both...

Chris.

Ted Dog · #8 Post by **Ted Dog** » Sun 04 Jan 2015, 01:36

Yes the UnicornQuirky is 32bit. All files are read write so add your own. Those where chosen due to ease of boot via ISO file but not limited only to that method. All GRUB2 is there.

sebus · #9 Post by **sebus** » Tue 06 Jan 2015, 20:41

I use Vmware Workstation 11 for UEFI boot testing.

Fatdog64-700b2.iso boot fine directly (in UEFI mode)
All works

With using USB UEFI stick & booting same iso, I do NOT have working mouse/keyboard once FD is loaded

Code: Select all

Kingston DataTraveler 108 USB Device
Disk ID: {7262287D-571D-4DDD-9837-D1F5E7EC1265}
Type   : USB
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : UNAVAILABLE
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 7     E   UEFI         FAT32  Removable   7552 MB  Healthy

Had to omit (hd0,msdos1) to be able to boot

sebus

Ted Dog · #10 Post by **Ted Dog** » Tue 06 Jan 2015, 20:54

sorry now it boots TOO Fast...

need to add waitdev=4 to kernel line so hardware has a chance to stabilize otherwise if its VMware contact M$ For support.

I have to add that line to my super fast server running on the metal..
That is a common issue.. more details on kernel configs check out the help section on the main menu or Fatdog64 homepage in the internet broswer.

Ted Dog · #11 Post by **Ted Dog** » Tue 06 Jan 2015, 21:01

If its occuring in VM and corrected by the waitdev please share that with the developer. We are all under the impression its hardware speed related. If the problem occurs in a VM then its ordering issue and would be nice to have a repeatable way of correcting a loading order problem.

Ted Dog · #12 Post by **Ted Dog** » Tue 06 Jan 2015, 21:27

Here is sample of other Grub entries that you may glean from. These require user to mount the iso and copy what is needed into folders.

Code: Select all

menuentry "Start LxPup64" {
	linux (hd0,msdos1)/LxPup64/vmlinuz
	initrd (hd0,msdos1)/LxPup64/initrd.gz
}
menuentry "Start Fatdog64" {
	linux (hd0,msdos1)/srs/vmlinuz
	initrd (hd0,msdos1)/srs/initrd
}

menuentry "Fatdog64 with savefile in USB device" {
	linux /vmlinuz rootfstype=ramfs waitdev=5
	initrd /initrd
}
menuentry "Fatdog64 with multisession support from DVD" {
	linux /vmlinuz rootfstype=ramfs savefile=direct:multi:sr0
	initrd /initrd
}
menuentry "Fatdog64 with LVM and mdadm support" {
	linux /vmlinuz withlvm withmdadm
	initrd /initrd
}
menuentry "Fatdog64 without savefile" {
	linux /vmlinuz savefile=none
	initrd /initrd
}
menuentry "Fatdog64 without graphical desktop" {
	linux /vmlinuz pfix=nox
	initrd /initrd
}
menuentry "Fatdog64 on low memory machines" {
	linux /vmlinuz rootfstype=ramfs
	initrd /initrd
}


menuentry "---" { true; }
menuentry "For problematic Radeon cards - disable radeon driver" {
	linux /vmlinuz blacklist=radeon 
	initrd /initrd
}
menuentry "For problematic Nvidia cards - disable nouveau driver" {
	linux /vmlinuz blacklist=nouveau 
	initrd /initrd
}

submenu "More options for machines with severe video problems" {
	menuentry "Set video resolution to 640x480" {
		terminal_output console
		set gfxmode=640x480
		set gfxpayload=keep
		terminal_output gfxterm
	}
	menuentry "Set video resolution to 800x600" {
		terminal_output console
		set gfxmode=800x600
		set gfxpayload=keep
		terminal_output gfxterm
	}
	menuentry "Set video resolution to 1024x768" {
		terminal_output console
		set gfxmode=1024x768
		set gfxpayload=keep
		terminal_output gfxterm
	}
	menuentry "List all supported video resolution" {
		videoinfo
		echo "Press Enter to continue ..."
		read
	}
	menuentry "Use video resolution not listed in this menu" {
		echo "Enter video resolution (WxH e.g. 800x600), press Enter to abort."
		read gfxmode
		terminal_output console		
		set gfxpayload=keep
		terminal_output gfxterm	
	}
	menuentry "Start Fatdog64 with the chosen resolution" {
		linux /vmlinuz nomodeset pfix=xorgwizard savefile=none
		initrd /initrd
	}
}

menuentry "---" { true; }
menuentry "Firmware configuration" {
	fwsetup
}
menuentry "Shutdown" {
	halt
}
menuentry "Reboot" {
	reboot
}

Ted Dog · #13 Post by **Ted Dog** » Tue 06 Jan 2015, 21:44

MacTel People you may wish to try
Fatdog64 with multisession support from DVD entry since the Mac HATES to boot from DVD and will spit it out and ignore your request 19 out of 20 tries booting directly from DVD. With Alt-M and a flash drive it will boot every time (slow)
Since Linux does not support read write from OS part of harddrive, that is one of the ways to save and reload data without touching actual OSX.

You can save sessions to the unused EFI, but OSX will nuke it if it has a major update. Apple used to let you control your major updates but Christmas day forced a time of day major update unannounced so now each and every boot your Mac will attempt to communicate to a US government computer to SET TIME

welcome to the NWO!

sebus · #14 Post by **sebus** » Tue 06 Jan 2015, 23:03

Ted Dog wrote:sorry now it boots TOO Fast... need to add waitdev=4 to kernel line so hardware has a chance to stabilize otherwise if its VMware contact M$ For support. I have to add that line to my super fast server running on the metal..
That is a common issue.. more details on kernel configs check out the help section on the main menu or Fatdog64 homepage in the internet broswer.

Well, I won't contact MS about Vmware product.
I won't contact Vmware either, as nobody would bother about iso boot from uefi usb (it is fun, but not really important)

Tried again & it worked fine (in Workstation 11 on another hardware)

But the boot is painfully slow in Workstation 11 (way way slower then boot directly from iso - which is blazing fast)

Volhout · #15 Post by **Volhout** » Sat 10 Jan 2015, 20:59

Hi Ted Dog,

Took a while before I understood what this was all about (this thread I mean) but now I understand, it is really great for trying different pups.
Simply add an iso to the stick, and create a grub entry (copy).

So simple... You can really get any pup to boot on a secure UEFI machine.

Great idea.

gcmartin · #16 Post by **gcmartin** » Sun 11 Jan 2015, 16:39

Am I seeing this correctly? This can be made into an installable to a DVD which boots the desired OS (ISO) that is contained on the DVD. Is that a correct view.

If so, this means a developer would

build and test his PUP into an ISO.
Create the boot manager entry as described herein.
Finalize his PUP into an distributable ISO which contains these 2 items.
Anyone could then boot the DVD containing the PUP on ANY PC, old or new.

Is this a "right-brain" view of the potential being presented?

NICE methods to move PUP into a universal installable arena no matter the PC.

The penalty (although this is very very minor as many of us rarely boot/reboot running PCs - daily or less) is that booting an ISO is bit longer than booting the kernel and sys progs, but, the benefit is way more than the slight penalty on boot.

Please comment on "correctness" in view, please.

Great

Great demonstration

Ted Dog · #17 Post by **Ted Dog** » Sun 11 Jan 2015, 21:12

two items one is yes if development encodes the main sfs files within inrtrd like fatdog64 does or bundles all in one like quirky. Then the loop boot works just moving iso file.
Second. If one or the other is on usb flashdrive, user can boot into either and use it to extract files for more common setups.

So you to answer your question, but my use of iso file method and zip file package was so Windows8 or Mac users can have a method to get a booting environment from WITH IN Windows8 (UEFI ) or Macs (EFI).

If the Fatdog64 developers move to this zip idea then the EFI image 10M size could be eliminated and replace by this. As A more general solution.

Ted Dog · #18 Post by **Ted Dog** » Thu 29 Jan 2015, 21:20

getting ready for new release of UEFI.zip would welcome Input. Adding other distros that allow boot from only self contained filesystems in initrd or kernel all in one Like unicornpup etc. Will have Slitaz support in next roll out and hopefully new April and Fatdog64 if they release new ISOs sometime soon ( expected both to have done so by now

)
Got my servers figure out so have actual host(s) to upload to now.

greengeek · #19 Post by **greengeek** » Sun 15 Feb 2015, 18:00

Ted Dog wrote:http://www.datafilehost.com/d/dc8bb366
after opening copy to base of a fat formatted usbdrive, then download iso files and copy to same area.
.

Hi TedDog, I clicked through to this thread from cthisbear's other thread here regarding "rEFInd" bootloader and had a look at the link you have provided above - when I click on that link it offers me a file called "UEFI" but I couldn't see any explanatory info there about what is actually in the UEFI file. I just wondered if the name could be changed slightly to indicate what is in there...
Does that "UEFI" file contain the rEFInd bootloader? (I didn't download it 'cos I don't have uefi hardware yet, but I'm sure I will be coming back here when my futre hardware requires it and it would be handy to have a bit more clarity about the content...)

cheers!

Ted Dog · #20 Post by **Ted Dog** » Sun 15 Feb 2015, 18:13

yes its a complete package, rEFInd and grub2 ready to run inside zip. Will support security keys for linuxes in secure boot mode, and a txtfile config for standard Grub2 boots BOTH windows 8.1 hardware and Macs and fully configurable to replace grub4dos roll in newer hardware.
Preset for a few versions of puppylinux spins that can be loop booted. IE just a copy of ISO file as is, no disc to burn nor dd scary stuff.
Made to be copied by windows or MacOSX and booted using default EFI mode.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

No-format install for UEFI based machines Win8 & MacTel

No-format install for UEFI based machines Win8 & MacTel

This actually works great

Re: No-format install for UEFI based machines Win8 & MacTel