K
Kenneth H. Brannigan
Hello,
I going mad trying to figure this out. I am using a process class to kick
off an executable that converts HTML to JPG files. If the HTML is very large
(Over 100,000 characters) the process launches the EXE and just sits. At
first I thought it was the EXE but if I run the same HTML through it from
the command line it works perfectly. I then decided to try and use classic
ASP Shell command. Same thing there. I also tried the System Task Scheduler
and again it hangs on large HTML files. All this was done on a windows 2000
Server machine.
I then decided to try it on Windows XP. IT WORKED!!! I know this HTML2JPG
converter uses the IE ActiveX Object. What I do not know is why it has
problems on Windows 2000 with only large HTML pages. Small ones work
perfectly and no matter what typing at the command line works. Is there
anything I can do to have Windows 2000 handle this process stuff like
Windows XP??
Please any help would be great!!!!
Thanks,
Ken
I going mad trying to figure this out. I am using a process class to kick
off an executable that converts HTML to JPG files. If the HTML is very large
(Over 100,000 characters) the process launches the EXE and just sits. At
first I thought it was the EXE but if I run the same HTML through it from
the command line it works perfectly. I then decided to try and use classic
ASP Shell command. Same thing there. I also tried the System Task Scheduler
and again it hangs on large HTML files. All this was done on a windows 2000
Server machine.
I then decided to try it on Windows XP. IT WORKED!!! I know this HTML2JPG
converter uses the IE ActiveX Object. What I do not know is why it has
problems on Windows 2000 with only large HTML pages. Small ones work
perfectly and no matter what typing at the command line works. Is there
anything I can do to have Windows 2000 handle this process stuff like
Windows XP??
Please any help would be great!!!!
Thanks,
Ken