Server Help

[CypherJF]

For those beginning w/ ASSS, I noticed the ZIP file is packaged wrong (ie: it's looking for files in config/, instead of ../config/); you will need to move the following from /bin/ to /:
* asss.exe
* pthreadVC.dll
* libdb4.dll

Note: Still doesn't seem to work w/ Catid's biller 1.11j. .sigh.
Note: Still doesn't support .39pr; obviously we/i knew expected this, but just reiterating.

@GREL: I get: 'D <billing> trying to connect to user db server at 127.0.0.1:1850'... Why is the billing trying to connect to the DB server, when the DB module is not loaded; and it's supposed to attempting to connect to the biller? Did I just setup a conf wrong.. or...

[CypherJF]

I also want to throw in here, what compiler did you use?

And, could you name "wincrap" to something not so... crappy... LOL...

[Grelminar]

If you read the README, you would have read that you're supposed to run bin/asss from the root directory. So it's not looking in the wrong directory, you're running it from the wrong place. It might help if I put a batch file or something in the root directory to run bin/asss.exe.

I'm trying to move away from the word "billing", since that's a historical accident and doesn't describe what it does. So I'm calling it the "user database server", which is more accurate. Obviously, I didn't change the module names yet, but I probably will eventually.

About the assertion failure: I currently don't know what's going on there, but I've seen it before, and so has at least one other person. This issue may disappear soon, because:

That build was compiled with MS Visual C++. However, since I have only the command-line tools from VC (which are a free download from MS), I'm not sure I want to support that long-term. I think mingw32 might be a better solution, and there's even a free IDE available for it, for those who like IDEs. I'll play around with it and see if I can come up with something that actually lets other people build it on windows (I doubt anyone will be able to make use of the Makefile that comes with the current windows package).

[Mine GO BOOM]

[Grelminar]

By "same problem" do you mean the assertion failure, or the not finding config files?

[Mine GO BOOM]

Assertion error. It correctly finds all the config files in all the ways I've tried (my little batch file and copying to root directory). If you'd want to use the START program for a batch file, here is its help output. Whenever I make batch files using start, I usually always put in the /NORMAL and /D, even if they are set to default.

Code: Show/Hide Starts a separate window to run a specified program or command. START ["title"] [/Dpath] [/I] [/MIN] [/MAX] [/SEPARATE | /SHARED]       [/LOW | /NORMAL | /HIGH | /REALTIME | /ABOVENORMAL | /BELOWNORMAL]       [/WAIT] [/B] [command/program]       [parameters]     "title"     Title to display in  window title bar.     path        Starting directory     B           Start application without creating a new window. The                 application has ^C handling ignored. Unless the application                 enables ^C processing, ^Break is the only way to interrupt                 the application     I           The new environment will be the original environment passed                 to the cmd.exe and not the current environment.     MIN         Start window minimized     MAX         Start window maximized     SEPARATE    Start 16-bit Windows program in separate memory space     SHARED      Start 16-bit Windows program in shared memory space     LOW         Start application in the IDLE priority class     NORMAL      Start application in the NORMAL priority class     HIGH        Start application in the HIGH priority class     REALTIME    Start application in the REALTIME priority class     ABOVENORMAL Start application in the ABOVENORMAL priority class     BELOWNORMAL Start application in the BELOWNORMAL priority class     WAIT        Start application and wait for it to terminate     command/program                 If it is an internal cmd command or a batch file then                 the command processor is run with the /K switch to cmd.exe.                 This means that the window will remain after the command                 has been run.                 If it is not an internal cmd command or batch file then                 it is a program and will run as either a windowed application                 or a console application.     parameters  These are the parameters passed to the command/program If Command Extensions are enabled, external command invocation through the command line or the START command changes as follows: non-executable files may be invoked through their file association just     by typing the name of the file as a command.  (e.g.  WORD.DOC would     launch the application associated with the .DOC file extension).     See the ASSOC and FTYPE commands for how to create these     associations from within a command script. When executing an application that is a 32-bit GUI application, CMD.EXE     does not wait for the application to terminate before returning to     the command prompt.  This new behavior does NOT occur if executing     within a command script. When executing a command line whose first token is the string "CMD "     without an extension or path qualifier, then "CMD" is replaced with     the value of the COMSPEC variable.  This prevents picking up CMD.EXE     from the current directory. When executing a command line whose first token does NOT contain an     extension, then CMD.EXE uses the value of the PATHEXT     environment variable to determine which extensions to look for     and in what order.  The default value for the PATHEXT variable     is:         .COM;.EXE;.BAT;.CMD     Notice the syntax is the same as the PATH variable, with     semicolons separating the different elements. When searching for an executable, if there is no match on any extension, then looks to see if the name matches a directory name.  If it does, the START command launches the Explorer on that path.  If done from the command line, it is the equivalent to doing a CD /D to that path.

[CypherJF]

I moved the files down a directory, and ran it from a .bat file anyways...



Thanks though for the win build, good foward steps $

[k0zy]

Quick Tip:
Open the included .conf, .h and readme files in WordPad instead of Notepad.
Notpad doesn't recognize the *nix \n as a new line, because windows needs \r\n.

Start->Run->"write"->Ok
OR
Start->(All )Programs->Accessories->WordPad
Drag and drop the .conf file from the explorer on the Titlebar from WordPad.

Bob Dole.. Bob Dole... Bob Dole...... bob dole.... bob... dole....
_________________
It's a shark! Oh my god! Unbelievable!

[CypherJF]

Right; I have shortcuts of Wordpad and Notepad in the 'Send To'... for this very reason...

[Nerusai]

Fixed win32 binary for asss.exe can be downloaded here, I'm not 100% sure everything is in it, but it ran fine here.

http://members.home.nl/siaon/asss-1.3.1win32.rar

[Mine GO BOOM]

[CypherJF]

I tried that as well, asss appears and then closes... I'll check it out more later tonite..

[CypherJF]

[Nerusai]

[Nerusai]

[CypherJF]

Says Unrecoverable error in loading module billing_ssc... tried the @ thing and it still didn't stay open; :/

[Maucaub]

1) The distributed binary also crashes with an assertion error on my system. I haven't invested the time to track down exactly why, yet, but I might if I get the time. Upon first glance, it would seem something's wrong with the compile/link in that distro because ....

