Eman problem with Windows SP3

[DArnold]

We encountered an issue with Eman when run on Windows SP3. Sharing the information here, recognizing this is unsupported Goodie code.

We found 2 problems with the following code from OcEMMWDisk>>doesNotUnderstand:
self instance ifNil: [ | tempDiskStream |
tempDiskStream := ( self fileName asAbtFileSpec
cfsStreamReadWriteIfError: [: e |
^ ExError newChild description: e description; signal ] ).

1. First #cfsStreamReadWriteIfError: results in a busy error under SP3. This is may be unique to our application since we are emailing as part of a MS Word OLE conversation. Obviously in our case Word still has the file open. This worked fine prior to SP3. We could have changed our code to make a copy of the Word document, and email the copy, but since Eman only reads the file, there is no need to open the file as read/write. So we have changed the code to use #cfsStreamReadIfError: instead. Others may prefer the concurrence protection that #cfsStreamReadWriteIfError: and SP3 now offers.

2.The error handling is broken; #cfsStreamReadWriteIfError: answers a CfsError on failure, which does not understand #description. Since we are already changing this method we just used #printString instead (i.e. ^ ExError newChild description: e printString; signal )

Dave

[marten]

We encountered an issue with Eman when run on Windows SP3. Sharing the information here, recognizing this is unsupported Goodie code.

We found 2 problems with the following code from OcEMMWDisk>>doesNotUnderstand:
self instance ifNil: [ | tempDiskStream |
tempDiskStream := ( self fileName asAbtFileSpec
cfsStreamReadWriteIfError: [: e |
^ ExError newChild description: e description; signal ] ).

1. First #cfsStreamReadWriteIfError: results in a busy error under SP3. This is may be unique to our application since we are emailing as part of a MS Word OLE conversation. Obviously in our case Word still has the file open. This worked fine prior to SP3. We could have changed our code to make a copy of the Word document, and email the copy, but since Eman only reads the file, there is no need to open the file as read/write. So we have changed the code to use #cfsStreamReadIfError: instead. Others may prefer the concurrence protection that #cfsStreamReadWriteIfError: and SP3 now offers.

You mean #cfsStreamReadOnlyIfError: ...

2.The error handling is broken; #cfsStreamReadWriteIfError: answers a CfsError on failure, which does not understand #description. Since we are already changing this method we just used #printString instead (i.e. ^ ExError newChild description: e printString; signal )
Dave

This is also true for
OcEMServerMessageManager>>consolidateMessageHandles

I've changed this in the distribution and republished it ...

Marten

[DArnold]

thanks Marten. Where is the current distribution of Eman?
The link in the goodies section (http://www.schrievkrom.de/uk/tips/small ... /index.htm.) is broken

Dave

[a3aan]

http://vastgoodies.com/maps/Obdobion%2C%20EMan%20-%20Distribution/EMan%20v2.0%20%20-%20004