HeyRick / BudgieSoft Old source code

The licence conditions

Libraries

Somebody, Peter Naulls?, has made a proper 32 bit version of DeskLib 2.30. I would recommend that you use this version for writing software; however to get my software compiled and up&running as quickly as possible, you'll probably want to download my version of DeskLib. Go here for more info.

You CANNOT use Desk v3.20 (etc) as too much has changed from it's DeskLib origins.

CastAVote

• The CastAVote BBS 'door', VoteModule supplied (BASIC)
  You can install this on an ArcBBS or ArmBBS server and provide voting facilities for your bulletin board. It's a complete all-in-one package.
   
  
• The unfinished "local vote" software (C)
  This was intended to provide the sysop with a GUI way of participating, but it seems most took part using the local login. Fair enough, I did it that way too! :-)
   
  
• NVP (Network Vote Protocol) to share votes via FidoNet (BASIC)
  A very useful extension to allow several BBSs to 'share' common votes. One BBS is designated the "MASTER" and it collates votes. All of the other BBSs are to be designated "SLAVE" and they send data to, and receive data from, the assigned master.
  Unlike "my competitor at the time", the selection of master and slave is arbitrary so long as those involved agree. Back in the main days of CastAVote, there were actually two masters and two vote 'networks'.
  Also, unlike my competitor, the system works using 4D-address style fidonet packets. This means that you can have CastAVote data relayed via Binkley along with all of the user messages or your own messages. There is no requirement to regularly FREQ from the designated master.
   
  
• VoteEdit (BASIC !?)
  One thing a sysop will need to do from time to time is clear out old votes (CastAVote can handle up to 220 votes), remove those which are potentially offensive or in bad taste, and the usual sorts of management functions.
  Rather than including this stuff in the door, I have written a separate stand-alone utility, VoteEdit, the vote database editor.
  This is the version written in BASIC (uses VoteModule so isn't horribly slow). I could have sworn I wrote a new version of this in C? Am I imagining things or was it a victim of my disc failure all those years ago?

In any case:

PATCH: If, upon trying to connect CastAVote to the BBS it appears to quit without even loading, then this may be because you are using the source release which does not have all of the resources.
A rather idiotic bit of coding on my part sets default options, then aborts if the configuration data is not located.
Look in the source for DEFPROCconfigure and at the end of that procedure you will see:

  ELSE
    PROCexitanddie(0)
  ENDIF
ENDPROC

Simply stick a REM in front of that PROC call, or remove it. Then CastAVote will work!

By the way, it defaults as doornumber%=23, you can call it as door 23 or alter this in DEFPROCconfigure...

Digitiser

I did want to expand this with better quality and colour, however neither HCCS nor the designer ever returned my emails (despite the Vision no longer being in production), and my ability to figure out ARM code was not up to that required to take apart a complex program. So, this is the best we have.

The inner core is properly © HCCS, the rest being my bolt-in. In any case, I don't imagine they'll argue - the code is completely 100% useless if you don't actually have an HCCS Digitiser!

Whatever, here's the code:

You also get, as an added benefit, a quick'n'simple viewer and a time-lapse program (edit the paths first!) which should be left running (with monitor off) and it will take a small snapshot every 30 seconds. I had a feeling that the landlord was coming into my room and coincidentally stuff was departing my room at roughly the same time frame. This cobbled-up software proved to be somewhat useful...

DoorLib

In order to build, just compile everything into the 'o' directory. Don't worry about missing functions. If any executables were created, delete them - we're only interested in the object files.
Then run the obey file supplied to build the "DoorLib" library. It will leave it there as "o.DoorLib"; which you can then copy into the "o" directory of applications that use DoorLib.

The code:

FetchMail

What FetchMail does is work with Argonet's Posty to manage and pre-process your emails. You can whizz though your emails before Posty gets to see them, deleting those that are undesired, bouncing those you don't want, and so forth.
You can also extract and save mailboxes.
This software was written in C.

OvHTML (for RISC OS)

Parlez

You will need DoorLib - sources above, or go here for prebuilt (APCS/26).

PATCH: You'll first need to copy in a version of the DoorLib library.

Next, you will need to create "s.getstat", which looks like this:

PC  RN 15

        AREA |C$$code|, CODE, READONLY
        EXPORT  arcbbsfiler_get_status_pointer

arcbbsfiler_get_status_pointer
        SWI     &41014
        MOVS    PC, R14

        END

Amend as necessary if you are building to APCS/32 - though, I don't know if ArcBBS itself ever had an APCS/32 build. I've not used it in a loooong time!

Now amend the MakeFile so the !RunImage is built as follows:

@.!RunImage:   @.o.parlez C:o.stubs DeskLib:o.DeskLib 
        link $(linkflags) @.o.parlez @.o.getstat @.o.doorlib C:o.stubs DeskLib:o.DeskLib

and the parlez object file is built as follows:

@.o.parlez:   @.c.parlez
        objasm $(objasmflags) -from @.s.getstat -to @.o.getstat
        cc $(ccflags) -o @.o.parlez @.c.parlez

It's a crappy makefile, but I can't be bothered to rewrite it - it works as it is...

SysOpChat

Teletext (for RISC OS)

!Teletext is, in my opinion, the best teletext viewer for RISC OS. The powerful scripting system makes it miles better than the commercial Teletext+... but hey, Paul Skirrow can probably list attributes his software has over mine (if any <grin>!).
In any case, full (BASIC) sources are here:

Note - the teletext driver module is supplied (with kind permission of the author), however it is not mine so please do not ask, nor expect, sources.
Furthermore, if you wish to distribute teletext software that uses this module, you really should ask Colin Granville for permission. Don't ask me, and don't assume "it is okay" - ASK!

More to come. If you have any requests - email me!