I also found the following in SDOC117A.ASC:
| As of version 1.15, there is a new security feature build in
| to SuperBBS. When running a registered version of SuperBBS,
| you will need to have a valid .SCC file. Without this file
| your system will not run.
|
| Once you have a correct .SCC file, you will NOT need to down-
| load a newer .SCC file when they come available.
|
| When you register, you will get a key and a .SCC file. Check
| the support nodes for more information on this subject.
So I guess the SBBS-KEY keygen by itself won't be enough
to get SuperBBS to run registered. I will have to dig a
bit deeper to figure out the .SCC file. It would be
helpful if there are any valid .SCC files I could look at.
SBBSKEY2.ZIP is available in file area 4 (cracks) on Another Millennium BBS (another.tel).
SBBSKEY2.ZIP is available in file area 4 (cracks) on Another Millennium BBS (another.tel).
Awesome work, AKAcastor! Do you know of any live/current SuperBBS boards?
SBBSKEY2.ZIP is available in file area 4 (cracks) on Another Mille BBS (another.tel).
Awesome work, AKAcastor! Do you know of any live/current SuperBBS board
Spectres bbs the lower planes runs on superbbs
Awesome work, AKAcastor! Do you know of any live/current SuperBBS boards?
--- SuperBBS v1.17-3 (Eval)
I figured out the .SCC key file for SuperBBS 1.17-3 and added it to the keygen - now the keygen is fully working and generates a reg # and
creates a .SCC file to place in the SBBS directory.
Then you better use this keygen! :)
I figured out the .SCC key file for SuperBBS 1.17-3 and added it to the keygen - now the keygen is fully working and generates a reg # and creates a .SCC file to place in the SBBS directory.
While I don't have a use for this particular crack, this
legit makes me feel good to see. It would be fun to make
a list of old BBS softwares, doors, etc. that are
abandoned and don't yet have cracks... then well you
know... crack 'em.
I figured out the .SCC key file for SuperBBS 1.17-3 and added it to the
keygen - now the keygen is fully working and generates a reg # and
creates a .SCC file to place in the SBBS directory.
AKAcaster is AKA the Crack Man :)
AKAcaster is AKA the Crack Man :)
"Crack Man" could have a couple other connotations that
might not be so good.. ;)
I figured out the .SCC key file for SuperBBS 1.17-3 and added it to t keygen - now the keygen is fully working and generates a reg # and creates a .SCC file to place in the SBBS directory.
AKAcaster is AKA the Crack Man :)
While I don't have a use for this particular crack, this legit makes me feel good to see. It would be fun to make a list of old BBS softwares, doors, etc. that are abandoned and don't yet have cracks... then well
you know... crack 'em.
soAKAcaster is AKA the Crack Man :)"Crack Man" could have a couple other connotations that might not be
good.. ;)
True. Have to think of another good name. BUt you'all know what I mean :)
That is a good idea. AKA, can I made a Google doc and post it for folks to add to??? Of course, wouldn't be asking for everything to get done - but might give people a place to post what they don't have access to in 2o24...
That is a good idea. AKA, can I made a Google doc and post it for fol to add to??? Of course, wouldn't be asking for everything to get done but might give people a place to post what they don't have access to 2o24...
A spreadsheet to track this stuff would be awesome! I haven't cracked
old DOS stuff in a very long time, some things to get my hands dirty
again would be fun :)
"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. ;)
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.
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.
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.
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.
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..
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 66 |
Nodes: | 4 (0 / 4) |
Uptime: | 05:19:31 |
Calls: | 620 |
Calls today: | 6 |
Files: | 7,638 |
Messages: | 293,362 |