Welcome, Guest |
You have to register before you can post on our site.
|
Online Users |
There are currently 766 online users. » 0 Member(s) | 760 Guest(s) Applebot, Baidu, Bing, Facebook, Google, Twitter
|
Latest Threads |
Ventoy enroll key manager...
Forum: Ventoy Discussion Forum
Last Post: Almighty1
Today, 05:02 AM
» Replies: 28
» Views: 44,410
|
Issues with windows vista...
Forum: Ventoy Discussion Forum
Last Post: johnson
08-26-2025, 06:48 AM
» Replies: 0
» Views: 609
|
What is Ventoy's boot fil...
Forum: Ventoy Discussion Forum
Last Post: Epictetus
08-24-2025, 12:47 PM
» Replies: 1
» Views: 1,003
|
Resolution issue on Windo...
Forum: Ventoy Discussion Forum
Last Post: pete
08-18-2025, 12:41 PM
» Replies: 2
» Views: 1,057
|
Ventoy-1.1.06 release
Forum: Ventoy Discussion Forum
Last Post: longpanda
08-18-2025, 03:49 AM
» Replies: 0
» Views: 878
|
请问在ventoy界面时能输入中文吗?
Forum: Ventoy Discussion Forum
Last Post: longpanda
08-16-2025, 01:06 PM
» Replies: 1
» Views: 947
|
The New Windows 11 Bypass...
Forum: Ventoy Discussion Forum
Last Post: peoriait
08-14-2025, 03:40 PM
» Replies: 1
» Views: 4,068
|
Is it possible to display...
Forum: Ventoy Plugin Forum
Last Post: vtFred
08-08-2025, 09:11 PM
» Replies: 0
» Views: 753
|
Marking up an NTFS or exF...
Forum: Ventoy Discussion Forum
Last Post: Steve2926
08-03-2025, 07:55 AM
» Replies: 1
» Views: 1,158
|
Subdirectories in Part 1 ...
Forum: Ventoy Discussion Forum
Last Post: VentoyMic
08-02-2025, 04:18 PM
» Replies: 1
» Views: 925
|
|
|
Ventoy 1.0.28: Prohibition for use in a non-standard environment |
Posted by: Van Flusen - 11-15-2020, 08:18 AM - Forum: Ventoy Discussion Forum
- Replies (1)
|
 |
Quote:Ventoy 1.0.28:
Recently, I received some special error reports, which finally proved to be the cause of the non-standard Ventoy environment. Especially use Ventoy in a single partition environment.
Although Ventoy displays Unofficial's label information, users will not care and will still think it is a Ventoy problem. Ventoy has been an overall design from the beginning, and has not considered integration into other bootloader or partition environments. Ventoy's verification and subsequent development of new features will not consider this non-standard usage. Therefore, I decided to prohibit the use of Ventoy in a non-standard environment and no longer accept requests for deregulation. Of course, this is just the default behavior of Ventoy. Ventoy is still 100% open source. If you want to apply Ventoy in your own environment, you can fork a branch and modify the source code implementation.
I use a flash drive created with Origianal Ventoy.
But I also use a flash drive created with E2B+agFM+Ventoy.
Some of the ISO's that were declared as tested a long time ago don't work for me with Ventoy anymore or work incorrectly.
For this purpose I use E2B+agFM+Ventoy, because some ISO's, which do not work properly with Ventoy, work in E2B+agFM for example as .imgPTN.
Both tools, Ventoy and E2B in combination with agFM have their advantages and disadvantages. Why not combine them?
It should be clear to every user to test a problem with Ventoy first with a Ventoy Original Flash drive before contacting longpanda.
Otherwise the problem is with E2B+agFM+Ventoy and therefore the problem should be reported to Steve at E2B.
That can't be that difficult!
After longpanda's decision to prevent Ventoy from being integrated into E2B, I now have to work with 2 Flash drives to take advantage of both tools.
What is your opinion about longpanda's decision?
|
|
|
Secure login for live mode? |
Posted by: HereIAmNow - 11-14-2020, 02:16 PM - Forum: Ventoy Discussion Forum
- No Replies
|
 |
I've tried to create a secure login using persistence with a live ISO (I was using Mint 20) but it always allowed me to login just by clicking the place to type a password, without actually typing it. This isn't very secure at all. Is there a way to enable this which would work?
Or otherwise, is there a way to put a secure login on Ventoy itself, before it even boots the OS? I don't care where the login is as long as it exists. Thanks.
|
|
|
Read-only Persistence? |
Posted by: HereIAmNow - 11-13-2020, 01:56 PM - Forum: Ventoy Discussion Forum
- Replies (6)
|
 |
