Keyring

[baelang]

Keyring home page:
http://members.fortunecity.com/baelang/
(crappy free hosting site. warning: popups)

EDIT: version 2.2 has now been released. (20021213)

redirect yourself here:
http://seq.sourceforge.net/showthread.php?s=&threadid=2613
for version 2.2 code.

---


This is release 2.1 of Keyring.

keyring.exe is a program to sniff encryption keys from the running everquest
program (eqgame or testeqgame).
Code is by BaeLang and based on posts by mvren, hoihoi, kal, UncleBen, and others
on the showeq sourceforge forums.

it works with showEQ version 4.3.2 (and later) with the appropriate libEQ.a.
see http://seq.sf.com for more information.

Features:
* supports multiple config files, allowing seporate ones for test and live.
* loops searching for the eqgame, no timing issues. also includes
UncleBen's debug privledge code so should be able to start up at any time.
* only sends the key when the key changes.
* sends the key via UDP. works with current version of showeq.
* accepts command line arguments
* easy to compile and install. comes with a makefile.
* works on XP and ME. i haven't tried it on any other OS.

BUGS:
* none known at the moment.

I compiled this with the free gcc compiler for windows that comes with the
cygwin distribution. cygwin is free, easy to install and update, and lets
you select from many, many, unix-type utillities including an x-server if
you so desire.
http://cygwin.com/faq/faq_toc.html

it should also compile as is with mingw, which is another free gcc compiler
for windows.
http://www.mingw.org/

it is also reported to work with lcc:
http://www.cs.virginia.edu/~lcc-win32/

minor modifications may be needed for other compilers. ymmv.

To get it going, here's what you have to do:

* verify that you have a compiler of some sort.
I strongly suggest the free ones listed above.
* download the attached tarball.
* extract the archive: tar -xzvf keyring.tar.gz
* cd keyring
* read the README file
* make
* make install
* cd c:\keyring
* using your favorite editor, edit the keyring.ini file
you will need to change the IP address and the udp port
to which the key will be sent. remember that the default port is
10000 but that is NOT the best choice.
* at the dos prompt run keyring.exe
or use the run prompt: start->run->C:\keyring\keyring.exe
or browse the fulesystem and double-click keyring.exe
* start up EQ and enjoy!
* leave this program running and start up EQ. you should be good to go.
* use ctrl-c to end keyring.exe after you have closed down EQ.

