My last request for the evening... I would like to see parchive DOS retargeted as a Win32 command line application. I can't imagine that there is anyone out there that has a use for an old 16 bit DOS application since no one not on Windows would run this and most of us who are on Windows would run it better as a Win32 app.
And less esoteric... my gui shell application is having trouble reading the output from par.exe... it looks like no data is coming back on either STDOUT or STDERR. Very odd but hopefully if the application were retargeted...
And no, I'm definitely not a programming god so I doubt there is a chance in hell I would be able to rebuild/recode the original source myself to do what I wanted to do.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
par.exe is nothing more than a spinoff from par for Unix. The source just happens to compile with djgpp, so it's easy to make the dos version with that.
If you know of a good cross-compiler that can build Win32 apps on Linux, I'll be happy to try and compile a Win32 version, but I'm not going to do much work on it.
The source should compile on most C compilers, so if you have a compiler on your box, just grab the sources and see if they compile.
This also means that the app follows some Unix conventions, such as outputting progress info etc. to stderr, letting the shell do the glob expanding, etc.
Outputting the version info is a good thought, though. I'll stick it in right now.
Willem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, I'll take one out of four on my requests. Still, I'm stuck in a difficult position because it seems I have absolutely no progmatic way to retrieve the output from the program making it useless to automate from inside another program. Once I complete my current project perhaps I will dig around in the source code to see if I can't figure out what's going on.
As a quick note, I did download the latest source and attempt to compile using MS Visual C++ 7.0. There were a larger number of syntax errors though and even trying to go through and resolve them I had a hard time understanding what the intent of the code was to correct the syntax.
And an after thought... perhaps a new feature to write the output to a file taken in as a command line argument. This would seem to be an easy request to implement and would be compatible so would require little testing and mucking around with to implement on multiple platforms.
Thanks for all your hard work, it looks like PAR files are already transforming many of the newsgroups I download from.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With a modification to types.h and fileops.c; and the addition of a readdir.c/.h that I borrowed from apache's source (first place I knew that had one) (and linking with the MS library to make it resolve wildcards, I was able to succesfully compile the program under MSVS 6. The problem I have now is that the MD5s don't match anymore.
Checking a.par
a.par: PAR file corrupt:control hash mismatch!
Which is not true because the real version of par.exe has no problems with the par file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My last request for the evening... I would like to see parchive DOS retargeted as a Win32 command line application. I can't imagine that there is anyone out there that has a use for an old 16 bit DOS application since no one not on Windows would run this and most of us who are on Windows would run it better as a Win32 app.
And less esoteric... my gui shell application is having trouble reading the output from par.exe... it looks like no data is coming back on either STDOUT or STDERR. Very odd but hopefully if the application were retargeted...
And no, I'm definitely not a programming god so I doubt there is a chance in hell I would be able to rebuild/recode the original source myself to do what I wanted to do.
Some comments here:
par.exe is nothing more than a spinoff from par for Unix. The source just happens to compile with djgpp, so it's easy to make the dos version with that.
If you know of a good cross-compiler that can build Win32 apps on Linux, I'll be happy to try and compile a Win32 version, but I'm not going to do much work on it.
The source should compile on most C compilers, so if you have a compiler on your box, just grab the sources and see if they compile.
This also means that the app follows some Unix conventions, such as outputting progress info etc. to stderr, letting the shell do the glob expanding, etc.
Outputting the version info is a good thought, though. I'll stick it in right now.
Willem.
Well, I'll take one out of four on my requests. Still, I'm stuck in a difficult position because it seems I have absolutely no progmatic way to retrieve the output from the program making it useless to automate from inside another program. Once I complete my current project perhaps I will dig around in the source code to see if I can't figure out what's going on.
As a quick note, I did download the latest source and attempt to compile using MS Visual C++ 7.0. There were a larger number of syntax errors though and even trying to go through and resolve them I had a hard time understanding what the intent of the code was to correct the syntax.
And an after thought... perhaps a new feature to write the output to a file taken in as a command line argument. This would seem to be an easy request to implement and would be compatible so would require little testing and mucking around with to implement on multiple platforms.
Thanks for all your hard work, it looks like PAR files are already transforming many of the newsgroups I download from.
With a modification to types.h and fileops.c; and the addition of a readdir.c/.h that I borrowed from apache's source (first place I knew that had one) (and linking with the MS library to make it resolve wildcards, I was able to succesfully compile the program under MSVS 6. The problem I have now is that the MD5s don't match anymore.
Checking a.par
a.par: PAR file corrupt:control hash mismatch!
Which is not true because the real version of par.exe has no problems with the par file.