Porteus

Posted: **21 Jul 2021, 22:33**

We are talking about an .xzm module right? Can you manually activate it?

Posted: **21 Jul 2021, 23:24**

AcnapyxoB wrote: ↑
20 Jul 2021, 18:43
I have а problem making encrypted (ext4, reisefs) file with Porteus SaveFile manager. Тhe file is generated, but then it is not recognized during boot !?
I think it does not depend on DE.

yep, there is some problem with this .. porting this function to python/pygobject from bash is proving a bit tricky ... more work to be done..
in the meantime the script(make-changes?) from 4.0 should still work with 5.0rc3..

Posted: **22 Jul 2021, 04:58**

I made encryptet ext4 save.dat file with Porteus 4.0 - no problem.

Posted: **22 Jul 2021, 05:02**

We are talking about an .xzm module right? Can you manually activate it?

I'm talking about encrypted save.dat file container formated ext4 or reserfs (I have not tried to format in ext2)

Posted: **22 Jul 2021, 05:03**

ncmprhnsbl wrote: ↑
21 Jul 2021, 23:24
. porting this function to python/pygobject from bash is proving a bit tricky ... more work to be done..

Why change it if bash works?

Added in 10 hours 51 minutes 5 seconds:

AcnapyxoB wrote: ↑
22 Jul 2021, 04:58
I made encryptet ext4 save.dat file with Porteus 4.0 - no problem.

I created a save.dat file on my NTFS drive and use the changes=EXIT cheatcode for it and it works.

Posted: **22 Jul 2021, 16:37**

Ed_P, there is some kind of missunderstanding. I gust tried on NTFS formated flash drive, save.dat file container with xfs and ext4 encrypted (with password).
Creating of file is OK, but during booot it's not recognized !
I'm using XFCE DE, but also tried on KDE few days ago.

Posted: **22 Jul 2021, 17:26**

When I reboot my save.dat file is recognized and my changes restored. The difference I think is I don't check the Encrypt my savefile option. So the problem is with the encryption/decryption functions. Ok, good to know.

Posted: **22 Jul 2021, 17:34**

Yes, problem is only with encrypted. Тhat is what I'm sayng from the beginning.

Posted: **23 Jul 2021, 05:21**

Ed_P wrote: ↑
15 Jul 2021, 19:15

Bicephale wrote: ↑
15 Jul 2021, 10:23
What's an INSTALLER good for if the OS needs to get installed before using it?! I really got to wonder or i need a nap...
Porteus can be installed from either a Windows system or a Linux system. It doesn't require Porteus, but if Porteus is being used it can't be using the copy2ram cheatcode. Not too hard a problem to resolve.

Time is short, life is precious.

Posted: **23 Jul 2021, 15:07**

AcnapyxoB wrote: ↑
22 Jul 2021, 17:34
Yes, problem is only with encrypted. Тhat is what I'm sayng from the beginning.

Sorry, I did not understand.

Bicephale wrote: ↑
23 Jul 2021, 05:21
Time is short, life is precious.

Totally agree.

Did you get your USB install to work?

Posted: **24 Jul 2021, 04:29**

Back in May there was one flash drive booting Porteus relatively fine, then i forgot about it, because of diversions...

My long-term goal still revolves around revalorisation of some old tablet, thinking if its less busy running the OS then more computational resources shall go to the final task: to capture & retransmit TV video from legacy 720 x 640 @ ~30 Hz NTSC (Roxio/VidBox) material - which never really proved useful as it was designed for Win7.

Basic/inclusive requirements for *all* users should start with making sure the OS can always boot one way or another, possibly by integrating 3rd-party resources like rEFind, and why not also seek inspiration from the Sergei Strelec Live WinPE (7/8/10) Microsoft-like method that is the only easy solution to reboot a broken Win7 setup, actually. Compliance to GUB2Win might be fine while i like rEFind a lot for its user interface (and different keys).

Perhaps i should install QEmu or similar and enjoy the convenience, but that would be on a less restrictive machine and i sort of know the unexpected involvement with fresh-new project ideas anyway. Hobby episodes need to be 1-afternoon type or i'll end up sleeping on my keyboard...

Once i collected enough courage to give it another try that's on my to-do list, just no promises. Only quick suggestions if not requests. Sorry.

Posted: **24 Jul 2021, 17:54**

Blaze wrote: ↑
11 Jul 2021, 14:19
Can you show output of this cmmand
Code: Select all
cat /proc/bus/input/devices
?

Code: Select all

I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:01/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds 
B: PROP=0
B: EV=120013
B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="HP Wireless hotkeys"
P: Phys=hpq6001/input0
S: Sysfs=/devices/virtual/input/input5
U: Uniq=
H: Handlers=kbd event5 rfkill 
B: PROP=0
B: EV=3
B: KEY=80000000000000 0 0 0

I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
U: Uniq=
H: Handlers=kbd event6 
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="HP WMI hotkeys"
P: Phys=wmi/input0
S: Sysfs=/devices/virtual/input/input7
U: Uniq=
H: Handlers=kbd event7 
B: PROP=0
B: EV=33
B: KEY=4000000000 0 1000700000000 2102400 0 0
B: MSC=10
B: SW=20

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input8
U: Uniq=
H: Handlers=event8 
B: PROP=0
B: EV=21
B: SW=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input9
U: Uniq=
H: Handlers=event9 
B: PROP=0
B: EV=21
B: SW=4

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input10
U: Uniq=
H: Handlers=event10 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input11
U: Uniq=
H: Handlers=event11 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input12
U: Uniq=
H: Handlers=event12 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=9"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input13
U: Uniq=
H: Handlers=event13 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=10"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input14
U: Uniq=
H: Handlers=event14 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=11"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input15
U: Uniq=
H: Handlers=event15 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=12"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input16
U: Uniq=
H: Handlers=event16 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0003 Vendor=05c8 Product=03d2 Version=0005
N: Name="HP TrueVision HD Camera: HP Tru"
P: Phys=usb-0000:00:14.0-6/button
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/input/input17
U: Uniq=
H: Handlers=kbd event17 
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

Posted: **25 Jul 2021, 05:43**

.jpg files on a connected iPhone do not display as pictures rather only as icons on Cinnamon's Nemo. Copied to the harddrive they display as photos in Nemo.

Added in 1 day 6 hours 47 minutes 20 seconds:
Unable to boot Porteus 5.0 rc3 in Legacy mode

Posted: **27 Jul 2021, 04:47**

AcnapyxoB wrote: ↑
20 Jul 2021, 18:43
I have а problem making encrypted (ext4, reisefs) file with Porteus SaveFile manager. Тhe file is generated, but then it is not recognized during boot !?
I think it does not depend on DE.
With v4.0 no problem.

Once created can you mount it manually?

Posted: **27 Jul 2021, 06:02**

babam, mounting result:

Code: Select all

using /dev/loop11

Please wait while I gather some info ....

NTFS signature is missing.
Failed to mount '/dev/loop39': Invalid argument
The device '/dev/loop39' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

Porteus

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports

Porteus-v5.0rc3 x86_64 bug reports