Splash Screen Stays Up

Post here if you are a new Porteus member and you're looking for some help.
mparillo
Black ninja
Black ninja
Posts: 32
Joined: 14 Mar 2014, 19:11
Distribution: Porteus-KDE-v4.0-x86_64.iso
Location: USA

Splash Screen Stays Up

Post#16 by mparillo » 06 May 2018, 01:48

Thank you all, and I apologize, but my profile distribution is out of date, and I no longer have that thumb drive. So, Donald's directions looked good to me, but when I followed them, my thumb drive is not bootable at all. That is, I do not even get the porteus splash screen.

donald
Full of knowledge
Full of knowledge
Posts: 2064
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Splash Screen Stays Up

Post#17 by donald » 06 May 2018, 04:41

That's weird..

any error messages?
maybe i should have written:
mount -o loop /Path/to/Porteus.iso /mnt/iso

you are trying to boot BIOS machines - sure?
Is the usb drive set to be the 1st boot device?
(in BIOS or (whichever) key to pop up the boot menu.)

my usb thumb drive has the boot flag

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Splash Screen Stays Up

Post#18 by Ed_P » 06 May 2018, 05:02

I really hope other new users aren't experiencing what you're going thru mparillo.
Ed

mparillo
Black ninja
Black ninja
Posts: 32
Joined: 14 Mar 2014, 19:11
Distribution: Porteus-KDE-v4.0-x86_64.iso
Location: USA

Splash Screen Stays Up

Post#19 by mparillo » 06 May 2018, 13:20

donald wrote:
06 May 2018, 04:41
That's weird..

any error messages? I did not see any error messages, but I will re-do everything and paste below.
maybe i should have written:
mount -o loop /Path/to/Porteus.iso /mnt/iso
Unless you edited your post, I see it in your excellent step-by-step instructions
you are trying to boot BIOS machines - sure? Yes, tested on two different machines which currently boot Manjaro KDE in BIOS mode.
Is the usb drive set to be the 1st boot device?
(in BIOS or (whichever) key to pop up the boot menu.) Yes, my thumb drive with Porteus Kiosk boots before Manjaro KDE.

my usb thumb drive has the boot flag I added it via KDE Partition Manager, but no change.

Code: Select all

[mparillo@MarcoManjaroHP0 ~]$ su
Password: 
[root@MarcoManjaroHP0 mparillo]# umount /dev/sdb1
umount: /dev/sdb1: not mounted.
[root@MarcoManjaroHP0 mparillo]# mkfs.ext4 /dev/sdb1
mke2fs 1.44.1 (24-Mar-2018)
/dev/sdb1 contains a ext4 file system
        last mounted on /mnt/usb on Sat May  5 18:30:10 2018
Proceed anyway? (y,N) y
Creating filesystem with 978432 4k blocks and 244800 inodes
Filesystem UUID: ac9a0f8b-6e5c-4337-afa0-8c759b8d3fda
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done 

[root@MarcoManjaroHP0 mparillo]# mkdir /mnt/iso
mkdir: cannot create directory ‘/mnt/iso’: File exists
[root@MarcoManjaroHP0 mparillo]# mkdir /mnt/usb
mkdir: cannot create directory ‘/mnt/usb’: File exists
[root@MarcoManjaroHP0 mparillo]# mount -o loop  /home/mparillo/Downloads/Porteus-LXQT-v4.0-x86_64.iso /mnt/iso
mount: /mnt/iso: WARNING: device write-protected, mounted read-only.
[root@MarcoManjaroHP0 mparillo]# mount /dev/sdb1 /mnt/usb
[root@MarcoManjaroHP0 mparillo]# cp -a /mnt/iso/* /mnt/usb/
[root@MarcoManjaroHP0 mparillo]# sync
[root@MarcoManjaroHP0 mparillo]# cd /mnt/usb/boot
[root@MarcoManjaroHP0 boot]# ./Porteus-installer-for-Linux.com
Verifying archive integrity... All good.
Uncompressing Porteus Installer......
















                             _.====.._
                           ,:._       ~-_
                               '\        ~-_
                                 \        \.
                               ,/           ~-_
                      -..__..-''   PORTEUS   ~~--..__

