"Crack Man" could have a couple other connotations that might not
be so good.. ;)

The first one's free... Others will be too, assuming I get around to more. ;)

The first "crack"? :P

I finally got a rount-tuit today, of course I can't find the archive I downloaded. Every chance its buried out in some dismembered network, I was expecting bench/desk installs on Monday but it got deferred and I have put it all back.

Not sure if its my timing or its dead in the water, but AM isn't answering.

Spec


*** THE READER V4.50 [freeware]
--- SuperBBS v1.17-3 (Eval)
* Origin: A camel is a horse designed by a committee. (21:3/101)

I finally got a rount-tuit today, of course I can't find the archive I downloaded. Every chance its buried out in some dismembered network, I was expecting bench/desk installs on Monday but it got
deferred and I have put it
all back.

I can definitely relate to 'where did that file go??' Sometimes we shouldn't be trusted with this much storage capacity. ;)

Not sure if its my timing or its dead in the water, but AM isn't answering.

I was able to connect to another.tel just now. I did notice a lot of bot connections this morning, so possibly there were enough simultaneous connections to tie up the entire system for a while. (time to tweak the bot detection).


Chris/akacastor

--- Maximus 3.01
* Origin: Another Millennium - Canada - another.tel (21:1/162)

Hey there,

Despite our brief chat, and realisation some of this wasn't working like I thought Super stubbornly refuses to appear registered. I suspect at this
point that its not really looking for the SCC file in \sbbs but \sbbs\node# have yet to try it though. Adding to the trickiness is that each "node" has
its own partial config as well, which I've added the reg code to, although it didn't alter the current state of affairs.

Spec


*** THE READER V4.50 [freeware]
--- SuperBBS v1.17-3 (Eval)
* Origin: A camel is a horse designed by a committee. (21:3/101)

Despite our brief chat, and realisation some of this wasn't working like I thought Super stubbornly refuses to appear registered. I suspect at this point that its not really looking for the SCC file in \sbbs but \sbbs\node# have yet to try it though. Adding to the trickiness is that each "node" has its own partial config as well, which I've added the reg
code to, although it
didn't alter the current state of affairs.

I thought that the SCC file should be in \sbbs, but after thinking about it a bit I realize I never tried a multinode installation. So you may have identified the problem!

Let me know if I can help troubleshoot. I can tell you that the timestamp of the .SCC file is important (the filename is based on the timestamp and they must match in order to be accepted by SuperBBS).


Chris/akacastor

--- Maximus 3.01
* Origin: Another Millennium - Canada - another.tel (21:1/162)

I don't have it here yet, but I've seen your reply.

After a fair amount of messing around, it isn't working..

ACC in both \sbbs and \sbbs\node#
Configs in \sbbs and \sbbs\node# all match.

I am inclined to think my NFS mount is at least partially responsible for date/time issues.. But it doesn't have a local drive so it kinda is what it is. Which if it is, makes it game over, I believe.

Spec


*** THE READER V4.50 [freeware]
--- SuperBBS v1.17-3 (Eval)
* Origin: A camel is a horse designed by a committee. (21:3/101)

ACC in both \sbbs and \sbbs\node#
Configs in \sbbs and \sbbs\node# all match.

I am inclined to think my NFS mount is at least partially responsible for date/time issues.. But it doesn't have a local drive so
it kinda is what it
is. Which if it is, makes it game over, I believe.

If you do a DIR listing on the key file, the file date should match what it was when it was first created by the keygen. If DIR shows the correct date/time then "it should be OK".

The multi-node setup is something I hadn't thought to test - I only tested the keygen in a single node setup, where the .SCC file goes in the main SBBS directory. I am not certain where it looks for the files in a multinode setup.

Just to double check - you did put the .SCC file in the SBBS directory AND also entered the matching registration code in the 'Registration' screen of the CONFIG program?

If all is fails, there is another option - before completing the keygen, I cracked the OVRSBBS.OVR file to disable the check for the key file. With the crack, you can replace OVRSBBS.OVR and enter a registration code in CONFIG, and then it will run in registered mode. (no need for .SCC file at all) I can put the original SBBS-KEY.ZIP (crack version) online if you want to try it. (I took it offline when I replaced it with the full keygen version SBBSKEY2.ZIP)


Chris/akacastor

--- Maximus 3.01
* Origin: Another Millennium - Canada - another.tel (21:1/162)

If you do a DIR listing on the key file, the file date should match what it was when it was first created by the keygen. If DIR shows the correct date/time then "it should be OK".

They appear to have the correct date time, at least all versions are consistent. I can't guarantee off hand they have the exact time I created them.though.

The multi-node setup is something I hadn't thought to test - I only tested the keygen in a single node setup, where the .SCC file goes in the main SBBS directory. I am not certain where it looks for the files in a multinode setup.

In the single node setup its usually the SBBS environment variable, followed
by the path, and current directory. It gets a little sketchier in multinode
and the earlier two settings can get in the way of node specific settings, or the other way around. I'm quite rusty at it now, but there used to be some you'd have to set in one location or the other and then delete the offending versions. I've tried all the permutations I can think of..

Spec


*** THE READER V4.50 [freeware]
--- SuperBBS v1.17-3 (Eval)
* Origin: A camel is a horse designed by a committee. (21:3/101)

If you do a DIR listing on the key file, the file
date should match what
it was when it was first created by the keygen. If
DIR shows the correct
date/time then "it should be OK".

They appear to have the correct date time, at least all versions are consistent. I can't guarantee off hand they have the exact time I created them.though.

I uploaded a tool 'SBBSDATE.ZIP' to Another Millennium BBS (another.tel) file area 4 (cracks).

Example output:
---------------

D:\PROJ\SBBS1173\KEYGEN>dir *.scc

Volume in drive D is DOSShare
Directory of D:\PROJ\SBBS1173\KEYGEN

577086CE SCC 32 04-10-24 1:12a
1 file(s) 32 bytes
2,147,450,880 bytes free

D:\PROJ\SBBS1173\KEYGEN>sbbsdate 577086ce.scc
File date: Wed Apr 10 01:12:00 2024
File size: 32
SCC filename: 577086CE.SCC

D:\PROJ\SBBS1173\KEYGEN>


The last line printed by SBBSDATE - "SCC filename:" - will print the expected filename for the .SCC file. The output from SBBSDATE should match the .SCC filename. If SBBSDATE gives a different filename, then that will be the cause of the problem registering SBBS.

In the single node setup its usually the SBBS
environment variable, followed
by the path, and current directory. It gets a little sketchier in multinode and the earlier two settings can get in the way of node
specific settings, or
the other way around. I'm quite rusty at it now, but there used to be some you'd have to set in one location or the other and then
delete the offending
versions. I've tried all the permutations I can think of..

I've been resisting configuring a multinode SBBS system here out of concern for opening a whole new can of worms for myself. :) But it is tempting, to get to the bottom of this.

I did put SBBS-KEY.ZIP - v1 of the keygen, which uses a cracked OVRSBBS.OVR to eliminate the .SCC files - back online on Another Millennium, in file area 4 (cracks). If you don't mind a cracked executable, it eliminates the .SCC file check altogether. (I do think the v2 of the keygen with correct .SCC file should be working also though.)


Chris/akacastor


--- Maximus 3.01
* Origin: Another Millennium - Canada - another.tel (21:1/162)