useage:
keyring.exe
-h print output help information (but you knew that, didn't you.)
-f <path/to/config/file> specifies the path to some config file
-v run in verbose mode (copious debug information)
-i <interval> specify the send interval in seconds.
-a <address> send-to ip address
-p <port> send-to udp port
-n <name> name of program to search for (i.e. eqgame or testeqgame)
-o <offset> key location
-e run once and Exit. (no looping)

feel free to send me patches. i maintain a small CVS repository for this code.

SECOND NOTE: Source code in Zip format is avaliable on the web page listed above, in addition to a binary distribution.

[a_necro00]

Compiles perfect with lcc also, a very simple & easy to use C compiler, it will even includes the needed libs automatically.

http://www.cs.virginia.edu/~lcc-win32/

Excellent work baelang, it sends the key every time I zone.

[fryfrog]

if you use the read access instead of full access, does that stop the error 5 when you close and re-open the scanner?

if that is the case, i'll toss an exit(0) into your while loop and just run the program (once) when ever i really need a decode isntead of looping it. i'm at work right now so i can't test to find out.

[baelang]

Originally posted by fryfrog
if you use the read access instead of full access, does that stop the error 5 when you close and re-open the scanner?

if that is the case, i'll toss an exit(0) into your while loop and just run the program (once) when ever i really need a decode isntead of looping it. i'm at work right now so i can't test to find out.

I plan to add a no-looping option. however, i haven't found a way to avoid error 5 (on xp) if you close it down and then restart. even messing with "at" and system services. it's probably just me though, since this is my first attempt at win32 programming.

[fryfrog]

check out the uncle ben's thread, his appears to work in the way described.

[MisterSpock]

The AT command in Windows 2000 launches the application with the SYSTEM account credentials.

This was considered an exploit, as you could run applications with higher security privs than you would normally have. This included the ability to give yourself administrator access.

This has been rectified in WinXP. Applications launched with AT run with the LOCALSERVICE account. LOCALSERVICE does not have the level of access that SYSTEM had, so you will get an error 5 on your program with AT in WinXP.

There are several ways to get around this problem. One is to include code in your sniffer to enable debug privs. There is another method that has been shown on this board at least once (that uses SetSecurityInfo and SetEntriesInAcl) that also works. With either of these code pieces included and called from your sniffer, you can launch it from the AT command.

Another possible method that should work (although I have not tested it) would be to add the LOCALSERVICE account to the Administrators group. In theory, it should also clear the error 5.

[fryfrog]

the error 5 happens when you run the program once, control-c it and try and run it again on the same eqgame.exe. i got around this by just putting a "press any key" pause into the loop so it wouldn't send the key unless i wanted it too... but with this method it is still active and hanging around. i just wanted a program that could run once, get and send key then exit. if i set an "exit(o)" right after the sending of the key... it would only run once on that eqgame.exe, getting an error on any further runs.

[dana523]

This is a stupid question but I need to ask it where do i extract the file to i do the tar but i get the error

tar (child): keyring.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed form previous errors

and i get it with tar -xzvf keyring.tar.gz and keyring[1].tar.gz

[baelang]

Originally posted by dana523
This is a stupid question but I need to ask it where do i extract the file to i do the tar but i get the error

tar (child): keyring.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed form previous errors

and i get it with tar -xzvf keyring.tar.gz and keyring[1].tar.gz

When you extract the archive, you need to either be in the directory where you saved keyring.tar.gz or specify the full path to it.

you could have saved that file anywhere on your computer, so i can't help you further than that.

except i should note that some web browsers may automatically uncompress the file when you save it. so if keyring.tar.gz isn't on your computer, you may have keyring.tar instead. the "z" option to gnu tar is for compression. if your archive isn't compressed, then leave off the z.

[dana523]

Ok great I got that going now i am in keyring but cannot edit the ip from here i type

edit C:\keyring\keyring.ini

i get bash:edit: command not found

also when i go into the cd \keyring.ini\ it goes to a > and a curosr

this dir im in is the keyring dir and the 2 files i have there are keyring.exe and keyring.ini

there is also another question when i go to run this i get

bash: keyring.exe: command not found

[Mr. Suspicious]

Ok great I got that going now i am in keyring but cannot edit the ip from here i type


Just use notepad or your prefered textfile editor.


bash: keyring.exe: command not found

Simply run the executable via start -> run OR browse to it using Windows Explorer and double click it OR go into a DOS command shell and CD to it and run it from there.

[baelang]

Originally posted by Mr. Suspicious


Simply run the executable via start -> run OR browse to it using Windows Explorer and double click it OR go into a DOS command shell and CD to it and run it from there.

or even specify the path in bash: ./keyring.exe or c:/keyring/keyring.exe

or add c:/keyring to your path environment variable.


EDIT: by the way, i am somewhat shocked that over 220 people have downloaded version 1 of keyring. i had no idea there were that many people interested in it.

[dana523]

ok great ty for that now i still have grey spawns any idea there

might have had the worng ip checking now

had the wrong ip got it going now thank you for all your help..

[baelang]

as promised, here is keyring version 2 code in zip format.

EDIT: see the latest version thread. (2.2 or later)

[dpaschal]

This may be a silly question, but can keyring be coded so we can compile it either for win32 or linux? I personally would like to run it on the linux box with showeq, or is that a bad thing?

[who_me_use_seq]

It is not a bad thing. It is an impossible thing. Think about it for a moment.

(The program runs on the box that you are running EQ on so it can scan ______?

Good Grasshopper.)

[high_jeeves]

Ummm... it could probably be modified to run on linux, but, since that would kill the entire point of using it (since it has to access EQ's memory space), I'm not sure what the point would be. Please do a bit of research on the subject before you post (atleast the announcements forum....)

--Jeeves

[baelang]

Originally posted by dpaschal
This may be a silly question, but can keyring be coded so we can compile it either for win32 or linux? I personally would like to run it on the linux box with showeq, or is that a bad thing?

do you mean for running everquest under winex? if that is what you mean then all you need to do is install winelib and you should be able to compile it for linux...i guess.

[dpaschal]

Originally posted by high_jeeves
Ummm... it could probably be modified to run on linux, but, since that would kill the entire point of using it (since it has to access EQ's memory space), I'm not sure what the point would be. Please do a bit of research on the subject before you post (atleast the announcements forum....)

--Jeeves

EEK! That kind of takes away from how showeq was built. Correct me if I am wrong, but showeq was built to run on a Linux os and sit undetected on another box to decrypt the packets and do it's thing. So now we want to introduce a program that sits on the same box as the eqclient runs and mess with the eqclient's memory space? Sounds quite dangerous. Maybe something will be invented so this will not have to be done. Maybe not, but I'll live with gps for now since that is about all I ever used showeq for anyway. It's a great program, but not worth the cost of being stupid by running 3rd party software on the same box that the client is. On the other hand, I suppose that they could detect if you were running showeq on another box on the network. I dunno, I think I am just debating with my own self :p

[shadowcat]

Actually that's why this forum was set up. It's for the key sniffers sitting on the same box as the eqclient. It doesn't "mess" with memory but simply reads it and determines the key that is then passed back (usually through UDP) to seq.

[Samefudge]

And the forum was set up in direct response to a changed client, changes that were made to BREAK ShowEQ, period. If you don't want a sniffer on your EQ box, be happy with GPS mode.

If you are still not clear on WHY we are doing this... catch up on your forum reading here, it's all been talked about.

[Howdy]

Regarding this:
* using your favorite editor, edit the keyring.ini file
you will need to change the IP address and the udp port
to which the key will be sent. remember that the default port is
10000 but that is NOT the best choice. What's the best way to determine which port to set this to? What other considerations need to be made on the Linux machine or with ShowEQ itself when choosing this port? I imagine I need to make adjustments there as well based on what I choose here?

Thanks for any help!

Howdy

[baelang]

Originally posted by Howdy
Regarding this: What's the best way to determine which port to set this to? What other considerations need to be made on the Linux machine or with ShowEQ itself when choosing this port? I imagine I need to make adjustments there as well based on what I choose here?


pick a port! any port!
http://seq.sourceforge.net/showthread.php?s=&threadid=2372

and of course you ought to look at the "decode" menu in showeq.

[EQWarrior86]

Greetings,

I am running Windows XP and using your Keysniffer and it works beautifully.. After patch I changed the offsets in the conf file and I am now getting an error 5 message even after reboot etc...

Anyone have any ideas on this?

[Nafeem]

Hmm anyone else having problems as of 11/19 patch? Even with the new offset, I cant seem to get showeq working. Maybe I am doing something wrong. But I have tried keyring -o 78AAD0 . My linux box shows up as getting incorrect packets. Is it just me? Or are others having problems with keyring 2.0 as well?

[maggotboy]

Originally posted by Nafeem
Hmm anyone else having problems as of 11/19 patch? Even with the new offset, I cant seem to get showeq working. Maybe I am doing something wrong. But I have tried keyring -o 78AAD0 . My linux box shows up as getting incorrect packets. Is it just me? Or are others having problems with keyring 2.0 as well?

I'm not using Keyring -- using my own sniffer ... and ShowEQ is running business as usual with the new relocated key. So I know at least that its not ShowEQ having a problem ...

Maggotboy

[edit to clarify its not ShowEQ]

[Nafeem]

Ya thats what I figured maggotboy. Getting C++ setup and gonna give yours a go. Looks great btw, was checking up on that thread.

Was just wondering though if keyring doesnt work with 11/19. I dont think it does.

[Burnereq]

I went in to the ini file and changed the offset. Loaded it up and everything decoded before I finished Zoning.
So I do believe it is working with the 11/19 changes.

Good Luck

[baelang]

Originally posted by Nafeem
Hmm anyone else having problems as of 11/19 patch? Even with the new offset, I cant seem to get showeq working. Maybe I am doing something wrong. But I have tried keyring -o 78AAD0 . My linux box shows up as getting incorrect packets. Is it just me? Or are others having problems with keyring 2.0 as well?

it has to be specified as 0x0078aad0

works fine for me. be sure you are using version 2 of keyring. (includes uncleben's code)

[showeqnewb]

Thank you SOOOOO MUCH!

I was using EQsniff and it was all manual and I typically ended up running SEQ as nothing but a map!

I was reading the tons of code post and pulling my hair out thinking that I would have to go crazy trying to figure out something I dont have a clue about!

Two things I had probs with on the setup:
I installed Cygwin but it could not find cygwin1.dll... so I copied that dll to the keyring directory

Then I was getting: "some sort of problem with the config file: C:\keyring\keyring.ini" So I copied keyring.ini from c:\keyring\conf to c:\keyring

[baelang]

Originally posted by showeqnewb
Two things I had probs with on the setup:
I installed Cygwin but it could not find cygwin1.dll... so I copied that dll to the keyring directory

Then I was getting: "some sort of problem with the config file: C:\keyring\keyring.ini" So I copied keyring.ini from c:\keyring\conf to c:\keyring

the cygwin1.dll needs to be either in the keyring directory OR the windows directory OR in your path to run keyring from a dos command prompt. if you run it from the cygwin bash prompt it isn't a problem.

make install should have put the config file in the right place. *shrug* not sure what happened there.

i will update my distribution for the new offset sometime in the next coupld of days when i get a chance.

[Talon]

The problem is, that cygwin can not be set to C:\keyring directory.

And so you can not begin with "make"

[Hobo]

Just a heads up for those using the binary distribution.

In the instructions it says to make a new folder named Keyring and extract to that folder. Do NOT make this folder, because when you do the extraction it makes the folder for you.

If you made the folder you will end up with the sniffer in C:\keyring\keyring folders instead of C:\keyring folder. If you have it in C:\keyring\keyring folder it doesn't work properly. So just extract it to plain old C:\ and let it create the keyring folder for you.

Other than this it works like a charm!


Hobo

[Adeon]

Having probs with keyring v2.

It seems it is passing a key to the ShowEQ box, but ShowEQ is still having problems with that Key.

Using the new offest..

Showeq reports ..

ProcessPacket() Inflate Error: InflateRes-3 msg=unknown compression method

Get other mesages like..

CharprofileCode:Not Decoded

I was wondering if because I am using Win98 the offset is different?

I have tried also using EQWIN so I could see the verbose output.. still the same issues. (Would EQWIN effect the Mem offset aswell?)

In verbose mode, efter a reset and reconnect to EQ.. I was still getting the same message from Keyring saying..
Sent key : 12345678.. (The number was the same both times) Shouldnt it be different?

I compiled Keyring using MinGW.. Compiled straight off the bat no problems.. Using v2 Code.

I am using ShowEQ 4.3.3

[baelang]

Originally posted by Talon
The problem is, that cygwin can not be set to C:\keyring directory.

And so you can not begin with "make"

cd c:/keyring works with cygwin bash. at least it does for me.

and make should be run in the directory you unzipped the source, not in the target directory.

[baelang]

Originally posted by Hobo
Just a heads up for those using the binary distribution.

In the instructions it says to make a new folder named Keyring and extract to that folder. Do NOT make this folder, because when you do the extraction it makes the folder for you.

If you made the folder you will end up with the sniffer in C:\keyring\keyring folders instead of C:\keyring folder. If you have it in C:\keyring\keyring folder it doesn't work properly. So just extract it to plain old C:\ and let it create the keyring folder for you.

Other than this it works like a charm!


Hobo

oops.

i will change the instructions.

[baelang]

Originally posted by Adeon
Having probs with keyring v2.

It seems it is passing a key to the ShowEQ box, but ShowEQ is still having problems with that Key.

Using the new offest..


there may be problems with giveing the offset on the command line, so you will have to edit the ini file instead. Also, be SURE you have the new offset and you are entering it in the same format as the old one. that is:

0x0078aad0

no caps and include the 0x00 at the begining.

[Enduron]

Well I went and got cygwin and tried to get it to compile...was getting an error with gcc ...come to find out I didnt have it installed, LOL,...so I got gcc...then had to get make (yes 2 different packages) and BOOM it compiled, no errors what so ever and it works wonderfully =)

Thanks Baelang =)

-e

[datadog]

Originally posted by Adeon
Using the new offest..
Showeq reports ..
ProcessPacket() Inflate Error: InflateRes-3 msg=unknown compression method
Get other mesages like..
CharprofileCode:Not Decoded

Originally posted by baelang
there may be problems with giveing the offset on the command line, so you will have to edit the ini file instead. Also, be SURE you have the new offset and you are entering it in the same format as the old one. that is:

0x0078aad0

no caps and include the 0x00 at the begining.

I am also having this problem.

I have tried sending the parameters using the INI and from the command line. Doesnt seem to make any difference.

I tried manually entering the 'key' that keyring sent. manual entry also results in the same error.

I verified im running the latest version of SEQ complied with the latest libEQ.a.

Any suggestions?
/shrug

[datadog]

Exact error message in SEQ as follows:

...
Your player's id is 3505
Decrypting and dispatching with key: 0x877dddea2d2e08e3
ProcessPacket () Inftlate Error: inflateRes=-3 msg=unknown compression method
Warning: Failed to decrypt queued Player Profile packet: 0.

BTW: running WinXP Home.. latest patch level

any ideas?

[bonkersbobcat]

You do have the right libEQ, right?

[abc]

I had this same problem.
It was because i had the wrong libEQ.a

Check your libEQ's md5sum and compare with the latest.

You also need to recompile after downloading the latest libEQ.a

[Mr. Suspicious]

Not sure, but i think you also need to recompile after downloading the latest libEQ.a

100% sure you DO need to recompile after downloading the latest libEQ.a (use search and read one of 100 messages where people tell others time after time they need to recompile anew after getting the new libEQ.a)

[sequser5516]

When I try to compile with Cygwin doing "gcc keyring.c -o keyring.exe"

I get a huge error about not finding Files such as Time.h, string.h, etc, etc.

What could this be?

[baelang]

Originally posted by sequser5516
When I try to compile with Cygwin doing "gcc keyring.c -o keyring.exe"

I get a huge error about not finding Files such as Time.h, string.h, etc, etc.

What could this be?

Well, that is not how you compile keyring. you should use the Makefile as per the instructions. if you don't have make, then you need to read the Makefile to see how to compile.

for version 1 of keyring, the command line would be:
gcc -o keyring.exe keyring.c -lth32 -lws2_32

for version 2 of keyring, it would be several commands, one for each object file and one to link all the objects with the libraries into the exe file.

If you ARE using the Makefile, then your libraries must not be in the default path. (or not installed) you'll have to figure out where they are and specify them to gcc on the command line or in the makefile.

[Adeon]

Just to be sure.. Downloaded latest LibEQ.a

Did the checksum.. Recompilled.. Cheched the 0x0078aad0 mem address in config, checked the port, IP etc all ok..

Compiled ran it in verbose mode..

When it finds the key..

SendSessionKey function called with key: 420197211

Always the same, even after reconnect reboot, rezone.. Does this refer to the mem address? Or is this supposed to be the Key, why dosnt it change..

Anyway its not working..

I did change the Name of the file and the config file name.. (Updated the source to reflect this in keyring.h.. I compiled it using the make file then renamed the .exe

The SHowEQ box recieves the Key.. BUT crashes during decode, and say Load Map "Crappy ANSI/ASCII chracters"

Failed to Decode...

:(

[Howdy]

One problem that I have with this sniffer is that you have to leave the folder name "Keyring" in place for it to work. You can change the name of the .exe to whatever ya want to be "stealthy", but it still has to sit in C:/keyring. Any way around this?

[fade2000]

Well I've tried unsuccessfully to get keyring running and I'm at wit's end.

Keyring runs fine. And apparently send a key (or something similar). I have the latest offset in the config file and I use the same port that I've listed to listen on ShowEQ (in the xml file that holds that setting).

At first I just got bad CRC error feedback when the key was sent to ShowEQ. After realizing I probably compiled the latest CVS build with the wrong libEQ.a, I got it from Smurfette's site and recompiled clean and re-installed.

Now my errors have changed, but I get a segmentation fault and crash of ShowEQ whenever the key is sent.

Keyring still gives the same feedback ... "Key sent to (blah.blah.blah:blah)."

But this isn't working. Has anyone seen similar problems here or am I better off trying a new keysniff proggy? I'm on XP, I figured this one would work well since it was tested and ran okay in XP.

[willied]

I got keyring running fine but showeq is not decoding. Im kinda new at this I wasn't sure how to know what ip address to sent it to so i found a website that displayed linux boxes IP add it was
www.lawrencegoetz.com/programs/ipinfo. it dispayed what I think is my ip add. I edited .ini file with this and offsets on keyrings website and set port to 666.

I have seq running and set port under decode menu to 666. I then star keyring from comand promt with no errors. I start eqw and when i log on char nothing decodes. I check command window and it shows sent the key to (ip address):666

Any idea what im doing wrong maby site isnt showing me correct ip add?

any help would be appriciated.

*edit* is there a way I can get the program to manualy display decode info incase I cant get it to send to linux box?

[datadog]

Running keyring with the -v option will display some helpful info.

Keyring is working fine for me. I have a telnet daemon (free one I found on the web somewhere) running on my EQ box behind EQ (not running EQW). I just leave a telnet window open from my SEQ box to the EQ box and run..

keyring -v -e

whenever I want a decode. I dont use it all the time. The -e option tells it to run once and quit.

I had some similar problems to those discussed here. All were resolved by getting a fresh copy of libEQ.a, updating from the latest cvs and recompiling SEQ, then setting the correct port number in the .ini file. I thought I read somewhere where baeling said you need to use a port above 10000 for this. I dont know why this is the case, but im using one above that range.

Also, make sure you have the correct offset.

[baelang]

Originally posted by Howdy
One problem that I have with this sniffer is that you have to leave the folder name "Keyring" in place for it to work. You can change the name of the .exe to whatever ya want to be "stealthy", but it still has to sit in C:/keyring. Any way around this?

either use the -f option to specify a different config file path , or edit the source code and change the default path to the config file and recompile.

[baelang]

Originally posted by willied
Any idea what im doing wrong maby site isnt showing me correct ip add?


on your linux box, type:
ifconfig -a

and that will give you all the information about your network interfaces and their ip addresses, netmasks, etc.

but you had to specify that information when you installed linux, so you ought to know what the ip address is. unless you are using DHCP.

[Molly]

this method is working great for me except it stops decoding if i port or go into another zone. if i shutdown eq and the keyring, then start them back it, it works fine for the zone im currently in. i did a search for zoning and decode zon to see if anyone else had this problem but i did not find anything.

[datadog]

by default keyring runs every 60 seconds. This parameter is editable in the .ini file.

Each time you zone, keyring needs to send a new key to the SEQ box. You may have to wait as long as 60 seconds for the key to be sent if you are running with the default settings.

Personally, i telnet into the EQ box from the SEQ box and run keyring -e -v whenever i want to see a decode (not always needed.. why risk having it running all the time).

Lots of free windows telnet servers out there. Check out download.com etc...

[cybris]

I can't even tell if keyring is sending the the key.

it says sending the key to the IP address and port Io I have setup in both keyring.ini and Seq Decoder menu.

I do have the latest libEQ.a and I also recomplied Seq after I downloaded it.

I have the latest offest setting in the .ini file.

Any clues?

[cybris]

nm that last post.

Thought it would load up when my toon loaded in.
All I had to do was zone once and everything lit up like a christmas tree :)
very happy now works great now.

[SZSEQ]

Unfortunately for me that is not the case.

I have SEQ 4.3.3 the newest LIBEQ.a with correct md5sum

Recompiled.

Keyring has correct IP and Memory offset. SEQ configured to hear on correct port. Keyring says sending key but nothing is decrypted. Help please :(

[AlphaBeta]

Are you sure you have the right libEQ.a? I had the same problem a while back where I was downloading the new libEQ.a but insted of replaceing it it just named it something else. I had to go in and delete the libEQ.a before I downloaded the new one.

[SZSEQ]

Yep, new rm libEQ.a download the new one, verify md5sum, recompile, jacked. I guess I lose :(

[Mr. Suspicious]

Willied:
I check command window and it shows sent the key to (ip address):666


You should be bonked on the head with a very thick dictionary. Please read the announcement section on what you are doing wrong (it's been posted oh... like 100 times in a 100 different threads (even THIS one!!!) aswell.

[SZSEQ]

AHH Thank you thank you, you are my hero!!

[mudtoe]

Looks like you can run it without a config file at all if you specify all the operands on the command line. I created a one line ".bat" file with all the operands and it works fine in a directory other than keyring with no config file. I'm using the -e option so I only do a single instance of a decode when needed.

Slightly off topic, is there a way to get SEQ to save the key port number? I seem to have to key it in every time, even though I've did a save preferences after putting it in.


mudtoe

[baelang]

Originally posted by mudtoe
Looks like you can run it without a config file at all if you specify all the operands on the command line. I created a one line ".bat" file with all the operands and it works fine in a directory other than keyring with no config file. I'm using the -e option so I only do a single instance of a decode when needed.

Slightly off topic, is there a way to get SEQ to save the key port number? I seem to have to key it in every time, even though I've did a save preferences after putting it in.


mudtoe

that will work with the latest version, but 2.1 had a problem with multiple options so it wouldn't work before.

Also, (although i haven't verified this) i think a config file must exist unless you use the -e option, although the config file can be empty.

[cheese_poker]

is there a way to get SEQ to save the key port number?

Yes. In SEQ there is a "save" function. Save preferences, or settings or something. Sorry I do not have access to my machine at the moment, but I did save my port setting and it works on subsequent power ups.

[baelang]

please move yourself on over to the newest version:

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