Beware of fake sites
This is the same as bug #88. Both have been temporarily fixed in source and the fixed binary will be released shortly.
This has been fixed in source, will be releasing a binary soon. The fix is really only temporary, as I try to determine the actual root cause of the issue (why the program is getting the wrong info on drive type from the OS). But if I can't root cuase this, I will at least try to get an update out soon.
Update translation line numbers
Merge commit 'ee3007'
Minor cleanups
Store selected filter from QFileDialog and make that the first one in the next file selection
initial merge for setup config
Please don't post empty merge requests. Let me know when you have something to contribute.
Merge commit '5cf549' into footstark2
Sorry for the massive delay. See my blog. I have merged this in a modified form, as I had to start from scratch on a new system (I don't have any Windows systems), and setting up the laptop forced an upgrade to the QT build environment, making this merge difficult (but I took the heart of it and made it work). My next step is to figure out why these odd drive types fail my initial screen in the first place (likely MS not following their api protocols, again).
Fixes startup crash with virtual devices
Update to QT 6.8, cleanup areas
Update ignore for all build* folders
Sorry for being gone for so long
win32
Merged, thanks.
Fixed an Italian translation
Merged, thanks.
Another fix to Italian translation
No changes.
Research & Develop
merger
No changes to merge.
This is awesome.
win
Sorry, didn't see this merge request earlier. I have had to greatly reduce the attention I pay to this app as I am working 60+ hours a week for a startup (even during lockdown - remote access). Add to that the constant changes to Windows (a Windows 10 update a couple of years ago completely invalidated a different bug fix, which would require a lot of extra code to detect and work through depending on Windows updates installed), and I just haven't had time to properly fix some of these issues. Is...
When you have something to merge, let me know. Closing this for now.
Nothing to merge.
Thanks, this is certainly very useful information.
Fail to start this application on windows 10.0.14393
Recover data of my external HDD writen by win32 Disk Imager by mistake
Closing as there isn't anything I can do to fix this. We already have a bug to add drive size to the selection drop-down.
There are utilities on the internet that can possibly help with data recovery. Unfortunately, most of my time and work is Linux based (this is the only Windows thing I do, and even then I don't have much free time for it anymore). Depending on how much was overwritten, you could be lucky and just need to rebuild your partition table. There are apps that can discover existing partitions and rebuild the table with 99% data recovery in this instance.
Did you try safely removing the drive after resizing it and then check with Win32DiskImager? We don't always get refreshed partition info if the OS makes changes without doing a full write (the OS can cache this info)
Cancel Read at definable point, either size or percentage
Heh. Ok. Interesting suggestion though.
Unfortunately, I have to put a lock on it otherwise Windows will be updating the filesystem as I am trying to read from the raw device (and Windows won't allow that). It would be like trying to read a file as you are formatting the media the file is sitting on. This is more of a Windows limitation, not an app limitation. The other part of this is that the mechanism to read from an image file vs a raw device is not separate code. The program passes a file handle to the read function. That handle can...
Unfortunately, I have to put a lock on it otherwise Windows will be updating the filesystem as I am trying to read from the raw device (and Windows won't allow that). It would be like trying to read a file as you are formatting the media the file is sitting on. This is more of a Windows limitation, not an app limitation.
Similar problem with RAM Disk users, but with encryption software.
Duplicate to error #47. I know what the problem is, but have no Windows system to reproduce/debug/fix/test at the moment.
This is a large part of why I haven't been able to do much development on this app in a while. Windows keeps changing little things that are devastating to this app, and it takes a lot of time and effort to reproduce the issue, then debug it. From the start, I have wanted to keep the code clean and functional across Windows releases. By clean, I mean no code that looks like this: If Windows XP do XPfunction(custom params) else if Windows Vista do Vista(custom params) else if Windows 7 ... You get...
This is very likely similar to bug #47. I haven't had time and resources (i.e. Windows system) to focus on this app in a while. Not sure how soon I will be able to get back to it.
App does not start up due to RAM Disk
Closed as it is a duplicate. Yes, I know what the issue is. No, I haven't had time & resources simultaniously to address it. Really sorry about this.
My appologies. I have not had any spare time to work on this project in a while. I hope to get back to it soon. Until then, the fix was added to the code base and will be in the next release. If you wish to test it out, feel free to check out the code and build it.
Do not create uninstall shortcut in start menu
Thant you for your contribution. This must have been a default for the installer that I just overlooked. Your merge is clean so I'll go ahead and pull it in.
Other than changing the file formatting from Unix to Dos (adds an extra character to each line), I don't see any changes. Please specify what has changed, so I can properly review this.
This is very useful information, thanks. Looks like MS has changed Windows internals again. I don't have an immediate solution at this time, and I am not sure when I will be able to get back to this.
Is there an actual merge request coming or did you inadvertently press the wrong button?
Language is not the same as locale
I'll take a look at this and see what I may have set wrong. Could be a QT library issue (which I don't control).
Thanks. I'll review this and add it shortly. Looks very clean and easy to pick apart (not a massive amount of changes in one pull). Tobin
Yes. There is no change in the file type as far as Win32DiskImager is concerned. It only reads/writes raw binary data, regardless of actual file format.
Thank you for your contribution. I renamed diskimager_en.ts to diskimager_ja.ts and committed it to the tree. Will copy the .qm file to the files area for users to download.
Add Japanese translation
Free Space Error
Remove unused DLL files from installer
Simple encryption support for when reading and writing to keep files safe from outside viewers.
Not sure if this is really feasible within the scope of this application. If the image that is being saved is coming from a device already encrypted, then the image will retain that encryption. If you are looking to share an image of unencrypted files, and only want encryption during the transfer to a 3rd party, there are other apps better suited for that. Also, by creating encryption support, I run the risk of US export restrictions. This alone is enough for me to reject this idea. Sorry.
Adjust window size for UHD screens
Prevent writing to usb hard drives
I am aware of this happening. Unfortunately, the current code base and GUI doesn't give many options for more selective control, and the WIndows APIs are horrid to say the least. I also have a dilema; on one hand I have users (such as yourself) wanting this fixed, but I also have an open feature request wanting the exact opposite. I will make no promises for the next release (I'm taking vacation time soon to start working on it again). Main priority is to address SD detection and possibly image compression...
Folks, please don't continue to report this. The fix is in the tree. It will be in the next release. Thanks.
Sorry, no news to report. The information you have provided is very useful, though. I will use it to further debug the problem when I can get some spare cycles. Thanks.
Win32DiskImager does not tolerate a mounted pCloud Drive
In the UI some input fields are too tiny
Closing this as it is a duplicate of #61. Please direct all future discussions to that bug, thanks.
Hmmm. This looks like just an installer wrapper, as I don't see any real code changes to Win32DiskImager (just binaries in the git tree). I'll keep this as an open feature request for when I get some serious dev time (hopefully soon).
I have added a change in the code that 'should' hopefully fix this issue. I'll have a dedicated Windows development system online soon (reorganizing my home office). I think the new system has the capability to test this feature (I'm mostly a Linux developer).
I'm not sure what would be required for a portable version. The program is written to be as light-weight and touch friendly as possible, without actually having a touch system to test on. I am open to any design changes you can come up with that would help. My development time has been extremely limited in the past few years, but I am trying to rebalance my work schedule. Hopefully, I can resume work on this project again soon.
Application crashes at startup
Further posts to this bug are being turned off. We already have an open bug tracking this duplicate issue. Since we know the root cause, we really don't need any additional 'me too' posts. Thanks.
Bad time informations with big files
This is a known issue and has a fix pending the next release.
Application crashes at startup
Yes, this is the same problem as the ramdisks, network mounts, etc. Pretty much any drive mounted that Win32DiskImager can't get info on using the Windows APIs (as documented) are causing the program to crash on boot. I haven't had time to revisit this, but I do have the problem fully root caused.
We do have checks in place currently. We ensure that the device is on the USB bus, it's marked as removable, and it's not above a certain size (which exact value escapes me at the moment, but it's on the order of 130GB or 250GB or something along those lines, I believe). These checks have caused problems with some card readers already, so any check is a bit of a trade-off. I don't mind the idea of exposing that value to the user, making it configurable, but I believe that one of Tobin's main goals...
It is possible that either QT is reducing duplication or some strings (i.e. filenames, directory names, etc) are not translated. If you see a string in the source that is NOT showing up in the translations and should be, please let me know. Thanks,
I'll look into it. I assume that this is to read/write the USB bridge device in raw format (what we do with SD and USB memory drives currently)? First, I would need to add code to show the drive info in the drive dropdown list as far too often people complain that it overwrote the wrong device (something I have not been able to reproduce). The code specifically blocks these devices to prevent that from happening. Bear in mind that this will be painfully slow, regardless of USB bus speed (which we...
Leaving this as open for now. This will require some heavy rework to the code and interface to support.
This should be fairly straight forward to add. I'll add it to the laundry list of todo items for the next release.
Add command option to specify the source of the image file
Make it possible to read or write to a file on a samba share device
I think once I fix the bug that is causing crashes when network drives and ramdisks are assigned drive letters, this should also resolve itsself. But I will do my best to verify it first. I am in the process of rebuilding my home network infrastructure to be able to support this and many other projects properly.
Respect "Start in" directory
This was added, but I found a bug in the code (hence why it fails). It has been fixed in the git tree and will be available in the next release.
This was also added to the downloadable translations for v1.0 for immediate use. I should have mentioned that when I marked it as pending.
Add Spanish translation
ISO images
automatically create hash-file after writing an image
This should be doable. All we would need to do is check if the hash type is enabled on read and write a file to <filename>.<hashtype> (ex: myimage.img and myimage.MD5).
automatically create hash-file after writing an image
Show how much time is about left
Closing as there has been no update from the original submitter as to what needs to change from current.