In my defense, when I released the first version, I had seen a total fo two 2 ZIX archives, and coded the utility based on what little knowledge I gained from dismantling those, plus incomplete and somewhat erroneous information found elsewhere.
It's little wonder that files should pop up which confuse UnZixWin. There are valid reasons why a person might want to extract such a file. Perhaps they want to peek inside it and see what it does. Perhaps they feel they have no option but to extract and execute these files. Perhaps they don't trust in any warnings from me. Or, perhaps they are just plain stupid.
In any case, it would be wrong to try to actively prevent users from doing with these files what they want.
All I can do is issue warnings. Your system, your rules. Extracted file is crap. Program doesn't do anything. Why Visual Basic? Why such a complex license aggreement? Why all the warnings? Where's your website at?
I used your program to extract an AVI file, but the result is garbage. It won't play in any player, whatever I do and whatever I install. You messed up! No I didn't. Crap in, crap out. Which is just as infested with spyware as WinZix is. You have simply come across such a file. I've come across at least one myself. So you never know. If it's not kosher, the status bar flashes pink to warn you. So, in short, cut your losses and throw that AVI away.
I ran UnZixWin and opened a Zix archive. But it just says 'Analyzing I've been waiting for hours, and nothing! Yes I did. So, I did like you said and downloaded the new version. It still won't work. Now what? When I run UnZixWin.
What's that about? You need to have the Visual Basic runtimes installed on your computer. For many users, these files have already been installed by other software, or perhaps by Windows Setup itself. Run that, accept Microsoft's end-user agreement, to extract the installation package. Then, run that package to set up the runtimes. After this, UnZixWin should run without trouble. DLL, a dll which is installed with Internet Explorer versions 5 and later. It is highly likely to be on your system already.
But if you don't have Internet Explorer installed, or have uninstalled it manually, you may get complaints about this file being missing. Because then you would see this utility in six months instead of right now, when it's needed.
It has already saved lots of people lots of grief. Why don't you supply a setup program like regular folks? Then nobody has to go through this stuff with the VB runtimes.
I felt people might be wary of setup programs after encountering the ones which infested their computers with spyware. Being able to run a utility out-of-the box was, I felt, a welcome change of style.
What's your take on it? I've tried to mimic the legalese practised by other software vendors, up to a point. You're probably using version 0. You should get hold of version 0. In my defense, when I released the first version, I had seen a total fo two 2 ZIX archives, and coded the utility based on what little knowledge I gained from dismantling those, plus incomplete and somewhat erroneous information found elsewhere.
It's little wonder that files should pop up which confuse UnZixWin. There are valid reasons why a person might want to extract such a file. Perhaps they want to peek inside it and see what it does. Perhaps they feel they have no option but to extract and execute these files. Perhaps they don't trust in any warnings from me.
Or, perhaps they are just plain stupid. In any case, it would be wrong to try to actively prevent users from doing with these files what they want.
All I can do is issue warnings. Your system, your rules. Installation wants to replace newer DLLs. Extracted file is crap. Why Visual Basic? Why such a complex license aggreement? Why all the warnings? Where's your website at? Due to some requests, I've added multiple-file export support. Bug Fixes: The main form would minimize itself every time a file was extracted, giving users who need to extract maybe hundreds of files a real headache.
This was due to a "feature" in the forms engine. While showing the progress dialog, I disabled the main form. It turns out that if you unload a child form when the main form is disabled, the whole app dives into the taskbar. Go figure. When the parsing encountered a file with a size of 0 bytes and a compressed size of 0 bytes, it assumed an error in, or corruption of, the archive. Turns out that zero-size files are perfectly legal, so I now allow for them by relaxing some of the checking.
Some minor flaws were fixed, which I hope nobody noticed anyway. Here's a quick rundown: Now handles and decompresses the new ZIX 2. This only applies to the credits screen and a certain error message so far. When I try to install version 0.
Don't fret. I'm looking at the setup program. It's the big square one with the picture of the computer and the floppies. I used your program to extract an AVI file, but the result is garbage.
It won't play in any player, whatever I do and whatever I install. You messed up! No I didn't. Crap in, crap out. Which is just as infested with spyware as WinZix is. You have simply come across such a file.
I've come across at least one myself. So you never know. If it's not kosher, the status bar flashes pink to warn you. Make sure your're not still seeding the file. If it's a media file, make sure your media player isn't still having it loaded. UnZixWin versions 0. That means that no other program can have it open for reading or writing at the time. This problem will go away in the next release.
I ran UnZixWin and opened a Zix archive. But it just says 'Analyzing I've been waiting for hours, and nothing! Yes I did. So, I did like you said and downloaded the new version. It still won't work. Now what? When I run UnZixWin. What's that about? You need to have the Visual Basic runtimes installed on your computer.
For many users, these files have already been installed by other software, or perhaps by Windows Setup itself. Run that, accept Microsoft's end-user agreement, to extract the installation package. Then, run that package to set up the runtimes.
After this, UnZixWin should run without trouble. DLL, a dll which is installed with Internet Explorer versions 5 and later. It is highly likely to be on your system already.
But if you don't have Internet Explorer installed, or have uninstalled it manually, you may get complaints about this file being missing. Because then you would see this utility in six months instead of right now, when it's needed. It has already saved lots of people lots of grief. Why don't you supply a setup program like regular folks? Then nobody has to go through this stuff with the VB runtimes. As of version 0. The new version requires some external components which require registration.
However, I resisted a setup package for quite some time. I felt people might be wary of setup programs after encountering the ones which infested their computers with spyware. Being able to run a utility out-of-the box was, I felt, a welcome change of style. What's your take on it? I've tried to mimic the legalese practised by other software vendors, up to a point.
0コメント