On 04/09/2011 04:43 PM, Steven Hirsch wrote:
First a question for other Lisa owners:
Could an error 10707 result from attempting to startup Lisa Office
from a ProFile that was configured while attached to a different
machine? I believe there's some sort of node-locking that occurs
during installation, but I'm not sure what the symptoms of a mismatch
might be.
http://lisafaq.sunder.net/lisafaq-sw-los_error_codes.html
10707 Cannot initialize the File System volume
So doesn't look like it can see the drive, or the file system is messed up?
If you move the ProFile to another Lisa, it should start up, but the
tools LisaWrite, etc. won't work.
I've seen this kind of thing when I had a Profile on a parallel port
card, and moved it to the motherboard parallel port or vice versa,
though with a different error code. Not sure that would help anything,
but if you did something like that, might be worth moving it to the same
slot and port. (Yes, it does care about which expansion slot # the card
is in.)
Baring that, the file system could just be toast and you'd need to run
scavenge or reinstall it.
I wish I could re-install... Per some of my other postings, neither
LisaTest nor Lisa Office install seem to think there's a workable drive
attached! The same drive(s) (I've tried three so far) pass format and
diagnostics on an Apple III. I've also been able to successfully install
MacWorksXL on all three using the same Lisa.
There must be something that Lisa OS / LisaTest does that is not involved
in MacWorks / MacOS use of the drive. Darned if I know what.
I'll keep looking for the obvious anyway (bad connections). Already tried
two or three different cables to connect the drive to the system.
Steve
--