YaPI (yet another Puppy Installer) install any Puppy iso

[bigpup]

This Pmount is not a pet-package as we are now in the 'Cutting edge' section - not 'Additional software'.

this version is also not a pet.

I disagree with the idea of not posting, as a pet-package, just because it is in the 'Cutting edge' section' of the forum.

AS we have already proven. Testing the final version, as a pet-package, also can find problems with the program.
A pet-package is also easier for people to use and help with testing.

In early stages of coding the program. I agree a pet-package is not the way to offer a program for testing and code tweaking. But when it looks like a good working program. Next step is to see how it works as a pet-package.

[L18L]

Is this where you wanted YaPI to do the shutdown?
After hitting OK here?
see image below.

It goes back to select a drive.
It does the shutdown after you select another drive.

Yes.
Exactly there.
You found another bug.
Fix it by deleting line number 721 which is:

Code: Select all

chooseDEVICE

. Feel free to create a pet.

[bigpup]

YaPI pet package with minor bug fixes.
Final release.

Made pet package in Precise 5.7.1
It seems to be able to install in any Puppy series 5 or newer.
So, should work in a lot of Puppy versions.

Some older Puppies will not offer SuperFloppy install option or have the refresh button in the iso list. They have too old a xdialog and not the proper SuperFloppy support files.
Frugal and full installs should work.

The pet will put YaPI menu entry in Setup.
The menu entry may not work in very old Puppy series 5 versions. However, run yapi from the console should work.
yapi file is in /usr/sbin

All install options should work, in the latest Puppy versions, made with Woof-CE.
Options:
Frugal
Full
SuperFloppy
Right click on iso file and select "open with.... yapi"

[bigpup]

Feel free to create a pet.

I did

This is not YaPI's problem, but is Tahrpup.
I am still trying to find the reason Tahrpup 6.0.5 (32 bit version) will not offer to do a SuperFloppy install.
It has something to do with the needed files for this code:

Code: Select all

# test and make make isohybrid
 [ "$(test_isohybrid)" = "hybr" ] || { isohybrid ${chosenISO} 2>/dev/null ; sync ; } #160303

It works in these Puppies:
Slacko 6.3.0
Slacko64 6.3.0
Tahrpup64 6.0.5 (64 bit version)

They all seem to have their own versions of the isohybrid needed files.
I have tried using different isohybrid files in Tahrpup 6.0.5 (32bit). Well, the ones from Slacko 6.3.0.
No help.

Could usr/bin/mkhybrid be involved in this?
If yes.
That is another mess of each version of Puppy having their own version of mkhybrid

Anyone got any ideas?

[L18L]

I am still trying to find the reason Tahrpup 6.0.5 (32 bit version) will not offer to do a SuperFloppy install.
It has something to do with the needed files for this code:

Code: Select all

# test and make make isohybrid
 [ "$(test_isohybrid)" = "hybr" ] || { isohybrid ${chosenISO} 2>/dev/null ; sync ; } #160303

Sorry, this code is faulty.
- The function test_hybrid needs an argument.(= ${chosenISO})
- Without argument the result of this function can never become "hybr"
- Thus isohybrid is always launched
- If it is not on the system (executable ELF) then the iso never gets converted
- Does no harm if it is already a hybrid iso
- Does no harm if it is not a hybrid iso.
- Not being installed as Superfloppy does no harm.
Just my humble opinion.

[bigpup]

Any input on this maybe offered as a replacement for the Puppy Universal Installer?

[B.K. Johnson]

@bigpup
Yapi did not work out for me when installing to USB flash drive, so I put it aside with the intent to return. I am back. Again it did not work, but I won't give any details as it was run from my hybrid tahr-6.0.2~6.0.5. I'll run it from another puppy and report if unsuccessful.

However, since you were very involv4d in the dialogs for YaPi, I am directing these comments about the texts in the dialog boxes to you for rewrite and clarification.

The dialogbox shown in Yapi_scrn-1 is confusing with 'this' and 'any'
Simply, the 2 options to install from are:

• the puppy now running
  any puppy.iso, wherever it is stored.

see the suggested changes in red.

Yapi_scrn_2
I don't understand what is being stated in the first sentence.
But foolishly, I am going to take a stab at restructuring the sentence and ask you to insert your understanding at the appropriate place (...). [I can't rewrite what I don't understand].

In the last sentence beginning with 'Or use a USB stick', the use of 'or' suggests it is an alternative. What is the stick an alternative to? A hard drive?
And, 'completely formatted' is redundant; I don't think we can partially format a drive.

