*.cpt files under Linux
Hello, I seem to have a collection of *.cpt files, probably coral paint I think. Is there any way of being able to access this files without buying a copy of coral paint (which may or may not even work)? Doing a web search seems to suggest that the best solution is to convert them in coral paint. It seems even gimp doesn't support *.cpt files. I suspect the files aren't really very important, however. So not worth going to considerable measures to recover them. Thanks -- Brian May <brian@microcomaustralia.com.au>
On 02/12/2012 12:21 PM, Brian May wrote:
Hello,
I seem to have a collection of *.cpt files, probably coral paint I think. Is there any way of being able to access this files without buying a copy of coral paint (which may or may not even work)?
Doing a web search seems to suggest that the best solution is to convert them in coral paint.
It seems even gimp doesn't support *.cpt files.
I suspect the files aren't really very important, however. So not worth going to considerable measures to recover them.
Thanks
A quick search on google came up with Xnview http://www.xnview.com/en/index.html Freeware for non-commercial use, with linux, windows and mac versions. I haven't tried it, or even gone as far as to read the licensing terms, but it may do what you need. Regards, Morrie.
On Sun, Feb 12, 2012, at 12:21 PM, Brian May wrote:
I seem to have a collection of *.cpt files, probably coral paint I think. Is there any way of being able to access this files without buying a copy of coral paint (which may or may not even work)?
Doing a web search seems to suggest that the best solution is to convert them in coral paint.
It seems even gimp doesn't support *.cpt files.
If your .cpt files are from Corel Paint 6, then two options: 1. XnView has a Linux version and will read .cpt files: http://www.xnview.com/en/formats.html 2. If that doesn't work, try Irfanview on Windows. Good luck! Regards Graeme
If your .cpt files are from Corel Paint 6, then two options:
No idea, what it is from. I think another family member "obtained" the software "somewhere" and I never really was particularly fond of it, or its proprietary format. $ file ~/Pictures/My\ Pictures/holidays/Grampians/F1000001.cpt /home/brian/Pictures/My Pictures/holidays/Grampians/F1000001.cpt: data
1. XnView has a Linux version and will read .cpt files:
Doesn't look hopeful :-( brian@andean:~/Desktop/XnView-1.70-x86-unknown-linux2.x-static-fc4$ ./bin/nview ~/Pictures/My\ Pictures/holidays/Grampians/F1000001.cpt ** NVIEW v4.51 Copyright 1991-2002 Pierre-E Gougelet (Sep 6 2005/15:28:19) ** Version for Linux x86 (X11) (All rights reserved) ** This is a freeware software Error --> Don't know how to read this picture
2. If that doesn't work, try Irfanview on Windows.
Ok, might have to do something like that eventually. Thanks for the suggestion. -- Brian May <brian@microcomaustralia.com.au>
On Sun, Feb 12, 2012 at 08:23:48PM +1100, Brian May wrote:
2. If that doesn't work, try Irfanview on Windows.
Ok, might have to do something like that eventually. Thanks for the suggestion.
FYI, some versions of Irfanview are known to work in some versions of wine. AFAICT, read "some" as "most". http://appdb.winehq.org/objectManager.php?sClass=application&iId=163 see also a list of Graphics Viewers: http://appdb.winehq.org/objectManager.php?sClass=category&iId=18&sAction=vie... BTW, debian's wine is still really ancient. you can find up-to-date wine packages for debian at: http://dev.carbon-project.org/debian/wine-unstable/ they're packaged by a debian developer, Kai Wasserbäch <curan@debian.org>. I have no idea why they're not NMU-ed into main or why he doesn't just take over the wine packages. i haven't used wine for several months (since around wine 1.3.34...i built a win7 box after my last HW upgrade, just for games), but I used to use this simple sh script to fetch the latest amd64 binary packages from this site (it's not an apt repo) ---cut here--- #! /bin/bash mkdir -p ~/dl/wine-unstable cd ~/dl/wine-unstable #ARCH=i386 ARCH=amd64 URL='http://dev.carbon-project.org/debian/wine-unstable/' FILES=$(lynx -dump -listonly "$URL" | \ egrep "\.dsc|_$ARCH.deb" | \ awk '{print $2}' | \ egrep -v -- '-dbg|-dev') VERSION=$(echo $FILES | sed -e 's/ /\n/g' | grep '\.dsc' | sed -e 's/[^ ]*_//' -e 's/\.dsc.*//') if [ ! -d "$VERSION" ] ; then mkdir "$VERSION" pushd "$VERSION" for f in $FILES; do snarf $f done echo now run as root: echo " dpkg -iGROEB $(pwd)/*.deb" popd else echo "Latest version ($VERSION) already downloaded" fi ---cut here--- the first time you fetch them, you'll probably need to manually install the following packages: libwine-alsa-unstable libwine-bin-unstable libwine-cms-unstable \ libwine-gl-unstable libwine-gphoto2-unstable libwine-ldap-unstable \ libwine-openal-unstable libwine-print-unstable libwine-sane-unstable \ libwine-unstable wine-bin-unstable wine-unstable on amd64, you'll also need various i386 compatibility libs, including libc6-i386, ia32-libs, and (i think) ia32-libs-gtk. and nvidia-glx-ia32 if you are using the proprietary nvidia-glx drivers, or fglrx-glx-ia32 for the proprietary amd/ati drivers. i have absolutely no idea how well wine works with the opensource ati or nouveau drivers. all i know is that it works extremely well with nvidia-glx. on i386, just modify the script to fetch the i386 binaries rather than amd64. anyway, after that, future updates can be installed with the 'dpkg -iGROEB' command that the script prints for convenient copy-and-paste. craig -- craig sanders <cas@taz.net.au>
participants (4)
-
Brian May -
Craig Sanders -
Graeme Cross -
Morrie Wyatt