YaPI (yet another Puppy Installer) install any Puppy iso

Under development: PCMCIA, wireless, etc.
Message
Author
User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#441 Post by bigpup »

Let's hope that is it.
A bad install of Yapi!

Thanks for the test!!!


I am not sure why yapi is doing this for you.

Make sure you are getting the yapi pet marked final release from the link in the first post.
Booted into tahr-6.0.6 with the cobbled installation.
Sure this is good and got all the normal support files/programs of a normal Puppy?

This is yapi running in Tahrpup64 6.0.6 with 32bit compatibility sfs loaded.
The search had to search 4drives with Windows 10 on two of them.
My results:
Attachments
capture21661.jpg
(11.44 KiB) Downloaded 184 times
capture21197.jpg
(135.52 KiB) Downloaded 168 times
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

#442 Post by B.K. Johnson »

Strange!!!
In an earlier post, I noted that YaPI in the cobbled 6.0.6 did not appear in Menu>Setup, but OK in other places.
Now I find that it isn't listed in the Uninstalled in PPM, so I am going to install over what exists. I did and it still is not listed among "Uninstall"

Running the new YaPI has essentially the same results. But launching from console selecting "any" gave the error shown in screenie=error_with_new_yapi. YaPI can't even find an ISO "under its nose".



Now, from the console, I'll cd to /root/ISOs then launch yapi like this:

Code: Select all

yapi tahr-6.0.6-uefi.iso 
. This was successful before.
...
It did not produce a populated drive despite what seemed to be all the correct dialogs. Scapping that proc.

I am back to using the tahr-6.0.2~6.0.5
No suprise that YaPI launched from Menu failed as before.
YaPI does not appear in PPM/Uninstalled. I seem to recall that it should. How else does one uninstall it? This looks like a badly created pet.

cd to /mnt/sda1/ISOs/
launched YaPI tahr-6.0.6-uefi.iso
all the correct dialogs seemed to appear including screenie=where2install-2

And results in a properly operating tahr-6.0.6 on flash drive.


Here is the console page of my successful install using tahr-6.02~6.0.5 and yapi command with iso parm

Code: Select all

root# yapi tahr-6.0.6-uefi.iso
ISO to be installed is: tahr-6.0.6-uefi.iso. SIZE is 243.

 Select WHERE to install to.
Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it which
could be identified for example by the help of the 'fuser' command.
/usr/sbin/yapi: line 472: [: /tmp/PUI/ISOBOOTER_sda: binary operator expected
chosenPARTITION=sdc1
cp: omitting directory ‘/tmp/PUI/ISO/help’
BINSTALLER=bootlace.com
80.0GB
8006MB
16.0GB
sdc|16GB_General_UDisk_
sda|80GB_ATA_SAMSUNG_HD082GJ_
sdb|7.8GB_KingstonDT_101_G2_
sdc|16GB_General_UDisk_
/usr/sbin/grub4dosconfig: line 739: 10505 Terminated              $GTKDIALOG -p DIALOG -c &> /dev/null
PCPARTS:
/dev/sdc1|vfat|15667200

LPART:/dev/sdc1|vfat|15667200
MYPUPPY=sdb1/tahr602/puppy_tahr_6.0.2.sfs
sdc1/tahr606uefi/puppy_tahr_6.0.6.sfs,initrd.gz|puppy_tahr_6.0.6



sdc1/tahr606uefi/puppy_tahr_6.0.6.sfs|puppy_tahr_6.0.6

1:0:3
/usr/sbin/grub4dosconfig: line 1353: 11547 Terminated              $GTKDIALOG -p DIALOG -c &> /dev/null
sdc1/tahr606uefi/puppy_tahr_6.0.6.sfs,initrd.gz|puppy_tahr_6.0.6
:Windows:
/dev/sdc Bootalbe: yes, yes
/usr/sbin/grub4dosconfig: line 2079: 13164 Terminated              $GTKDIALOG -p DIALOG -c &> /dev/null
head: cannot open ‘/tmp/PUI/PUIfrom’ for reading: No such file or directory
root# 

I am coming to some conclusions:
  • * The problem is my hardware configuration.
    * There may be something wrong with my flash drive with the "cobbled" tahr-6.0.6.
    * Since you can't duplicate my experience, then there is a conflict between the GUI, the search function and my hardware.
System-wide search
I think I've said this before: searching the entire system is not appropriate. If the system has multiple drives and/or large drives, it will take a very long time to find the target - a waste of time. I submit that most if not all of us keep our ISOs in some known location; there's no need for a system-wide search. The user will normally know which ISO s(he) wants to install. Why not let the user navigate via a browse button and related code to the known location. Having a system-wide search function here is "finding work for a tool" demonstration.

It seems to me that search is appropriate when you don't know where the target is. Furthermore, I can't conceive that the user does not know the exact ISO s(he) wants to "burn". It is better IMHO to provide the means to navigate to the known location where ISOs are kept. But if there is an odd set of circumstances that warrant a system-wide search, the user can use pFind before using YaPI. Alternatively, the developer could provide both the ability to browse to a known place plus an independent "Search for ISOs" button for those odd cases. It is bad design to force all to use the system-wide search.

Another example of bad design is that once you begin the process, there is no way of backing out. Neither "Cancel" or "X" on the task-bar allows you to quit.

Trying yapi with -h or --help does not provide a help screen. Instead, yapi is launched. YaPI has no escape route once it starts - another poor design decision. YaPI does not make an entry in PPM/Uninstall. Hence, it does not provide the standard way to easily delete a properly created pet.
Your placement of Puppy installs and iso's is not really the best.
snip
All my Puppy installs are just on a partition.
Example:
/mnt/sda1/xenialpup647085uefi
The argument that I have my ISOs too deep in a path is a specious one. Where you choose to place your ISOs or I, mine should not affect the efficacy of the search, even if there needs to be one. One should not design software solely on one's likes, environment or how the developer uses it.



Bye to YaPI GUI
These unsuccessful trials using YaPI from the Menu and from the console without an iso as a parameter, mark the end of my contribution. What has given me success is cd to where the target iso is, then yapi with the named iso. I'll use this procedure until there is a complete rewrite of YaPI.

Thanks for staying with me through this ordeal. Unfortunately, nobody else is interested.

Adios amigo!
Attachments
where2install-2.png
List of devices where O/S can be installed
(22.08 KiB) Downloaded 126 times
error_with_new_yapi.png
error with new YaPI
(13.37 KiB) Downloaded 132 times
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]

