Post here if you are a new Porteus member and you're looking for some help.
-
beny
- Full of knowledge

- Posts: 2253
- Joined: 02 Jan 2011, 11:33
- Location: italy
Post#2
by beny » 01 Jan 2021, 22:37
hi, when you have this message, hit tab key and you have the boot option,but not the graphic menu ,try if work for you.. or you have to grab other vesamenu.c32 the file look 150.3 KiB
beny
-
glestwid
- Samurai

- Posts: 182
- Joined: 09 Jan 2018, 20:05
- Distribution: Porteus-XFCE 5.0 i586
Post#3
by glestwid » 01 Jan 2021, 22:46
Ok, this seems to be working now. But how can t ask the author to fix the broken VESAMENU.C32 ?
glestwid
-
beny
- Full of knowledge

- Posts: 2253
- Joined: 02 Jan 2011, 11:33
- Location: italy
Post#4
by beny » 01 Jan 2021, 23:08
hi if you have a sylinux directory you can grab from it, the boot directory is not compressed so you can change the files inside as you wish.
beny
-
Blaze
- DEV Team

- Posts: 3996
- Joined: 28 Dec 2010, 11:31
- Distribution: ⟰ Porteus current ☯ all DEs ☯
- Location: ☭ Russian Federation, Lipetsk region, Dankov
-
Contact:
Post#5
by Blaze » 02 Jan 2021, 08:12
What's wrong with vesamenu.c32? I don't have any issue.
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
Blaze
-
fulalas
- DEV Team

- Posts: 2058
- Joined: 26 Oct 2016, 15:34
- Distribution: Porteus
- Location: Brazil
Post#6
by fulalas » 02 Jan 2021, 09:53
I've seen this issue before. Usually the unit where Porteus is placed has either some corrupted file (running a scan disk would be nice in this case) or the boot sector wasn't properly set (running usb-stick/boot/Porteus-installer-for* would be nice in this case).
fulalas
-
glestwid
- Samurai

- Posts: 182
- Joined: 09 Jan 2018, 20:05
- Distribution: Porteus-XFCE 5.0 i586
Post#7
by glestwid » 02 Jan 2021, 12:11
I ran Porteus-installer-for-Windows twice on 2 different USB drives, and the error was the same. Is there a MD5 checksum list for the ISOs and their content?
glestwid
-
AcnapyxoB
- Contributor

- Posts: 234
- Joined: 24 Dec 2014, 10:15
- Distribution: Porteus
- Location: Tellus
Post#8
by AcnapyxoB » 02 Jan 2021, 14:13
Porteus v5.01 KDE x86_64
AcnapyxoB
-
Ed_P
- Contributor

- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#9
by Ed_P » 02 Jan 2021, 17:26
Be sure the ISO file isn't fragmented.
Ed_P
-
glestwid
- Samurai

- Posts: 182
- Joined: 09 Jan 2018, 20:05
- Distribution: Porteus-XFCE 5.0 i586
Post#10
by glestwid » 02 Jan 2021, 17:59
Ed_P wrote: ↑02 Jan 2021, 17:26
Be sure the ISO file isn't fragmented.
How can I make sure that the files are not fragmented?
glestwid
-
Ed_P
- Contributor

- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#11
by Ed_P » 03 Jan 2021, 15:09
In Windows I use Auslogics's DiskDefrag Portable. Not sure how to determine it in Linux.

Ed_P