#COM32 FILE RUFUS DOWNLOAD UPDATE#
#COM32 FILE RUFUS DOWNLOAD SOFTWARE#
#COM32 FILE RUFUS DOWNLOAD ISO#

c32 file check while ensuring that the completed USB drive works with the Rufus-provided version of SYSLINUX.

#COM32 FILE RUFUS DOWNLOAD SOFTWARE#

As a user, I tend to get annoyed when software downloads start climbing into the tens of megabytes, not hundreds of kilobytes, but I understand if you have your own goals for keeping the Rufus binary below a certain size.Д®ither way, the original intent behind this line of inquiry was to draw attention to an area where I felt you could simplify the implementation of the. If you moved the Rufus SYSLINUX baseline to 5.x it would be even less (~50K).

c32 files would indeed be a large increase relative to the current Rufus binary, but it's not a huge amount of data in absolute terms (~200K).

#COM32 FILE RUFUS DOWNLOAD ISO#

Increasing the Rufus download size by 50% just for the sake of people using an old ISO doesn't seem very desirable.Д¬ircling back to your earlier comment, embedding the. Yeah, when you put it that way, retaining the on-demand download mechanic wouldn't make much sense if you're always replacing the. c32 files.ДЇYI, SYSLINUX 5.x changed the COM32 format to ELF and simultaneously reduced the size of both menu.c32 and vesamenu.c32 quite a bit compared to the 3.x or 4.x series, so that's a guaranteed compatibility break in the future and throws off the assumption of ever increasing file size as an indication of newer versions.ДЇorcing everybody to go through a download when they will most likely be fine would be a very poor design decision, and will make Rufus inconvenient to use. I just think that a matching filename alone should be enough to trigger the prompt to download and replace the. I'm not looking to bloat the Rufus binary. I think the current method of downloading the. The originals could be renamed and placed alongside the new versions in case the user needed to recover them at some point. They're almost certainly ISOLINUX files and we probably want to replace them proactively to ensure compatibility. The specific filenames in question aren't exactly common, so I don't think that blinding replacing these files is necessarily such a bad idea. It looks like things changed again between 4.x and 5.x (see below). c32 format to break compatibility between 3.x (my example) and 4.x (Rufus). c32 files are more likely not compatible with whatever version Rufus happens to provide at a given time. c32 format to know how far cross-version compatibility extends, but I think it would be safer to assume that existing.

#COM32 FILE RUFUS DOWNLOAD UPDATE#

The next version will update OLD_C32_THRESHOLD as per your findings.

On the other hand, adjusting the size is very easy. Increasing the Rufus download size by 50% just for the sake of people using an old ISO doesn't seem very desirable. c32's, so it's just old ISOs that have a problem. ISOs that use a relatively up to date version of SysLinux should work just fine without having to replace. c32, so I definitely don't want to embed these files within Rufus always and blindly replace them. If you think a file check is not necessary, can you explain what you have in mind? The thing is, we get the filesize when scanning an ISO directory, which means we don't have to implement a cumbersome workaround where we would have to extract the file and peek into it for a version, if there is one. Why is a file size check necessary for this feature?Д«ecause few people need to download vesamenu.c32 and a check on file size, which can easily be adjusted from user reports such as yours, is much easier to implement when scanning an ISO than trying to check the c32 for a version which may or may not be present.

Com32 file rufus download