B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

#443 Post by B.K. Johnson »

My tahr-6.0.6 (via yapi tahr-6.0.6-uefi at console) was up and running for 14 hours yesterday before my wireless mouse froze (battery). And this morning, it has been running for nearly 4 hours.

I downloaded and manually installed Firefox 55.0.3 and Seamonkey 2.48, downloaded & installed cursor themes, emelfm2, pFind 1.3 and apulse, set up LibreOffice from my repository; pup-event to prompt for save at shutdown. The only negativity is that I haven't got apulse to work, but in all fairness, I did not spend much time with it and had not used it before.
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#444 Post by bigpup »

in the cobbled 6.0.6
You never explained what that was.
Sounds to me like a not normal Tahrpup 6.0.6.

My tahr-6.0.6 (via yapi tahr-6.0.6-uefi at console).
This should be a clean install of Tahrpup 6.0.6 even with the stuff you added to it.

Install yapi in it.
It should have:
yapi listed in the uninstall section of PPM.
menu >Setup >yapi in the menu.
(yapi will be the last item in Setup. I have had so many things added to the setup section of the menu, that I had to scroll the setup section to see yapi)

Try running yapi.
Maybe the yapi search will work better for you.

I can not duplicate the problems you are seeing running yapi in a fresh clean install of Tahrpup64 6.0.6 or Tahrpup 6.0.6.

However, I do not have iso's 5 layers deep in a Windows file system and having to use a Linux program ntfs-3g to access and read stuff located there.
All my iso's are in directories or Windows folders one layer deep. Basically a directory or folder just on the partition.

yapi should definitely have no problems installed to Tahrpup 6.0.5.
It was developed running in Tahrpup 6.0.5
Last edited by bigpup on Tue 29 Aug 2017, 12:53, edited 3 times in total.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#445 Post by bigpup »

Trying yapi with -h or --help does not provide a help screen.
yapi is not a terminal (console) program, so it is not going to have terminal command options.
No -h or --help, because nothing to put in it.

All the needed help is built into the yapi windows. There is a help button, you push, in the windows that need one.
Why not let the user navigate via a browse button and related code to the known location.
The biggest reason not to have this, was the location had to be already mounted to work.
A browse option will not mount a location.
It will only browse mounted locations.

A search can mount and unmount and search automatically.

A browse window is manual selection by navigating to locations. Again it will only see already mounted locations.

The help screen, if you hit the help button on the window for selecting what to install.
Explains going directly to the iso.

I guess I could add an explanation of how to navigate in Rox and how to mount a location to navigate to it.

Why in a help screen. Because this is not a normal way of using yapi. It is an alternate way.
Attachments
capture959.png
(7.37 KiB) Downloaded 118 times
Last edited by bigpup on Tue 29 Aug 2017, 12:35, edited 1 time in total.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#446 Post by bigpup »