==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--

Installing Porteus to /dev/sdb1
WARNING: Make sure this is the right partition before proceeding.

Type 'ok' to continue or press Ctrl+c to exit.
ok
Flushing filesystem buffers...

Using extlinux bootloader.

Installation finished successfully.
You may reboot your PC now and start using Porteus.
Please check the /boot/docs folder for additional information about
the installation process, Porteus requirements and booting parameters.
In case of making tweaks to the bootloader config,
please edit: /mnt/usb/boot/syslinux/porteus.cfg file.

Press Enter to exit.




[root@MarcoManjaroHP0 boot]# exit
exit
[mparillo@MarcoManjaroHP0 ~]$ cat  /mnt/usb/boot/syslinux/porteus.cfg
PROMPT 0
TIMEOUT 90
UI vesamenu.c32
DEFAULT GRAPHICAL
MENU BACKGROUND porteus.png
MENU TITLE Porteus-4.0 64bit

MENU WIDTH 30
MENU MARGIN 2
MENU ROWS 10
MENU HELPMSGROW 17
MENU TIMEOUTROW 28
MENU TABMSGROW 15
MENU CMDLINEROW 22
MENU HSHIFT 4
MENU VSHIFT 5

        menu color screen       37;40      #00000000 #00000000 none
        menu color border       30;44      #00000000 #00000000 none
        menu color title        1;36;44    #ffF6FF00 #30003f07 none
        menu color unsel        37;44      #ffffffff #00000000 none
        menu color hotkey       1;37;44    #ff8037b7 #00000000 none
        menu color sel          7;37;40    #ff111B78 #003f7fbf none
        menu color hotsel       1;7;37;40  #ffaf67f7 #003f7fbf none
        menu color scrollbar    30;44      #00000000 #00000000 none

        menu color tabmsg       31;40      #ffB6F538 #00000000 none
        menu color cmdmark      1;36;40    #ffff0000 #00000000 none
        menu color cmdline      37;40      #ffffffff #ff000000 none
        menu color pwdborder    30;47      #ffff0000 #00000000 std
        menu color pwdheader    31;47      #ffff0000 #00000000 std
        menu color pwdentry     30;47      #ffff0000 #00000000 std
        menu color timeout_msg  37;40      #ff809aef #00000000 none
        menu color timeout      1;37;40    #ffb72f9f #00000000 none
        menu color help         37;40      #ffD5F538 #00000000 none
        menu color msg07        37;40      #90ffffff #00000000 std


LABEL GRAPHICAL
MENU LABEL Graphics mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND changes=/porteus
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL fresh
MENU LABEL Always Fresh
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND nomagic base_only norootcopy
TEXT HELP
    Normally Porteus saves all changes
    to the /porteus/changes/ directory
    on the boot media (if writable)
    and restores them next boot.
    Use this option to start a fresh
    system, changes are not read from
    or written to any device
ENDTEXT

LABEL copy2ram
MENU LABEL Copy To RAM
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND copy2ram
TEXT HELP
    Run Porteus the same as above,
    but first copy all data to RAM
    to get a huge speed increase
    (needs >768MB)
ENDTEXT

LABEL text
MENU LABEL Text mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND 3
TEXT HELP
    Run Porteus in text mode and
    start the command prompt only
ENDTEXT

LABEL intel
MENU LABEL Intel ucode update
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/intel-ucode.cpio,/boot/syslinux/initrd.xz
APPEND nomagic base_only norootcopy
TEXT HELP
    This mode upgrades your intel microcode
    for use with intel processors that
    receive the TSC_DEADLINE error message
ENDTEXT

LABEL pxe-boot
MENU LABEL Porteus as PXE server
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND pxe
TEXT HELP
    Run Porteus as usual, but also
    initialize a PXE server.
    This will allow you to boot Porteus
    on other computers over a network
ENDTEXT

MENU SEPARATOR

LABEL plop
MENU LABEL PLoP BootManager
KERNEL /boot/syslinux/plpbt
TEXT HELP
    Run the plop boot manager.
    This utility provides handy
    boot-USB options for machines
    with vintage/defective BIOS
