Dicom server 1.4.16(k) released !

This is translated from Russian - error is: instruction from address 0x00494965 referenced to memory with address 0x0061524d. Memory cannot be "written"/

And next error is: Access violation in modulr ntdll.dll ...read of address 00000000

OK, I tried it on two other comps. First is WinXP, limited user and 2nd with the Win7, also limited user
Result was the same.

First print attempt was sucessfull, but second was not good with error - Access violation in module cqDicom.dll.

UPD:
On Win7-64bits I've got the same messages

Quote from marcelvanherk

And if you try another printer?

Yes. For WinXP it was Samsung 1210 ML (network), for Win7-32 was Canon MF device connected directly.

Also I experimented with virtual PDFCreator and Microsoft XPS Document writer.
Result was the same - first time it ok, but in second got error like "Access violation at address 10031e18 in module cqDicom.dll Read of address 0000004c"

Hi, Marcel!

I did try this option "'print selected images on local ....'" .

And the result was the same - error in cqDicom.dll

Shure that's all will be corrected in the next release!

Thanks for your attention!

I tried this third option.

Situation is similar, but error came from the ntdll.dll.

Ok!
I deleted files from 'printer_files' directory. There was only one - 'accesstest.log' zero length.
Nothing has changed.
DICOM images for testing purposes I took from ClearCanvas examples.
It's looking like from CR, CT, DX, MR, MG, RF modalities.

Those images, that was inside of Conquest zip file ( HEAD EXP2) gave me the following errors
from the first attempt to print:
'dgate.exe - Application error
Intruction from address "0x00494965" referenced to memory address "0x0061524d" Memory can't be "written" '
And second message is - 'Access violation at address 7c910a19 in module "ntdll.dll" Read of address 0000000000'
And images can't be printed at all/

Now I'm tring to print from my examples.
Here I have two images from CT.
Using the second option - 'print selected images to ...'
and choose film format "4x6" I got the following:
'Access violation at address 7c910a19 in module "ntdll.dll" Read of address 0000000000'
But image is printed.

Now I' trying CR modality and
Conquest is printing in first time, but in second
it's gives me 'Access violation at address 7c910a19 in module "ntdll.dll" Read of address 0000000000'

Now MR modality
First attempt - everything is OK!
Second - error like 'Access violation at address 10031e18 in module 'cqDicom.dll Read of address 0000004c''

Everything was done with an images from ClearCanvas example.

I only changed 'LargeFileSizeKB = 24576'

# This file contains configuration information for the DICOM server
# Do not edit unless you know what you are doing


[sscscp]
MicroPACS                = sscscp
Edition                  = Personal


# Network configuration: server name and TCP/IP port#
MyACRNema                = CONQUESTSRV1
TCPPort                  = 5678


# Reference to other files: known dicom servers; database layout; sops
ACRNemaMap               = acrnema.map
kFactorFile              = dicom.sql
SOPClassList             = dgatesop.lst


# Host(ignored), name, username and password for ODBC data source
SQLHost                  = localhost
SQLServer                = I:\dicomserver\Data\dbase\conquest.db3
Username                 = 
Password                 = 
SqLite                   = 1
BrowseThroughDBF         = 1
DoubleBackSlashToDB      = 0
UseEscapeStringConstants = 0


# Configure database
TruncateFieldNames       = 10
MaxFieldLength           = 254
MaxFileNameLength        = 255
FixPhilips               = 0
FixKodak                 = 0
KeepAlive                = 0
LargeFileSizeKB          = 24576
PrintSquareLandscape     = 0
UseKpacsDecompression    = 1
ZipTime                  = 05:
UIDPrefix                = 1.2.826.0.1.3680043.2.135.734745.46421390
EnableReadAheadThread    = 1
PatientQuerySortOrder    = 
StudyQuerySortOrder      = 
SeriesQuerySortOrder     = 
ImageQuerySortOrder      = 
EnableComputedFields     = 1
IndexDBF                 = 1
PackDBF                  = 0
LongQueryDBF             = 1000
TCPIPTimeOut             = 300
FailHoldOff              = 60
RetryDelay               = 100
RetryForwardFailed       = 0
ImportExportDragAndDrop  = 0
QueueSize                = 128
WorkListMode             = 0
WorkListReturnsISO_IR_100 = 1
DebugLevel               = 0
Prefetcher               = 0
LRUSort                  = 
AllowTruncate            = 
DecompressNon16BitsJpeg  = 1
UseBuiltInJPEG           = 1
LossyQuality             = 95
IgnoreOutOfMemoryErrors  = 0
NoDICOMCheck             = 0
PadAEWithZeros           = 0
FileNameSyntax           = 4


# Configuration of compression for incoming images and archival
DroppedFileCompression   = un
IncomingCompression      = un
ArchiveCompression       = as


# Names of the database tables
PatientTableName         = DICOMPatients
StudyTableName           = DICOMStudies
SeriesTableName          = DICOMSeries
ImageTableName           = DICOMImages
DMarkTableName           = DICOMAccessUpdates
RegisteredMOPDeviceTable = RegisteredMOPIDs
UIDToMOPIDTable          = UIDToMOPID
UIDToCDRIDTable          = UIDToCDRID


# Banner and host for debug information
PACSName                 = CONQUESTSRV1
OperatorConsole          = 127.0.0.1


# Configure email of error messages
MailHost                 = 
MailPort                 = smtp
MailSignon               = 
MailFromName             = 
MailRcptName1            = 
MailCollectTime          = 1
MailWaitTime             = 10


# Configuration of disk(s) to store images
MAGDeviceThreshhold      = 0
MAGDeviceFullThreshHold  = 30
IgnoreMAGDeviceThreshold = 0
MAGDevices               = 1
MAGDevice0               = I:\dicomserver\data\
NightlyCleanThreshhold   = 0

Quote from marcelvanherk

is there something special with drive i:\ ?

Nothing !

This is simple windows disk on primary partition, in my working notebook.
And such things are happened on 4 comps. Three of them has Russian windows on board,
but one has English Win 7.

Maybe I will upload the whole directory of Conquest to some file exchange service?

Quote from marcelvanherk

But maybe it is specific to a russian OS.

Yes. A lot of russian words.

Marcel,
can I give you a reference to my Bitcasa file through the private messages?
It's my zipped folder+examples. Size ~ 93Mb.