Please read the whole post because I approach this from several angles:
I'm trying to figure out how to do something and I have a few related questions. I want to be able to make a live Linux that will persist, but then I can set it to use the persistence file as read-only, so that it will still keep all the changes that I've made to that point, but not make any new ones, so I can save on wear and tear for my USB stick, and lock in the settings that I want.
First of all, when exactly does Ventoy update its persistence file - during shutdown or at any arbitrary time? So if I yank the USB drive before shutting down then will that prevent it from writing?
But more importantly, how can I make the file read-only, so that once I have it all set up the way that I want it, I can prevent further changes, and also save on wear and tear for my USB stick? Is there some line I can put into the .json file to just prevent it from writing anything to the drive?
I've tried disabling persistence in the .json file but that seems to ignore the file completely, thus reverting everything to defaults, but I need to be able to read and use the customizations that I've made. And I've also tried making the persistence file itself read-only (I disabled all write capabilities for all users), but it still somehow keeps updating, without even changing the date modified information!
Alternatively, is there a way that I can take all of the data in the persistence file and just put that into the ISO itself, to update it and build a new ISO or modify the existing one, so that I can just boot from that and turn off persistence?
And if none of this stuff is possible then PLEASE consider making an update for a new .json parameter to make persistence read-only! It should be very easy to implement - just use whatever function is for writing to the drive and make it conditional. I even tried looking into the source code myself but there are so many files and folders that I can't figure out how to fix it, much less how to even compile it so that I can redeploy it onto a USB stick (I'm new to Linux, btw).
|
|
|
Is this a bug in LInux upgrade to v1.0.27 |
Posted by: GCMartin - 11-11-2020, 03:59 AM - Forum: Ventoy Discussion Forum
- Replies (2)
|
 |
Is this a bug in LInux upgrade to v1.0.27?
The USB is an 8GB USB V2.0 unit with its ISOs in partititon #1 and Ventoy on partition #2. Mount command message suggest a bug???
Code: root# ./Ventoy2Disk.sh -u /dev/sde
**********************************************
Ventoy: 1.0.27
longpanda admin@ventoy.net
https://www.ventoy.net
**********************************************
Upgrade operation is safe, all the data in the 1st partition (iso files and other) will be unchanged!
Update Ventoy 1.0.20 ===> 1.0.27 Continue? (y/n)y
mount-FULL: /initrd/mnt/dev_save/boot-isos/Ventoy/ventoy-1.0.27-linux/tmp_mnt: special device /dev/sde2 does not exist.
Update Ventoy to /dev/sde successfully finished.
root#
ALSO
For the use of the "upgrade" ventoy command, is there documentation on its use? It is a "blind" command with NO evidence of whether the prior created ventoy commands was used on the upgrade. How is a user to know if the UEFI feature continues on the USB unit?
Any documentation on proper use of upgrade would be useful in understanding its outcome. The command (CMD) option is present in help, but NOTHING exist of its proper use when past multiple ventoy options were used to originally create the Ventoy USB unit.
Further, if the unit was created months ago and any user cannot remember what options was used, is Ventoy capable of knowing what those options were and preserve them as it upgrades the Ventoy USB unit?
Thanks in advance for any help
|
|
|
Ventoy ISO - An idea for LongPanda |
Posted by: GCMartin - 11-08-2020, 03:22 PM - Forum: Ventoy Discussion Forum
- Replies (2)
|
 |
The Ventoy ISO is created with one specific mission: Create/Update a Ventoy USB. It offers no other services. They work, although, it does need improvements that would be provided by ANY modern Window manager. In fact, excepting for the most die-hearts, EVERYONE understands use of a desktop window manager from Windows users, to noobs, to die-hearts...everyone. And EVERY window manager offers some basic services such as logout, reboot, shutdown, etc.
Having tested and used the Ventoy ISO I wonder if its author will consider a couple suggestions or ideas that would improve, at a glance, use that would work with everyone, yet yield the very things the authors wants a user to meet for USB creation:
- An example of one idea is for the Ventoy ISO author to review the RescueZilla ISO. Like Ventoy, it, too, is purpose-built and it offers much/most in its user interface that would meet what the Ventoy ISO author would want for Ventoy users. (THIS IS NOT a request to use Rescuezilla, merely it offers an example of a "user look" for Ventoy's ISO) There are many other ISO examples which are purpose-built that might be favorable to creates support screens which would be similar to what is used in Ventoy's Microsoft UI.
- Another purpose-built example is the GParted ISO (there are several other purpose-built example ISOs on the internet)
- Another idea is a Linux window manager that has a built-in means for the kind of screen UI that would match the UI used by Ventoy under Microsoft's desktop. These window managers, all, possess the capability for shutdown/restart that Ventoy would not need to bother itself with.
Again, these are ideas that would exceed what is current in Ventoy's ISO. As it stands today, NONE Of the 3 means (Windows app, Linux app, or Ventoy ISO) for Ventoy building of its USBs match in either appearance or implementation. If users saw the same thing across all products, Ventoy builders would have less work while user use would benefit, as well.
The ideas presented here is offered as ideas to provide a consistent interface across all of the Ventoy build methods, where possible.
FYI
|
|
|
Does not start Windows PE Gandalf Redstone 5 |
Posted by: David - 11-07-2020, 12:08 PM - Forum: Ventoy Discussion Forum
- Replies (11)
|
 |
Translated By Bing...
Hello.
I can't start Windows PE Gandalf Redstone 5.
On my USB Ventoy I have 3 ISO:
Windows 10.
Windows PE Sergei Strelec.
Windows PE Gandalf Redstone 5.
Windows 10 and Windows PE Sergei Strelec start correctly, but with Windows PE Gandalf Redstone 5 I get black screen with error message:
Windows has encountered a problem communicating wi th a device connected to your computer.
This error can be caused by unplugging a removable storage device such as an external uSB drive while the device is in use, or by faulty hardware such as is failing. Make sure any removable storage is properly a hard drive or CD-ROM drive that connected and then restart your computer.
If you continue to receive thi s error message, contact the hardware manufacturer.
Status: Oxc00000e9 Info: An unexpected I/O error has occurred.
|
|
|
|