Jaf
Posts: 70
Joined: 2/1/2006
Status: offline
|
quote:
I tried h2acons on a couple of largish files saved by FireFox, and it crashed. This was in a COMMAND.COM DOS box under Windows 2000. I can't access CMD.EXE on the computer at work because it's been prohibited by the IT Dept. on grounds of security. Is COMMAND.COM the reason, i.e., h2acons didn't have enough resources? Forgot to try GUI Detagger on those files, but will try to remember if I see this again.
There have been some bugs that I've fixed recently that could cause crashes. They're comparatively rare, but caused by particular combinations of HTML in the source code.
Do you mean crashes as opposed to "hung"? Large files can cause performance issues, and again I've made a number of recent improvements when dealing with both large files (especially long forum pages) and when processing 1000's of files at one time. These improvements make processing huge files (typically multi-Mb nested tables) up to 100 times faster, meaning they finish in a reasonable time instead of appearing to hang forever
These changes will be made available in the next release, but in the meantime I hope to soon get an "Early Adopter" version out, so any registered user who wants to try them can sign up for that.
If COMMAND.COM is a genuine DOS box, then I wouldn't expect h2acons to even run, as it's not a DOS program, but a windows console app.
In the old DOS boxes memory used to be restricted to around 1Mb. I can see that being a problem. Detagger loads the whole file into memory at various points, so the memory required probably peaks at a small multiple of the file size. In a restricted memory environment that could indeed be a problem. It's not usually a problem under Windows because it can use virtual memory, and in any case the maximum requirements are probably a few Mbs (or 10s of Mbs) which is small by today's standards.
Also one final point, the windows version of Detagger can itself be run using the same command line arguments as h2acons. I don't normally recommend this as - being a Windows app - it tries to grab focus. You can limit this to some extent by setting the behaviour under the
Settings -> Drag'n'Drop
menu option. These options are intended to configure what happens when you drop a file on a Detagger icon, but the also affect the behaviour of Detagger when run from a command line. If the conversion goes well, you can suppress the status dialog, the invocation of the main program, and the automatic launching of the results file.
However I wouldn't expect the windows version to perform any better (and probably worse) in a true command line environment.
quote:
Please can you make h2acons announce its version number when you enter h2acons /? the way that most command line utilities do?
That's a good idea. I've implemented this. The existing version shows the version number when it runs, but only as "2.4". I've changed that to show the full version number (currently "2.4.0.25" as I write), and to also show that on the help summary.
Since we are also in contact via email over this issue, I have sent you the latest version with this change in. Hopefully this will help us determine what the problem is.
|
Printable Version
h2acons queries - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread