comp.lang.idl-pvwave archive: archive » CALL

Home » Public Forums » archive » CALL_EXTERNAL problems (re: DICOM)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: CALL_EXTERNAL problems (re: DICOM) [message #18400 is a reply to message #18327]

Mon, 27 December 1999 00:00

Karri Kaksonen
Messages: 27
Registered: October 1999

Junior Member

Richard,

I did almost the same thing but the other way around.
In my setup I used Callable IDL from my C-code and used
a commercial Dicom toolkit instead of Mallindkrodt.

I don't know if you find any help from this but the things
I have found to be necessary for my toolkit are:
set_port( pTran, "104" );
set_protocol( pTran, "tcpip" );
set_source( pTran, "NORDSTAR_MR_SCP" );
status = listen( pTran, &listen_fd);

In addition to this the PACS is usually set up to accept
connections from certain physical wires only. Which means
that you cannot just move your machine to another place in
the house and plug it in the net. At least in one hospital
they tied the legal machines to an IP-address and a physical
twisted-pair port.

I could not find anything wrong in your description of how
to do this. If it had been a Windows-machine I could easily
have added all kind of silly "special" gimmicks like opening
the socket with the "rb" flags. Tricks with TCP/IP byteorder
being different, cache-bugs in the NT etc.

--
Regards,

Karri Kaksonen
Picker Nordstar

Report message to a moderator

[Message index]

		CALL_EXTERNAL problems (re: DICOM) By: Richard Tyc on Wed, 22 December 1999 00:00
		Re: CALL_EXTERNAL problems (re: DICOM) By: Karri Kaksonen on Mon, 27 December 1999 00:00

Previous Topic:	How do I execute an IDL program from a shortcut in Windows 98?
Next Topic:	Puzzled about event loops

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Oct 11 00:54:56 PDT 2025

Total time taken to generate the page: 0.72073 seconds