ENDTEXT

LABEL hd
MENU LABEL Boot from the first hd
COM32 chain.c32
APPEND hd0 1
TEXT HELP
    Don't start Porteus at all, but
    rather run any operating system
    installed on the first partition
    of the hard drive
ENDTEXT
[mparillo@MarcoManjaroHP0 ~]$ 

donald
Full of knowledge
Full of knowledge
Posts: 2064
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Splash Screen Stays Up

Post#20 by donald » 06 May 2018, 15:23

This looks Ok....it didn't boot to the porteus splash screen?

Hmm...
--> which currently boot in BIOS mode.<--
Could it be that this does not work the same way as a real BIOS machine?

Try to install Porteus as described in USB_INSTALLATION.txt for EFI systems.

As a last resort - for testing purposes only - you could run the isohybrid command
(if you have it on your system - it is part of the syslinux package)
against a copy of the Porteus iso and dd this one onto the usb drive.
Bear in mind that the drive will only contain a iso9660 filesystem (write protected).
If this one runs, well than there should be a way to install Porteus normally.

mparillo
Black ninja
Black ninja
Posts: 32
Joined: 14 Mar 2014, 19:11
Distribution: Porteus-KDE-v4.0-x86_64.iso
Location: USA

Splash Screen Stays Up

Post#21 by mparillo » 06 May 2018, 19:32

No splash screen. The only difference I noticed on the EFI section was to format FAT32 (I was already copying all folders anyway), so:

Code: Select all

