[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem with AppleCommander
In article <wPydneruxtqH6FbSnZ2dnUVZ_uCdnZ2d@giganews.com>,
Steven Hirsch <snhirsch@gmail.com> wrote:
> On 06/02/2012 11:22 PM, John B. Matthews wrote:
> > In article <gMmdnWFP2ch26lfSnZ2dnUVZ_r-dnZ2d@giganews.com>,
> > Steven Hirsch <snhirsch@gmail.com> wrote:
> >
> >> My usual luck with Java strikes again. I'm unable to import a file into a
> >> valid ProDOS 140k image.
> >
> > I just tried AppleCommander-1.3.5.11.jar and AppleCommander-
> > 1.3.5.8.jar on Ubuntu 10/OpenJDK. I imported some text (TXT) and an
> > Applesoft (BAS) program. It looks like the resources are there:
> >
> > $ jar tf AppleCommander.jar | grep TextBundle
> > com/webcodepro/applecommander/util/TextBundle.class
> > com/webcodepro/applecommander/util/TextBundle.properties
> >
> > Anything else to go on?
>
> Ok, I think the issue was insufficient space on the target ProDOS
> diskette image. The command line tool flagged this error and exited
> gracefully. The GUI just blows up with the traceback.
Ah, good to know; thanks. The command line functions and the JUnit
regression tests operate at about the same level, so this problem may
have remained latent for some time.
--
John B. Matthews
trashgod at gmail dot com
<http://sites.google.com/site/drjohnbmatthews>