Anyone running CompuPic?

1999-09-10 Thread Tom Embt

Not sure which list this should go to, so if I'm in error feel free to
point me in the right direction.

I was wondering if anyone has had any luck running CompuPic
(http://linux.compupic.com) under FreeBSD?  It's an excellent image viewer
that can do some basic file management as well.  Along with Agent, it's one
of the few good apps available for Windoze, and I was excited when I heard
there was a free *NIX version available.  

Unfortunately, I haven't been able to get it to run.  I'm not in FreeBSD
right now so I'm working from memory, but I had some trouble with the
install process (it is obviously not as portable as they'd have you
believe).  I seem to recall setting $UID and installing bash, but the
script still bombed after it was installed.  Then I had to brandelf it.  I
tried both "Linux" and "FreeBSD" branding and one was working better than
the other though I don't recall which.  End result:  It starts to load,
brings up a splash screen, and exits.  I do recall it leaving messages on
the console but forget which signal it was dying with.  I can get more info
if it's wanted but first I'm just asking if anyone else has either had
better luck than I.

Here's a quote from the website:


"CompuPic is highly portable, and Photodex intends to support as many
target platforms as possible over time. CompuPic for Linux (and UNIX) is
available as a statically linked executable with no library dependencies
whatsoever. You need only a Linux or UNIX kernel to run CompuPic.

CompuPic has been tested with major Linux and BSD distributions and had no
distribution specific issues.

If you represent a hardware manufacturer or Linux/UNIX distribution
publisher, you can contact Paul Schmidt to discuss Photodex's development
plans for a specific platform.

Paul Schmidt
VP Technology
Photodex Corporation
1106 Clayton Lane #200W
Austin, TX 78723
(512) 406-3061 - voice
(512) 452-6825 - fax
[EMAIL PROTECTED]"



They seem to make a point of saying "Linux/UNIX" and not referring to all
of *NIX OS's as "Linux", even going so far as to mention BSD once.  I was
therefor a bit surprised when the binary wouldn't run on FreeBSD.  I wonder
if The Powers That Be would be interested in pursuing the last sentence there?

FYI: My system is SMP 4.0-CURRENT from a day or two ago, XFree86 3.3.3.4
from packages, KDE-1.1 from packages, Linux emu running, etc.  As far as my
FreeBSD proficiency, lets just say I'm probably not the kind of person that
ought to be running -CURRENT :) so I don't think I'd be much help in
tracking down the problem (aside from being a guinea pig).


of course there also exists the possibility that I forgot to insert tab A
into slot B and CompuPic indeed runs perfectly in FBSD for everyone else..
and how did it get to be 3AM ?  Ugh.  well thanks to anyone who can
clue me in,



Tom Embt ICQ UIN:  11245398
[EMAIL PROTECTED] d:-)

--
"You're one of those condescending Unix computer users!"
"Here's a nickel, kid.  Get yourself a better computer" - Dilbert.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone running CompuPic?

1999-09-10 Thread Mike Muir


I get the same problem, after brandelfing to linux and running it, the
splash screen comes up and...disappears with:

compupic: abnormal termination: (null)

Brandelf -t FreeBSD segfaults it without even showing the splash screen.

Nice helpful error message.. can anyone shed some light on that?

Tom Embt wrote:
 Unfortunately, I haven't been able to get it to run.  I'm not in FreeBSD
 right now so I'm working from memory, but I had some trouble with the
 install process (it is obviously not as portable as they'd have you
 believe).  I seem to recall setting $UID and installing bash, but the
 script still bombed after it was installed.  Then I had to brandelf it.  I
 tried both "Linux" and "FreeBSD" branding and one was working better than
 the other though I don't recall which.  End result:  It starts to load,
 brings up a splash screen, and exits.  I do recall it leaving messages on
 the console but forget which signal it was dying with.  I can get more info
 if it's wanted but first I'm just asking if anyone else has either had
 better luck than I.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message