[mparillo@MarcoManjaroHP0 ~]$ su
Password: 
[root@MarcoManjaroHP0 mparillo]# dd if=/dev/sdb bs=512 count=1 | hexdump -C
00000000  33 c0 fa 8e d8 8e d0 bc  00 7c 89 e6 06 57 8e c0  |3........|...W..|
00000010  fb fc bf 00 06 b9 00 01  f3 a5 ea 1f 06 00 00 52  |...............R|
1+0 records in
1+0 records out
00000020  52 b4 41 bb aa 55 31 c9  30 f6 f9 cd 13 72 13 81  |R.A..U1.0....r..|
512 bytes copied, 0.00181924 s, 281 kB/s
00000030  fb 55 aa 75 0d d1 e9 73  09 66 c7 06 8d 06 b4 42  |.U.u...s.f.....B|
00000040  eb 15 5a b4 08 cd 13 83  e1 3f 51 0f b6 c6 40 f7  |..Z......?Q...@.|
00000050  e1 52 50 66 31 c0 66 99  e8 66 00 e8 21 01 4d 69  |.RPf1.f..f..!.Mi|
00000060  73 73 69 6e 67 20 6f 70  65 72 61 74 69 6e 67 20  |ssing operating |
00000070  73 79 73 74 65 6d 2e 0d  0a 66 60 66 31 d2 bb 00  |system...f`f1...|
00000080  7c 66 52 66 50 06 53 6a  01 6a 10 89 e6 66 f7 36  ||fRfP.Sj.j...f.6|
00000090  f4 7b c0 e4 06 88 e1 88  c5 92 f6 36 f8 7b 88 c6  |.{.........6.{..|
000000a0  08 e1 41 b8 01 02 8a 16  fa 7b cd 13 8d 64 10 66  |..A......{...d.f|
000000b0  61 c3 e8 c4 ff be be 7d  bf be 07 b9 20 00 f3 a5  |a......}.... ...|
000000c0  c3 66 60 89 e5 bb be 07  b9 04 00 31 c0 53 51 f6  |.f`........1.SQ.|
000000d0  07 80 74 03 40 89 de 83  c3 10 e2 f3 48 74 5b 79  |..t.@.......Ht[y|
000000e0  39 59 5b 8a 47 04 3c 0f  74 06 24 7f 3c 05 75 22  |9Y[.G.<.t.$.<.u"|
000000f0  66 8b 47 08 66 8b 56 14  66 01 d0 66 21 d2 75 03  |f.G.f.V.f..f!.u.|
00000100  66 89 c2 e8 ac ff 72 03  e8 b6 ff 66 8b 46 1c e8  |f.....r....f.F..|
00000110  a0 ff 83 c3 10 e2 cc 66  61 c3 e8 62 00 4d 75 6c  |.......fa..b.Mul|
00000120  74 69 70 6c 65 20 61 63  74 69 76 65 20 70 61 72  |tiple active par|
00000130  74 69 74 69 6f 6e 73 2e  0d 0a 66 8b 44 08 66 03  |titions...f.D.f.|
00000140  46 1c 66 89 44 08 e8 30  ff 72 13 81 3e fe 7d 55  |F.f.D..0.r..>.}U|
00000150  aa 0f 85 06 ff bc fa 7b  5a 5f 07 fa ff e4 e8 1e  |.......{Z_......|
00000160  00 4f 70 65 72 61 74 69  6e 67 20 73 79 73 74 65  |.Operating syste|
00000170  6d 20 6c 6f 61 64 20 65  72 72 6f 72 2e 0d 0a 5e  |m load error...^|
00000180  ac b4 0e 8a 3e 62 04 b3  07 cd 10 3c 0a 75 f1 cd  |....>b.....<.u..|
00000190  18 f4 eb fd 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001b0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 80 00  |................|
000001c0  01 00 ee fe ff ff 01 00  00 00 ff 7f 77 00 00 00  |............w...|
000001d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200
[root@MarcoManjaroHP0 mparillo]# dd if=/dev/zero of=/dev/sdb bs=512 count=1
1+0 records in
1+0 records out
512 bytes copied, 0.00456277 s, 112 kB/s
[root@MarcoManjaroHP0 mparillo]# fdisk -l /dev/sdb
Disk /dev/sdb: 3.8 GiB, 4009754624 bytes, 7831552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[root@MarcoManjaroHP0 mparillo]# fdisk /dev/sdb

Welcome to fdisk (util-linux 2.32).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

The old iso9660 signature will be removed by a write command.

Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x6c23b533.

Command (m for help): n
Partition type
   p   primary (0 primary, 0 extended, 4 free)
   e   extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 
First sector (2048-7831551, default 2048): 
Last sector, +sectors or +size{K,M,G,T,P} (2048-7831551, default 7831551): 

Created a new partition 1 of type 'Linux' and of size 3.8 GiB.
Partition #1 contains a ext4 signature.

Do you want to remove the signature? [Y]es/[N]o: y

The signature will be removed by a write command.

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

[root@MarcoManjaroHP0 mparillo]# mkfs.vfat -F 32 /dev/sdb1
mkfs.fat 4.1 (2017-01-24)
[root@MarcoManjaroHP0 mparillo]# mount -o loop  /home/mparillo/Downloads/Porteus-LXQT-v4.0-x86_64.iso /mnt/iso
mount: /mnt/iso: WARNING: device write-protected, mounted read-only.
[root@MarcoManjaroHP0 mparillo]# mount /dev/sdb1 /mnt/usb
[root@MarcoManjaroHP0 mparillo]# cp -a /mnt/iso/* /mnt/usb/
[root@MarcoManjaroHP0 mparillo]# sync
[root@MarcoManjaroHP0 mparillo]# cd /mnt/usb/boot
[root@MarcoManjaroHP0 boot]# ./Porteus-installer-for-Linux.com
Verifying archive integrity... All good.
Uncompressing Porteus Installer......
                             _.====.._
                           ,:._       ~-_
                               '\        ~-_
                                 \        \.
                               ,/           ~-_
                      -..__..-''   PORTEUS   ~~--..__

==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--

Installing Porteus to /dev/sdb1
WARNING: Make sure this is the right partition before proceeding.

Type 'ok' to continue or press Ctrl+c to exit.
ok
Flushing filesystem buffers...

Using extlinux bootloader.

Installation finished successfully.
You may reboot your PC now and start using Porteus.
Please check the /boot/docs folder for additional information about
the installation process, Porteus requirements and booting parameters.
In case of making tweaks to the bootloader config,
please edit: /mnt/usb/boot/syslinux/porteus.cfg file.

Press Enter to exit.

[root@MarcoManjaroHP0 boot]# exit
exit
[mparillo@MarcoManjaroHP0 ~]$ cat  /mnt/usb/boot/syslinux/porteus.cfg
PROMPT 0
TIMEOUT 90
UI vesamenu.c32
DEFAULT GRAPHICAL
MENU BACKGROUND porteus.png
MENU TITLE Porteus-4.0 64bit

MENU WIDTH 30
MENU MARGIN 2
MENU ROWS 10
MENU HELPMSGROW 17
MENU TIMEOUTROW 28
MENU TABMSGROW 15
MENU CMDLINEROW 22
MENU HSHIFT 4
MENU VSHIFT 5

        menu color screen       37;40      #00000000 #00000000 none
        menu color border       30;44      #00000000 #00000000 none
        menu color title        1;36;44    #ffF6FF00 #30003f07 none
        menu color unsel        37;44      #ffffffff #00000000 none
        menu color hotkey       1;37;44    #ff8037b7 #00000000 none
        menu color sel          7;37;40    #ff111B78 #003f7fbf none
        menu color hotsel       1;7;37;40  #ffaf67f7 #003f7fbf none
        menu color scrollbar    30;44      #00000000 #00000000 none

        menu color tabmsg       31;40      #ffB6F538 #00000000 none
        menu color cmdmark      1;36;40    #ffff0000 #00000000 none
        menu color cmdline      37;40      #ffffffff #ff000000 none
        menu color pwdborder    30;47      #ffff0000 #00000000 std
        menu color pwdheader    31;47      #ffff0000 #00000000 std
        menu color pwdentry     30;47      #ffff0000 #00000000 std
        menu color timeout_msg  37;40      #ff809aef #00000000 none
        menu color timeout      1;37;40    #ffb72f9f #00000000 none
        menu color help         37;40      #ffD5F538 #00000000 none
        menu color msg07        37;40      #90ffffff #00000000 std


LABEL GRAPHICAL
MENU LABEL Graphics mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND changes=/porteus
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL fresh
MENU LABEL Always Fresh
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND nomagic base_only norootcopy
TEXT HELP
    Normally Porteus saves all changes
    to the /porteus/changes/ directory
    on the boot media (if writable)
    and restores them next boot.
    Use this option to start a fresh
    system, changes are not read from
    or written to any device
ENDTEXT

LABEL copy2ram
MENU LABEL Copy To RAM
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND copy2ram
TEXT HELP
    Run Porteus the same as above,
    but first copy all data to RAM
    to get a huge speed increase
    (needs >768MB)
ENDTEXT

LABEL text
MENU LABEL Text mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND 3
TEXT HELP
    Run Porteus in text mode and
    start the command prompt only
ENDTEXT

LABEL intel
MENU LABEL Intel ucode update
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/intel-ucode.cpio,/boot/syslinux/initrd.xz
APPEND nomagic base_only norootcopy
TEXT HELP
    This mode upgrades your intel microcode
    for use with intel processors that
    receive the TSC_DEADLINE error message
ENDTEXT

LABEL pxe-boot
MENU LABEL Porteus as PXE server
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND pxe
TEXT HELP
    Run Porteus as usual, but also
    initialize a PXE server.
    This will allow you to boot Porteus
    on other computers over a network
ENDTEXT

MENU SEPARATOR

LABEL plop
MENU LABEL PLoP BootManager
KERNEL /boot/syslinux/plpbt
TEXT HELP
    Run the plop boot manager.
    This utility provides handy
    boot-USB options for machines
    with vintage/defective BIOS
ENDTEXT

LABEL hd
MENU LABEL Boot from the first hd
COM32 chain.c32
APPEND hd0 1
TEXT HELP
    Don't start Porteus at all, but
    rather run any operating system
    installed on the first partition
    of the hard drive
ENDTEXT
AND IT WORKS!!!! Thank you so much.

Now the rest is my problem. It seems if the old Porteus custom builder allowed you to select a browser and install it to your ISO. Plus I guess I need to switch back to KDE, as the LXQt network manager is too bare-bones for a newbie like me to connect to my Wi-FI. Last, with a FAT32 filesystem, I cannot make permanent changes, can I? To keep my network manager settings and browser?

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Splash Screen Stays Up

Post#22 by Ed_P » 06 May 2018, 21:16

:Yahoo!:

For a browser go to the Porteus Menu -> Internet section and click on the Browser Selection and Update Tool. You will find a selection of browsers to choose from. Once selected and downloaded copy from the /tmp folder the browser module to your /modules folder and active it.

As for settings and etc, yes they can be saved on a FAT32 system. :happy62: And NTFS systems too. There a couple of ways to do it. One is to create a save.dat file another is to create a module of your changes.
Ed

mparillo
Black ninja
Black ninja
Posts: 32
Joined: 14 Mar 2014, 19:11
Distribution: Porteus-KDE-v4.0-x86_64.iso
Location: USA

Splash Screen Stays Up

Post#23 by mparillo » 08 May 2018, 23:01

Thank you. Now more progress. I can save 'state'. What I did was take my working FAT32 thumb drive, and use the installer to write to a different thumb drive (ext4). Now, if I take the graphical option, my Plasma System Settings, Wireless network and Dolphin settings are 'remembered' across re-boots.

I was able to download chromium to /tmp, followed these directions successfully.

But 'always fresh' is not based on the things I was able to change since my install (wireless, chromium, etc,), but based on the initial install? That is, 'always fresh' does not just 'forget' what I do in the 'always fresh' session, but if forgets all my customization, correct?

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Splash Screen Stays Up

Post#24 by Ed_P » 08 May 2018, 23:30

mparillo wrote:
08 May 2018, 23:01
That is, 'always fresh' does not just 'forget' what I do in the 'always fresh' session, but if forgets all my customization, correct?
Yup. :happy62:
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Splash Screen Stays Up

Post#25 by Ed_P » 10 May 2018, 03:50

You're awfully quiet mparillo. I suspect you want a system that has your customizations and can't be changed. :)
Ed

mparillo
Black ninja
Black ninja
Posts: 32
Joined: 14 Mar 2014, 19:11
Distribution: Porteus-KDE-v4.0-x86_64.iso
Location: USA

Splash Screen Stays Up

Post#26 by mparillo » 12 May 2018, 17:42

That would be ideal, yes, basically a full distro optimized for 'always fresh'.
- I already have, and like, Porteus Kiosk, which, after install, has a web browser and my wifi access point and password. This is ideal for my use case of home banking, Amazon, shopping, etc.
- The old Porteus used to allow you to pick your DE, browser, etc, and it would build an ISO amounting to much of what I would like in a full distro just for me, which was a good result, though I used to have to pick my wifi access point and enter the password in always fresh.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Splash Screen Stays Up

Post#27 by Ed_P » 12 May 2018, 18:26

I understand. And to that end I have a system I named Always Fresh '. It's the Always Fresh menu plus the modules cheatcode and my /modules directory includes a module I make named mychanges.xzm.

So to achieve your goal you need to:

1. Copy the Always Fresh menu in your "Splash Screen". Put it between the Graphical and Always Fresh entry and add to it the modules= cheatcode that you see in the Graphical menu entry.

2. For this step there are a copy of options for creating a module of your changes. The approach I suggest is fairly easy to impliment but requires several steps.
2.a Boot the new AF menu option.
2.b Customize the system the way you want.
2.c Save your changes. Terminal > save-changes /address to your porteus/modules/mychanges.xzm
2.d Reboot the new AF menu option.

:)
Ed

mparillo
Black ninja
Black ninja
Posts: 32
Joined: 14 Mar 2014, 19:11
Distribution: Porteus-KDE-v4.0-x86_64.iso
Location: USA

Splash Screen Stays Up

Post#28 by mparillo » 14 May 2018, 22:55

Thank you very much.
Is there a step by step guide for these? As in a tutorial for a complete newbie?

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Splash Screen Stays Up

Post#29 by Ed_P » 15 May 2018, 01:30

Gee, I thought I gave you a step by step guide. :( You can check out this webpage to see if it helps.
http://www.porteus.org/component/conten ... -v-10.html
Ed

Post Reply