@Akeo OMFSM Thank you! You've coded my second favorite piece of software ever. (Truecrypt is still #1 tho) Rufus has *everything* I needed for my project. I've been working on a custom usb windows installer + supporting files/images .wim files for 2 months now and Rufus was the perfect tool to solve the actual usb booting aspect. I can now create a single usb stick capable of dual-booting 32+64 bit UEFIs, + bios boot + supporting different PE boot options + support for wim files > 4gb (in .esd format of course) thanks to Rufus. (swm is such a klugey workaround) Thank you Thank you Thank you! If I wasn't broke, I'd donate >.< so my endless thanks is all I can offer for the terrific piece of software.
akeo thanks for your hard work for updating rufus , i have request ... can i get the time of usb creating ? something like log
you're right i'm not asking about adding this extra feature NOT THAT just want if rufus made log file (had creation time) while creating USB that's all ,,, i know it's unseful feature to added
But you are. Please don't assume that adding an extra line in the log is a no brainer operation. This will require both coding and maintaining the feature, neither of which are zero-time operations (especially the second one). You clearly haven't read the FAQ entry I linked to above. There's no such thing as "I know people will want that" when all it really boils down to something you would like. In other words, please don't conflate your own wishes with a feature that the vast majority of people will actually have use for. I am well placed to tell that almost all the people who use Rufus just want to create a bootable USB and couldn't care less about keeping data on how long it took them to create it once it's over, especially in something as obscure as an internal Log. Also, please understand that the Log is designed as a means for me, the developer, to help people when they encounter issues, by allowing me to take a peek at the information that I deem relevant to help with troubleshooting, without having access to the user's computer. Unfortunately for you, I really don't see any need to know how long the last USB creation operation took as something that I have any use for in terms of troubleshooting. You are of course free to try to use the Log. But please understand what it is meant to be used for, and don't expect me to add bells and whistles to it just to grant your wishes of using Rufus and its Log as a benchmarking tools (which they aren't).
Although Rufus is useful, Akeo appears to have an attitude problem to the users' questions/requests. Yes you already spent much time and efforts in developing this tool for anyone to use it for free (and I am sure all its users are grateful for that), therefore, it appears that you think that people should use whatever already in there, and any further request is not welcome. Look at the authors of 7-zip. He gladly irons out all the bugs that users reported; carefully considers all the feature requests and implement most of them when deemed beneficial. Personally I haven't used Rufus for more than a year now. I use CMD to create USBs based on WinPE/Windows7/8/10, and use YUMI or other tools to create Linux boot USBs, as I do prefer to keep the dual boot ability under BIOS and UEFI. Anyway, just my 2 cents to share. I am sure you will not be happy to read this post, however just wanted to share what I think after reading your posts.
It's easy to get a bad impression from people who act rude or dismissive. Attitudes and motivations are very complex. You'd really need to know someone in real life to suggest that they have an "attitude problem" I have times where I get really rude for a while and times where I get really nice for a while. I imagine a lot of people are the same way.
@Akeo: ignore the rants. If they don't like it, they are free to make their own tool or move to another. Thank you for this wonderful tool you've made. Please, just don't drop Windows XP support in future releases (I don't know if you ever plan to do it, but I hope not ).
Planning to introduce a poll? I vote goes for dropping XP support completely with 3.x, and advise users to go for 2.x if they want it.
As as you keep Rufus 2.x available on your site for download, it's fine by me if you want to drop WinXP support in Rufus 3.x. I have some old machines that I run Windows XP SP3 on them and I test various software which makes me to install Windows XP SP3 quite a few times. I used your tool with success so far. Anyway, I have older versions of Rufus saved on my HDDs, just in case.
Yes, when you say Rufus doesn't support XP 64 bit at all, then there is no need of XP support in version 3.x. I second Tito's comment for poll.
Oh yes, I voted a categorical "Yes". No need to add extra code and unnecessary job to Akeo which could lead to bugs. XP stays up to version 2.x
Lets hope Akeo keeps download links for the older versions ... Then that would be the "Yes" remove XP support from Rufus 3.0
Just in case I started to collect since this last version onwards till release of v3 although I believe v2.3 is the last one previous v3, dunno.