Cancel button in every window.
Well, I guess there could be.
At present time, the cancel button is in the locations that seemed to be a point at which you would want to choose to cancel.

By navigating to the iso and running yapi.
You are not seeing all the normal windows.
This bypasses some of the selection screens.

You can always just kill the window, at anytime, by clicking the X at right top of window. Basically canceling the program.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

#447 Post by B.K. Johnson »

bigpup, I did not need to follow your instructions for I have been doing the steps so often. But as proof to you, I tried again and have provided info and screenies for the steps along the way.

My almost pristine tahr-6.0.6-uefi is running

Code: Select all

root# which yapi
root# 
YaPI is not installed yet.

Downloaded a new YaPI, installed the pet and tested the install. The selected yapi is:
YaPI 2016-03-25 final release
see screenie=YaPI successfully installed

Code: Select all

root# which yapi
/usr/sbin/yapi
root# 
YaPI appears in Menu>Setup
YaPI is in the PPM/Uninstall. see screenie=yapi now in uninstall.png

See screenie= drive icons before addition of new drive.png
Inserted a brand new (never used) 16 Gb flash drive
See screenie= drive icons after addition of new drive.png

Launching YaPI from Menu>Setup
see screenies=seq-1 to seq-6
At seq-3, I selected the 'any' option and click OK.
At seq-4 is the search ...wait dialog which ends with
seq-5, a part of the Usage for Xdialog script.
On closing the box, a popup with Goodbye was shown and deleted too quickly for me to make a screenie.
seq-6: Chosen ISO not found. Restart please. This message despite me not choosing an ISO. Clicked OK to end.

The screenie=location of iso does not matter shows a /ISO directory at /mnt/sda1 and two ISOs within. This shows that it matters not whether the ISOs are located one or five levels deep - in my hardware configuration.

Can I suggest that you ask L18L for help. He likes to use gettext and i18n in his scripts; I don't know what they are but I have a 'gut feeling' that their use is the cause.

BTW, I only found out today that I can right-click an ISO and select
"open with.... yapi". It is there in the thread, but once I saw Frugal, I ignored the rest of the blurb.
Attachments
location of iso does not matter.png
doesn't work whether ISOs are 1 or 5 levels deep
(35.61 KiB) Downloaded 79 times
seq-6.png
screen 6
(5.3 KiB) Downloaded 83 times
seq-5.png
screen 5
(11.1 KiB) Downloaded 86 times
seq-4.png
screen 4
(4.5 KiB) Downloaded 82 times
seq-3.png
screen 3
(17.43 KiB) Downloaded 75 times
seq-2.png
screen 2
(49.36 KiB) Downloaded 160 times
seq-1.png
screen 1
(9.78 KiB) Downloaded 83 times
drive icons before addition of new drive.png
the drive icons before new drive added
(12.35 KiB) Downloaded 90 times
yapi now in uninstall.png
yapi shows in PPM/Uninstall
(20.91 KiB) Downloaded 90 times
YaPI successfully installed.png
yapi installed
(16.27 KiB) Downloaded 85 times
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]

B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

#448 Post by B.K. Johnson »

bigpup wrote:
As for help.
All the needed help is built into the yapi windows. There is a help button, you push, in the windows that need one.
There were 2 reasons for me trying yapi -h (---help).
1.At some point during my trials I had seen something like yapi [this] [][], so I assumed it was runable from the console.
2. If runable from the console, then like all normal unix/linux scripts, I assumed it would have a -help parameter .

When -h borked, I decided to try yapi tahr-6.0.6-uefi.iso from the console. Nothing in the thread told me it would work. I did so based solely on the seeing of yapi [this] which suggested a possible yapi [any] where 'any' would be an iso.

B.K. Johnson wrote:
Why not let the user navigate via a browse button and related code to the known location.
bigpup wrote:
The biggest reason not to have this, was the location had to be already mounted to work.
A browse option will not mount a location.
It will only browse mounted locations.

A search can mount and unmount and search automatically.

A browse window is manual selection by navigating to locations. Again it will only see already mounted locations.
So if I had (say 16 drives) and even if I knew that the ISO I wanted to install was on sdc7, I would have to mount sdc7 first. I cede the point that the search would be best, if and only if, I the user has no idea on which device is the ISO I want. But if I knew the ISO is on device sdc7, it would take much less time to mount, navigate and select than to wait for the search to complete then peruse the list of ISOs the search returned. My 80 Gb took a fairly long time. I don't want to guess how long it took to search your 4 drives.
The help screen, if you hit the help button on the window for selecting what to install.
Explains going directly to the iso.
I explained before my reason(s) for using yapi -h. So, I won't repeat. But let me add.
I saw the help in that dialog-box you refer to, but I would have expected a help button there to be context sensitive and as I was not in doubt about what install from the "actual running tahrpup" or another puppy stored somewhere else meant, I did not push the button.
I guess I could add an explanation of how to navigate in Rox and how to mount a location to navigate to it.