Yapi normally creates a FAT32 formatted partition. If you want to ...., then create at least one Linux formatted partition. If you use a USB stick, it will be reformatted (so also a hard drive).

[bigpup]

The dialogbox shown in Yapi_scrn-1 is confusing with 'this' and 'any'
Simply, the 2 options to install from are:

the puppy now running
any puppy.iso, wherever it is stored.

The first statement line changes to match the Puppy version you are running Yapi in.
It actually states the Puppy version name.
This makes sure you understand what version of Puppy you are choosing to install.
So, I am not going to change that.

[bigpup]

Yapi_scrn_2
I don't understand what is being stated in the first sentence.
But foolishly, I am going to take a stab at restructuring the sentence and ask you to insert your understanding at the appropriate place (...). [I can't rewrite what I don't understand]. Wink

In the last sentence beginning with 'Or use a USB stick', the use of 'or' suggests it is an alternative. What is the stick an alternative to? A hard drive?
And, 'completely formatted' is redundant; I don't think we can partially format a drive.

I can see your confusion.

I will work on that one.

Thanks for input!

[sc0ttman]

Great idea... Easy way to install different ISOs,

Here is an example of my take on it:

NOTE this is not used, tested or intended to be complete!!
It is just an example.

USE AT YOUR OWN RISK

Modify as you need, the drive selection probably needs updating ...

It uses only the dd method, you need a BLANK drive to use!!

It does no safety checks on your drive, it DOES NOT confirm before install

This is just 'in theory'.. You would be the first to actually test and use it, I don't have any spare USBs to test..

If your house blows up don't blame me...

Code: Select all

#!/bin/sh

# install a puppy iso to a disk device
# just an example, not a real app

set -a 

go(){
	# check if ISO file
	[ "`file "$ISO_FILE" | grep 'CD-ROM filesystem'`" = '' ] && Xdialog --msgbox "Choose a valid ISO file.." 0 0 && exit 1
	
	
	# make sure file exists
	[ ! -f "$ISO_FILE" ] && Xdialog --msgbox "File does not exist" 0 0 && echo 1
	
	# make Hybrid ISO if needed
	[ "`file "$ISO_FILE" | grep 'bootable'`" = '' ] && echo "Converting to Hybrid ISO..." && isohybrid "$ISO_FILE"
	
	# error if not a hybrid ISO 
	[ $? -eq 1 ] && Xdialog --msgbox "Error, cannot make '$ISO_FILE' into a Hybrid ISO" 0 0 && exit 1
	
	# unmount the chosen device before we install to it!
	umount "/dev/$DEVICE" 2>/dev/null
	
	# exit if we didn't unmount ok
	[ $? -eq 1 ] && Xdialog --msgbox "Error. Check device '$DEVICE' exists and is NOT mounted." 0 0 && exit 1
	
	# flag
	done=false
	
	echo "Installing '$ISO_FILE' to '$DEVICE ... '"
	
	# do the install and mark $done as true, then sync
	dd bs=4M if="$ISO_FILE" of="/dev/$DEVICE" && done=true && sync
	
	# print final message
	if [ "$done" = true ];then
		Xdialog --msgbox "Success: Installed `basename "$ISO_FILE"` to /dev/$DEVICE" 0 0
	else 
		Xdialog --msgbox "Error: `basename "$ISO_FILE"` not installed! Something went wrong!" 0 0 
		exit 1
	fi

}
export -f go

# get list of devices to install to
make_device_list (){
	for x in `ls -1 /dev/ | grep -E '^sd|^hd' | grep [0-9] | tr '\n' ' ' `
	 do
		DEVICES_LIST="$DEVICES_LIST<item>$x</item>"
	done
	DEVICES_LIST="<list><variable>DEVICE</variable>
$DEVICES_LIST
</list>"
}
export -f make_device_list

make_device_list

gui='
<window title="ISO Installer">
<vbox>
	<frame>
		<text><label>"Choose the ISO to install"</label></text>
		<hbox>
		  <entry accept="filename">
			<label>Select an ISO file</label>
			<variable>ISO_FILE</variable>
		  </entry>
		  <button>
			<input file stock="gtk-open"></input>
			<variable>BROWSE_ISO</variable>
			<action type="fileselect">ISO_FILE</action>
		  </button>
		</hbox>
	</frame>
	<frame>
		<text><label>"Choose the device to install to"</label></text>
		<hbox>
		  '$DEVICES_LIST'
		</hbox>
	</frame>
	<frame>
      <button>
        <label>"GO"</label>
        <input file stock="gtk-ok"></input>
        <variable>GO</variable>
        <action>go $ISO_FILE $DEVICE</action>
      </button>
	</frame>
