Hi there Jamie,
Just to be clear, the two programs that you mentioned aren't from the
Seattle Proteome Center (SPC), and you might find more support if you write
directly to those programs' maintainers. But if anyone else on the list has
experience, of course they are welcome to respond here.
Hi guys, I am having problems with the protein names in peptide
prophet. The protein names appear with the appendix unmapped like
gi464220_unmapped. Pointing with the cursor to this link the message
appears: originally identified as gi464220 in database. If I try
to look at the protein
read in 0 1+, 0 2+, 0 3+, 0 4+, 0 5+, 0 6+, 0 7+ spectra with min prob
0.05
Looks like something has gone wrong before you got to ProteinProphet, it
seems. You'll need to back up a few steps and figure out what happened.
-Original Message-
From: spctools-discuss@googlegroups.com
It should be possible, all you should need to do is alter (or create)
Makefile.config.incl to include the line
PERL_BIN=C:/Perl64/bin/perl
Then do make all install or possibly make clean all install for safety.
If you succeed, please let the list know.
Brian
-Original Message-
From:
Hi Brian,
I am trying to install TPP 4.2.1 with 64 bit Active State Perl on Windows
Server.
Can you elaborate on the process you are suggesting?
Create a file called: Makefile.config.incl which will contain the line:
PERL_BIN=C:/Perl64/bin/perl
Once created; where do I put this file
Sorry, I was thinking you were planning to do your own 64 bit build of TPP,
which involves MinGW etc.
If you don't want to do that, you might be able to hack it by creating a
junction (Windows-speak for directory symbolic link, see
http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx)
Ok, thanks for the additional information. Before I try the suggested hack, I
would like to know if anyone has run the TPP with 64-bit Perl? There is quite
a large amount of Perl used in the TPP and I am not sure if that perl code will
run properly using the 64-bit Perl interpreter.
Ron
When I think about it, that hack's probably doomed in the current release
due to some perl module dependencies on a 32 bit perl distribution libs (I
killed these dependencies off for upcoming releases, though).
So you might want to build your own, or install the 32 bit perl as well, or
wait a