Why in a help screen. Because this is not a normal way of using yapi. It is an alternate way.
No! No! A help screen in a dialog-box is supposed to enhance the users' understanding of the options presented in the dialogbox. You shouldn't just put any and everything in a help. I don't think developers should try to explain frugal vs full install or how to navigate in Rox in an installation. Some basic knowledge has to be assumed.

You must be tired of me harping about design, so I'll stop now.
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]

B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

#449 Post by B.K. Johnson »

bigpup wrote:
Cancel button in every window.
Well, I guess there could be.
At present time, the cancel button is in the locations that seemed to be a point at which you would want to choose to cancel.
Not could. Should. Always give the user the option to back out at any time.

I saw one dialog-box with a Cancel button. It worked.
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]

B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

#450 Post by B.K. Johnson »

Using the right-click on an ISO > Open with ...Yapi option.
Earlier, I wrote that:
  • 1. I had not seen mention of this option in the thread (though it was there) and
    2. The Help button in a dialog-box noted the option, but I had not pressed the help button as I did not need any help in the context of the page.
The new flash drive I had used in the last failed attempt with Yapi from Menu>Yapi was still inserted in the USB port. From a ROX window, I right-clicked the tahr-6.0.6-uefi.iso at /sda1/ISOs, and chose Open with ...>Yapi.
Yapi went through its paces and was even able to advise that although my pristine flash drive did not have the boot flag set, I could continue with Grub4Dos then use gParted after to set the boot flag. That was a very nice touch. Very nice indeed. :) :)

So, there are 2 successful modes to use YaPI (for me, YMV):
  • 1. From the console, enter yapi <name of your target iso>
    2. right-click of an ISO > Open with ...Yapi
The option from Menu>Yapi still does not work, despite the same screens as the successful options, and despite the availability of ISOS at /mnt/sda1/ISOs/, just 1 level deep..
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]

B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

#451 Post by B.K. Johnson »

@bigpup
I just saw where you inquired what is my 'cobbled' tahr-6.0.6.

I did mention how it came to be, but it got lost in our exchanges and I had not gave it that name reference.

Well, my attempt at creating a syslinux based system using the standard procedure of copying [main].sfs, vmlinuz and initrd to the flash had unexpectedly failed. The screen log before it crashed said it was looking for tahr-6.0.6.sfs in sda1. At about the same time, we were discussing why rcrsn51's isobooter made drives had the complete iso in one partition, sdx1, and the components in sdx4. On a lark, I decided to put a copy of puppy-tahr-6.0.6.sfs in the root; the iso components were in a directory in the root. It worked when I rebooted. Hence 'cobbled'.
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#452 Post by bigpup »

Thanks for all the testing and trying different things!

If something is wrong I want to know about it.
I am considering your change suggestions, so do not think I do not want to look at them!
Me and L18L were about the only ones really testing YaPI.
We knew what it was doing and what we wanted it to do.
Your outside input is good info!!

At this time trying to figure out this search problem of yours.

I am trying to reproduce your problem with search and I am not seeing it.
It works for me with no problem, running yapi the normal way, installed to Tahrpup 6.0.6 or Tahrpup64 6.0.6.

How about doing one more test?

One thing to try.
Could be a mount/unmount issue, but yapi usually corrects for that.

So mount the partition the one layer deep isos directory is in.

Try yapi started from the menu >Setup >YaPI

Any difference with the search?


I have a topic on YaPI posted in the forum Additional Software >System.
http://www.murga-linux.com/puppy/viewtopic.php?t=107601
This is the finished release version.
The pet posted there should be the same one you are using.

By your images you seem to be using it.

As you can see, no one is posting any info about using YaPI.
Well, You.
Thanks!!
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

#453 Post by B.K. Johnson »

One thing to try.
Could be a mount/unmount issue, but yapi usually corrects for that.

So mount the partition the one layer deep isos directory is in.

Try yapi started from the menu >Setup >YaPI

Any difference with the search?
All my isos (both the set that's 1 deep and the set that's 5 deep) are on the same partition=Windows C:=sda1. That drive/partition is always mounted.

