"Armistead, Jason" <[EMAIL PROTECTED]> asked:
> After advising another poster to upgrade his Plextor firmware version, I
> thought I'd better look at the Plextor web site to see if I needed to do the
> same. There was a 1.08 version of firmware for my drive (currently 1.07),
> so I downloaded it.
>
> I also downloaded the following Plextor firmware upgrade utility files from
> Jorg's FTP site, being careful to use BINARY mode, but can't get them to run
> on my system. Previous firmware upgrades were done using Windows 9x with no
> problems, but now I've got it connected to Linux, I thought I might as well
> try to do it locally (rather than move the drive around to another machine).
>
> [root@engcdburner bin]# ll px*
> -rwxr-xr-x 1 root root 67394 Jan 22 11:26
> pxupdate-1.15-i586-linux
> -rwxr-xr-x 1 root root 73311 Jan 22 11:26
> pxupdate-1.18-i586-linux
> [root@engcdburner bin]#
>
> It looks like it downloaded OK, and it appears to be a recognisable
> executable as far as the OS appears to be concerned
>
> [root@engcdburner bin]# file pxupdate-1.18-i586-linux
> pxupdate-1.18-i586-linux: ELF 32-bit LSB executable, Intel 80386, version 1,
> dynamically linked (uses shared libs), not stripped
>
> (same thing happens for the 1.15 version)
>
> Yet when I try to run it I get:
>
> [root@engcdburner bin]# ./pxupdate-1.18-i586-linux
> bash: ./pxupdate-1.18-i586-linux: No such file or directory
Library version? Compiled with funny options? I once suggested linking
binaries static to avoid library problems, but Joerg didn't like that,
either because it doesn't meet some standard or he couldn't make it
work. Perhaps someone who has it working could relink static, or you
could build from source if it's available.
> (same thing happens for the 1.15 version)
>
> My operating system details as follows:
>
> [root@engcdburner bin]# uname -a
> Linux engcdburner.au.otis.com 2.2.16-22 #1 Tue Aug 22 16:16:55 EDT 2000 i586
> unknown
>
> This is RedHat 7.0 on a Pentium 166/MMX
>
> Any ideas or help appreciated
Actually the library issue might be related to ldso config, you might
check what libraries it wants and if you have them you could try
LD_LIBRARY_PATH setting to get the right library used.
Seriously odd.
--
-bill davidsen ([EMAIL PROTECTED])
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