</vbox>
</window>'

gtkdialog -s <<< "$gui" 2>/dev/null 

[B.K. Johnson]

bigpup wrote:

The first statement line changes to match the Puppy version you are running Yapi in.
<snip>
So, I am not going to change that.

my original post used: from the puppy now running. You want to show the name of the o/s running. That name must be held in a variable, so just restructure to from puppy [var] now running.

What was bothersome was 'this" and 'any' followed by a space then text which made the dialogbox look amateurish. 'this' is a yapi command parameter; I can't see the need for it in the GUI. That said, change or not is up to you.

BFN

[B.K. Johnson]

@bigpup
I think this is the right place for this report, rather than elsewhere.

As stated in an earlier post, yapi running with tahr_6.0.2~6.0.5 failed. It failed on a second trial.

Using a 'cobbled' tahr-6.0.6, I launched yapi from Menu>Setup. Since I am running from tahr-6.0.6 and installing a tahr-6.0.6, at the third screen, I selected the first option,( i.e. installing from a running puppy) and clicked OK. It failed. A dialogbox advised that it was searching then a subsequent box displayed "Usage of Xdialog" script.

I launched yapi again from Menu>Setup. This time I selected the second option: From a puppy.iso wherever it is located. Yapi reported (a) searching for isos on mounted storage (b) please wait (c) Xdialog help - Usage for Xdialog. On my closing "Usage for Xdialog", a new dialog box advised - Chosen ISO not found ... Another failure!
Chosen ISO ???? I did not choose any ISO. A dialogbox for inserting the name of an ISO or for selection was never presented.
No iso was found. Ridiculous! A search with pfind-6.3 for *.iso returned 29 instances.

There are 2 things I noted as possible reasons for the failures:

• * The iso name in storage is tahr-6.0.6-uefi.iso and is possibly different from the running tahr-6.0.6.
  * The ISO is on my Windows drive and located 5 levels deep.

After 4 mistrials with the GUI, I tried the command line.

Code: Select all

root# cd "/mnt/sda1/Documents and Settings/user/My Documents/Downloads/PUPPIES/tahr-6.0.6/"
root# yapi tahr-6.0.6-uefi.iso sdc1

I got an error because I used sdc1 (probably should have been sdc)
Ultimately, tahr-6.0.6 was successfully installed. A single FAT32 partition.

Yapi literally forces one to use Grub4Dos. I don't usually use it as my bootloader, but in the interest of getting the installation done ASAP, i followed the program.

Summary
Yapi (GUI) failed to find any of 29 ISOs on my system. This may be due to either a defective/ineffective search function or its inability to search sufficient levels deep.
Yapi (CLI) successfully installed tahr-6.0.6 to a flash drive. The drive had one formatted FAT32 partition.
Yapi uses the Grub4Dos bootloader exclusively. The YaPI instructions advise that you will have to install a bootloader, but tells only how to use Grub4Dos. Syslinux is completely ignored.

It works! I much prefer the finished product than that produced by isobooter. However, the graphics need some polish to make it look more professional.

screenie of the installed tahr-6.0.6-uefi enclosed.

[bigpup]

* The ISO is on my Windows drive and located 5 levels deep.

Searching Windows folders has been an issue.
Slow and all the layers of folders in Windows.

In fact, when searching Windows locations. Yapi will seem to stop working, because it can take so long.

Exactly where are your iso's?

/sda1/Documents and Settings/user/My Documents/Downloads/PUPPIES/tahr-6.0.6/

That is a lot of layers to search.

A dialogbox advised that it was searching then a subsequent box displayed "Usage of Xdialog" script.

More details please.
Not understanding this "Usage of Xdialog" script.

Using a 'cobbled' tahr-6.0.6

So, this is not an official version of Tahr-6.0.6?
That could be a problem.
Also, not totally sure Tahr 6.0.6 is totally bug free, yet.

Why only Grub4dos boot loader?
Way not.
It works.
Offers other boot options in menu.
Can boot more than one installed Puppy on the same storage device.

Superfloppy is for a single Puppy on a single USB flash drive.
Only that Puppy will be on drive.
Basically a live Puppy install.

[bigpup]

After 4 mistrials with the GUI, I tried the command line.
Code:
root# cd "/mnt/sda1/Documents and Settings/user/My Documents/Downloads/PUPPIES/tahr-6.0.6/"
root# yapi tahr-6.0.6-uefi.iso sdc1

You basically went directly to the iso.

Yapi can do that from the file manager.
Navigate to the iso.
Right click on it.
Select run with..... or send to.......
Select yapi.

