![]() ![]() Is there an easy way, they can "try-before-you-buy" various OSs with Rufus? Even if a laptop is new, how would you suggest to try with Rufus say an upgraded WinPE, WinXP, ThinPC7, WES7 to see what the hardware can handle? So they would look for an OS version that combines new features with less strain on hardware. Yet some hardware isn't new, it changed hands many times. Yet another category is "empty" users - they want to install or upgrade OS, most often Windows. Did you study, how they're different from "Linux exploration" ISOs in terms of boot? There may be quite a few IMA images in this category too. What set of ISO based tools Rufus is currently ready to support from that department, keeping in mind 95% Windows users and 2% Linux. ![]() Or they need to quickly backup & restore a drive. Or their drive emits an unusual noise or looses sectors, or data needs recovery, or a partition gets lost. Or, they purchased a new external drive that needs to be partitioned beyond what standard OS routings can do. If you have such in mind, what would be your suggestions to try with Rufus?Īnother category is "broken" users, meaning the guys who would never need any such tool until one day their PC don't boot anymore and needs service. When it comes to ISO support selection, would it be a good idea to identify demand groups? I see, you noted earlier, many users want to try Linux - that's "explorers" group, and possibly you identified centered around isolinux based - right? Many users in this category have obsolete hardware, and probably would want to start from a very small Distro. I personally don't need any (extra) features, and won't report any bugs, so you don't need to weight them against demand - hope it makes things easier. What I mean foremost is to invite others to share test results and suggestions, those users who can't do without such tool. I have already addressed one and plan on addressing the other. How about differences in ISOs of the same general type - how automation will work?Currently, only disk-by-label and older vesamenu.c32 incompatibilities seem to account for differences in the same general types. The big difference is that, once a method is supported, it should support all existing ISOs of the same type, unless the bootloader itself changes drastically. I mean, there will be a DB type arrangementIf you want to call the detection of a handful of types a DB, sure. XP/PE and BCDW/.ima also appear to be that way. Anything isolinux or bootmgr based is exceedindly easy to detect, on account of the fact that the bootloaders themselves don't vary that much and use a very static and specific set of files, that are easy to detect. ![]() How would the tool differentiate or sort an ISO to a certain type - by identifying presence of marker files?Again, already explained. If you're not happy with this coverage, knock yourself out in telling everybody how much the tool sucks and could have been so much better if only I had followed the "one true way". Even if Rufus is to support these types of ISO exclusively, I think I'll have covered a wide enough base to consider it feature-complete in terms of ISO support. So, how many supported ISO "types" are planned for this toolWell, you don't appear to read what I write, so I'll have to repeat what I stated previously:Įverything that's bootmgr or isolinux based (currently implemented) as well as XP-PE based (planned) as well as possibly BCDW+.ima based (if there is demand), as long as the post boot process is either USB-aware or USB-agnostic. This should save us, as well as all the followers of this thread some time. Preemptively, then, can I please ask you to take a minute to check my posts or the Rufus pages, and point me to a place where I stated that Rufus aims at being universal? ![]() Can't guarantee that they will all be addressed as quickly as that one, but I'll do my best.Īs mentioned in the application itself, the homepage as well as my very second post from this thread, anybody is very much invited to use the github facility to report issues and request enhancements.įor example, it would be nice to figure out, what approach he thinks is the best to generalize this tool in terms of ISO type detectionThat's childishly simple: Someone reports an ISO that doesn't seem to work, and I see what I can do, knowing that I'll probably have to explain to you that feature requests are weighted against expected demand, and, also most likely, the difference between generic and universal. But there're more things to talk about: some bugsBring them on, and I'll address them just like I did for the issue with bootmgr based ISOs on XP. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |