Save file dose not work

Post here if you are a new Porteus member and you're looking for some help.
DonaldJ
White ninja
White ninja
Posts: 6
Joined: 24 May 2019, 04:04
Distribution: 4

Save file dose not work

Post#1 by DonaldJ » 24 May 2019, 04:28

I am new to Porteus I have it on a usb stick formatted fat 32 it was put their by multi boot program from windows

I have used the save file from system save file manager save file I used create save file

it makes the file open the porteus-v4.0-x86_64.cfg and place the location in

the content of the file are


-----------------------------------------------------------------------------------------------------------
### This is the porteus config file.
### You may put cheatcodes here one per line.
### Cheatcodes must start at the beginning of the line (no space before).
### Any line with the "#" character at the start is ignored.
###
### For a list of cheatcodes check /usr/doc/porteus/cheatcodes.txt

### EXAMPLES

## This tells porteus whence to boot
# from=/mnt/sda2/porteus

## This tells porteus to boot into text mode
# 3

## Tell porteus to delay boot for 5 seconds
# delay=5

## Tell porteus where the changes folder is
# changes=/mnt/sda2/changes

## This tells porteus which timezone settings you prefer
# timezone=America/Sao_Paulo

## Set keybord to Brazilian Portuguese
# kmap=br




changes=UUID:1117-3F3A/mnt/sdb1/multiboot/Porteus-XFCE-v4.0-x86_64/porteussave.dat


I got the UUID of the drive from gpart and placed it in to try to get it to work

any ideas of what I could do to get it to work

User avatar
Ed_P
Contributor
Contributor
Posts: 4907
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Save file dose not work

Post#2 by Ed_P » 24 May 2019, 14:59

Hello DonaldJ, welcome to Porteus.

You need the changes= cheatcode to look more like mine. changes=EXIT:UUID:8486-DDC5/changes/porteussave.dat

In your case I think that would be more like one of these.
changes=UUID:1117-3F3A/multiboot/Porteus-XFCE-v4.0-x86_64/porteussave.dat or changes=UUID:1117-3F3A/Porteus-XFCE-v4.0-x86_64/porteussave.dat

Have fun. :)
Ed

DonaldJ
White ninja
White ninja
Posts: 6
Joined: 24 May 2019, 04:04
Distribution: 4

Save file dose not work

Post#3 by DonaldJ » 25 May 2019, 03:41

I tried both of our suggested code with no even tried some variations but with no better results still dose not save changes .

Do not know what to do next

User avatar
Ed_P
Contributor
Contributor
Posts: 4907
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Save file dose not work

Post#4 by Ed_P » 25 May 2019, 04:40

:hmmm: I will assume after each change you exited Porteus and restarted it. So, let's look at your drive's folder structure. Can you post it? ls -g /mnt/sdb1/multiboot/ and ls -g /mnt/sdb1/multiboot/Porteus*

-update-

Another possibility is to add the change= cheatcode to the porteus.cfg file in the /boot/syslinux/ folder.

And in regards to this:
DonaldJ wrote:
24 May 2019, 04:28
put their by multi boot program from windows
What program are you using to boot your USB drive and what does it's config look like for Porteus?
Ed

DonaldJ
White ninja
White ninja
Posts: 6
Joined: 24 May 2019, 04:04
Distribution: 4

Save file dose not work

Post#5 by DonaldJ » 26 May 2019, 03:31

ls -g /mnt/sdb1/multiboot/

the result of that is ( out put )

total 1408
drwxrwxrwx 2 root 32768 May 22 09:53 ISOS/
-rwxrwxrwx 1 root 55 May 25 15:36 Installed.txt*
drwxrwxrwx 6 root 32768 May 22 09:53 MX-18.2_x64/
drwxrwxrwx 9 root 32768 May 23 22:29 Porteus-XFCE-v4.0-x86_64/
-rwxrwxrwx 1 root 49639 Feb 26 12:45 YUMI-Copying.txt*
-rwxrwxrwx 1 root 12682 Feb 26 12:48 YUMI-Readme.txt*
-rwxrwxrwx 1 root 24560 Mar 3 2017 chain.c32*
-rwxrwxrwx 1 root 337197 Mar 3 2017 grub.exe*
-r-xr-xr-x 1 root 122308 May 22 09:53 ldlinux.c32*
-r-xr-xr-x 1 root 69632 May 22 09:53 ldlinux.sys*
-rwxrwxrwx 1 root 0 May 1 2017 legacy-yumi*
-rwxrwxrwx 1 root 186500 Mar 3 2017 libcom32.c32*
-rwxrwxrwx 1 root 24148 Mar 3 2017 libutil.c32*
-rwxrwxrwx 1 root 18092 Mar 3 2017 license.txt*
-rwxrwxrwx 1 root 4660 Mar 3 2017 linux.c32*
-rwxrwxrwx 1 root 26140 Mar 3 2017 memdisk*
drwxrwxrwx 2 root 32768 May 22 09:53 menu/
-rwxrwxrwx 1 root 26596 Mar 3 2017 menu.c32*
drwxrwxrwx 4 root 32768 May 25 15:36 slax-64bit-9.6.0/
-rwxrwxrwx 1 root 781 May 22 09:53 syslinux.cfg*
-rwxrwxrwx 1 root 27104 Mar 3 2017 vesamenu.c32*
-rwxrwxrwx 1 root 42496 Mar 3 2017 wimboot*
-rwxrwxrwx 1 root 9659 Mar 3 2017 yumi.png*

