developing these kindof things with 3rd party hardware - is a complex endeavour.

how fast is the thumbnails at the moment?

---

there is no standard for this kindof thing -
suggest you get chris to look at the

catalyst webpage - files page-
http://localhost:8080/catws/files.html

if you look at the html source for this-

Code:
<MovieInfo folder=000 file=000 name="000openwhite.pct"/>

<tr>

<td height=30 width=71 valign=center><img src="Resources/_clear.gif" border=0 width=1 height=1 alt="">0</td>

<td width=69 valign=center><img src="Resources/_clear.gif" border=0 width=1 height=1 alt="">0</td>

<td width=138 valign=top><img src="Resources/_clear.gif" border=0 width=1 height=1 alt=""> <img src="Images/000_000.jpg" border = 0 width=80 height=60 alt="">

</td>

<td width=158 valign=center><img src="Resources/_clear.gif" border=0 width=1 height=1 alt="">000openwhite.pct</td>

<td width=225 valign=top><img src="Resources/_clear.gif" border=0 width=1 height=1 alt=""> </td>

</tr>
you will see that every file that is available has its own xml tag called 'MovieInfo' - this is my own xml tag - and you can do this type of thing with web pages - you can put your own information inside them.

Code:
<MovieInfo folder=000 file=000 name="000openwhite.pct"/>
chris needs to parse this file - and to look at all these tags in this file ( if he doesnt ) which will tell him exactly which files are there accessible in a library - and which are not.
He shouldnt need to be accessing any files that dont exist - as he can get a list of all the files that do exist.

I intend to add more information to this xml tag in future so he should not presume any parameter order, or parameter count - but thats a good thing about xml.
At the moment only the file folder, file, and name are indicated, in the future other types of information could be placed here.