Whats latest libEQ.a file?

[evercamp]

Yes I did a seach, and even following the FAQ.

2.9 - How can I tell if I am using the correct libEQ.a file?
From a terminal window type the following:
# cd /usr/lib
# md5sum libEQ.a
This will output a unique number in the following format:
23249b5a6a04f2b900449d9c4aa0994a libEQ.a
If this number matches the current md5sum found in the ShowEQ Announcement


I went into the announcement thread and saw nothing on what I should be looking for to ensure I am using the latest lib..

Should I be checking elsewhere?


Thanks all!

[Mr. Suspicious]

I went into the announcement thread and saw nothing on what I should be looking for to ensure I am using the latest lib..

Look here: http://seq.sourceforge.net/ it's written, right there.

[Poncho]

Make sure when you are checking the announcements that you scroll back longer than 30 days....doing this will reveal the following thread:

http://seq.sourceforge.net/showthread.php?s=&threadid=2420

Erase any previous version before downloading to save yourself some problems.

Gluck

~Poncho

<edit> Mr. Suspicious -- That is not always true to date, just take a gander at the latest offset listed there, little old if you ask me....

[Mr. Suspicious]

He's asking for the MD5sum for the libEQ.a\

The MD5sum as printed on the very main page of this forum has always been kept uptodate. Another great spot to look for it is the documentation that comes with the software *after you've updated to the most recent version of the software*, hint: file with the cryptic name: README.libEQ

[z26o]

Anyone else notice that the main page shows this:

The current md5sum of libEQ.a (28/Oct/02): feeeecba3f8c4d1559b338e60747dbb0 Which of course is not the latest libeq.
Or is my cach screwed up?

z

[Mr. Suspicious]

Stats: Threads: 2,689, Posts: 18,847
Welcome to our newest forum member, Singe

The current md5sum of libEQ.a (28/Oct/02): ddaac48baaa3e9b015984a366748ed72
Use of any other libEQ.a is not recommended and could be a possible trojan.

The current memory offset is 0x0078bcb8 as of 6 Dec 02 (If there has been a patch since this date, it may not be accurate or updated yet)


It's your cache I suppose. Anyway. There's only ONE official spot for the most current libEQ.a file and md5sum: The documentation

[monster69]

Originally posted by z26o
Anyone else notice that the main page shows this:
Which of course is not the latest libeq.
Or is my cach screwed up?

z


Sorry to dig this up but I was noticing that my seq.sourceforge.net front page reports the incorrect libEQ.a md5sum also.

I have discovered that it is because in "user cp" under "options" I have choosen the "SEQ Blue" Style set.

If I change it back to the default style set, the md5sum is reported correctly.

Dunno why its reading 2 different sets of text for the different style sets, but whoever updates the md5sums needs to be aware they should update it in 2 places.

Monster

[NHRAfan]

what gives? I have my style set to default, I changed it to SEQ blue, then back again and I STILL get the wrong md5sum.


The current md5sum of libEQ.a (28/Oct/02): ddaac48baaa3e9b015984a366748ed72
Use of any other libEQ.a is not recommended and could be a possible trojan.

The current memory offset is 0x007c1950 as of 28 Jan 03 (If there has been a patch since this date, it may not be accurate or updated yet)

I have my browser set to look for an updated page every time I go to a site. It would be nice to get the right md5sum.

[CybMax]

Same here.. I have never fiddled round with anything of changing styles or whatnot.. So if the page is not displayed correctly from the "default" setup you get when registering.. something is actually WRONG!

I have checked this from 3 different pc's on 3 different ISP net's just to be sure aint no "hidden proxy" or similar involved here.. Although same account, so it may be acount based i recon.

So.. One can no longer trust the "updated information that is always posted on the main page" i take it? :)

[cryptorad]

Here's a cut and paste of the first page info..

=================

Stats: Threads: 2,984, Posts: 22,091
Welcome to our newest forum member, GrumpyGnome

The current md5sum of libEQ.a (28/Oct/02): ddaac48baaa3e9b015984a366748ed72
Use of any other libEQ.a is not recommended and could be a possible trojan.

The current memory offset is 0x007c1950 as of 28 Jan 03 (If there has been a patch since this date, it may not be accurate or updated yet)

Read this before asking any questions. Then use use this. After you have read and used both options, then and ONLY then should you ask your question. If your question is answered in either of those two locations, EXPECT TO BE FLAMED for being too stupid to read. You have been warned.




Want to support ShowEQ and the EFF... and recieve a nifty icon and tag to show you contributed? Click here.
For more information, click here. The time now is 03:03 PM.
You last visited: 02-27-2003 04:08 AM.

==============================

See the last two sentences??

If they are anywhere near today's (whatever today is) date, then I think you can assume you have the correct information. I doubt it is a script written for your own PC to fulfill.. since.. that would defeat the purpose of it.

[Ratt]

It's true. I don't update SEQ Blue.

I keep putting off a method to dynamically take the libEQ and Offset data from elsewhere... which is why it doesn't get updated often. It's a pain in the ass to update it the way it is.

Eventually, I'll get around to making it dynamic. Maybe today. Maybe not :)

[h3x]

this is what i have on my main page with the blue layout
The current md5sum of libEQ.a (28/Oct/02): feeeecba3f8c4d1559b338e60747dbb0

a journey to http://libeq.trifocus.net/
revealed that
Linux/i386 - HTTP FTP Size: 5652 MD5: 1f9be1dc9c56619a34d916c52bd551c2

changing my layout to the default gives me
The current md5sum of libEQ.a (28/Oct/02): ddaac48baaa3e9b015984a366748ed72

[Ratt]

Ok, I've made the md5 and offset stuff dynamic for both blue and default.

It should be updated much more frequently now after I get the other devs on board.

[pagan]

Has anyone else noticed the libEQ.a file found at ftp://azriel.trifocus.net (found under /debian/dists/showeq since /pub/<arch>/<os> is gone) does not display the same checksum found at http://seq.sourceforge.net ?

I noticed my seq client was running a little "funny" to say the least. Searched around here a bit to see if I could track down what was causing the odd behavior and found out my libEQ.a checksum was different then whats posted at http://seq.sourceforge.net . Got the libEQ.a file from ftp://smurfette.trifocus.net (in /pub/libeq/i386/linux since (again) /pub/<arch>/<os> does not exist as stated in ALOT of places) ran md5sum on the new libEQ.a and boom, same as on http://seq.sourceforge.net.

Rebuilt seq with the new libEQ.a and everything seems to be functioning normaly (as can be expected at least) I still find the GPS mode to be VERY useful.

Why is libEQ.a at azriel's site different?

[casey]

the ftp dir structure is the same for azriel and smurfette. the i386/linux binary can be found at /pub/libeq/i386/linux/libEQ.a on either server.

casey@azriel:/usr/ftp/pub/libeq/i386/linux$ md5sum libEQ.a
ddaac48baaa3e9b015984a366748ed72 libEQ.a

casey@smurfette:/home/ftp/pub/libeq/i386/linux$ md5sum libEQ.a
ddaac48baaa3e9b015984a366748ed72 libEQ.a


the libeq debian package is not an "official" source (and thats the reason its not in readme.libeq). Its not guaranteed to be up to date, becuase i am pretty lazy at updating the packages. The files listed in the readme however, are always up to date, and available.

[pagan]

Hmmm I even double checked right befor posting... sore the directory tree was missing/different. Interesting.

Oh well, thanks for the heads up on the debian package.