Document Security

[johnnaryry]

I love the improvements made to the newest version of iSilo! I use an "old school" m500 w/ a 256MB SD card and the new version works so much faster that I'm delaying any thoughts of a hardware upgrade. The big thing I miss with the new version is security. What happened to the ability to make individual documents "private"? I'm a medical professional and I must have this feature! Why did it go away and are there plans to bring it back? Is there perhaps a work-around for this issue?

Thanks in Advance for Your Help

--ryan

[iSilo]

The new document list view implementation prevented a practical implementation of the private document feature.

Perhaps equivalent functionality will be possible in the future in a different form. If you could perhaps explain the particular reason you require the feature, perhaps your particular needs can also be taken under consideration for such a redesigned feature.

As an alternative, if you converted the documents yourself and what you want to do is prevent others from accessing those documents, you can reconvert the documents to have them require a password and/or a registration code. See the Security tab in the iSiloX Properties dialog for these options.

[johnnaryry]

I am a medical professional and frequently carry patient records and case histories aboard my handheld. Until the last update (4.05), iSilo was my doc-reader of choice for these records, however the removal of practical security options forces me to use TealDoc instead. I use iSiloMac to convert docs to the iSilo format (iSiloX does not work with my iMac). Medical people like me need the security option to protect patient confidentiality.

--ryan

[Voltage Spike]

There are a few issues here:


Why can't you use iSiloX? The only real hurdle appears to be a PowerPC processor. If this is the case, then upgrade! ;)
Why can't you use the password option (http://isilox.com/support/manual/ixl/ixlSecurityOptions.htm#Password)? I am guessing the answer is related to your use of iSiloMac.
Why can't you continue to use the older version of iSilo (http://isilo.com/download/401/iSiloPalmOS.htm)? Is the speed difference that great between iSilo 4.01 and TealDoc?


It would appear that all of the issues relate to the first problem. If you could elaborate on that point a bit, then perhaps we can help you out.

[johnnaryry]

I maintain a large number of volumes on my Palm (approximately 300 of more in iSilo format), so the newest version does yield a considerable gain in speed, plus the interface is far superior to the previous when dealing with long document lists. Therefore I am extremely reluctant to backtrack to version 4.01...

I have tried several times to install iSiloX to my machine. I have a 333Mhz iMac with 288MB ram, running OS 8.6. Each attempt to run the iSiloX installer only gets me as far as the EULA; when I hit the [Continue] button the app crashes giving me the "Type 1 Error" message. Is there perhaps some way I could get the necessary files in a zipped format? I am appreciative of any help available.

Thanks --ryan

[Voltage Spike]

Is there perhaps some way I could get the necessary files in a zipped format?

I sent you a private message with a link to the "iSiloX" program from within the "iSiloX.app/Contents/MacOSClassic" folder of the Mac OS X installation. I don't know if this will work, but it is worth a shot.

[johnnaryry]

Thanks for your effort. I was able to download the zip, but when it opened, I was left with a "unidentified file type" called "iSiloX" the would not open or launch. What gives? I'm about to give up on this... :confused:

--ryan

[iSilo]

Doing a google search for "type 1 error macintosh" brings up a number of links about Type 1 Errors. It seems that type 1 errors relate to out of memory issues. Maybe you could try installing iSiloX and try some of the suggestions on those pages. Here are links to the first two from the google search:

http://8help.osu.edu/33682.html
http://www.ihug.co.nz/help/dialup/mac/troubleshooting/error11.html

[Voltage Spike]

As I had feared, I think the program needs a resource fork that was lost in the transfer. Unfortunately, I do not believe I have any compression programs capable of preserving the resource fork that will work with pre-Mac OS X.

Good luck with increasing the memory. I remember those days. :p