[bigpup]

Let me add.

L18L did all the coding on Yapi and only he understands totally what he did.

Any good coder want to tweak it??

[bigpup]

B.K. Johnson.

Just to see what happens.
Could you put some iso's in a folder just on the partition Windows is on.

Do a Yapi search and see what it finds.

Also, the partition has had a Windows defrag and chkdsk run on it recently?

[B.K. Johnson]

bigpup wrote:

Just to see what happens.
Could you put some iso's in a folder just on the partition Windows is on.

That is where all my ISOs are. The drive is a single partition with Windows as drive C:.
This is the path to tahr-6.0.6-uefi on the partition:

Code: Select all

/mnt/sda1/Documents and Settings/user/My Documents/Downloads/PUPPIES/tahr-6.0.6/tahr-6.0.6-uefi.iso

I do not have a directory of iso's. Each ISO is in a direcyory along with associated files.

Do a Yapi search and see what it finds.

I would set up a temporary directory with a couple iso's but I don't know how to do a yapi search. When I first saw your message, I was in tahr-6.0.2~6.0.5. I typed yapi -h in the console but one of the installation dialogboxes opens up and went through the entire sequence of dialogboxes.
I rebooted into tahr-6.0.6-uefi and got the same result. Send the command string

Also, the partition has had a Windows defrag and chkdsk run on it recently?

Not recently. I haven't logged into Windows to do anything in over a year, I only end up in Windows if my flash drive does not boot for some reason. However, almost everything I save goes on that drive and it is nearly full. In line with your thinking, I need to transfer some of the files from the drive to free up some space. I'll then defrag the drive,

[bigpup]

What I am saying is to put a iso in a directory(folder) just on the partition.
Run Yapi normally.
No special commands.
When you get to the window to choose what to install.
Select "any other Puppy.iso from all storage locations".
See if it finds any iso's.

Example:
The partition is sda1.
Make a directory named "puppy" on partition sda1.
Put an iso in directory puppy.
the search would only have to look in

Code: Select all

/mnt/sda1/puppy

I need to transfer some of the files from the drive to free up some space. I'll then defrag the drive,

Depending on how fragmented the drive is, you could have problems getting a good file transfer.
I would defrag first and then transfer files.
Again, it depends on how bad drive is fragmented.

Your placement of Puppy installs and iso's is not really the best.
Think about it.

Code: Select all

/mnt/sda1/Documents and Settings/user/My Documents/Downloads/PUPPIES/tahr-6.0.6/

That is a lot of directories(folders), to drill down through(my term), just to get to Puppy files and programs.
Any time Puppy needs to go back to the drive to get something. It has to take time to drill down again through all that.

All my Puppy installs are just on a partition.
Example:
/mnt/sda1/xenialpup647085uefi
(Xenialpup64 7.0.8.5 uefi in directory xenialpup647085uefi).

[B.K. Johnson]

@bigpup
I moved files to an external drive until the Windows drive was 19% free.
booted to Windows and defragged the drive. The largest defragmented file that remained was System Volume Information.

Booted into tahr-6.0.6 with the cobbled installation.
Created a ISOs directory to /root and copied 2 puppy iso's to it.
There wasn't a Yapi desktop entry in the Menu>Setup (or any sub category) when I looked. 'which yapi' at the console showed yapi installed to /usr/sbin/ and a /usr/share/applications/yapi.desktop existed with good data.
Menu>Setup>Menu Manager had yapi listed, so I closed the dialogbox. Yapi now appeared in the menu.

I launched yapi. The welcome screen, then the screen describing the options (frugal etc), then advice that the search began.

That lingered for quite a while, eventually making way for the Usage of Xdialog script.

On closing the screen, a small dialogbox appeared momentarily ... disappeared too fast for me to read.
Then the box informing that the chosen iso was not found appeared.
I clicked OK to end the FAILED session.

[B.K. Johnson]

@bigpup
[episode after defrag-chapter 2]

cd to /root/ISOs
at console yapi
Got the screens I have come to expect, but i got a new one after closing the Usage for Xdialog (screenie).
The strangest thing is that although I had selected the 2nd item on the menu, the message
"No isos for this tahr 6.0.6 ..."
It seems that somehow yapi is selecting "this", the first option. Secondly, tahr 6.0.6 may be the name within the running puppy, but the on disk puppy is tahr-6.0.6-uefi.
[UPDATE]
I just saw that the screen output when I launched yapi from the console shows errors - screenie = error_@console.
This suggests that I may have a defective version of yapi. So I am retrieving a new copy of the pet. I'll install after comparing.