Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 11,202
» Latest member: davidw
» Forum threads: 1,501
» Forum posts: 6,172
Full Statistics
|
|
|
本地硬盘上的vlnk文件是不可见的吗 |
Posted by: kero990 - 03-11-2022, 02:17 AM - Forum: Ventoy Discussion Forum
- Replies (7)
|
|
最近一直在用这台arm64的机器测试ventoy,我把他安装到了本地硬盘,同时还有一个u盘版的,都是最新的1.7
现在的问题是,我在本地硬盘给两个iso创建了vlnk,和iso在一起,但在ventoy下,他们是不可见的,无论我用本地硬盘的ventoy还是用u盘启动,这几个vlnk都是不可见的
但我把文件拷贝到u盘上,立刻就可见了。
这是什么奇怪的限制吗?
如果我给一个本地iso创建了vlnk,并拷到了u盘上,但我的u盘上有相同的iso,这时启动vlnk,会调用哪个iso?本地的还是u盘的?
另外,说明文档里提到,直接用f2启动本地硬盘时,插件时不可用的。
那么我给本地硬盘上的iso创建了vlnk,并把它拷贝到u盘,我应该给vlnk创建数据持久化文件,还是给本地iso?
但是如果我给u盘上的vlnk创建持久化文件,是不是这个dat也只能放在u盘而不能丢在本地硬盘?这台机器对u盘的读写速度不太理想,所以不太想放到u盘去
|
|
|
Non-fatal error booting some ISOs |
Posted by: Midas - 03-10-2022, 03:06 PM - Forum: Ventoy Discussion Forum
- Replies (2)
|
|
I got new hardware -- a Lenovo ThinkCentre M93p -- and while booting Ubuntu, Mint and Q4OS ISOs I've been facing the following error:
Code: [FIRMWARE BUG] TSC_DEADLINE disabled due to errata
Please update microcode to version: 0x22
According to https://askubuntu.com/questions/984970/, this is an update issue -- but it doesn't show itself if Mint, for example, is installed to local disk, so I am left wondering if it is somehow related to Ventoy.
Another similar error I saw occasionally is this:
Code: ACPI [FIRMWARE BUG] BIOS _OSI(**) query ignored
A comment at https://bugzilla.kernel.org/show_bug.cgi?id=194865 says this is just a report -- perhaps related to the my de-activation of some BIOS features -- but then again it didn't show when Mint was directly installed.
Oh, and I forgot to tell I tested those ISOs under Ventoy v1.0.70, 1.0.32 and 1.0.24 with similar results...
|
|
|
Design ventoy mod_ventoy 1.0.70 |
Posted by: AlexBryansk - 03-08-2022, 11:07 PM - Forum: Ventoy Discussion Forum
- Replies (3)
|
|
1. Added the plugin "menu_mytheme". Now you can set any directory (the "dir" key) your theme (the "mytheme" key).
I have all the themes in one folder - "/ventoy/theme", but you can place them wherever you want.
Themes have also been added for: Vento Menu Extension Plugin(press F6) and Browse Ventoy Disk (press F2).
These are the keys "theme_ExternalMenu" and "theme_FileManagerVentoy" respectively.
Plugin example:
Code: "menu_mytheme": {
"theme_FileManagerVentoy": "/ventoy/theme/themeFM.txt",
"theme_ExternalMenu": "/ventoy/theme/themeext.txt",
"through_inscription": "март 2022г",
"hotkey_tip": "h:справка F1:Memdisk F2:Power F3:ListView F4:Localboot F5:Tools F6:загрузка-Kubuntu F7:графика/текст",
"mythemes": [
{
"dir": "/ISO/Antivirus",
"mytheme": "/ventoy/theme/themeantivirus.txt"
},
{
"dir": "/ISO/linux",
"mytheme": "/ventoy/theme/themelinux.txt"
},
{
"dir": "/ISO/sistem utilit",
"mytheme": "/ventoy/theme/themeremont.txt"
},
{
"dir": "/ISO/multiboot",
"mytheme": "/ventoy/theme/themeboot.txt"
},
{
"dir": "/ISO/Install windows",
"mytheme": "/ventoy/theme/themewindows.txt"
}
]
},
2. I added a label "through_inscription", which can be added to each topic so that there is the same
inscription on all topics - I have this date of editing the ventoy flash drive. To do this, add in the themes:
Code: + hbox{
left = 80%
top = 95%
width = 10%
height = 25
+ label {text = "@VTOY_THROUGH_INSCRIPTION@" color = "#33ff00" align = "left"}
}
3. Added the ability to change the label "@VTOY_HOTKEY_TIP@", via the key "hotkey_tip". For example, to
translate it into a local language.
In order for the "menu_mytheme" plugin to work, you need to add the "VTOY_MENU_THEME" key with
the value "1" to the "Ventoy Global Control Plugin":
Code: "control": [
...
{ "VTOY_MENU_THEME": "1" },
...
],
The main menu theme is set as before in the "Ventoy Theme Plugin":
Code: "theme": {
"file": "/ventoy/theme/theme.txt",
"gfxmode": "1024x768x32",
...
},
The rest of the changes are not in the "menu_mytheme" plugin.
4. If you put the file "help.txt " on the path "/ventoy/help.txt ". Then by pressing the F6 button,
not the internal help will be displayed, but the contents of this file. So you can write a help
in the local language. The encoding of the UTF-8 file.
In the editor:
in the ventoy:
5. Added support for text files - *.txt. It is convenient in the catalog with iso, img images... place
a text file description. The encoding of the UTF-8 file.
6. I returned the old purpose to the F2 button - the "Power" menu. And the "Browse Ventoy Disk" mode
was added to the top item of the main menu. The file name for the icon is "iconFM.png".
The video of the work can be viewed in the topic: Design ventoy
You can download the modified files from the following links:
mod_ventoy-1.0.70-linux.tar.gz
mod_ventoy-1.0.70-livecd.iso
mod_ventoy-1.0.70-windows.zip
Example of the file "ventoy.json" on the path "ventoy-1.0.70/plugin/ventoy/ventoy.json".
|
|
|
Acer legacy boot seen as efi |
Posted by: rg66 - 03-08-2022, 09:09 AM - Forum: Ventoy Discussion Forum
- Replies (2)
|
|
I have an Acer Extensa ex2510 laptop with latest BIOS set to legacy. When I boot ventoy-1.0.70 it thinks its efi and doesn't show F4 > Search and boot Grub4dos. Opening console and running: echo "$grub_platform" gives "efi". My grub4dos disk boots without any issues.
TIA
|
|
|
[SOLVED] VToy doesn’t support taking snaps? |
Posted by: hd_scania - 03-08-2022, 08:32 AM - Forum: Ventoy Discussion Forum
- Replies (1)
|
|
On rEFInd i could easily take snaps by F10 and saved on /boot/efi/screenshot_nnn.bmp
On KDE Plasma 5 i also still could easily take snaps by Spectacle on your own instructed dir
Even though on Windows i also could still easily take snaps gonab saved by MSPaint on also your own instructed dir
However on VToy? I didn’t saw any manuals on taking VToy snaps and saving dirs
|
|
|
F keys problem in browser menu |
Posted by: serhat100 - 03-07-2022, 07:51 AM - Forum: Ventoy Discussion Forum
- Replies (6)
|
|
Hello long panda; I want to talk about a problem. If the code { "VTOY_DEFAULT_IMAGE": "F2>" }, is defined in the ventoy.json file
F keys work in the browser menu. But if this code is not defined ventoy.json, when we go to the browser menu with F2 in the first boot menu,
Except for F1 memdisk and ctrl hotkeys, other F keys don't work. Also, when I enter vt_browser_disk in the grub console, the F keys are fine.
is working.
|
|
|
[SOLVED] FreeBSD 13.1-STABLE not booting |
Posted by: hd_scania - 03-07-2022, 06:50 AM - Forum: Ventoy Discussion Forum
- Replies (3)
|
|
The FreeBSD 13.1-STABLE ‘‘memstick.img’’ installer says,
Code: /dev/ufs/FreeBSD_install
not found to be mounted in error code 19 for Ventoy 1.0.70
Do i consider switching to ISO files (LiveDVD’s) instead of ‘‘memstick.img’’ files (LiveUSB’s) and try again with Ventoy?
|
|
|
wepe无法进入,会直接重启,望解决下 |
Posted by: fzy008 - 02-28-2022, 01:11 AM - Forum: Ventoy Discussion Forum
- Replies (2)
|
|
描述下问题:
U盘是4GB的,安装好ventoy后,又从wepe(V2.1和V1.2两个版本)导出iso文件到U盘中。然后插入U盘,重启电脑(联想笔记本)。
我的启动是选择的legacy(主板虽有uefi但是没有对应的BIOS,会无法识别任何硬盘或U盘)模式,可以正确识别到U盘中的两个ISO,选择1个进入。
到了启动wepe的阶段,如果选择直接进入wepe,在等待一会儿后,会失去响应,然后自动重启,且重启后无法识别U盘,会直接进入原有系统。此时只能进入电脑系统,再重启才能再次识别U盘。
再进入wepe时,如果选择的是带有1024*768分辨率模式的话,会在屏幕上出现一个黑框,叠加在ventoy的界面之上,然后再无响应,一会儿后会自动重启。其余情况与上方的一样。
这俩wepe我都有直接安装入另外俩U盘,他们可以正常使用。
对了,ventoy我使用的是最新版,1.0.70版。
|
|
|
|