On Thu, 07 Feb 2019 11:26:15 -0600, Savageduck
wrote:

Tony Cooper wrote:
On Thu, 07 Feb 2019 21:48:48 +1300, Eric Stevens
wrote:

I have 436 photographs of the front and back of coins. I am trying to
use variables to organise them in matched front and back pairs. Every
thing is going well until I get to apply the data sets when I get the
message "Could not apply the data set because of a disk error".

PSErrorLog.txt is full of records such as "2019:02:04 15:27:14 :
e:\ps\ps20\win64_release\20181219.r.30\photoshop\m ain\interfaces\utrackresouceimp.h
134 : REQUIRE failed".

Searches on the Internet suggest that it may be something to do with
the scratch file. Normally it is on drive C: which has 298GB free. I
have tried switching it over to D: which has 720GB free but it makes
no difference.

I have posted my problem on Adobe forums but so far have not received
any reply.

Does anyone have any idea of what my problem could be and what I can
do to fix it?

I really don't follow your problem, but I also have several hundred
photos of the front and back of coins. Each photo was given a file
name like 121-1855a or 121-1855b. 121-1855a is the face of a coin
minted in 1855 and 121-1855b is the obverse. The first number
indicates the coin is a $1.00 US gold coin and this is the 21st $1.00
US gold coin in the series. The $5.00 US gold coins have 5xx numbers
and so on.

There is a third photo in my series that is 121-1855s that is a photo
of the "slabbed" coin after it was sent to a professional grading
service. The 1855 Seated Liberty $1.00 gold coin is valued anywhere
from $225 to $7,000 depending on the grade assigned. The grading
service (PCGS) assigns a grade based on condition and seals the coin
in a container called a "slab".

I don't understand why a simple file-naming system would not display
the coins in the proper sequence using, say, Bridge.

I'm sure I misunderstand your problem, though.


All of what you have said makes sense to me, and should be a solution for
Eric’s sorting problem. However, the mystery of the ERROR remains what
seems to be a peculiar Windows issue.

Now that I have identified the cause, it is quite possible that it is
a Photoshop issue which is independent of the operating system.
--

Regards,

Eric Stevens