Hi Eduard and Bushranger,
I played with the WebGate a bit too. Basically it bypasses the dicom server completely - it runs even when the server is down. The ASP pages connect to a database through standard windows calls. I am sure that EXCLUDES using the built-in dbaseIII driver for WebGate. I got it to run by installing an microsoft SQL server, and configuring a conquest dicom server to use that - all default settings except using filenamesyntax of 4 or 9 (.dcm extension).
The DICOM images are served to the client by setting a virtual directory to the data directory of conquest (I gave anonymous users read and browse rights - not very safe). Start - settings - control panel - admin - IIS - local computer - web sites - default web site - new virtual directory; Alias img - directory c:\dicomserver\data - rights read/runscripts/browse.
EZDicom must have been extended to be able to retrieve images over a http protocol. This is not hard to do, I managed to get the K-PACS viewer to do that too. I used some stuff from http://www.cryer.co.uk/brian/delphi/wininet.htm.
So far so good. I managed to allow localhost to run the OCX's and then - nothing. No images appeared, whatever I tried. I verified generation of the URL's of the dicom images by adding <%Response.write AXParam%> to series.asp and its shows lots of stuff like:
Name-CT-20051101-Specials^RTprostaatBlaas|Name-CT-20051101-Specials^RTprostaatBlaas||1.3.12.2.1107.5.1.4.49205.30000005110110110064000000365|
http://localhost/img/20505943/1.3.12.2.1107.5.1.4.49205.
30000005110110110064000000365_0002_000084_11706165340006.dcm,...
Eduard can you help?
In any case, I would like to add in the future a similar option to the built-in CGI web server, using an OCX derived from K-PACS. This would allow any database driver to be used since the server would provide all information to the CGI program.
Marcel