Zadig crash on launch on Windows XP #25
Comments
|
I've been testing Zadig XP 2.1.0 on physical machines with Windows XP SP3 installed, and I have not observed any crash. Your report is also the only one I got about a crash on XP, and I have seen more than 1,000 downloads of the 2.1.0 XP version so far, without any similar report (so I have to assume that it worked for these other 999 XP users). This means that, whatever it is, it is linked to your specific environment, and without access to it, it will be very difficult to troubleshoot...
Whoever posted that is wrong. Zadig does not need .NET or any kind of additional framework to run. Since I can't replicate the crash, I'm afraid the only option I see would be for you to recompile Zadig from its source using Visual Studio 2012 or later, and run it in the Visual Studio debugger to see where it crashes. Or you can try installing DebugView and see if there are any messages that can be of interest there (as the latest verstion of Zadig will try to send some output to DebugView), but since it seems to crash on startup, I'm not sure there will be much to help. |
|
I had no doubt that this was a rare issue. No one ships or recommends software that crashes immediately, and Zadig comes recommended. But, there's a first time for everything. I tried it with DebugView and there were no messages. My system is a desktop Athlon 1.2 GHz with "only" 786 Mbytes of RAM. There's no chance Zadig needs some huge amount of RAM, is there? I watched in Task Manager, and at the point of the crash, Zadig has 10,688 K allocated. As for Visual Studio, I'm pretty sure this machine doesn't meet the minimum system requirements. |
|
OK, can you try this then?:
|
|
Okay. Here is the xusb.log output: |
|
Thanks. I'm not seeing much of anything suspicious with your devices. Can you confirm that you have a |
|
Yep. Riched20.dll is there. |
|
It looks like you don't have the |
|
USERPROFILE is already set to "C:\Documents and Settings\Operator" (2nd line of previous post). |
|
My bad. I thought that the value was empty and that the prompt was just repeated. Well, I don't have any further ideas, so I'm afraid you'll have to debug Zadig on that specific machine to find out why it crashes... |
|
One last thing you may want to try, to see if it helps, is download this sample |
|
Sorry. Thanks for the ideas, but it still crashes. I have been playing around, but nothing I have done has changed the situation yet. |
|
FYI, Booting Windows in Safe Mode made no difference in the problem. I tried a couple of other things with that xusb.exe Option "-i : print topology and speed info". Here is the output for my USB mouse: And here is the output for my TV/SDR Dongle: The crash occurs whether or not the dongle is plugged in. |
|
Same crash here, I cannot install Zadig (XP version). My system is an eBox 3310MX, running Windows XP SP3, processor is a Vortex86MX+. My plan is to use a SDR dongle as well, I'm using it flawlessly in other machines. |
|
Tried same steps you proposed:
|
|
Riched20.dll and riched32.dll are present on c:\windows\system32. |
|
I'm not seeing much of anything that looks wrong, and without being able to run a debugger on your machine, it will be very difficult to identify the cause of the crash. Also what happens if you go to the device manager and uninstall the |
|
I have very little space left but tell me the minimum necessary to debug and I'll try. Yes, same crash even with no dongle connected and driver removed. This is the exception thrown if it is of any help: |
|
Which version of Visual Studio and .NET should I try to install to debug Zadig? Minimum possible please, as I don't have too much space left. |
|
Visual Studio 2012 is what you should use, as this is the only version of VS for which I provide the solution files. Zadig is NOT a .NET application, so you don't need to bother about that. To debug Zadig, you will need to recompile libwdi by following this guide. I still haven't given up on trying to provide a debug version that works with gdb, but I've been busy with other things... |
|
Thanks Pete. I see the minimum requirement for Visual Studio 12 is Windows 7, but this machine only runs Windows XP. Do I need to recompile in this same machine, or could it be done in another one running Windows XP as well? |
|
Well, unless you got through a remote install of the debugger, you don't have to install VS on the same machine, and I remember using VS 2012 to remote debug an app on an XP machine in the past. |
|
Finally no way to install Visual Studio on that machine, there is very few space left. So I hope Pete can provide us a debug version or give up trying to use Zadig on that little box. |
|
I have the same issue while trying to use Zadig on an older PC with XP SP3 installed. Error code 0xc000001d at address 0x0040b9f9. |
|
I'll see what I can do, but I'm afraid to say that, with Windows XP having reached its official end of life, investigating XP specific issues has become low priority for me... |
|
Figured out, that a Zadig Version 1.1 works fine, thus for me no need to dig any further in the XP issue. |
|
I really understand your position, it sounds logical. Bt I'm sure that even when official Windows XP lifetime is over, it will still last for a while on lower end device such thinclients and so on. Anyway, thanks a lot for your great piece of software working fine on other platforms. |
|
I have just published a BETA version of Zadig that may fix some of the crash issues reported here. |
|
Oh nice !! I thought this was a lost cause :) |
|
Note: Zadig 2.1.1 has now been released. Please let me know if it also fixes this issue on XP. |
|
Hi Pete, sorry for the delay. No good news, zadig_xp_2.1.1.exe still crashes, "program encountered a problem and need to be closed". |
|
Pete, I'm sorry for the delay also. I no longer have the machine or environment to reproduce my original crash report. |
|
Since Windows XP is officially retired, and my time is too limited for that, I am not planning to spend any effort investigating XP specific issues. I will therefore close this issue. I will however accept a fix, if anybody still using Windows XP wants to investigate and try to patch the problem. libwdi/Zadig is Free Software for precisely that reason. |
I get the message "zadig_xp_2.1.0.exe has encountered a problem and needs to close" immediately on every launch of Zadig. I am using the XP-specific version. I have tried some older versions back to 2.0.1.161, and they all crash the same way. This happens immediately on running the program. Host is an older XP system, but fully patched to service pack 3. I installed the Microsoft .net framework, because I saw a post that it was required. Nothing changed. Detail from the error:
I am planning to use Zadig in connection with an SDR dongle, but I haven't even gotten that far yet.
The text was updated successfully, but these errors were encountered: