Unable to open

[anmldr]

I have a Macbook that is a dual boot for Mac OS x or Windows Vista. I have iSiloX installed for both of these OS.

I have an external drive that has a "shared folder" that contains a lot of HTML documents. So, if I boot to either Vista or OS X, I am able to access these same exact documents.

When I use iSiloX to convert these documents on OS X, there is a long list of "Unable to open" errors. But, if I convert these same exact documents with iSiloX in Vista, iSiloX is able to find these documents.

Some of the names of the documents do in fact have a space in the names of the HTML files. Could this be the problem? Just so you know, iSilo is able to find many documents with spaces in the names, I just found this to be one thing in that these same documents share with each other.

Linda

[iSilo]

It is probably not a space issue since you say that other files with spaces in their names get converted. It might be the length of the path to the files. Are paths of the files that are reported us unopen to be opened particularly long?

[anmldr]

All of the files are in the same exact directory and so the path to all of them is the same length. However, the names of the files are fairly long. The shortest that did not convert is "Desoxycorticosterone%20Pivalate.htm". The others that did not convert are longer than this one.

So, it probably is a name issue.

The good news is that I have a dual boot Macbook and so it is an easy thing to just reboot into Windows Vista and use iSiloX in Windows and everything converts normally no matter what the length of the file's name.

So, it is not a problem for me. I just thought that you might like to know that iSiloX on the Mac wasn't acting like iSiloX in Windows on this issue.

BTW, this is a Mac OS X with Version 10.5.5 if that makes a difference.

Linda

[iSilo]

There is a 31 character limit per path component, so that name is definitely too long. It is a limit because iSiloX for Mac was written to be compatible with Mac OS 8.x/9.x and Mac OS X. We would need to rewrite iSiloX as a Mac OS X native application to address that limit. It has been something we have been looking to do for a long time, but other priorities have always superceded it.

[anmldr]

No need to rewrite it for my sake. I was just reporting an issue that I did not know if you knew about. iSiloX for Windows works fine for me.

Linda

[iSilo]

You mentioned that you have a dual boot system. Presumably you have applications on both Mac OS X and Windows that you like to use, such as iSiloX. As a recommendation you might want to take a look at VMware's Fusion product, which allows you to run Windows programs side-by-side with your Mac OS X applications under Mac OS X, which negates the need to have to reboot depending on which OS you want to use.