So I decided to unmount sda1 and try Yapi from Menu>Setup>YaPI. I saw that YaPI mounted the drive during the search. And restored its status to unmounted at the end, But the result was the same ==>Usage of Xdilog and no ISOs found. This is really perplexing.

Couple more shots.
  • 1. 5 isos in a directory on a flash drive. Both this and original drive unmounted. Same result.
    2. 5 isos in a directory on a flash drive. Original drive unmounted. Flash drive mounted. Same result.
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#454 Post by bigpup »

Thanks for testing!
2. 5 isos in a directory on a flash drive. Original drive unmounted. Flash drive mounted. Same result.
That should work with no problem.
That works for me and should for you!

I have no idea why you are having this problem.

What format is the USB flash drive?

Maybe a bad download and or install of Tahrpup 6.0.6 :idea:
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

#455 Post by B.K. Johnson »

What format is the USB flash drive?
FAT32
Maybe a bad download and or install of Tahrpup 6.0.6 Idea
You are thinking! Good one but "no cigar".
Attachments
tahr-606-md5-verification.png
The md5 checks out OK.
(23.92 KiB) Downloaded 199 times
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#456 Post by bigpup »

I just do not understand this.

You are doing everything I am doing.

It is working OK for me running in the same version of Puppy you are running it in.

Do not remember if we talked about your computers specs.
Put that would be a real long shot.

If Rox can access it, no reason YaPI would not.

Nothing you may have done to alter the core Puppy files?
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

#457 Post by B.K. Johnson »

YaPI is your baby and so I understand your desire to have it work for me. But, for me, I am not worrying about it anymore. I know 2 ways of installing puppy to a flash drive using YaPI and that's good enough for me. So far I am happy with the tahr-6.0.6 installation it did. By virture of it using one partition, makes it better in my eyes than isobooter.

If you can, try using a straight 32 bit. Else, give it a break until you get that eureka moment.
BFN
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]

B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

#458 Post by B.K. Johnson »

How do I set up an additional menu item with Grub4Dos
As I have written elsewhere, I don't usually use Grub4Dos, but I have been forced/encouraged :wink: to do so in YaPI.

I want to have another instance of tahr-6.0.6 (say tahr606uefiempty). What do I do?
Do I (a) just add within menu.lst a menu item similar to what is currently there, but give it a different title to be like:

Code: Select all

title Puppy tahr 6.0.6 empty (sdb1/tahr606uefi)
find --set-root --ignore-floppies --ignore-cd /tahr606uefi/initrd.gz
  kernel /tahr606uefi/vmlinuz   psubdir=tahr606uefi pmedia=usbflash pfix=fsck
  initrd /tahr606uefi/initrd.gz
OR (b) copy /tahr606uefi somewhere else, rename it to say /tahr606uefiempty then move it to the flash drive? AND create the menu item as:

Code: Select all

title Puppy tahr 6.0.6 empty (sdb1/tahr606uefiempty)
find --set-root --ignore-floppies --ignore-cd /tahr606uefiempty/initrd.gz
  kernel /tahr606uefiempty/vmlinuz  psubdir=tahr606uefiempty pmedia=usbflash pfix=fsck
  initrd /tahr606uefiempty/initrd.gz
This is the current menu item in menu.lst

Code: Select all

title Puppy tahr 6.0.6 (sdb1/tahr606uefi)
  find --set-root --ignore-floppies --ignore-cd /tahr606uefi/initrd.gz
  kernel /tahr606uefi/vmlinuz   psubdir=tahr606uefi pmedia=usbflash pfix=fsck
  initrd /tahr606uefi/initrd.gz
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]

B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

#459 Post by B.K. Johnson »

Re:How do I set up an additional menu item with Grub4Dos
here, I think I found the answer in menu-advanced.lst.
But other advice is welcome.
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#460 Post by bigpup »

I want to have another instance of tahr-6.0.6 (say tahr606uefiempty). What do I do?
If it is a complete new install of Tahr- 6.0.6
So, basically you have two installs.

If they are both on the same partition.
Give the directory a slightly different name from normal for the second one.
Your example should work:

Code: Select all

tahr606uefiempty
Just add something to the directory name already used by the installation process.

After installing and modifying the directory name.

Rerun Grub4dos Bootloader Config.
It should make a new menu with all listed on it.

It may give a warning message about finding two installs of
Tahr 6.0.6, but just answer that is OK.

If the installs were on differentpartitions.
Should just have to rerun Grub4dos Bootloader Config.

Just to be safe, I am not sure about this.
To keep one from using the other ones save.
On the new installed Tahr- 6.0.6.
Give the save a added name, when you make it.
At boot, you may still get offer on which save to use.
However, you will have two different ones to select.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

Post Reply