Why the Outdated Uploaded & Compressed Method #762
Replies: 3 comments
-
Hey @dorkydicken , thanks for reporting your issue. In our latest winesapOS 3.4.0 update, we tried to simplify this whole process. We are always open to suggestions on more ways to improve! I am not sure what you mean by the "outdated upload" or how there is a "compressed image inside of another compressed image". There is only one IMG file inside of a single compressed ZIP file. Due to storage restrictions from our hosting provider and to help with users who have metered ISP connections, we compress our images. The process to flash the image is:
Let me know if that helps or not. If not, could you also provide the exact steps for us to replicate your issue? |
Beta Was this translation helpful? Give feedback.
-
The methodology of uploading a compressed image inside another compressed image. .img is already compressed, same as with an .iso, there's no need to put it inside of a .zip In my experience of trying to deal with that on windows it confused the windows system and I had an extracted folder with the name .img at the end of it, whereas just straight uploading the img file wouldn't cause that inconsistency on nearly any os. Windows 11 natively handles zip files, so that might be where the issue came from, the goofy folder name etc. I did finally get it to write with Rufus, balenaEtcher didn't like the very exact same img for some reason or another, quite possible due to the double compression. On top of that sometimes, very rarely it can cause corruptions when extracting. Then for some reason when I move the .img file to another folder outside of the folder with .img at the end of it, it didn't want to write successfully and would just fail, resulting in a nonbootable usb stick, whereas if I left it in that funny folder name it'd write correctly. It's like those people who compress a rar and then put it inside a zip and then inside 7z and then into a xz file, it doesn't really change the size one bit by that much of a difference, if anything it creates more problems. Is what I meant by being outdated. |
Beta Was this translation helpful? Give feedback.
-
Thanks so much for the clarification. The IMG file, in our case, is actually a raw uncompressed image format. It is basically a 1:1 copy of a disk drive we use to build winesapOS. https://en.wikipedia.org/wiki/IMG_(file_format) We compress it to save space. Below are the size comparisons. You can see the size differences when looking at the file properties in Windows, too.
In Windows 11, if you double-click on a ZIP file, it will decompress it to a temporary directory. I find that usually has issues with most programs. I recommend right-clicking on the ZIP file and select "Extract All..." instead. Otherwise, it sounds like Rufus was able to read from that temporary directory. I will update our documentation to mention that. Hopefully that helps to clarify the situation. Let me know if you have any other questions, comments, or concerns! |
Beta Was this translation helpful? Give feedback.
-
Isn't this type of uploading obsolete now anyways?
It also wants to cause the user issues when attempting to write to a usb stick, because it's a compressed image inside of another compressed image.
Redundant much?
Both Rufus and BalenaEtcher don't want to write the image and say it's failed.
Beta Was this translation helpful? Give feedback.
All reactions