(F)or (Y)our (I)nformation: =========================== My home phone number is 214-790-6265 after 7pm CST to 1AM on weekdays and usually anytime during the weekend Or, send me a Crashmail message to 8:930/20 (214)790-0754 ... Smlnet reads and writes a .Msg file as stated in the FSC documents. This format is the same as seen on Opus and similar boards. Nodelist.Idx and Nodelist.dat are Version 6. BinkleyTerm uses these files when polling other systems. Fido-Net is Zone 1 Rbbs-Net is Zone 8 Mysetup.Zip includes everything on my setup. I am dead-end net/node, with a Hst 19.2K locked. So, hence, have smlnet.fos option for Node1 turned on(Y) for fossil support. Directory structures are described in the enclosed binkley.bat For my setup: BinkleyTerm 2.2 answers the phone and polls other systems Qmail 1.0 imports/exports the echomail ParseLst keeps track of the Nodelist RBBS-PC Bulletin Board Program ReplyLnk Creates ReplyLinks for all messages Renum uses Confmail 3 option to pack/renum old messages Michael Davis of 8:930/1 has created a file called Setup6.Zip (soon to be Setup7.Zip). He provides excellent instructions and batch files for the beginner to setup a Netmail system. You can download (or Freq) the file from him, or other fashionable locations in the universe. Smlindex.Exe and Smlmport.Exe create an index file of the messages in the conference, so if you renumber the conference you must run smlindex.exe to recreate a matching smlindex.dat file for it. If possible, put all Smlnet related files (except Smlindex.exe and Smlmport.exe) into a separate subdirectory from other programs. This will make it easier for you to modify/maintain the configuration files. A sample of my NET.BAT that a remote caller can call directly from RBBS looks like: CD \RBBS\NET Copy \RBBS\Dorinfo%1.Def Smlnet %1 CD \RBBS Smlchk.Exe will check the validity of your Smlnet.Cnf file only. But, you should still verify this configuration files when setting up to make sure they are correct: Smlnet.Adv <- Advertisement Smlnet.Cnf <- main Configuration file Smlnet.Dsz <- DSZ setup Smlnet.Fos <- Fossil setup Smlnet.Nam <- Name list setup for Netmail Smlnet.Off <- Off time of program (for multinode systems) Smlnet.Zon <- MultiZone setup Smlnet.Des <- Detail Descriptions of each echo conference Smlnet 1F has fossil support. The assembly code is developed by Ken Bachman from help of the fossil documents that were found in x00 files. It does Block Read and Write I/O with the Fossil, and supports upto 38400 baud. It has been successfully tested on local systems running x00 fossil driver. also, successful on normal systems and locked- baudrate systems. My config.sys line to setup x00 for the locked baud rate at 19.2 is: DEVICE = X00.sys B,0,19200 T=512 R=8192 these and are other settings were setup to suggestions in Mike Davis's Setup?.Zip documents. Fossil support and DSZ: Smlnet replaces the port [COM] found in the smlnet.dsz with the text portx ?,? found from the smlnet.fos file. It will only do this when the fossil is turned on (Y). You might need a newer version of DSZ to have the portx support. I found that a Dec 88 version of dsz didn't have the portx command, but the recent Mar 89 did. when portx support was added to DSZ, I don't know. If the DSZ doesn't have the portx support, DSZ will error out. Again, you do not have to activate Fossil support (Y in Smlnet.Fos) if you don't want to. Dorinfo?.def vrs Pcboard.sys Personally, I like the Dorinfo?.def for there is a much stronger standard for it then Pcboard.sys. Also, the Dorinfo?.def has everything that is necessary whereas for the pcboard.sys, Smlnet.exe needs to read the Users file to get the callers security level. I will try to keep a copy of translator programs on my system that anyone can download. So, then if they are running an Opus board, and can't find one locally that will make a Pcboard.sys or dorinfo?.def, you hopefully can find it here. Smlware echoconference is available on Rbbs-Net. I haven't the foggiest if it is available on Fido-Net or any others. If you want it on Fido-Net or other, then please send me sufficient info on who I need to contact to do so. Suggested Procedure for adding new echo conferences. 1. MD (Make) the Subdirectory 2. Add the new echo to the Areas.BBS file 3. Send a message to your hub to start receiving the echo 4. then wait till a day or two till some messages arrive in the echo 5. add the echo to the smlnet.cnf file - first you need to assign a unique id# number. (sml-chk will output unused id# numbers that you can use) - add the unique id#, subdirectory drive:\path, and description of the new echo. Probably, best to add it in the echo list so that the echo decriptions are in alphabetical order for easier finding for the remote caller. 6. run sml-chk to help verify that you didn't make any mistakes when you added the echo in smlnet.cnf