Well even the CAESAR test doesn't seem to work here. But that's quite normal as my sniffer can't see any traffic. However, when I open up a terminal connection in VMWare I am able to see the data on the "real" pc.
But apperantly the SDConnect toolkit doesn't use that COM-port. I also found something else. If you go to C:\program files\SDConnect Toolkit\bin\ I guess there is the server that regulates the communication. In that folder there is a file called toolkit.ini that is a file that holds the settings
Code:
; Skip COM ports from Part D detection (Example: SkipComPorts=3,4,5)
;SkipComPorts=4
; Use only this COM ports for Part D detection (Example: UseComPorts=1,2)
; Anforderung Fuss/Probst
UseComPorts=2
There it would be possible to change the com-port from the default number 2 to any other.
I don't understand the meaning of the "Part D" and "Part D2" yet. Could there be some explanation??
It quite sucks for me. Its the first time I try to use it and I encounter all kinds of problems.
Yet another problem is that the software is supplied already installed on a hard disk. I don't got the Star software DVD with DAS and WIS and Xentry. And that seems pretty hard to find.. If somebody could help me on to that? That would be very nice
Bookmarks