[comp.sys.amiga.programmer] Molec3D; to anyone for whom it works

jordan@unix.cis.pitt.edu (Kenneth D Jordan) (06/22/91)

To anyone for whom Molec3D (fish disk 482) actually works:

Despite my best efforts I still can't get Molec3D to read its own demo
files.  The error I always get is a requester with the following message:

	Undefined connect-item: A##*

where A## is the last center in the last bond, and * is some nonprinting
character.  I get the same result on three machines:

	1.  A1000 with 512k chip and 512k fast RAM (KS 1.2)
	2.  A1000 with 512k chip and  2M  fast RAM (KS 1.3)
	3.  A3000 with  1M  chip and  8M  fast RAM (KS 2.0)

This is getting rather frustrating, especially since it

	1.  looks useful for things I'm presently working on
	2.  claims to work on "any Amiga"
	3.  goes so far as to specify someone who performed "testing"

I downloaded it from isca.icaen.uiowa.edu several times, unpacking it
on an A1000, and A3000, and a UNIX host on which I installed a different
port of lharc than I have running on my Amigas.  I also found it on
minnehaha.rhrk.uni-kl.de and downloaded it from there (in ff482.lzh),
with all files comparing identical.

To those on the net for whom Molec3D actually works:

	1.  Where did you get it?
	2.  If possible, would you send either file sizes and checksums
	    or the Molec3D program and a working data file to me at
	    nystrom@a.psc.edu?
	3.  What is your hardware configuration?
	4.  I get a system crash if I select "CANCEL" in the file
	    requester.  Is this behavior also anomalous?

To anyone else:

	1.  Do you have Dr. Stefan Albrecht's E-Mail address?  I'd like
	    to correspond with him concerning possible extensions to
	    Molec3D to handle Gaussian xx style Z matrices.

-------------------------------------------------------------------------------
         Nick Nystrom    University of Pittsburgh    nystrom@a.psc.edu
-------------------------------------------------------------------------------

-- 
-------------------------------------------------------------------------------
         Nick Nystrom    University of Pittsburgh    nystrom@a.psc.edu
-------------------------------------------------------------------------------

hrmeyer@ucselx.sdsu.edu (meyer h) (06/24/91)

In article <142845@unix.cis.pitt.edu> jordan@unix.cis.pitt.edu (Kenneth D Jordan) writes:
>To anyone for whom Molec3D (fish disk 482) actually works:

    stuff deleted

>	1.  Where did you get it?
>	2.  If possible, would you send either file sizes and checksums
>	    or the Molec3D program and a working data file to me at
>	    nystrom@a.psc.edu?
>	3.  What is your hardware configuration?
>	4.  I get a system crash if I select "CANCEL" in the file
>	    requester.  Is this behavior also anomalous?



Sorry to rush to get off what I can rather than running more detailed 
experiments, but my base system is being taken offline for major changes 
starting 24 June; they say it may be a week.  

I don't have any answers, but I do have a couple more data points.

I got Molec3D from isca.  It runs on 1 of the 2 A2000's I have access to.  

I tried it first on one with 1.2 ROM, and .5 M chip RAM, running 1.3 .  It's 
a 5 M machine, with 4 M on an 8-up!.  The only hardware that has been altered 
was I took it in for the problem of eating the first character typed, which I 
believe entailed removing one capacitor.  Molec3D works fine on this machine.  

I then took it to a newer A2000, with 1.3 ROM, 1 M chip RAM, AmigaDOS 1.3, and 
2 M RAM in a GVP Impact + 8 that I am just using for a RAM expansion until I 
add a hard drive.  It wouldn't run.  Something flickered when I double-clicked 
the icon, but all I could see was that the amount of available RAM changed.  
I normally have ARP and some non-standard libraries, so I booted with the 
latest plain vanilla system disk I have, the one that came with the second 
A2000.  This time the program loaded and seemed to be running, but complained 
with a requestor as you describe when I tried to load an example I had looked 
at with the other machine.  

Took the exact same disks (boot from vanilla system) back to the first 
machine, and it still worked fine.  

Now I gotta get this sent before the University machine turns into a pumpkin.  

Harry R. Meyer   hrmeyer@ucselx.sdsu.edu