2) If I recompile with my copy of VC6, it works fine, no changes to the code necessary. I will also rebuild using the free VC Toolkit once I find the time.

3) @Cypher: My recompiled version works with my biller using the billing_ssc module, so it should work with VIE-compatible billers if compiled and configured properly.

4) doc/ is missing files in the windows distro, specifically the userguide and the devguide. The files are present in the linux distro.

5) Wincrap? Come on, now ....

[Smong]

I also get the arenaman assertion error (I'm using win98se).

The billing works with subbill, but says

[CypherJF]

>> this was just for debugging purposes... all parties not involved can disregard

[Smong]

Incase anyone is wondering, the two logs I posted were from the biller consoles.

[Nerusai]

Same build runs like a charm here(Btw, my build does miss the billing modules and my ISP won't let me upload the fixed version so if you want it, I'm often on as Nerusai on SSCX)

I'm 100% virusfree as well, so that's not it.

[Solo Ace]

100%? And you're running Windows?

[Grelminar]

The "invalid packet 21" is expected. It's a packet that the ssc biller understands, and I expect others don't, but asss always sends it anyway.

I'm not sure what's wrong with catid's biller. I might give it a shot if I have time, but I expect it'll be easy for anyone to track down, as the source to both sides is available.

Sorry about the assertions and other weirdness in that version. It was my first try, and clearly it didn't work so well. I can't really debug stuff with vc, since I only have the free tools. But: I'm working now on getting it working under mingw in the dev-c++ ide. I should have a package that'll be buildable out-of-the-box (after installing dev-c++), and be much easier to maintain and debug.

[Grelminar]

oh, and it's missing the pdf/html versions of the user guide and dev guide because those are generated by latex and some other tools, which would be extremely difficult to get running on windows. up-to-date versions of those documents should be available on sscx.net/asss/.