ls -g /mnt/sdc1/multiboot/Porteus

the result was


/bin/ls: cannot access '/mnt/sdc1/multiboot/Porteus': No such file or directory




after doing this I placed the save file in /mnt/sdb1/multiboot/

but it did not work

the save file is made by the create a save file application in porteus it all so opens the potious-v4 .0-86_64.cfg file and places the cheat code in the file . I have not put this in at startup and the save file application has written the cheat code in the file and it dose not work

so I have tried to change what the application had written in the file with no success either .

The program in windows that created the boot-able usb is called yumi it labels the usb it works off of multi boot

User avatar
Ed_P
Contributor
Contributor
Posts: 4907
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Save file dose not work

Post#6 by Ed_P » 26 May 2019, 05:01

DonaldJ wrote:
26 May 2019, 03:31
ls -g /mnt/sdc1/multiboot/Porteus

the result was


/bin/ls: cannot access '/mnt/sdc1/multiboot/Porteus': No such file or directory
Missing the "*" and wrong drive letter. Should have been:

Code: Select all

ls -g /mnt/sdb1/multiboot/Porteus*

What does /mnt/sdb1/multiboot/syslinux.cfg look like?

An easier way to create a bootable Porteus drive is to:
  • format the drive as FAT
  • copy the contents of the Porteus ISO file to the drive
  • In the drive's /boot folder execute the Porteus-installer-for-Linux.com if you're on a Linux system or Porteus-installer-for-Windows.exe if you're on a Windows system.
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 6093
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Save file dose not work

Post#7 by brokenman » 26 May 2019, 16:13

In a root terminal type this:

Code: Select all

blkid
Use the UUID that appears in this form:
changes=UUID:1117-3F3A/multiboot/Porteus-XFCE-v4.0-x86_64/porteussave.dat

Using the UUID and the partition path together is incorrect. /mnt/sdb1 is the same as UUID:1117-3F3A
You may also use a folder that resides on a fat32 partition.
Example: changes=/dev/sdb1/mysavefolder
How do i become super user?
Wear your underpants on the outside and put on a cape.

DonaldJ
White ninja
White ninja
Posts: 6
Joined: 24 May 2019, 04:04
Distribution: 4

Save file dose not work

Post#8 by DonaldJ » 26 May 2019, 21:45

The out put of the

blkid

-------------------------------------------------------------------------------------------------------------------------
guest@porteus:~$ blkid
bash: blkid: command not found
guest@porteus:~$ su
Password:
root@porteus:/home/guest# blkid
/dev/sda1: UUID="60D9-F8CC" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="581b8589-2940-439e-8b55-6843a960a134"
/dev/sda3: LABEL="Windows" UUID="2A3C97C43C978A09" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="53148765-2662-40b6-b08a-ee540dabcd00"
/dev/sda4: LABEL=" persistence" UUID="260CA92D0CA8F947" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="5095c366-f395-4bd0-bbdb-9056f7dcce18"
/dev/sda5: LABEL="Windows RE tools" UUID="8860AD1360AD0950" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="34350a96-1cd9-4331-82f5-931e9d4936f1"
/dev/sda6: LABEL="homeantiX" UUID="5c13a7d1-64e0-414b-8ce6-e2a925b273db" TYPE="ext4" PARTLABEL="Basic data partition" PARTUUID="ddb7716b-2022-4e57-abcc-d90a0edecb52"
/dev/sdb1: UUID="c1fb9efc-1493-4d50-82e3-d55b96af8ece" TYPE="ext4"
/dev/sdb2: UUID="823bb761-2fb2-44e1-b6c4-12c18a01c788" TYPE="swap"
/dev/sdc1: LABEL="MULTIBOOT" UUID="1117-3F3A" TYPE="vfat" PARTUUID="6ae005da-01"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop14: TYPE="squashfs"
/dev/loop15: TYPE="squashfs"
/dev/loop16: TYPE="squashfs"
/dev/loop17: TYPE="squashfs"
/dev/loop18: TYPE="squashfs"
/dev/loop19: TYPE="squashfs"
/dev/loop20: TYPE="squashfs"
/dev/loop21: TYPE="squashfs"
/dev/loop22: TYPE="squashfs"
/dev/loop23: TYPE="squashfs"
/dev/loop24: TYPE="squashfs"
/dev/loop25: TYPE="squashfs"
/dev/loop26: TYPE="squashfs"
/dev/loop27: TYPE="squashfs"
/dev/loop28: TYPE="squashfs"
/dev/loop29: TYPE="squashfs"
/dev/loop30: TYPE="squashfs"
/dev/loop31: TYPE="squashfs"
/dev/loop32: TYPE="squashfs"
/dev/loop33: TYPE="squashfs"
/dev/loop34: TYPE="squashfs"
/dev/loop35: TYPE="squashfs"
/dev/loop36: TYPE="squashfs"
/dev/loop37: TYPE="squashfs"
/dev/loop38: TYPE="squashfs"
/dev/loop39: TYPE="squashfs"
/dev/loop40: TYPE="squashfs"
/dev/loop41: TYPE="squashfs"
/dev/loop42: TYPE="squashfs"
/dev/loop43: TYPE="squashfs"
/dev/loop44: TYPE="squashfs"
/dev/loop45: TYPE="squashfs"
/dev/loop46: TYPE="squashfs"
/dev/loop47: TYPE="squashfs"
/dev/loop48: TYPE="squashfs"
/dev/loop49: TYPE="squashfs"
/dev/loop50: TYPE="squashfs"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="dcb08286-62d1-4ea4-a67f-036bd4ef55bb"
root@porteus:/home/guest#


the line place in the porteus-v4.0-x86_64.cfg had no effect


but what has seemed to work is to copy the home directory to the multiboot usb and then to copy the home directory on the usb back to the copy of poreous in ram

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 2054
Joined: 20 Mar 2012, 03:42
Distribution: 5.0rc1-64bit all-DE+more
Location: australia
Contact:

Save file dose not work

Post#9 by ncmprhnsbl » 26 May 2019, 22:57

this is partly related to this bug: porteus-v4.0-x86_64.cfg ignores changes
not sure using the APPEND line in <your usb>/multiboot/Porteus-XFCE-v4.0-x86_64/porteus/boot/syslinux/porteus.cfg will work either..
it depends on how this multiboot usb boots, ie. does it use grub? does it somehow chain load syslinux?
the yumi website seems to suggest grub..
your ls -g /mnt/sdb1/multiboot/ appears to show lots of symlinks..
what's in menu/ , i wonder ?
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

DonaldJ
White ninja
White ninja
Posts: 6
Joined: 24 May 2019, 04:04
Distribution: 4

Save file dose not work

Post#10 by DonaldJ » 27 May 2019, 18:43

to ED I tried installing both from windows and from linux as in the documation it fialed both way that is why I useded the yui installer yumi
and after finding a way to boot porteous the save file dose not seem to be working the way it say in the documntation



Is thier a version of porteus were this is not a problem and the cheat codes will work I could use that

User avatar
Ed_P
Contributor
Contributor
Posts: 4907
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Save file dose not work

Post#11 by Ed_P » 27 May 2019, 21:46

DonaldJ to help you we need more information.
Ed_P wrote:
25 May 2019, 04:40
what does it's config look like for Porteus?
Ed_P wrote:
26 May 2019, 05:01
/bin/ls: cannot access '/mnt/sdc1/multiboot/Porteus': No such file or directory
Missing the "*" and wrong drive letter. Should have been:

Code: Select all

ls -g /mnt/sdb1/multiboot/Porteus*
What does /mnt/sdb1/multiboot/syslinux.cfg look like?
ncmprhnsbl wrote:
26 May 2019, 22:57
what's in menu/ , i wonder ?
DonaldJ wrote:
27 May 2019, 18:43
I tried installing both from windows and from linux as in the documation it fialed both way
To resolve we need to how it failed, what error message(s) did you get? Installing to a USB drive is usually fast and easy.
Ed

DonaldJ
White ninja
White ninja
Posts: 6
Joined: 24 May 2019, 04:04
Distribution: 4

Save file dose not work

Post#12 by DonaldJ » 28 May 2019, 01:30

How it filed was I ran the script no error message I tried to reboot off the usb I ended in grub shell

I have an hp computer I have turned of secure boot and have booted other Linux from a usb on this computer .

After getting a grub shell . Which is not that uncommon with Linux distro I found an other way to boot it . The windows method end the same in a grub shell

is your distro support by etcher or any of the other programs in Linux or windows and I could just use that . I have seen other on this forum who have used yumi . For they also have a usb stick with a multi
boot directory

I have been looking long and hard before posting and have invested a great deal of time

before posting


But maybe we should narrow of focus we now have problem here

1) the install dose not work

2) the save file dose not work


on the save file I tired putting the save changes line at boot up by pressing tab it was the same did not work no changes saved . So the statement generated by the create save file app did not work at boot up nor the statement with the UUID so the bug report on cheat code should be amended to say the cheat codes do not work at all

User avatar
Ed_P
Contributor
Contributor
Posts: 4907
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Save file dose not work

Post#13 by Ed_P » 28 May 2019, 03:56

If you want to stick with Yumi's booting I can't help you. I've never had a reason to use it.

My Porteus USB drive does boot, in fact I just booted it on my EFI system, and it invokes a grub2 menu with options to boot to UEFI Porteus 4.0 menu, Reboot and Shutdown. I select the top option which opens the standard Porteus menu and then the Porteus boot option I want. What grub boot options did you get? What happened when you selected the Porteus menu option?

And my changes=EXIT cheatcode is an option in my porteus.cfg file and works fine for me.
Ed

nanZor
Samurai
Samurai
Posts: 169
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.0 RC1 XFCE
Location: Los Angeles

Save file dose not work

Post#14 by nanZor » 28 May 2019, 08:22

Donald - how about we cut out the variables, and use the native tools so we're all on the same page to get you up and running. But, yeah, there are two minor stumbling blocks which are easy to overcome.

1) Native windows burning tool has a specific sequence.
2) For 64-bit, the place where the porteus savefile tool puts the changes= cheatcode is wrong.

Let's dedicate a usb stick solely to Porteus. Do a quick format in windows on it, and make sure the capacity is very close to what it is supposed to be. Just in case you've got a dud stick. Now eject it nicely and *physically remove it* from the box.

Run an md5sum on your downloaded iso just to make sure that is ok.

In the windows file manager, double-click on the Porteus iso. Windows will now "mount" the iso. If you don't see any folders and files, you may have to tell windows to "expand" the view. In your typical windows box with just a hard drive, this will show up as a cd/dvd drive, usually D:

Now insert your blank usb stick. That shows up typically as E: The pattern here is that we want to put in our stick that we want to put porteus on AFTER we've mounted the iso itself - hence the admonition to have it physically removed until the iso mounting step has been performed.

Highlight all the files and folders in the mounted D: drive. Drag them to the E: drive.

*** IN THE E: drive ***, navigate to the BOOT folder. *RIGHT CLICK* on the Porteus-installer-for-Windows.exe executable. This makes sure you are running it with administrator rights.

The installer will now make the E: drive bootable. Hit any key to do so, and then any key again to exit.

But don't just rip it out now. Eject it nicely. And oh, we might as well not leave the Porteus iso mounted either! "Eject" the mounted porteus drive so the iso is no longer mounted. No need to leave that open now.

tbc ..
Last edited by nanZor on 28 May 2019, 08:40, edited 2 times in total.
That's a UNIX book - cool. -Garth

nanZor
Samurai
Samurai
Posts: 169
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.0 RC1 XFCE
Location: Los Angeles

Save file dose not work

Post#15 by nanZor » 28 May 2019, 08:34

The savefile tool while helpful, (and appreciated!) has an issue where the changes= location just doesn't work. Other values, like delay and so forth do, BUT changes= doesn't. It will work in the older location.

So, let the tool write to the <usb path>/porteus/porteus-v4.0-x86_64.cfg so you can view what it proposes for changes=

BUT, take that and put the changes=<your/usb/path> to this file instead:

<usb/path>/boot/syslinux/porteus.cfg

In the porteus.cfg file, in each menu entry that you want the changes=<your/path> to be effective, add it to the end of each line that starts with APPEND.

You probably don't want to do this to the "Always Fresh" section. Up to you.

Once that is written and saved, reboot before making any system wide changes. In fact, just to make sure you've got it right, when you reboot and hit the splash screen, hit the TAB key to view the boot line. Your change should show right there.

If your setup is simple enough, you may not have to use the UUID's if you just want to kick the tires a little bit on just this system. Ideal, yes but absolutely necessary for simpler setups - maybe not.

Hopefully this helps get over some of the humps and gets us on the same page to take it further if necessary.

Tip: once successful, you may want to edit or comment OUT the changes=<path> line that was put into the <usb path>/porteus/porteus-v4.0-x86_64.cfg to avoid any confusion about it working if you look at it later down the road.
That's a UNIX book - cool. -Garth

Post Reply