INSTALL.EXE.x/SKCSETUP.HLP

119.9 KB 36ccdbcbc52db153…

FBHF¡▀A▄'⌠ ╒══════════════════════╕ ╒════════════════════════╕
│████ ██ █ ██ █ ██ ██│ │████ ██ █ ██▀▀ ████ ██ █│
│██ █ ██ █ ██ █ ██ ██│ │██ ██ █ ██ ██ ██ █│
│██▄▄ ██▄▀ ██ █ ██ ██│ │██ ██▄█ ██▄▄ ██ ██▄▀│
│▄▄ █ ██ █ ██ █ ██ ██│ │██ ██ █ ██ ██ ██ █│
╒════════╕│██ █ ██ █ ██ █ ██ ██╘═╛██ ██ █ ██ ██ ██ █│╒═════════╕
│████████││████ ██ █ ████ ████ ████ ████ ██ █ ████ ████ ██ █││█████████│
╘════════╛│████ ██ █ ████ ████ ████ ████ ██ █ ████ ████ ██ █│╘═════════╛
│████ ██ █ ████ ████ ████ ████ ██ █ ████ ████ ██ █│
│████ ██ █ ████ ▀▀▀▀╒═════════╕▀▀ ▀ ████ ████ ██ █│
│████ ▀▀ ▀╒═════════╛ ╘═════════╕▀▀▀▀ ██ █│
╘═════════╛ ╘═════════╛

Helpsystem for SKCSETUP Version 4.0
Last update: 08.08.1996

Hilfe-Index

If you don't know how to use the help, press ENTER twice.

A *BIG THANKS* goes to Conrad Justus Köhler, who has done a great job on translating the german help partly to the english language. His parts are very easy to identify: The parts written in good english are done by him, the parts completely ununderstoodable are done by me.. ;))
í'
■ Menu System ■

'
■ Menü Check ■

'
■ Menü Extern ■

'
■ TD0 Test ■

ITD0 files are a special kind of archives holding complete disk contents.
£Here you can define a tester for TD0 files. The TD0 compressor has a file calles TDCHECK.EXE, that should be entered here with the path, where it is found.
CThe option "use it" switches wether SKC should check TD0's or not.

'Ω
About the help:
Help about help
Help index

SKC global:
Parameters
Uploadchecking
External files
Environment var's

Support-Sites

Music while coding ;)

╙/W
oçƒ,╣╘╙'
■ Help on the Helpsystem ■

òThis program gives you to each menu entry a seperate help. If you don't know what one seperate options does mean just go to that option an press F1.
─A helpwindow will be opened then that looks like that you are viewing at the moment. You can scroll through it with the cursor or with clicking the mouse to the upper or lower part of the window.
Many helpwindows have marked "crossreferences". You may choose them with pushing the TAB or the Shift+TAB key. If you selected a crossreference you want wo have a new help on press ENTER. You also get the crossreference by duoble clicking with the mouse on it.
tYou get back from the crossreference to the prior helpwindow with pushing the Alt+F1 key or the right mouse button.
▓v'├
■ The mouse ■
│
│<-------- Connection to your PC
│
┌──┴─╥────┐
│ 1 ║ 2 │ 1 = left mouse button
├────╨────┤ 2 = right mouse button
│ │
│ │
└─────────┘

ÇThis help is a joke. If you have a mouse you know how it looks like and how it is handled, if not you don't need this help. ;-)
ÜOne interesting information: The right mousebutton (1) will result the same as ENTER in many dialogues, in helpwindows it will result the same as Alt+F1.
'º
■ The keyboard ■
│
Connection to your PC ────── │
│
┌───────────────────────────┬───┴─┐
│┌┐ ┌┬┬┬┐ ┌┬┬┬┐ ┌┬┬┬┐ ┌┬┬┐ │■ ■ ■│
│└┘ └┴┴┴┘ └┴┴┴┘ └┴┴┴┘ └┴┴┘ │┌┬┬┬┐│
│┌┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┐ ┌┬┬┐ │├┼┼┼┤│
│├┼┼┼┼┼┼┼┼┼┼┼┼┼┼┼┼┼┼┤ ├┼┼┤ │├┼┼┼┤│
│├┴┼┼┴┼┴┴┴┴┴┴┴┴┼┴┼┼┴┤ └┴┴┘ │├┼┼┼┤│
│└─┘└─┴────────┴─┘└─┘ │└┴┴┴┘│
└───────────────────────────┴─────┘

dThis interesting thing should ley directly in front of you (perhaps search under your fingers..;) )
'
■ The F1-Key ■

áNornmaly this key is located in the left upper corner of your Keyboard right besid your ESC key. In most of the cases it is the second key in the first row. ;)
S''
■ Choose a filename ■

òWith this dialogue you can choose a file. You will find in the input line the actually choosed file or a wildcard if you didn't selected a file yet.
┐You'll find filenames matching the wildcard in the window below the inputline. If you choose one of these files (ENTER or clicking with the mouse on it) it will be putted into the inputline.
▐If you scroll the window to the end you'll find a list auf directories found in the actual directory. If you choose a directory from it, the window will be refreshed, new files collected from that directory are displayed.
'
■ Choose a directory ■

ëYou can choose an existing directory in this dialogue. If you entered a valid directory earlier, this directory will be displayed first.
├Press TAB once to select the list of directories. With oushing ENTER on a directory the list will change into the selceted directory. With pushing on "Drives" you are able to choose a new drive.
EThe button [REVERT] will revert your selections to the first state..
3Press the [OK] button to accept the new selection.

''G
■ Parameters of SKC ■

/A Half mode first part (*)
/B Half mode second part (*)
/BASE Scan over your complete filebase (*)
/SUB Process subdirectories, too (Wildcardmode)

/C:<Name> Load configuration <Name>
/PKI:<Name> Load compressor definition <Name> (w/o dir!)
/ARE:<Name> Load area definition <Name> (w/o dir!)

/DUP Enable the dupecheck
/N:<Node> Specify actual node
/P:<Port> Specify actual COM
/B:<Baud> Specify actual baudrate. Only in noFOSSIL mode
/.<Ext> Use copressor with extension <Ext> for converting.
/. Disable converting
/X<+|-> Switch on|off extendet infos
/DAT<+|-> Switch on|off the use of FILES.SKC
/OLD- Swithes the datecheck on files off.
/TIC Swtiches on the option to change TIC, netmails and outbound.

å(*) = If this parameter is used it has to be the first. Else the first parameter is the name or the wildcard of the file(s) to check.
BAll parameters overwrite settings made in the configuration file.
üè Æîù┴ xΣ ^'+
■ Installing SKC for uploadchecking ■

¿The main use of SKC is the upload test, of course. It has an infomative userinterface, that looks nearly the same as seen localy. (If the user understands ANSi or AVT)
╘Here are coming the possibilities known to me to install SKC as upload tester in several BBS environments. If you use SKC in an environment unknown to me, I would be happy about your report about how you did it. c
BBS Softwares :
RemoteAccess 1.x
RemoteAccess 2.x
Super BBS 1.17
Ezycom 1.02/1.10
Proboard 2.x
Proboard 2.x menu
PCBoard
Concord O.O1G
Turbo-Mail 2.06
Maximus/2

Filedoors :
EFT 2
FileDoor (XFD) 3.1

Other :
Terminate

─█≥ 7Ne|ô╝╙°'+
■ Environment variables used by SKC ■

lThe Environment variable SKOVR controls how SKC (and other SkullSOft Tools) handles its overlay file. Normaly SKC tries to load it's overlay into the EMS or XMS. If you want to disable one or both of these routines or want to load SKC it#s overlay buffer into the UMB (your shells will have more memory then!), you can control this with this environment variable.
An example:
SET SKOVR=UMB,NOXMS

,SKC will try to load it's overlay buffer into the UMB (and saving about 30kB of memory for shells) and won't try to load the Overlay to the XMS. HINT: Trying to load the overlay buffer into the UMB is a nice thing, but it won't work on all systems. E.g. systems using QEMM will crash, if you try it!
'
■ RemoteAccess 1.+ ■

bInstead of your normal upload-statement in your file-menu put a GOSUB (Parameter SKCUPL) into it.
^Then create a new menu called SKCUPL. This menu contains 3 statements executet automatically: ì
- Upload file
- Menu type 7 (Exec)
Parameter: SKULLCHK.EXE *0 /N:*N /P:*P [/C:<Config>] /DUP *M
- Menu type 3 (Return from Gosub)

öIf your user wants to upload something, RA will GOSUB to the new menu SKCUPL and will execute the upload there. After that SKC will be with the actual file-directory (*0) given to it and - if you want to - a special configuration-file. *M will do a memory-swap. SKC will scan all new (yet unchecked files) in the actual file-directory now. After this, the menu will lead the user back to your file-menu.
'
■ RemoteAccess 2.+ ■

!Start RACONFIG and open the menu
OPTIONS > FILES > UPLOAD SCAN
&Enter there the following parameters:
Scan Online : Yes (or Ask)
Failed Scan : Unlisted
Scan Utility : SKULLCHK.EXE @ </C:Config> /N:*N /P:*P /DUP *M

┐If you enter "Yes" at the first input, upload will be scanned online always. If you enter "Ask", the user will be ask, if the file and the ratios should be processed now or after his logoff.
²NEVER enter "Deleted" at the Failed Scan promt !! RA will mark bad uploads as deleted, but will give the user the FULL account for the upload. No virus-message will be displayed, as it is normally. If this is a bug or a feature, only Andrew knows it...

'
■ Super BBS bis 1.17 ■

╩SKC doesn't support the new version of SBBS 1.18. The configurations named here are for SBBS up to the version 1.17. but you should be able to use SKC as upload processor in the same way as for V.1.17.
LStart CONFIG.EXE and open the menue PATH and enter at the Virus-Scan-promt:
5<Path>SKULLCHK.EXE /A %1 [/C:<Config>] /N:*N /DUP *S
After this open the menu
FILES > Global Options
Edit the following: F
Virus Check : Yes
No unpack before scanning : Yes

kNow change the upload-statement in your files-menue to a GOSUB to an upload-menu. Create this upload-menu: ç
- UPLOAD file
- Menu type 7 (Exec)
Parameter: <Path>SKULLCHK.EXE /B /N:*N [/C:<Config>] *S
- Menu type 3 (Return from Gosub)

¥If an upload was finished, SBBS will start the internal virus-scanner. This is SKC running in /A mode. The archive will be checkt for integrity and virus.
kAfter this, SKC will be started in /B mode. This will do the converting and the changing of the FILES.BBS.
rThe splitted filemode is needed with SBBS. SBBS still doesn't handle upload converting while virus-scanning.. :-(
'
■ Ezycom 1.02/1.10 ■

pPlease edit or create the file UPCONV.BAT in the Ezycom main-directory. This file should only contain one line: B
<Pfad>SKULLCHK.EXE %1%4.%6 /.%5 /N:%TASK% [/C:<Config>] /DUP

:(I have added an example batch into the TOOLS\ directory)
After an upload, now SKC will be called. SKC will convert then the archive to that type of archiv, that is given in CONFIG.EXE for the actual filearea. If you want your files to be globaly converted into the format specified in SKCSETUP.EXE, you have to delete the /.%5 from the line
l/N:%TASK% will give SKC the current Node. If you don't have a multiline-box, you can delete this statement.
== Remarks ==

αIn any case you should enter a bad- and a virus directory in SKCSETUP.EXE ! If Ezycom finds a file after the check, it will accept it! Ezycom won't handle any errorlevels of SKC, because they are destroyed by the batch-job.
╒You should disable the GIF-converting for the uploade-check. Ezycom won't accept GIF uploads, that are converted to JPG after upload-scan, it will mark them as bad! You can enable it for the base-mode, of course.
XWatch out with the description-options! If you enabled one of them (DIZ,SDI,GIF..) and SKC found any meaningfull description, it will be _impossible_ for the user to mark the upload as private! The cause of that is in the poor(buggy?) internal description-processing of Ezycom. Can't do anything about this with the versions of Ezycom, I know.

'
■ PcBoard ■

>There is no basemode implemented for PCB but an upload check.
üPlease switch your filebasetype to PCB 15.1 and create the following PCBTEST.BAT (an example is included in the TOOLS\ subdir) : ╧
@echo off
if "%2" == "UPLOAD" goto check
goto ende
:check
del PCBFAIL.TXT >NUL
<SKC directory>\SKULLCHK.EXE %1 /PCBUD=%3 /DUP
IF ERRORLEVEL 1 goto fail
goto ende
:fail
REM > PCBFAIL.TXT
:ende

be'

■ Concord O.O1 Gamma ■

JThere is no basemode implemented for Concord, yet, but an upload testing.
╜Please switch your filebasetype to Concord O.O1 and enter for the longdescriptions' char a ">". You should delete the entry for PFILES.BBS in order to avoid dupe entries in your FILES.BBS.
%Open CSETUP and enter the following:
!General > Path > Virus Scanner : " <Path>\SKULLCHK.EXE %1 /. /DUP

-General > File System > Ext Upload Checker : Yes

σ*ATTENTION* Concord is able to generate exit files for the upload scanner and is able to read new descriptions from it. But it is not possible to tell Concord, that the extension of the checked archive had changed. This would easy be possible with the exitfiles, but Concord will ignore any extension changings :-( For that reason I have added the /. parameter in the settings above to avoid conflicts ! This seems to be a heritage of the SBBS times. The SBBS had the same problems.
c|j½'
■ ProBoard 2.1x ■

sProboard 2.1x supports an upload tester directly. Sorry to say: This support is implemented that poor, that I can't advice you to configure SKC as upload tester inside of PBCFG. You'll get more troubles then benefits from doing so. I hope this will be fixed in one of the later releases of Proboard. I would advice you to use the menu-solution to use SKC under ProBoard.
>But here is the description how to add SKC into PBCFG anyhow:
Run PbCfg.Exe. Open the menu:
Options, File Transfer

Enter the following values there:
Upload scanner : <Path>\SKULLCHK.EXE @<FILE>@ /P:*P /N:*# /DUP
Type : Errorlevel
Action : None

Special settings in SKCSETUP:
Basemode = Proboard 2.x

b
c░
'(
■ Menu upload with ProBoard 2.1x ■

┐I can't advice you to configure SKC in PBCFG. The reason is: ProBoard will call the upload processor before adding the uploaded filename and it's description to the filebase. The upload processor will add the filename and the description to the filebase. After this, ProBoard will do the same ignoring the work, the upload tester had done before. This means the files are listed twice: Once with the correct DIZ descriptions done by the upload processor and once with the user entered description, done by PB. This is realy not usefull, PB should enter the filename and the user description vbefore calling the upload processor in order to get all benefits of a powerfull upload processor like SKC. :-(
±For that reason I advice you to use a menu construction, that will do the upload testing and ratio updating correctly and openeing you the world to SKC features. For that you'll need 3 files that can be found in the TOOLS\ directory of SKC.
¬UPLOAD.PBM : Instead of calling the upload menu type 33 of ProBoard you should call this menue via a menu GOSUB. Please copy this file to the menu directory of ProBoard.
üPB2TEST.BAT : Please copy this file to the directory where ProBoard is called from. This testbatch will be called from the menu UPLOAD.PBM after the upload is done. In this you only have to change the directory setting of SKC (Environment variable SKCDIR in the batch). If you have changd the logfile parameter in UPLOAD.PBM you have to use the same name inside of the batch (PB2LOG).
]PB2RATIO.EXE : If you test your uploads via this menu solution, the ratio of the uploader wouldn't be updated, if SKC failed the file for virus or anything. The ratio update will be done by PB2RATIO. The PB2TEST will call PB2RATIO directly after calling SKC. If you are not interested in Ratio updatings, you may comment the calling of PBRATIO out.
'

■ Maximus/2 ■

[SKC doesn't support Maximus/2 directly. But it may be used as uploadtester, as I was told.
îThis CHECK.CMD was written by a Maximus/2 sysop (Andreas Oeser, 2:240/5020.12). I don't know, if it realy works, because I never testet it.
<Zitat Anfang>
Prog: CHECK.CMD ┼
/*************************************************************/
/* Erstellt die Datei SKULLCH.BAT nach einem Upload */
/* */
/* Maximus ruft durch das Keyword Upload Check Virus in der */
/* MAX.CTL dieses Programm auf und uebergibt als Parameter */
/* das Direcory incl. Drive und abschliessenden Backslash, */
/* den Filenamen ohne Extensions sowie schliesslich die */
/* Extension inkl. anfuehrenden Punkt. */
/*************************************************************/

arg directory filename endung Misc /*Uebernimmt die von Max uebergebenen
Parameter*/
file1=directory filename endung /* speichert alle Parameter in einer
Variablen */
file=SPACE(file1,0," ") /* Entfernt die Leerzeichen aus den
Parametern */

/* Erstellt die Batchdatei SKULLCHK.BAT und schreibt die */
/* angegebenen Zeilen hinein */

batfile="SKULLCH.BAT"
rc=lineout(skullch.bat,"@ECHO OFF")
rc=lineout(skullch.bat,"E:")
rc=lineout(skullch.bat,"CD\DFUE\SKULLCHK")
rc=lineout(skullch.bat,"E:\MAXIMUS\FOSSDUMM\DUMMDOS %1 SKULLCHK "file "/N:%1
/P:0")

EOP:CHECK.CMD

·Den Portparameter, habe ich jetzt direkt mit P:0 angegeben, da es mit den COM Ports sonst Probleme geben kann. Weil unter OS/2 ja keine COM Ports sondern nur Handles vergeben werden. Dieses BS erstaunt mich auch nach ueber 2 Jahren immer wieder :-).

<Zitat Ende>
'
■ FileDoor (XFD) 3.1+ ■

%Edit your configuration-file of XFD:
(- Enter the option "ExitAfterUpload1" : =
<Path>SKULLCHK.EXE $U\$F [/C:<Config-file>] /DUP $M $N

8The config-file is optional, only secify it, if needed. è
$M will force a swapping of XFD before SKC is started. With the parameter
$N XFD will call SKC only, if the upload was successfull.

C- You have to switch on the XFD-option in SKCSETUP, of course.. ;)
y- You should disable the option "Update FILES.SKC", because SKC will work in a temporary directory when called under XFD
'
■ Eft 2.+ ■

lStart the config tool of Eft and enter at every ArcExtension you wish to be processed by SKC the following:
-<Path>SkullChk.Exe $1 [/C:<Configfile>] /DUP
5The config-file is optional, use it only, if needed.
$Enter GOOD at the Good-file-prompt.
.Enable on all protokolls the ArcCheck-option.
}!! IMPORTANT: Enter at all ArcCheck-Window-Coordinates 0 ! If you try to run SKC in an Eft-window, your system will hang up!
oEnable on all protokolls the "Write EXITINFO.EFT"-switch, if you want SKC to hand descriptions of the uploads.
<You have to enable the Eft-switch in SKCSETUP, of course...
'
■ Turbo-Mail 2.06 ■

▒SKC supports Turbo-Mail completely. TMAIL is checking it's uploads offline allways. This is normaly done with the tool VIRSCAN.EXE. This will be replaced by SKC in the batches.
cPlease search in your START.BAT for the line that starts VIRSCAN. it should nearly look like that: &
if exist vscan%1.spl virscan.exe

9Please replace this line with to new lines in the batch: b
if exist vscan%1.spl c:\tmail\skc\skullchk.exe @vscan%1.spl /N:%1 /P:0 /DUP
del vscan%1.spl

3Of course you have to change the directory to SKC.
(Special settings in SKCSETUP for TMAIL: J
Filebase : Turbo-Mail
FILES.BBS : INHALT
DupeDir : <TMAIL\>DUPE

╡A basemode is not implemented for TMAIL, but it very easy completely emulated: Please create a textfile holding all the directories of your binary boards. Call it e.g. BRETTER.SKC.
2The "Basemode" for TMAIL would be done like this:
)SKULLCHK.EXE @BRETTER.SKC <more options>
╞ATTENTION: SKC will change the VirusCheck flag in the INHALT files but will ignore them itself. If you want to do basescans you have to let SKC create it's FILES.SKC's for marking files as checked.
ùJ '
■ Terminate ■

òThis, of course, is now configuration for online-checking. I added this chapter, because many "normal" user asked me, how to use SKC with Terminate.
^So: If you don't have any BBS running, please switch the filebasetype in SKCSETUP to <none>.
)After that configure SKC to your wishes.
zNow you can enter SKC in the menu Options (ALT+O) under "Files and Directories" in the entry "Do after upload" like that: 8
<Path>SKULLCHK.EXE <DownLoadDirectory\*.*> /P:0 $M

ìIf you have more than one download-directory, that all are subdirectories of a main download-directory, you can enter something like this: ;
<Path>SKULLCHK.EXE <DownloadRootDir\*.*> /P:0 /SUB $M

ºIt produces a smaller phone-bill, if you run SKC in a batch after Terminate, because the "Do after download" will be executed after every download, this means online!
NIf you download a description file from a RemoteAccess 2.+ BBS (named FILE_ID.?) you can run the little tool DESC2BBS.EXE included in the distribution archive, wich will convert the description file to a FILES.BBS. If you copy this FILES.BBS to your download directory, you can use the FILE_ID.DIZ creation-feature odf SKC, too.

bΣ''ñ
■ External files used by SKC ■

┌───────────────────────────────────────────────────────┐
│ Tools and files found in the maindirectory of SKC │
└───────────────────────────────────────────────────────┘
SKULLCHK.ARE
SKULLCHK.CLR
SKULLCHK.LNG
SKULLCHK.PKI
SKULLCHK.SCN
TEST-DMS.EXE
DMS-DIZ.EXE

┌───────────────────────────────────────────────────────┐
│ Files found in the directoy <SKC main>\CTL\ : │
└───────────────────────────────────────────────────────┘
BANNER.SKC
DIZTAGS.SKC
DUMMYS.SKC
IGNORE.SKC
FILE_ID.SKC
PTHROUGH.SKC
UNWNAME.SKC
UNWRAND.SKC

┌───────────────────────────────────────────────────────┐
│ Files fond in the directory <SKC main>\ANS\ : │
└───────────────────────────────────────────────────────┘
BACKGRND.ANS/AVT Will be used as background by SKC
BADARC.ANS/AVT Will be displayed if a bad archive was found
DUPEARC.ANS/AVT Will be displayed if a dupe file was found
VIRARC.ANS/AVT Will be displayed on virus alerts
OLDARC.ANS/AVT ..if the file is too old
PROMPT.ANS/AVT Used as enter-prompt.
HACKARC.ANS/AVT ..if a file was listed in the hacklist.

pIn all of these ANSi/AVT files are macros possible. But they don't make sense in all files. (Exeption PROMPT.*)
Else, who needs it: ⁿ
BACKGRND.BIN Background used by SKCSETUP (e.g. saved with TheDraw)

┌─────────────────────────────────────────────────────┐
│ VOC files in the directory <SKC main>\VOC\ : │
└─────────────────────────────────────────────────────┘

║SKC is able to play VOC files in specific events. These VOC files have to be located in the VOC\ subdirectory of SKC. More details are found in the description of VOC files used by SKC.
╪τ÷ !"#"2#⌠$'(!)0%?*N&]+╚Å╗'
■ SKULLCHK.ARE ■

YThis file holds informations aboot what area should be checked in basemode and wich not.
g''
■ SKULLCHK.CLR ■

.This file holds the color definitions of SKC.
╥+'
■ SKULLCHK.LNG ■

ëThis is the language file of SKC. Two language files are available: english and German. If you want to create a new one, please tell me.
'
■ SKULLCHK.PKI ■

╢This file holds your compressor setups. If you want to tell some other sysops your compressor setup, you may give them this file. it is system independent (it holds no directories).
¼,'
■ SKULLCHK.SCN ■

2This file holds your virus tester configurations.
₧,'
■ DMS Archivetesting ■

SKC is able to call 2 external tools for DMS archive testing and extracting of DIZ files insinde of DMS files. These files are found in the distribution archive in the subdirectory TOOLS\ and have to be moved to the SKC maindirectory, if SKC should use them:
TEST-DMS.EXE
DMS-DIZ.EXE

bTEST-DMS is used to check DMS files, DMS-DIZ is called to extract DIZ files from the DMS archive.
åDMS archives are (afaik) only used on amiga systems. But some PC-sysops wished a support for DMS files in SKC, so I implemented this.
Because I don't have any informations about DMS files myself, I had to use third party tools to do the DMS check. These tools were handed to me by a sysop. I don't know the original author of the tools, sorry, but I want to say thank you to the unknown coder.
gHINT: One sysop told me about DMS-DIZ to be unstable on some DMS files. So be carefull, if you use it.
' *
■ CTL\BANNER.SKC : Bannertemplate ■

╦This is an ASCII file that will be used as template for the file stamped on archives. This file holds normaly some interesting informations about your BBS or about what virus scanner was used and so on.
]At the moment the only compressors known to me supporting banners are ZIP, ARJ, SQZ and RAR.
AOn extracting of stamped archives the user will see your banner.
RYou may use macros inside this template that will be replaced on runtime of SKC : b
@FILE_ID.DIZ Will be replaced by the description extracted from the
archive or the filebase.
@FNAME Will be replaced by the filename of the archive.
@NODE Will be replaced by ths actual node (or "local" if the node
is 0)
@NOWDATE Will be replaced by the actual date.
@NOWTIME Will be replaced by the actual time.
@REGISTERED Will be replaced by the regcode of SKC.
@SCAN Will be replaced by the names of the virus testers used on
that archive
@SKCVERSION Will be replaced by the actual version ID of SKC

',
■ CTL\DIZTAGS.SKC : List of DIZ tags ■

,This is the opposite to dummy descriptions.
ΘEverytime SKC is importing descriptions to the filebase it will first look inside the DIZTAGS.SKC, if a part of a description line is listed here. If this is the case, the line of the description won't be imported into the filebase.
'E' 5
■ CTL\PTHROUGH.SKC : List of DIZ passthroughs ■

/This is the harder variant of the DIZTAGS.SKC.
If a part of a line of the DIZ file is listed inside of the PTHROUGH.SKC the complete line will be deleted from the DIZ. Because these lines won't be imported to the filebase neither, you don't have to put the same lines to the PTHROUGH.SKC and to the DIZTAGS.SKC.
lSo: Be CARFULLY with everything you write into this file, you may loose important informations of the DiZ !
<This feature is only available for registered users of SKC.
$X'M
■ CTL\UNWRAND.SKC : File for detecting random adds inside of archives ■

!This file controls the random file deleting feature of SKC. Random files are files that changes in size, name and contents. They can't be detected by he CRC or name unwanted method. I have added an example to the distribution archive that describes clearly how to build this control file.
╝This is a feature only available in the profi version of SKC. All non-profi versions allow 3 template definitions in order to test the feature and to be able to delete his own random add.
' 9
■ CTL\DUMMYS.SKC : Liste mit Dummy Beschreibungen ■

CThis textfile is holding dummy descriptions used in your filebase.
6Dummy descriptions are descriptions like "No description available". They are added by some tools to your filebase. When SKC is creating DIZ files for the archives, it should never use these descriptions for it. This means, you have to tell SKC wich lines in descriptions it should never use for DIZ creation.
!Please add all dummy descriptions to this textfile. If a line in the filebase descriptions contains one of the dummy entries, it will be ignored while DIZ creation. "Contains" means: If you added "Uploaded by" to the list, a line like "Uploaded by Grischa Brockhaus" will be ignored, too.
êPlease be carefull with this feature. An entry like "missing" would result SKC to ignore a line like "Shows all missing files in base".
'
■ CTL\IGNORE.SKC ■

èThis is a textfile holding filenames on each line, that should be ignored while searching for to be checked files. Wildcards are allowed.
KThis file should contain e.g. FILES.SKC, FILES.BBS, NODELIST.A* and so on.
'
■ CTL\FILE_ID.SKC ■

éYou can define the look of new FILE_ID.DIZ files created by SKC. You may define frames around them or little BBS logos and so on.
╛This is done with a text control file called FILE_ID.SKC that has to be placed in the CTL\ subdir of SKC. i have added an example file to the distribution archive, please have a look at it.
GIn this control file the following macros will be replaced at runtime: i
@FDESC:<width> Description trimmed/cutted to width.
@FDESCW:<width> Description wrapped to width.

└Lines holding one of these macros will be repeated for each description line. Perhaps you don't understand this now ? Please have a look into the example and play around a little bit with it.
CThis feature is only available with the registered version of SKC.
'G
■ CTL\UNWNAME.SKC : List holding unwanted filenames in archives ■

+This is a textfile holding filenames of unwanted filenames in archives each line. If in an archive a filename is found, that is found in that listfile, it will be deleted from the archive. You may use it to delete bbs adds known to you from uploads. but be carefull: An entry *.EXE would be fatal !
ßThe other kind of unwanted files detecting is the method comparing the contents of files, the so called CRC method. If you have adds changing their name but not their contents, please adopt it to the CRC database of SKC with '
SKC <DBdir> CRCADOPT=<TheAdd.Exe>

cIf you have adds changing their name and contents, please use the method for deleting random adds.
&╩'≥
■ Macros that may be used in ANSi files of SKC ■

@FILE Will be replaced by the actually processed filename.
@HAK The flag found in the Hacklist for the actual file.
@OLDDATE1 Oldest date allowed (DD-MM-YY)
@OLDDATE2 oldest date allowed (MM-DD-YY)
@OLDDAYS Maximum allowed fileage in days.
@SCAN The virus scanners used on that file.
@DUP Maximum of allowed dupes in archives in percent.
@USER Name of the user, if a dropfile was found.

}These macros will be overwritten exactly. If the checked file was TEST.RAR the macro @FILE would be overwritten with "TEST."
╦For that reason you may extend the macros with @'s. @FILE@@@@@@@ would be overwritten with "TEST.RAR " e.g. This can be done with all of the macros. Have a look at the examples in the ANS\ directory.

üç'''"
■ SkullSoft Support-Sites ■

ñPlease remember that all support sites of SkullSoft do this for hobby. It might take a while sometimes for answering your questions, please be patience. Thank you!
∩If you have any problem relating this program please tell them the according support site. Try to specify your problem and your environment resulting it as clearly as possibly in order to reproduce the error and to make support effective.
7All support sites will manage your registrations, too: <
Support in Germany
Support outside Germany

-≈0'
AThe following countries of germany have SkullSoft support sites: 8
Berlin
Hamburg

.K/d'4
■ Support-Sites in Berlin ■

* SOLO Box Berlin
Sysop : Uwe Doelling
Online : 24h
Line 1 : +49-30-99400200 (BBS/FAX) FidoNet : 2:2410/1001
Line 2 : +49-30-99400201 (ISDN) FidoNet : 2:2410/1002
Line 4 : +49-30-99400205 (ISDN)
NeroNet : 25:560/10 Liberty: 98:130/10 GerNet: 21:489/800

* AQOT
Sysop : Sven Leutloff
Online : 24h
Line 1 : +49-30-46507611 (BBS/FAX) FidoNet : 2:2410/1003
Line 2 : +49-30-46507612 (ISDN) FidoNet : 2:2410/1004
GerNet : 21:489/802

'╩
■ Support-Site Hamburg ■

* JOEY's BBS
Sysop : Jens Erbe
Line 1 : +49-(0)40-210-2382 FidoNet : 2:240/5100
Line 2 : +49-(0)40-210-2138 FidoNet : 2:240/5101
Line 3 : +49-(0)40-210-2339 FidoNet : 2:240/5102
Line 4 : +49-(0)40-217845 FidoNet : 2:240/5103
Line 5 : +49-(0)40-213056 FidoNet : 2:240/5104
Line ISDN: +49-(0)40-21090290 FidoNet : 2:240/5105

'~
■ Support-Sites outside Germany ■

USA
Itala
Sweden
Netherlands
Austria

If you want to do the support in a country outside of Germany not listed here, you would be *very* welcomed ! Please tell me :
!Grischa Brockhaus, 2:2410/1001.1
1-3>2O4`5q'
■ Support-Site USA ■

9We are desperately searching for support in the states !

'ë
■ Support-Site Sweden ■

* Spider Nest
+46-26-132521 (BBS)
Sysop : Ulf Rygaard
Online : 24h
FidoNet : 2:205/264

'▄
■ Support-Site Italy ■

* The Bits BBS
+39-81-665060 (BBS)
+39-81-76162695 (BBS/FAX)
Sysop : Aris Ferrara
FidoNet : 2:335/225.0 & 230.0
VirNet : 9:395/106.0
RAFNet : 95:3300/205.0

'M
■ Support-Site for the Netherlands ■

* Connection VLD
Sysop : Nico van Vliet
Line 1 : +31-10-4707040, 2:286/420 2400-28800 BPS VFC
Line 2 : +31-10-2479390, 2:286/421 14400-33600 BPS V..all
Line 3 : +31-10-2479560, 2:286/422 14400-64000 BPS ZYX,ISDN,V34
Internet : sysop@connvld.xs4all.nl

'╕
■ Support-Site for Austria ■

* Lipo's BBS
Sysop : Roland E. Lipovits
Line 1 : +43-3356-75525, 2:31/11 2400-28800 BPS VFC
Internet : rel@lipo.co.at

''
■ !!! Error !!! ■

₧This version of SKC will run only with a valid keyfile. If you are a registered user, please test if you keyfile SKC.KEY is found in the maindirectory of SKC
'
■ !!! Error !!! ■

CThe compressor configuration file (SKULLCHK.PKI) can't be opened !
gThis file is found in the distribution archive of SKC and has to be found in the maindirectory of SKC.
'
■ !!! Error !!! ■

SKCSETUP was unable to read the configuration file choosed by you. The reason might be, that the file is damaged or not there.
'
■ !!! Error !!! ■

A problem occured while trying to read the area definition file of you BBS. The reason might be, that the file wasn't found (Did you set the BBS environment variable correctly ?) or that SKC doesn't support a /BASE check on the base selected by you actualy. (e.g. Concord and PCB).
'
■ !!! Error !!! ■

'The choosed file is of 0 bytes length.
ÖThe method to check for CRC depents on the contents of the file, so it is realy absurd, to mark a 0 byte file for it. Please put it to the UNWNAME file.
'
■ Information ■

XDie von Ihnen ausgewählte Datei ist bereits in der CRC unerwünschten Liste eingetragen.
'
■ !!! Error !!! ■

aPlease specify description filenames without wildcards ! You have to enter the names one by one.
''
■ Menu Space ■

XThis menu is opened with Alt+<Space>. It holds some global options for SKCSETUP itself.
'
■ About ■

tThis dialogue holds information about SKCSETUP. It tells you about the version and registration status of SKCSETUP.

'
■ Exit the program ■

\This option will end SKCSETUP. The actual configuration will be saved before automatically.
''
■ Menu Files ■

@This menu holds topics about saving and loading configurations.
'
■ Save confirguration ■

;Here you have the chance to save the actual configuration.
VThis is not neccessary to do, because all configurations will be saved automatically.
¼But you can enter a new name for the configuration file with this option, if you want. SKCSETUP will ask you for the name to save the configuration under before saving it.
'
■ Load configuration ■

QWith this option you are able to load a prior saved configuration into SKCSETUP.
''
■ Save configuration as default ■

BThis option will save the actual configuration as "SKULLCHK.CFG".
⌐If you don't explicit specify a configuration with the /C: parameter, SKC will load this configuration at startup. This means. SKUlLCK.CFG is the default configuration.
'
■ Load configuration ■

QWith this option you are able to load a prior saved configuration into SKCSETUP.
;Please choose the configuration file you want to load now.
''
■ Checking options ■

WThis is a dialogue for you to setup how files are to be checked and how to treat them.
'
■ Archive treatment ■

CThese are some global switches to setup the treatment of archives.
Virus scan:
₧Ought files and archives to be scanned for viruses? If you switch this on, you must have installed at least one of the virus scanners in the respective menu.
Banner stamping:
æIf you would like a text logo being stamped onto an archive, there must of course exist one, and the respective packer must support this option.
Insert advertisement:
{You want to add an advertisement file to an archive? Of course also here the advert file must be stated in the file setup. ,
Random adds (only for registered users):
çDefine, if SKC should add random adds to the archives. You have to define and setup your Template correctly for make this option work.
Process SFX archives:
Here you may turn on or off, whether SKC is going to unpack selfextracting archives and check them, or is going to treat them like a standard executable file. Treatment of their SFX archives can also be setup for individual packers. (see also packer setup SFX)
Don't touch AV archives:
Some AV archives may be changed partly without distroying their AV code (only known for ZIP's logo at the moment). If you want SKC leave AV archives completely untouched, you have to switch on this option. You have to define the repack switch for the compressor similair, of course.

₧#r T╩╜╝
'
■ Delete unwanted ■

½SKC can delete files in an archive, considering certain criteria. Here you may setup globally, if it is supposed to and which criteria are to be observed while in action.
Delete unwanted names:
You whish to kill unwanted files in an archive considering their NAMES? Therefore, you have to setup a list of unwanted files.
Delete unwanted CRCs:
≥Unwanted files always changing their names, or being named like a file that could be important in an Archive, should be detected by their CRCs. Toggle here, whether you would like unwanted files being deleted, observing their respective CRC.
Add new CRCs to name list:
AIf SKC has detected a file by it's CRC and it's name is not yet in the list of unwanted files, should the name of the file then be entered into? Be CAUTIOUS using this option! Imagine an unwanted, CRC-detected file, has been renamed into INSTALL.EXE. Then any INSTALL.EXE will be deleted from subsequently checked files. .
Delete random adds (Only for Profi-Users):
ÄSome adds don't have the same name and the the same contents. SKC is able to detect them, if they are partly the same, what is mostly the case, because a BBS logo will be found or something. All non-profi versions allow 3 template definitions in order to test the feature and to be able to delete his own random add. For more details on that feature have a closer look at the file CTL\UNWRAND.SKC.
*F&s'
■ Verifying archives ■

QTurn this on if you wish archives to be checked, only if they are real archives.
|To achieve this, the packer ID stated in the configuration will be checked whether it matches the one of the archive or not. This also happens with files in an archive, if you have chosen to check also archives in an archive (Check depth<> 1). If the packer IDs do not match, the file/archive will just be accepted as it is, without being checked, so think about turning this on!
CTo take the greatest advance as possible, the packer IDs must be set up in the most exact way (as few #00 as possible). But this could result in no more being able to recognize SFX archives of the respective packer. So just try out, how many letters of the packer ID you can enter unproblematically into the configuration.
╙This option takes also effect on MOD/GIF a.s.0 testings. If this option is not set to "always" SKC won't check, if the releated file is realy a file of that type. The file won't be denied on internal conflicts.
ZNow you have got 3 possibilities of selection. Either you just switch it ON ("always"), then SKC behaves like this whenever checking an archive with a defined file extension. Or you switch it to "imbedded". Then only archives found in an archive will be treated the way discussed above, but the main archives are checked for CRC errors as usual.
For me, this option appears to be the most suitable one. E.g. I got some games, containing .ARC files in their archives. But these were no ARC-archives, simply data files being named that way. SKC ignores these "sub-archives" in the case he is instructed to use the "imbedded" method.
DAs a third option, you can totally turn OFF this way of processing.
JR')
■ Stamping a date onto an archive ■

πArchives tend to be dated in a way, that does not tell too much about their creation dates. As soon as an archive is being changed, it's date is changed, too. Employ SKC to give your uploads correct and expressive dates again.
#You may use the following options:
Touch arc:

Never:
5The archive will never be "touched" to another date.

Today:
NThe archive date will be set to today's date (mostly the date of the upload).
Oldest:
TThe archive will be touched to the date of the oldest file included in the archive.
Newest:
TThe archive will be touched to the date of the newest file included in the archive.
(There are two more additional switches:
Date from EXE/COM:
HOnly EXE and COM files will be taken into consideraton for the date calculation. Touch Arc set to "newest" means, that the new archive date is copied from the newest EXE or COM file instead of the newest archived file in general. If no EXE or COM is found, the other files will be used as calculation base for the archive date.
Date from DIZ only:
uThe date of the FILE_ID.DIZ will be used to set the new archive date. If none is found, proceeding goes on as usual.
3So if all switches are turned ON, a DIZ is being looked for. If there is none in the archive, it will be searched for EXE/COM files, if these do not exist either, the very rest is being processed. Of this selection the current "Touch arc" setting will be used to complete the search for a new archive date.
'
■ Checking depth ■

.Here one can setup, up to which depth of imbedded archives/subdirectories an archive is to be checked. If it is set to 2 for example, SKC is going to check archives and directories in an archive, but not archives in an archive embedded into another one. I do NOT to indend to give any more examples ;)
HIf a 0 is specified here, SKC will check as deeply as it is neccessary.
TExample: An Archive UPLOAD.ZIP contains an archive UNDER.ZIP and a directory UNDER. ╚
depth 1 depth 2 depth 3 ... depth 0
UPLOAD.ZIP
└──────┬─ UNDER.ZIP
│ └──────── ..\UNDER2
└─ ..\UNDER
└──────── UNDER2.ZIP

▄Using checking depth 1, SKC would only test the contents of UPLOAD.ZIP for viruses, checking depth 2 would effect an extraction of UNDER.ZIP, so it's contents as well as the ones of the directory UNDER could be scanned.
áProviding the case, in the archive UNDER.ZIP would be one further archive, it would only be extracted and checked when using checking depth 3 (or 0 of course).
''
■ Conversion options ■

fIn this dialogue you may setup, how SKC will behave while converting archives. Available options are: ╕
Conversion packer
Convert SFX archives
Delete original files
Read conversion packer entry from filebase

Lå+M│+Nα+O
+'
■ Conversion packer ■

1Setup here, what conversion packer should be used by default. You should, of course, define a conversion packer, that is available on your system and correctly set up. Beside of this, the conversion packer should be able to compress subdirs, else you will loose important informations from your archives!
:If you define "---", archives normaly won't be converted.
PThis setting will perhaps be overwritten by the settings of your filebase area.
BThis setting will always be overwritten by the /.<Ext> parameter.
åNormaly all archives will now be converted to that archive type. Only archives of a copression type with never convert set on, won't.
O╒»è
'!
■ Converting SFX archives ■

iIf switched on, SFX archives will be converted to normal archives and after this converted, if possible.
'!
■ Delete original archive ■

»This option should always set to ON, and only be switched in some testing circumstances. If you switch this off, the original archives won't be deleted after converting them.
'0
■ Read conversion packer from area setup ■

╣Some BBS software (RA2 and Ezycom) are able to hold informations about converting for each area of their filebase. If you don't want SKC to ignore this settings, switch this option on.
αFor that option, SKC will compare the extensions of the compressors defined in the area setups against it's own extensions in the compressor setup. But SKC will use it's own compressor definitions for the compressor shells.
''
■ Files & directories ■

IHere, files and directories needed by SKC to check files are determined.
'
■ Files & directories ■

IHere, files and directories needed by SKC to check files are determined.
Possible entries in this menu: ╝
Insert Big Insert
MinArc Big Arc
Random add

Logfile
HackList

Compressor dir
Virus dir Heurist
Bad dir Old dir
DupeDir

Tmp Drive

RïS¥
R⌐S╗T─
U╥V█WτX≈ Y Z[$\-]8 '
■ Advertisement file ■

òThis is a file which is usually put into every possible archiv, as far as circumstances allow. (Option must be turned on and the archive's size must
ßYou can define from which archive size on this file should be added. Packing large advertisements into small archives is only annoying. "MinArc" specifies the minimum size (KB) of an archive to add the advertisement file to.
Dialogue: Files & Dirs
Qí'
■ Big advertisement file ■

¥If you have a really large advertisement file, e.g. a BBS demo, you can specify a minimum file size to insert it instead of the normal sized advertisement..
╖The point "BIG INSERT" defines the appropriate file (or leave empty) while "Big Arc" defines from which archive size on this advert. file should be inserted instead of the usual one.
Dialogue: Files & Dirs
RíQâ'
■ Random add template ■

éSpecify here the template, SKC should use for generating random add's. A random add is a file, that differs in name and contents.
uYou may use the same macros inside the template, you may use in the Banner Template. SKC will generate with it an advertisement file <Random>.SKC and will add this file to archives if the option Random add was switched on in the check dialogue and if the archive is smaller as the size defined with MinArc. An example for the random add template is added as CTL\RANDOM.ADD
─It yould be a nice idea to make your SKC delete your random add in order to don't add them twice. This means you should add the part in your random add always staying the same to CTL\UNWRAND.SKC.
Dialogue: Files & Dirs
#µFe
&╠QΘ'
■ Log file ■

░Please specify the neme of the log file that SKC is supposed to use. If you use a "$N" in the file name specification, it will be replaced by the currently active node mumber.
äThat means if you enter "SKC$N.LOG", SKC is going to use SKC001.LOG for logging on line 1, on line 2 it is going to use SKC002.LOG.
Dialogue: Files & Dirs
QU'
■ Hack list ■

Please state the file name of the hack list SKC should use. Leaving blank this menu entry, the feature will remain turned off.
Dialogue: Files & Dirs
`6 Qƒ'
■ Compressor directory ■

αSpecify here, in which directory all your archiver programs are stored. If you leave blank this menu entry, SKC will go and look for archiver progrms in the system PATH (see DOS documentation for PATH environment variable).
÷If you have put all your packers in one directory and you stated this in the SKC configuration, finding the archiver programs will be enourmosly faster than leaving blank the field, because it won't need to search the whole system PATH for them.
Dialogue: Files & Dirs
Q',
■ Directory for virus infected files ■

This is the Directory where infected files are moved to. Leaving this line empty is the order to always delete infected files.
Dialog: Files & Dirs
Q╢'D
■ Directory for files that didn't passed the heuristic check ■

┼This is the directory, where SKC will move files to, that didn't passed the heuristic check of one of your virus scanners. If this entry is empty, the files will be deleted instead of moving them.
sBut files will only be moved or deleted, if the Heuristic fail switch of the concerning virus scanner was enabled.
¬æ º<'!
■ Directory for bad files ■

àEnter the name of an existing directory to move bad archives to. If bad files ought to be deleted immediately, leave the line empty.
Dialog: Files & Dirs
Q▒'*
■ Directory for advanced age files ■

¢Files being too old (see also menu rejecting files) will be moved into the directory stated here. Leaving this line empty all these files will be deleted.
Dialog: Files & Dirs
xNQ╨''
■ Directory for duplicate files ■

░Files recognized as duplicates will be moved into the directory entered in the current menu field. To have these files deleted immeditely after finding them, leave line empty.
Dialog: Files & Dirs
ü<
QΓ'(
■ Hard drive for temporary files ■

1After glimpsing through your hard drives' trees, select one to unpack archived files. Most likely you should select a RAMDRIVE, but please assure that it is large enough. In the case that you have rather large files, please state the letter of a usual hard drive with an appropriate amount of free space.
Dialog: Files & Dirs
Qd'
■ Mailer ■

╕SKC is designed to refresh files belonging to your mailer while working on BBS archives. If you do not use a mailer or you do not know what that is, just leave the entry fields empty.
2When SKC converts files, file attaches and TIC-files made for the old archives are no more correct. These files can be refreshed and corrected by SKC. But he will only be willing to work in that way if you are willing to feed him with an parameter /TIC , additional to the other ones, on the command line.
'
■ Mailers' dialogue ■

ZPlease enter 3 directories SKC needs to refresh and correct mailer files (if neccessary).
Netmail:
UState the netmail directory where netmails with outbound file attaches are located.

Outbound:
aThis is only valid for the 4D Binkley style outbound: Please enter your main outbound directory.
TIC Files:
╡Here we need the name of the directory where your hatcher puts outbound TIC-files. In any case, SKC will correct the CRC, additionally also the file name, if it has been converted.
^X'
■ Hack-list ■

╔SKC supports the official hack-list being part of the hack-report by Lee Jackson (Co-moderator, FidoNet international echo SHAREWARE (1:382/95)). At the moment, it is available at several BBS systems.
╕The hack-report refers about archives being spread via BBS systems being doubtful in some way. These may be hacked versions of files, files containing trojan horses or pirated copies.
9All these files are summarized in one standardized list. &
The old standard: HACK????.COL :

rThis list contains one of these file names without extension per line; lines beginning with ;; are comment lines. &
The new standard: HACK????.IDX :

½Recently, the list is spread in another, more precise standard: Lines beginning with ;; are still comment lines. All further lines are made up using the following method:
Filename,year,flag
σFilename is the file name without extension, year is the release year of the respective hack-report and flag is a shortcut for the kind of hack. At the moment, following flags are used, furter ones can be added without problems. ò
HAK hacked file
HOX hoax alarm (virus simulators e.g.)
TRO trojan horse
PIR pirate copy
QUE somehow questionnable files

qSKC supports both standards; you may even use both standards at the same time mixed together in one hack-report.
╨If you use the .IDX standard, you will HAVE TO specify the hack list flags that one file must posess to be rejected using the file rejection menu. You should enter all known flags, maybe except the QUE flag.
FFiles found in the hack-list will be treated like defective archives.

x╜''

■ Static filenames ■

Here you can change names of files that normaly have a static filename. In this way you can define e.g. a different banner file for each configuration, if you want to. All entries leaved empty will have the static name hardcoded in SKC. So normaly you can ignore this dialogue.
There are 2 columns:
CTL\
(Here you can change names of files found in the CTL\ subdirectory of SKC. They are normaly calles <name of the entry>.SKC. If you want to redefine the names, you have to enter an name and an extension, please do *not* enter a directory, the files still have to be found in the CTL\ subdirectory.
ANS\
╞These are the names of the files found in the ANS\ subdirectory. Because this files are found in different formats (ANS/AVT), please enter the name of the file only without extension and directory.
Example:
pYou entered at ANS\BACKGRND "BGROUND". SKC will now load the file ANS\BGROUND.ANS/AVT for background paintings. 8''2
■ Settings concerning the file base in use ■

8Use this dialogue to setup treatment of your file base.
Options available:
File base
File door
Refresh FILES.BBS
No CDROM areas
Areas for base checking
Name of FILES.BBS
Name of PFILES.BBS
Long descriptions character
Download counter brackets

câdáe╜f┌g≈hi1jNkk'
■ File base ■

╫Please tell SKC here which type of a file base your BBS is using. These options are significant for the /BASE mode of SKC. Also, SKC will present itself as optimized for this BBS type when checking online uploads.
Supported are: ó
Concord O.O1g *
Ezy 1.02
Ezy 1.10
PB 2.12
PCB 15.1 *
RA 1.11
RA 2.00
RA 2.50
SBBS 1.17
TMAIL 2.06 *
WME 1.00ß

DPlease select the file base type your BBS software is setup to use.
U* : For this BBS type only upload checking, but no base checking is yet implemented.
'
■ File door ■

αNow select the file door you are using. If you do not use an external file door at all, you should not turn on one either, EXCEPT that you are sure about your file door being completely compatible to one stated in the list.
-XFD 3.01 and Eft 2.00 expect certain files after a file check, which SKC has to create when the door was executed. Generally, SKC reacts in a way optimized to the respective door, if it is executed with a file name or a file name wildcard as parameter. In the /BASE mode, these options are of no use.
' 3
■ Refresh FILES.BBS, even if not neccessary ■

sSome filebases doesn't have a need for FILES.BBS files. This is the case for binary filebases like RA2 and Ezycom.
So there is normaly no need to use the FILES.BBS besides the normal binary filebase. On the other hand SKC needs much more time to update FILES.BBS tham the binary filebases. In other words: Normaly you should disable this switch, if you are using a binary filebase.
¢But some tools still needs the FILES.BBS even if the filebase is of a binary style. If you are still using on of this tools you may switch this option on.
SAll bases that needs the FILES.BBS, this option should be switchted on, of course.
h[ '
■ No CDROM areas ■
gIf enabled SKC will ignore areas in the /BASE check that are marked as CDROM areas (RA2, PB2, Ezycom).
In most cases it doesn't make sense to test CDROM areas in the base check of SKC. You could also disable this areas via the Area Setup, but this will be very hard, if you have many CDROM areas. This switch overrules any configuration made in the area setup concerning CDROM areas.
g²
'1
■ Selecting file areas for /BASE checking ■

µIf you have correctly setup your file base and the approppriate environment variable has been set, a listing of all your file areas will appear. Using the cursor keys, choose the file areas to include in an SKC base check or not.
ÄPlease keep in mind to exclude e.g. AMIGA file areas, if the stored archives contain data that cannot be handled by an IBM compatible system.
qA little square in front of the area name means, that the respective file area will be checked in a /BASE check.
'*
■ Name of the description textfile ■

ëHere, enter the name of the text file, in which the names and the descriptions of your files are stored. Usually, this is the FILES.BBS.
╡In the file modes using the FILES.BBS, this file will be refreshed with the new archive extensions after archive conversion, and also with the descriptions, if found in an archive.
ÄFor security reasons, FILES.BBS will never be created, only it will be changed. New file names are neither inserted in this description file.
'2
■ Name of the private description textfile ■

@This is the same like FILES.BBS, but is used for private files.
If a name is stated in this file, SKC is going too look on for a file that was not found in FILES.BBS. If a certain file could not be located in any of both description files, it will be entered in this file. PFILES.BBS will also be created if it was not found.
=Entering this statement is especially important for upload checking in FILES.BBS systems, supporting PFILES.BBS. Because, if files are not found in the FILES.BBS, their entry would just be appended to the FILES.BBS, which would cause private uploads to appear publicly. Entrance in this data field will prevent that.
hI '&
■ Long descriptions' character ■

çThe long descriptions' character specifies the character preceding the lines belonging altogether to one description in the FILES.BBS.
DFor RA, specify a + , for SBBS it seems to be a > and for PCB a | .
iOf course, this option is only interesting for file bases not working binarily, but e.g. with FILES.BBS.
'+
■ Brackets around download counters ■

ñThe download counter start/end is specified by one character each, which embrace the download counter statement in FILES.BBS. Usually these are a pair of brackets.
▄SKC does of course not change this statement, it is only important when importing new descriptions to FILES.BBS, for that the old download counters won't get lost when SKC checks the file's description in the FILES.BBS.
gAlso this option is only interesting for file bases which do not work binary, but e.g. with FILES-BBS!

''/
■ Options concerning file descriptions ■

SKC is able to read out and create several kinds of file descriptions. Here, you may configure in what way this should happen.
Available options are: B
DIZ options
DIZ filters
Extra descriptions
dummy description
DIZ tag
DIZ tagging mode
HighBit filter exceptions
RA2 description width
DIZ files
VENDINFO.DIZ

m╦nφop.qQrssæt»u╦vδ'
■ DIZ otions ■

7At this point, there are two options available to you:
ÄGet DIZ from archive: If turned ON, DIZ files (whose names are also configurable) will be extracted from archives and put into the file base.
-Put DIZ into archive: This is the exact opposite. If an archive does not contain one of the previously conigured DIZ files, a description imported from the file base will be added to the archive as a DIZ. How you would like this newly created DIZ to look like you may setup with the file FILE_ID.SKC.
uâ)■'
■ DIZ filters ■

qSKC allows you to apply several filters to import description files as suitably as possible into your file base.
,You may choose among the following filters:
High bit filter:
HAll high bit characters will be filtered before importing. High bit characters are such characters with an ASCII code number greater than 127. In most cases these are frames, but also umlauts and other special characters. That's why you should define some exceptions for this kind of filtering, at least for the German umlauts.
Replace spaces:
NThis is an option especially desgined for RA2. If you selected the @DF method of file description output, RA2 will try to reformat these descriptions. This looks extremely ugly when doing so with a previously well formatted or put-into-frame file description. But SKC can replace spaces (blanks) with a character looking like a space, but not letting RA2 break up the line at this point any more. Disadvantage: When somebody tries to find a so-treated file description by using word search in the BBS, he is not going to find anything if he is looking for an expression containing a blank.
ANSi filter:
ÆIt seems to become popular, putting colourful ANSi DIZs into archives. If you wish so, SKC will filter out ANSi codes before importing into base.
WildCat Filter:
'Filter for WildCat color codes (@xx@).
PCB Filter:
LThis is the same thing like the ansi filter, but for PCB colour codes (@X).
Ezycom Filter:
-Filter for Ezycom 1.10 colour codes in DIZs.
PB2 Filter:
,and the respective filter for ProBoard 2.0.
s╔
' (
■ Automatically describing files ■

ïIf you want it to, SKC is going to describe certain files of itself. Setup here, which files you would like being described automatically.
Picture description:

╘SKC can create a sense making description for some picture formats. This description will only consist of the picture file resolution. At the moment, SKC is able to make a description for JPG, GIF and PCX files.
Sound description:

╬SKC can also make descriptions for sound files. They consist of statements concerning number of samples, patterns and if possible even their names. At the moment, SKC supports MOD, S2M and S3M sound files.
ATTENTION!: If your file base does support multi-line descriptions, this selfmade description will be written OVER the old one, entered by the user. When using one-line description methods like Ezycom and Eft do, the old description will be overwritten with the recently created one.
'
■ "Dummy" description ■

╥SKC adds files, not yet found in the file base, to it when they were converted or a description file has been found. If SKC could NOT find or create a description, SKC will use the description configured HERE.
'
■ DIZ tag ■

╖Here you may enter a tag line, which SKC is then going to append to DIZ files. You could enter a small origin line of your BBS here or a line called "passtrough" in the world of PCB.
ZThe DIZ tag mode option lets you setup, to which DIZ files your tag line should be added.
■FILE_ID.DIZ files are imported into the file bases of many BBSs, together with your tag line! Imagine what kind of advertisement that could mean for you!!! Well, why don't you register this version of SKC, this is only a little gadget for such users. ;)
MOf course, SKC is NOT going to import your DIZtag into your own file base...
çYou may completely configure the outfit of newly created DIz files. Do this by editing the external text control-file CTL\FILE_ID.SKC.
r╧)∞'
■ DIZ tagging mode ■

╨To be honest: This is really not my favourite feature of SKC because I know, what it is going to trigger...a FLOOD of tag lines in DIZ files as known from PCB. Well, at least it is only for registered users:
DSetup here, which DIZ files are to be tagged with your DIZ tagline.
6ATTENTION: Your own DIZ tag will never be imported into the file base, but it will NOT be deleted from your DIZ automatically, meaning that your tag line would be added more than one time when checking multiple times. To prevent this, please enter your own DIZ tag into the external control file PTHROUGH.SKC.
,Never: DIZ files will not be tagged at all.
ANew: Your DIZ tag line will only be added to newly created DIZs.
yExist: Your DIZ tag will only be added to areadily existing DIZs. This DOES make sense, e.g. when using the FILE_ID.SKC.
gNew&Exist: This is the convention of NEW and EXIST, meaning a tag line will be added to all DIZ files.
q$%[)H'7
■ Exceptions when filtering high bit characters ■

╜If you have enabled the highbit filter you are able to define now some exeptions for that setting. The german "Umlaute" are highbits for example and should be put to the highbit exeptions.
nP'4
■ File description width available using RA2 ■

)This is a special feature fo RA2 sysops.
)If you have choosen @DF in RA for displaying the file descriptions online, RA2 will try to wordwrap the lines. This looks realy stupid on framed or formatted DIZ's for example. You have 2 choices in SKC now for stoping RA doing this. One possibility (prefered by me) is the Space Replacer of SKC.
ºThe second possibility is to let SKC fill up the description lines with spaces at the end to match the width defined here. This will make RA wrap the lines correctly.
»The disatvantages: The descriptions look hoorible in external tools like RAMGR. And if you change the width of the descriptions, you have to reenter all the old descriptions.
₧The disadvantages of the Space Replacer mentioned above: If a user searches a file with the keyword search, inputs that hold spaces won't be find, of course.
nr' 1
■ Entering the names of description files ■

Please enter here the names of files in archives which SKC is supposed to import as a description into the file base. The order in which you state these file names IS IMPORTANT, because SKC is according to this order when searching an archive for description files.
╟For example, SKC could import a FILE_ID.ANS preferredly and only if it is not available, import the FILE_ID.DIZ. I HOPE this is going to take effect on these ANSi DIZ files becoming more and more common. They should now be renamed to FILE_ID.ANS, while FILE_ID.DIZ stays ASCii. The same with PCB colour codes: PCB SysOps could preferredly import FILE_ID.PCB and usual DIZ files could be FREED of PCB colour codes. Maybe this could become a new standard??
FOne could also try to check for a FILE_ID.ENG before the FILE_ID.DIZ.
xATTENTION!: Ezycom 1.10 SysOps should state a FILE_ID.CLR at first if they want to use DIZ files with EZY colour codes.
'
■ Export VENDINFO.DIZ ■

kWith this dialogue you can define how and if SKC should export VENDINFO.DIZ from archives to your filebase
SIZE
HThis defines, what size of description may be exported. Normaly this should be "450 chars", if you want to export the description looking like a FILE_ID.DIZ. If you don't have longdescriptions in your filebase you may choose for example the oneline description. "Don't export" will disable the exporting of VENDINFO.DIZ at all.
PROCESS
\This options defines, if you want the VENDINFO exported with higher or lower priority than other DIZ files. Normaly you should choose "before" (the higher priority), because VENDINFO descriptions have in most cases a more original state. If you choose "after", a DIZ file will be exported if found and only if not found, the VENDINFO will be used.
w^'
■ VENDINFO.DIZ ■

ƒThe VENDINFO.DIZ file is a description file of the american shareware association ASP. This format is mostly found in archives of members of the ASP, but it is also often found in other archives. This file doesn't hold descriptions of defferent sizes but also informations about distribution licenses, prices, support and so on. The VENDINF.DIZ file holds nearly everything, what should be known about the archive.
pThis file seems to be very popular in distributor circles because of the distribution and license informations.
KVENDINFO.DIZ holds an readyble ASCII part and a binary part. SKC will only read the binary part, because this part is very difficult to change. This makes it nearly secure to have the original unaltered description given by the author of the archive. Especially mentioned: The description won't be altered with taglines and so on. ''
■ Rejecting files ■

ƒIn this dialogue, you may setup, which files SKC is going to reject, considering which criteria. Such files will be treated as though they were bad or broken.
%The following options are available: ε
Rejection according to file age:
Oldest date
Oldest day
BaseDate

Rejection according to quality:
GIF resolution
JPG resolution
PCX resolution
MOD resolution

Rejection according to file name:
Hacklist flags

yz{%|X}h~xêÇ╜'"
■ Maximum allowed file age ■

╤Users uploading really OLD files are annoying. SKC can reject such uploads and treat them like bad files, so the BBS system is not going to credit it at all because the file has already been deleted or moved.
╦Here you can state exactly this maximum allowed file age. Simultaneously, the touching option will be observed. If this is set up correctly, even stamping today's date onto the uploaded file is useless.
UIf the maximum age is pointing out a smaller allowed file age, it will be activated.
IDz╩'+
■ Maximum allowed file age in DAYs. ■

╤Users uploading really OLD files are annoying. SKC can reject such uploads and treat them like bad files, so the BBS system is not going to credit it at all because the file has already been deleted or moved.
╦Here you can state exactly this maximum allowed file age. Simultaneously, the touching option will be observed. If this is set up correctly, even stamping today's date onto the uploaded file is useless.
VIf the maximum date is pointing out a smaller allowed file age, it will be activated.
IMz╙'<
■ Read maximum allowed file age from file area setup ■

OGlobally using a maximum file age for the whole file base has turned out to be rather unuseful. That is why it is possible with RA 2.0 to setup a maximum file age for each area. So it has become possible for me to allow any file age in my source code areas, while any upload into another area being older than a year will be rejected.
╜SKC will only react to this when using RA 2 as BBS software. If files are checked, SKC is looking for a maximum file age being configured for the current file area and if possible uses it.
hAny other files outside the file base will be treated as set up as default: Oldest date and oldest day.
yÖz⌐
'
■ GIF resolution ■

äThis defines a minimal GIF resolution allowed on your system. If the checked GIF has a minor resulution, it will be treaded as bad.
'
■ JPG resolution ■

äThis defines a minimal JPG resolution allowed on your system. If the checked JPG has a minor resulution, it will be treaded as bad.
'
■ PCX resolution ■

äThis defines a minimal PCX resolution allowed on your system. If the checked PCX has a minor resulution, it will be treaded as bad.
'
■ MOD quality ■

~This defines a minimal MOD quality allowed on your system. If the checked MOD has a minor quality, it will be treaded as bad.
'
■ Hack list flags ■

}If you are using a hack list of the newer standard (HACK????.IDX), you have to enter the flags of files you wantt to reject.
-Flags PIR, TRO, HAK und HOX are recommended.

`- ''
■ Internal dupe check ■

¿You can let SKC check, whether an uploaded file is already in your file base or has at least been there. SKC is using a very fast index system (DB\DUPE*.DBC) for that.
4SKC has two levels of checking for duplicate files:
σ-> File dupe check: Always when SKC is testing a file, it will save information about it, so it can always be recognized again. When checking an archive (meaning the file extension is stated in the packer configuration), it is going to save the file name without extension. When checking another file (a GIF or EXE file e.g.), SKC is going to calculate it's CRC checksum ans save it. If SKC notices an entry as already saved, it will report the file as duplicate and reject it as bad.
£For this check, INITDUPE.EXE should have run over your file base to make checking for Dupes effective even in the beginning. This is not urgingly required.
p-> Contents dupe check: To take advantage of this option, you are required to become professionally registered.
░When SKC has extracted an archive, it is going to check it's contents and saves all CRC checksums of the archived files. While doing that, he can again recognize files in the archive which have already been in the file base, even in an archive with maybe another name! You may now setup, how many percent of archived files need to be dupes to reject the whole archive as duplicate. A percentage of 80% has evided as recommendeable.
sThe contents dupe check makes it impossible to your users to upload archives being repacked out of other archives.
ÜOf course, this dupe check is going to take some more time, but it is strongly optimized and will only be noticeable when checking really large archives.
╓The dupe checking is generally configured in the dupes dialogue and will be activated by the additional command line parameter /DUP . Without adding this parameter, a dupe check is not going to be executed at all!
éΘ'*
■ Setting up duplicate files check ■

éPlease setup here, whether SKC is going to execute a file or a contents dupe check when indicated by the optional parameter /DUP.
╣The switch "Base dupe flag" will cause SKC to check the dupecheck flag in the filebase before doing the dupecheck. This is only possible with RA2, other filebases don't have that flag.
|Also setup the minimum percentage of dupes neccessary for the extended dupe check to reject the whole archive as duplicate.
The option "Min Size" holds the information about the minimal size of the files should be processed while contents dupe checking. Because the contents of a file will be checked, the size should at least be 1 (byte). Perhaps a higher input would be a good idea.
[The contents dupe check is only available in the professionally registered version of SKC.

üs
''
■ COM port configuration ■

Available options: h
Port number
Use FOSSIL
Use FIFO
INT for the port
Port addresses

ä7àKå_çsêç'
■ Standard port number ■

sHer you define, wich Port SKC should use normaly. Setting this to 0 means local, no output/input to/from the port.
ÖThis setting will be overwritten by the parameter /P:<Port>. This means: You don't have to create a single configuration for every node for that reason.
'
■ Using the FOSSIL ■

ÅSKC has to ways to talk to the port. The on is, to use a prior loaded and setted FOSSIL driver, the other way is to use internal COM routines.
╓If you have already loaded a FOSSIL for your BBS, SKC should use the FOSSIL, too. If you run SKC via ISDN, you should load CFos and switch SKC to FOSSIL output. The internal routines won't work with ISDN directly.
íIf you don't use a FOSSIL, you have to set up all the other entries in the dialogue correctly. You don't need all the other entries, if SKC is using the FOSSIL.
┼If SKC doesn't use the FOSSIL, it has to know about the actual baudrate used at the COM. You can specify it with the /B:<Baudrate> parameter or let SKC read it from DORINFO.DEF or DOOR.SYS itself.
'
■ Using the FIFO ■

0Should the internal COM routines use the FIFO ?
à$'
■ Port interrupt ■

UDefine the interrupt that should be used by the internal COM routines for that port.
àI'
■ Port address ■

UDefine the addresses that should be used by the internal COM routines for that port.
àG''
■ Sound options ■

+This is rather thought as a little gag...:
cSKC is now able to play .VOC files using a SoundBlaster compatible sound board or the PC speaker.
9Using this dialogue, you may configure these VOC-events.
Options available: Ü
Play VOCs
SoundBlaster auto detection
SoundBlaster installed
SoundBlaster port
SoundBlaster interrupt

Å╫
è√ïî7ìUÄs'
■ Playing VOCs ■

JThis is a feature for sysops loving little blinks and beeps (like me ;) )
⌐SKC can play in specific events VOC files. If you have a SoundBlaster compatible soundcard, it will play them using the card. Otherwise SKC will try to use the speaker.
äIf you want to play SKC sounds enable this option. If you switch the option of, the rest of the dialogue is of no interest for you.
Ås'%
■ SoundBlaster auto detection ■

⌐SKC is able to detect an existing Soundblaster and it's settings automatically on your system. If a Soundblaster was detected, SKC will play the VOCs using the Blaster.
╪This option nomaly can be switched on. But SKC will do some system tests then, wich might crash some systems (e.g. some networking systems). If this is the case, switch this option of and enter the settings manualy.
'
■ Soundblaster installed ■

ÜIf you disabled Soundblaster auto detction, you have to tell SkC her, if a SoundBlaster is installed on you system. Else SKC will try to use the speaker.
ï1'
■ SoundBlaster's Port ■

ÇIf you disabled Soundblaster auto detction, you define hexadecimally the port here, that your Soundblaster is using. (e.g. 220)
ï.'
Available options: "
■ Soundblaster's interrupt ■

zIf you disabled Soundblaster auto detction, you define the interrupt here, that your Soundblaster is using. (e.g. 5 or 7)
ïH'+
■ Eplanations concerning VOC-events ■

ZSKC is using the following VOCs, if found in the VOC\ subdir of the SKC system directory: E
WELCOME.VOC At startup
CLICK.VOC When another action is performed
BADARC.VOC If archive is considered as bad
VIRUS.VOC If archive contaminated with a virus
TOOOLD.VOC If archive is too old
DUPE.VOC If a duplicate file was found
BOOTING.VOC Before rebooting the system
THEEND.VOC When all action is done

About the PC-speaker routine:
If there was no SoundBlaster card detected or not correctly configured, SKC will try to play the .VOC files using the PC-speaker. In the case that you are having problems with this routine, DO turn it off using the play VOCs dialogue, because I will not care any further about it! It is completely unimportant for the actual work of SKC. It does not even run on all systems unproblematically; on 2 out of about 10 tested systems, the sound output was rather noisy, but on all the others it did work very well.
îI would like to say thanks to Martin Bene for this really first class routine and support I got, when I even came on with questions... :-)
¿This option is only working under DOS, as soon as SKC detects a multitasker, it will disable the VOC routines, because they are programmed very near to the hardware.
öI did also test the routine under DESQview, there, everything runs perfectly, although the timeslicing in this case will be turned off COMPLETELY.
That is why I also implemented the /MTVOC command line parameter, which will suppress disabling of the routines under a multitasker. Please feel free to use this one TO YOUR OWN DANGER, under OS/2 and WIN*$&% your system is certainly going to hang up instantly.
,All these restrictions are only valid for sound output via PC speaker, SoundBlaster cards cause problems only very rarely. In one case, the autodetection routine crashed a network server [ ;)))) ]. This can be avoided by disabling the autodetect routine and entering the valid parameters manually.

è┬ï░
''+
■ Dialogue of miscellaneous options ■

ZThis is a dialogue concerning miscellaneous options, which did not fit anywhere else :-)
Available options here:
Zooming windows
Extended infos
Fast new files scan
Mulitline check
Semaphore usage
Update FILES.SKC
Create SKCDONE
Enter before EXEC

Environment
Ansi output
Swap type
Log level

æúÆ╕ô═öΓò≈ùû!ÿ6ÖMÜb¢w£î'
■ Zooming windows ■

╦SKC can zoom its windows in and out. This does look nice, however it does also steal time when used online, but also this only very little. So it is not really AQOT, but rather a question of your taste.
'
■ Extended info ■

]Turning this on means SKC switching into 50-lines-mode when starting up, of course only if your hardware supports this. In the upper half of the screen you will see the checker's screen as the online user sees it. In the lower part, some extended information concerning the currently checked file(s) is being displayed, e.g. the DIZ file, if found.
YIf no VGA graphics adaptor is found at runtime, this option is turned off automatically.
'
■ Fast new files scan ■

cThis is a setting concerning your base scan. If you turn this on, SKC is going to attempt to find out as fast as possible whether there are new files located or not. If not, it will jump to the next area instantly. Turning off the FNS, SKC will search EVERY area. You should try turning FNS off if you have the feeling that SKC does not notice new files.
'
■ Multiline check ■

mIf somehow the opportunity could turn up that two or more SKCs could run parallelly, please DO turn this on.
'
■ Using semaphores ■

ùThis should be turned on on rather critical multiline systems. One copy of SKC will wait for the other one to finish if working in the same directory.
'
■ Update FILES.SKC ■

ëShould SKC memorize checked files in the FILES.SKC and therefor don't check files ? This should disabled only if you have a good reason.
xOne reason for example could be that SKC is always checking in temporary directories as it is done under XFD or AllFix. #
Menu of miscellaneous options

¥D É!'
■ Create SKCDONE ■

╥SKC is able to write all checked file into textfiles created in it's homedirectory. Accepted files will be written to SKCDONE.<Node>, bad files to SKCBAD.<Node>, virusinfected files to SKCVIR.<Node> and so on.
You *have to* enable this option, if you want to use the util PB2RATIO. You may enable it, if you want to use it as a semaphore. You could check e.g. after exiting your BBS for the SKCDONE file and run your request processor index updater e.g., if found. #
Menu of miscellaneous options

É≡'
■ Enter before EXEC ■

═In order to prevent external tools from asking for keyboard input SKC is able to put a Enter to your the keyboardbufffer. This will have the same result as pressing Enter manually before each shell. But some Multitaskers like e.g. DESQview don't maintain a seperated keyboardbuffer for each task. This will result Enter "pressings" in your foreground task, while SKC is running in the background. If this is the case on your system please disable this feature.
FHINT: SKC will try first to use KSTACK of the 4DOS package. Only if not installed, SKC will write directly to the keyboardbuffer. The advantage is: Tools clearing the keyboardbuffer first may be manipulated, too. If possible you should have KSTACK installed. (Perhaps this will also solve the problem with DV discussed above) #
Menu of miscellaneous options

É5'
■ Environment ■

╠Adjust here, under which environment conditions SKC will have to work. You can choose an operating system manually or choose AUTO to have SKC testing by himself which operating system it's working under.
sBecause SKC is checking some ports and interrupts while testing, there could be problems in critical environments. #
Menu of miscellaneous options

ÉZ'
■ Output ■

]Adjust here, how SKC shall present itself to a user online. It has got two ways of doing so:
ûa) A pure ASCII screen. This is very fast though designed informative and attractive. It should be used if your BBS is not connected to a fast modem.
xb) A colourful screen, looking very much like the one you see locally. This screen can be displayed in ANSi and AVATAR.
<You have 3 possibilities of configuring the user's display:

ASCII:
+The fast ASCII screen will always be used.
Color detect (AUTO):
╫SKC tries to use the coloured screen. It also attempts to recognize which colour emulation the user's terminal supports. First, it is tested for AVATAR, then for ANSi.. if both fails, SKC will use the ASCII screen.

Dropfile:
½SKC is going to use the configuration the BBS user is using. For that, there must be a recent DORINFOx.DEF (AVT/ANS) or DOOR.SYS (ANS) available in the current directory. #
Menu of miscellaneous options

É¥'
■ Swap Typ ■

»Here you define the kind of swapping SKC should use if it swaps before a shell. The best choice is to let SKC swap to EMS, but some system circumstances may deny this option. #
Menu of miscellaneous options

É┼'
■ Log level ■

tUsually, SKC creates an exends a log file while working. Setup here, how detailled this log file is supposed to be.
ùAssuming a log level of 1, only the most important things will be logged, at a log level of 3, anything that can blow up the log file, will be logged.
vIf you encounter problems with SKC, you should probably switch the logging level to 3, otherwise switch it to 1 or 2. #
Menu of miscellaneous options

É£'
■ FILES.SKC ■

åSKC memorizes areadily checked files in text files in the respective directories. These are the .DAT files; they are named FILES.SKC.
JMaintenance of these files is possible with the included utility SKCTOOL.
]At least you should call SKCTOOL DATPACK daily in order to hold the databases tiny and fast.

''$
■ Configuring virus scanners ■

ZHere, all virus scanners to be used with SKC are to be configured. Options available are: ₧
Name
EXE
Parameters
Logfile
Errorlevel 1
Errorlevel 2
Heuristic EL
Use it
Options
Export
Import

ƒéáÉí₧ó¼ú║ñ╚Ñ╓ªΣº≥¿⌐'
■ Name of the scanner ■

╞Here, please enter the name and maybe the version number of the currently used scanner. This is the name that will be shown to the user online while scanning an upload with the respective scanner.
oAlso, it will be listed in the import list, shown when importing an SKC standard scanner identification file.
⌐'
■ EXE-file ■

äThis is the file that will be executed by SKC. Please state the file name WITHOUT parameters, they must be entered one line below.
sWith F3 you may select the EXE file in a dialogue, e.g. if you lost the directorie's or the name of the EXE file.
'#
■ Parameter of the VScanner ■

;Here you define the parameters to be given to the scanner.
╛Normaly directories or files to be scanned will be added behind the parameters given here. But you can let SKC insert the directory/file inside the list with specifying the macro @@D in it.
ÜAnother macro is @@N, that will be replaces by the actual nodenumber. With this macro you can (and should) define node depending logfiles of the scanner.
óó'
■ Log file ■

ªSome scanners are designed to create a log file concerning the scanning procedure, containing nearer information about a virus found, at least the name of the virus.
If you state a name of the log file here, SKC will move the log file created together with the contaminated archive to the virus directory and rename it to <ARCHIVE_NAME>.SKV . So you have the possibility to check later, which one of your scanners reported the virus contamination.
▒You can use the macro @@N inside of the name, that will be replaces by the actual nodenumber at runtime. This makes it possible to use a seperate virscan logfile for each node.
X6'7
■ First errorlevel returned when virus is found ■

┼This is the normal errorlevel returned by the virus scanner, if a virus was found. Please refer to the manual of your scanner for details or import the scanner from the example file "VIRUSCAN.SKC"
aYou may define one more errorlevel, if your scanner returnes two different errorlevels on virus.
⌐εñ'=
■ Alternative errorlevel returned when virus is found ■

╜This is the alternative errorlevel returned by the scanner when virus is found. If your scanner only returns one errorlevel enter a 0 here and enter the errorlevel as the first errorlevel.
úΘ'6
■ Errorlevel returned on heuristic virus alert ■

If your scanner supports "heuristic" virus scanning you can enter here the errorlevel returned by the scanner on heuristic alerts. because heuristic alerts are not 100% secure, SKC will handle this alerts seperately. If your doesn't support heuristic scans, please enter a 0 here.
ÇIn the options field you can define, if SKC should fail the checked file, when a heuristic alert was reported. (heuristic fail)
¬Pº┬'
■ Use it (VScan) ■

¬Using this switch, you can easily disable usage of a virus scanner without losing the configuration. If switch is turned on, the scanner will be used, else, it will not.
'$
■ Options (VScan) ■

Swap out:
═If the scanner is not having enough memory when executed by SKC, enable this option. SKC will then swap a big part of itself out of memory to EMS or hard disk and so leave lots more memory to the scanner.
Subdirs:
Is your scanner able to scan subdirectories? Disabling this, the scanner will be instructed to scan every subdirectory singularly; when enabled it will only be instructed to scan the main directory, which is the faster method that is supported by almost all modern virus scanners.
Scan always:
.Usually, SKC executes the scanner only, if there is an .EXE, .COM or .OV? file found. Using this switch, you can let the scanner be executed anyway. This is not neccessary in most cases. [Attention, there are WinWord macro viruses spread which are implemented in WinWord text document macro records!!]
Boot on virus:
╛If a virus was found, should the system be rebooted?! This is a very extreme security function for fearful minds, because one can assume that a virus cannot become active by checking an infected file (I have no idea how...). This option requires that your system restarts the BBS automatically at startup time. Also, you should never enable this under OS/2, in this environment it only closes the current task, which is not desirable in any way.
Log out user:
5When a virus was found, should the user automatically be disconnected from the BBS? This option is made for security reasons to ensure the user notices his bad deeds and to motivate him to scan his HD before performing further activities. Also, it is very probable that he is going to upload further viruses.
No wildcards:
Some scanners cannot handle wildcards at all. They want to be given a _directory_. If this is the case with your scanner, so do turn on this option. The consequences are, that this scanner is not going to be used to check single files like EXEs, but only for scanning unpacked archives.
Heuristic fail:
jIf files failed the heuristic scan of this scanner, should the file be moved to the heuristic directory ?

¬┬Y'+
■ Exporting scanners' configuration ■

╔You can export the current one or all the scanners to a readable standardized text file. You can give this to friends who do not know how to use the respective scanner(s) or just send it as a message.
nThe normal name for this text file is VIRUSCAN.SKC, but of course you may rename this file to any other name.
')
■ Importing scanner configuration ■

nYou can import a scanner configuration from a text file exported using SKCSETUP. I included one file VIRUSCAN.SKC in the SKC archive, in which some of the scanners I tested are already pre-configured. You only need to adjust the paths to your system environment, then the scanner is installed completely. If you even want to USE it, please enable the use it option.
¿bªë'%
■ Heuristic Scan, Explanation ■

ⁿThe normal method for detecting viruses in files is to search for matching keywords inside of them. This method depends on the fact, that the scanner has to know the virus before it can detect the virus. New viruses can't be detected with this method.
ΣFor that reason many scanners supports the so called heuristic scan. This method doesn't search for keywords but for suspicious things in the file normaly only found in infected files. If many suspicious things are found, the scanner assumes that the file is possible infected. This is the only possibility to detect unknown virus infections automatically. But this means also, that virus alerts reported by the heuristic scan aren't 100% secure, false alarms are more than possible.
┌SKC is able to support the heuristic scan of your antivirus processor. You have to enter therefore the heuristic errorlevel returned by the processor and tell SKC, if it should fail files triggering a heuristic alert.

Ñqº╗''
■ Packer configuration ■

ÄExternal packers are neccessary for SKC to work on archives. Here you may configure how SKC is supposed to handle packers and their archives.
îThe most common packer programs are already pre-configured, so if you are not used to them, just leave the archiver information unchanged.
'%
■ Dialogue Packer adjustments ■

'
■ Picking a packer ■

/Using this list, you can easily pick a packer.
╧Wth Shift+Cursor you may change the position of the actualy choosed compressors inside the compressor configuration. If you do so, please remember to adjust you converting compressor in all configurations !
'
■ Archive extension ■

┌This is the extension the archives of a packer do usually have. Files are worked on with this packer if they possess the stated extension; if two packer entries have the same extension, the second one will be ignored.
'
'In this box you can switch to options: 6
■ Swapping out SKC before executing the packer ■

÷Some packers cannot satisfy their hunger for memory with the amount that SKC is leaving them. For these packers you must turn on this option. SKC will then swap out a very big part of itself of the memory to provide more memory for the archiver.
■ Never convert ■

UIf you have defined a converting acker but don't want files of this type to be converted, please switch this option on. This switch is nice for sysops only wanting exotic compressors to be converted. If you are one of them, please define your converting packer and after this switch this option on on all compressors called "normal" by you.
Lâ'
■ Packer's EXE ■

─Now enter the EXE file of the appropriate archiver program. Do not state a directory here, the packer will be found in the packers' directory or in the system path, e.g. PKZIP.EXE for .ZIP files.
WÆ'
■ Unpacker's EXE ■

¥With the here-stated EXE-file, archives possessing the appropriate extension will be unpacked with. In many cases this is the same file as the packer's EXE!
îDo not state a directory here, the unpacker will be found in the packers' directory or in the system path, e.g. PKUNZIP.EXE for .ZIP files.
W∙'%
■ Packing without directories ■

╝These parameters are received by the packer, together with the archive name, if a file is being packed into the archive WITHOUT its directory, e.g. the advertisement file inserted by SKC.
'"
■ Packing with directories ■

sPlease enter the parameters given to the archiver to pack files together with their directories into the archive.
ATTENTION:
ÖIf the packer does NOT support this, do NOT use it as the conversion packer, because otherwise very important archive information can be lost easily!!
''
■ Unpacking without directories ■

FParameter for decrompressing archives without restauring directories.
'$
■ Unpacking with directories ■

FParameter for decrompressing archives and restauring the directories.
'
■ Testing of archives ■

RParameter to give to the packer for testing its archives for their CRC-integrity.
'&
■ Deleting files in an archive ■

GThe parameter which makes the packer deleting files out of an archive.
'
■ List file letter ■

╗Letter that is being placed in front of a the name of a list of files being supposed to be handled by the compressor program. This list is being used to delete or add more than one file.
æIf the packer does not support this kind of a list, please leave this entryfield empty, SKC will tell the file names to the archiver singularly.
'
■ Stamping a logo ■

ÅParameter for commenting an archive, it stamps the BBS logo onto it. If the selected packer does not support this, leave the entryfield empty.
'!
■ Parameter for logo file ■

1Parameter placed before the name of a logo file.
')
■ Logo for files of this archiver ■

ÜYou can state a separate logo for each archiver. It must be located in the CTL subdirectory of SKC, so do only state the name, NOT the path or directory!
DLeaving this field empty means that the standard logo will be used.
▐This is useful e.g. for the archiver program RAR, which is the only known packer directly supporting an ANSi logo. So you can use a normal ASCII logo as standard and parallelly define an ANSi logo only for the RAR packer.
u#ε
'
■ Repacking archives ■

èPlease enter here, whether checked archives ought to be packed completely NEW or files shall only be deleted from or added to an archive.
(You can choose between 4 possibilities:

Never:
àArchives of this type will never be repacked. This should be the usual case, because repacking them usually does not make any sense.
On -AV:
An archive will be repacked if an AV envelope was found. This could be interesting for you if you also want to convert or change -AV protected archives (this is usually NOT done, see translator's comment). ARJ archives e.g. do not allow any write access if AV-protected.
Not -AV:
{This is the contra point of "On -AV". All archives without an AV envelope will be repacked. This shouldn't be neccessary normaly. But with some compressors repacking archives is faster than deleting and adding files from and to the archives. This is the case with solid archives. This option might be interesting, too, if a new incompatible version of a compressor is coming up.
Always:
∞Archives will ALWAYS be repacked. This dos not make sense in most cases, all AV securities will be lost e.g. But maybe your packer packs archives more dense when packing completely new instead of only adding to and deleting from them?!
! Hint:
If an archive is repacked this will of course be done with the files on your harddisk. This means: If you have an active virus hooking in your memory unrecognized, the contents of the whole archive will be infected after in most cases. This is not possible, if you don't repack archives.
DFor that (and other) reasons normaly repacking should switched off.
┬ì'
#
■ Treatment of SFX archives ■

╠Setup here, how SFX-Files (self-extracting archives) of the packer ought to be handled. SFX-archives can only be recognized if the correct pack-ID was stated and if it does also turn up in the SFX files.
Most SFX-Archives are standard archives of the respective packer type with a small .EXE file "glued" before. This is also what SKC assumes. It will look behind this EXE-file, whether there is a known ID and if YES, it will treat the file as an SFX-archive.
ùAgain, we have 3 possibilities of SKC treating SFX-files. Check out for yourself, which possibility applies most to you and delivers the best results:
¡The FAST one: SKC cuts off the EXE-Header from the SFX and renames the resulting file. This works with many SFXs, but not with all and should be enjoyed with a lot of care!
The SLOW one: SKC lets the archive being unpacked by its respective (un)packer program. This is the safest method, but not all archivers can handle the extension .EXE if they are being told to unpack one of them. All modern packers are supposed to support this!
åNO repacking: If both possibilities fail, you can only turn off the treatment of SFX archives of this packer. (Just check that out..)
└»'
■ Packer's errorlevels ■

äHere, errorlevels given back by the respective archiver program must be entered. Please see your packers' documentations for these.
'

■ Packer's errorlevels ■

èHere, errorlevels given back by the archiver program in special situations must be entered. Please refer to the packers's documentations.
öSKC will react in a special way to these errorlevels if received from the packer program. Archives will e.g. not be rejected as bad in these cases.
Disk full:
$This errorlevel is received from the packer if it cannot unpack the archive any further because the conversion drive is full. This errorlevel is VERY important, because if it is recognized by SKC, it will not attempt to convert or repack an uncomplete archive, otherwise, data would be lost.

Mem low:
·On reception of this errorlevel, further treatment of the archive will be cancelled. If you find this errorlevel in your log file, you should turn on the swap option for this packer. If this is already the case, you must free up more memory for SKC.
Not found:

ôThis errorlevel is returned if a file was not found, e.g. the logo file or the advertisement file. Please check your configuration in these cases.

Password:
fReceiving this errorlevel when unpacking, treating this archive will be stopped, because it cannot be unpacked automatically. ATTENTION: Many packers return the same errorlevel as they do when confronted with a defective archive (CRC error). If you would enter this as the PWD errorlevel, all broken archives would be treated as password protected and OK!!!
»'
■ Pack-ID ■

úAlmost all types of archives can be recognized by recognizing a special identification at the beginning of the archive. For that, look at some archives of the same type using a hex-editor and compare the first 8 bytes. Usually, some of these bytes are always the same. Looking at this packer-ID, SKC can identify the type of archive. It uses the pack-ID to verify archives and to recognize an SFX archive of this type.
Example:
τLet's assume, one type of archive is always beginning with $60 $EA (ARJ). The other 6 Bytes of the ID are different. For bytes in the ID which differ, a $00 must be entered. The appropriate entry for this type of archive would be:
60 EA 00 00
00 00 00 00

'
■ Pack-ID-editor ■

ÑHere, please state the pack-ID of the archive. State the values inquired using the hex-editor as hexadecimal values, changing bytes in the ID must be stated as a 0.
└0'
■ AV Security ■

ìAll of the modern compressors have the ability for Authenticity Verification of the archives. The AV secures the originality of the archive.
┐For example: Most of the archives holding virus scanning tools have an AV Code. Many sysop deny Antivirus archives without a valid AV code, because signatures and EXE's might be manipulated.
?SKC itself is delivered in a RAR archive with my AV Code, too.
PYou should handle archives with AV codes as originals and leave them unchanged.

''
■ UNP: EXE file ■

êHere you enter the EXE file that should be used for that entry. It will be used to decompress EXE files before scanning them for virus.
╞k'
■ UNP: Options ■

ZHere you can define wether SKC should swap out of memory before calling the EXE extractor
You can switch the option "generic" on if you want to use this decompressor on all EXE files with unknown copression type or with a compression type for that no extractor was defined before. Please use the generic extractor as last entry, because all entries after it will be ignored.
IThe swithc "Use it" tells SKC wether it should use or ignore this entry.
╞c
'
■ UNP: EXE compressors ■

ÆHere you define wich kind of EXE compressor this decompressor is able to handle. Please test this before definig it or you might get in trouble !
VIf you have defined the decompressor as generic, all options in this box are ignored.
╟º'
■ Decompress EXE files ■

╔Today most of the EXE files are compressed with an EXE Compressor. In this files viruses might be hidden, because they are compressed together with the EXE file. But they are still completely active !
With this option you can tell SKC to try to extract EXE files before scanning them. Many EXE decompressors are available in the BBS's. SKC itself will detect some of the compressors itself. (AVPACK, AiNPACK, COMPACK, DIET, EXEPACK, LiNK, LZEXE, PKLiTE, TiNYPROG, UCEXE, WWP, XPACK).
ÑOn all unidentified compressors a generic decompressor will be called, if defined. SKC will hand the compressed and the extracted EXE to the virus testing programm.
`WARNING: To use EXE decompressors in automatical maintenances is dangerous. They are easily able to kill the system. Every new decompressor should be tested for problems. And only by you validated compressor types should be processed by an decompressor. If possible *please* don't use a decompressor as generic! (Also have a look at EXE decompressors)
╟R╟√'
■ EXE Extractors ■

Please don't confuse compressed EXE files with (self extracting) SFX arechives. EXE files are normal executables that are compressed but still are executable in the same way they were original. Another advantage of this compression is that the executables are crypted and hard to modify.
╘But exactly this might result problems. If an EXE was infected with a virus before it was compressed, the virus is still completely active in the compressed file but hardly to detect by antivirus scanning tools.
/There are some tools that make it possible to decompress these files to the original state. This makes it possible for the virus scanner again to detect possible virusinfections of the EXE. That is the reason, why SKC holds the feature to decompress EXE files before scanning using these decompressors.
╖These decompressors traces the files before decompressing them. This means, they hook into the system in a very unstable way. For that reason it is more than possible that your BBS is somewhat unstable if EXE decompressors are defined and used by SKC. You should test each decompressor very hardly before adding it into SKCSETUP. And you should never use decompressors as generic decompressors, if you run your system unwatched for long !
''$
■ Setting up GIF compression ■

áThis option was originally thought for compressing of .GIF files to .JPG files, but you can also pack your .GIF files with GifBlaster, GifLite or even PKZIP.
Available options: ╛
Packer:
EXE of .GIF-packer
Parameters
New extension

Switches:
Active
Swap
Fail
ChDir

== ATTENTION! ==

*If you use SKC as online-checker with EzyCom, please DO turn OFF this option because Ezycom is goin to mark these files as BAD; it does not accept any other file extension than the one of the uploaded file. This does not apply to tools like GifLite, which DO leave the .GIF extension unchanged.
╔µ╩·╦╠/═D╬Y╧n'
■ GIF-packer EXE-file ■

uHere, state the file name of the GIF-packer executable. Select it with the aready familiar file manager of SKCSETUP.
'
■ GIF-packer parameters ■

All parameters needed by your compression program have to be entered here. Because usually the file name of the respective GIF file is one of these, I have made some macros available, SKC will replace with current values when starting the compression program: #
$F will be replaced with the complete path and name of the current GIF file.
$D will be replaced with the GIF's directory with a \ at the end.
$N will be replaced with the GIF's file name without extension.
$E will be replaced with the extension of the GIF file, which is always GIF

gExample: The file C:\FILES\PICS\MARINA.GIF is being checked.. The macroes will be replaced like this: G
$F C:\FILES\PICS\MARINA.GIF
$D C:\FILES\PICS\
$N MARINA
$E GIF

&The correct entry for CJPEG would be:
$F $D$N.JPG
'*
■ File extension after GIF packing ■

Because all kinds of compressors are possible to be used to pack a GIF file, SKC does need to know the extension the file will have after being compressed. SKC will also check, wheter the respective file is existing or not after executing the compressor program.
'"
■ Toggling GIF compression ■

;This option is designed to turn GIF compression ON or OFF.
'.
■ Swapping out before compressing GIFs ■

╒If your .GIF compressor needs a lot of memory, you should turn on this option. SKC will then swap out of memory before executing the compression program. My test resulted in this not being neccessary for CJPEG.
'.
■ Treating errors of packing GIF files ■

@How should SKC react if there were problems while packing a GIF file? Problems may be an errorlevel received from the compressor program or a non-compressed file with the new extension. Turn on FAIL to let SKC treat the file like a bad archive; turn it off to let SKC ignore the problem and work on with the .GIF file.
':
■ Move into the GIF's directory before converting? ■

~Some .GIF.compressors do not understand directory-statements received together with other parameters. They can only work on files being aligned in the current directory. So this is why SKC has the option to move into the respective directory before executing the compressor program. These compressors can be used together with SKC without problems when this option is turned on.

''
■ Menu Tools ■

eThis menu holds some tools for SKC, e.g. the CRC unwanted editor and the color configuration of SKC.
''
■ Editor for unwanted CRC files ■

πThe informations about unwanted files detected via their CRC (this means: by their contents) are saved in a binary file not readable for humans. It holds informations about the CRC, the size and the name of CRC unwanted files.
▐You can delete entries in the editor with the DEL button/key or restore deleted entries. Entries marked for deleting are ignored by SKC. If you want do get the entries out of your database, you have to pack the base with: $
SKCTOOL <DB directory> CRCPACK

ÇIf you search a file for the name, please start to enter the name at the input. The list will jump to the first matching entry.
'
■ Colorsetup of SKC ■

½With this dialogue you can setup the colors for SKC in order to match them for your background ANSi BACKGRND.ANS. You can change the color of each part of the SKC screen.
pIn the "group" window you can select a group of items, in the item window you select the item to change itself.
Ç''U ■ Help Index ■

"Dummy" description
AV Security
About
Advertisement file
Alternative errorlevel returned when virus is found
Archive extension
Archive treatment
Automatically describing files
Available options
Big advertisement file
Brackets around download counters
COM port configuration
CTL\BANNER.SKC Bannerdatei
CTL\DIZTAGS.SKC Liste mit DIZ Tags
CTL\DUMMYS.SKC Liste mit Dummy Beschreibungen
CTL\FILE_ID.SKC
CTL\IGNORE.SKC
CTL\PTHROUGH.SKC Liste mit DIZ Passthroughs
CTL\UNWNAME.SKC Liste unerwünschter Dateinamen
CTL\UNWRAND.SKC Steuerdatei zum Erkennen von Zufallsdateien
Checking depth
Checking options
Colorsetup of SKC
Compressor directory
Concord O.O1 Gamma
Configuring virus scanners
Conversion options
Conversion packer
Converting SFX archives
DIZ filters
DIZ otions
DIZ tag
DIZ tagging mode
DMS Archivtest
Datei auswählen
Delete original archive
Delete unwanted
Deleting files in an archive
Dialogue Packer adjustments
Dialogue of miscellaneous options
Die F1-Taste
Die Maus
Die Tastatur
Directory for advanced age files
Directory for bad files
Directory for duplicate files
Directory for files that didn't passed the heuristic check
Directory for virus infected files
EXE Dateien entpacken
EXE Entpacker
EXE-file
Editor for unwanted CRC files
Eft 2.+
Entering the names of description files
Environment
Environmentvariablen
Eplanations concerning VOC-events
Errorlevel returned on heuristic virus alert
Exceptions when filtering high bit characters
Exit the program
Export VENDINFO.DIZ
Exporting scanners' configuration
Extended info
Externe Dateien, die SKC benutzt
Ezycom 1.02/1.10
FILES.SKC
Fast new files scan
Feste Dateinamen
File base
File description width available using RA2
File door
File extension after GIF packing
FileDoor (XFD) 3.1+
Files & directories
Files & directories
First errorlevel returned when virus is found
GIF resolution
GIF-packer EXE-file
GIF-packer parameters
Hack list
Hack list flags
Hack-list
Hard drive for temporary files
Heuristic Scan, Explanation
Hilfe zum Hilfe System
Importing scanner configuration
In this box you can switch to options
Information
Installation als Uploadchecker
Internal dupe check
JPG resolution
List file letter
Load configuration
Log file
Log file
Log level
Logo for files of this archiver
Long descriptions' character
MOD quality
Mailer
Mailers' dialogue
Makros in den ANSi Dateien
Maximum allowed file age
Maximum allowed file age in DAYs.
Maximus/2
Menu Files
Menu Space
Menu System
Menu Tools
Menu upload unter ProBoard 2.1x
Menü Check
Menü Extern
Move into the GIF's directory before converting?
Multiline check
Music while coding ;)
Name of the description textfile
Name of the private description textfile
Name of the scanner
No CDROM areas
Options (VScan)
Options concerning file descriptions
Output
PCX resolution
Pack-ID
Pack-ID-editor
Packer configuration
Packer's EXE
Packer's errorlevels
Packer's errorlevels
Packing with directories
Packing without directories
Parameter for logo file
Parameter of the VScanner
Parameter von SKC
PcBoard
Picking a packer
Playing VOCs
Port address
Port interrupt
ProBoard 2.1x
Random add template
Read conversion packer from area setup
Read maximum allowed file age from file area setup
Refresh FILES.BBS, even if not neccessary
Rejecting files
RemoteAccess 1.+
RemoteAccess 2.+
Repacking archives
SKULLCHK.ARE
SKULLCHK.CLR
SKULLCHK.LNG
SKULLCHK.PKI
SKULLCHK.SCN
Save configuration as default
Save confirguration
Selecting file areas for /BASE checking
Setting up GIF compression
Setting up duplicate files check
Settings concerning the file base in use
SkullSoft Support-Sites
Sound options
SoundBlaster auto detection
SoundBlaster's Port
Soundblaster installed
Stamping a date onto an archive
Stamping a logo
Standard port number
Super BBS bis 1.17
Support-Site Hamburg
Support-Site Italy
Support-Site Sweden
Support-Site USA
Support-Site for Austria
Support-Site for the Netherlands
Support-Sites in Berlin
Support-Sites outside Germany
Swap Typ
Swapping out before compressing GIFs
TD0 Test
Terminate
Testing of archives
The following countries of germany have SkullSoft support sites
Toggling GIF compression
Treating errors of packing GIF files
Treatment of SFX archives
Turbo-Mail 2.06
UNP EXE Datei
UNP EXE Packer
UNP Optionen
Unpacker's EXE
Unpacking with directories
Unpacking without directories
Update FILES.SKC
Use it (VScan)
Using semaphores
Using the FIFO
Using the FOSSIL
VENDINFO.DIZ
Verifying archives
Verzeichnis auswählen
Zooming windows

╔p┬)>6R=ñQ3«åFÖo¼Ä╠S▀k≈!â#2$O#'t.)ñ(╡%┼,*≤/&$<JbEr╥äWù¡₧┴K▌L±Mnm*
q6r?"Q
aNrGï╖£¼║É╫! ·[ ZB\[Yz:X╢"╞┌╟±
á╤
)u2'Ö[hÅ~!Ñí,s╧-?■v¿%!ÆH
W y¥ï ôûa½c╜ t╚*d⌠ ╦ !Q6PKú`-|Å╔ƒ╩┤V╦ Ç╓`τ ]≥¬/⌐G»h%;Å
£ü╝}╤╕ßD≤ó U £ ╗& jG e ^r _z +ì y⌐ z├ !µ @±
=²

╨

"
C

O
╧\
0öÄ
╘ƒ
h╢
i╪
(ƒfº'l8$Ü^~f└v┴½Å░Ñ┐│╛╔│▀▓∙║í/J]¡fèxêåçöñ
T│O╚&{≡2e$
)xO
`
r
╝ä
ÿ
ª
┤
┬
!╨
C▐
A²
g'╚;éW by(,úë╝
ï╦ìΦî²I╣6äG]/q3ç2¢1░5┬4▄ .■0¢6═@$fp ╢{-É?╠╤╬δ$╜,├=
┼L─\▒j╡z┤ûù╡ª╟ò╫åΘà∙wH-æD'
'
■ Music while coding ;) ■

╟You are realy interested in this ? Well okay: While coding this version I've heard mostly the following groups : NOFX (to make my brain faster) and Skunkanancie (to make my head bang on errors) ;-))
'▄.LiçΣ $
6tà╞(/I"4%µ)╙/Ä1q5[8∞?GZIⁿK╡P¥U∩\t]╬]~^`_╛_~c∞gKiÄk╤mUq[rûuùx²{N~Γ~ü≥éBä¿ä:àåuç<êë▄ëâè┼ï╡î3ì┬ì?Ä╒ÄbÅ╟ÅBæ└æδÆ▓ô4ö╨Öåƒåª»¼▒h▓A╡▄╡╜╢Ñ╕╣║║ë╝?╛k┴ε┬║├δ┼╔╞h╚A╔>╩M╦┘╠∞╬╤┼╫╡█▌┌▀ΓαΣ¢µ╥ΦΘΩ─φ?∩z±╩≤√⌡cⁿ++Z[e
■`≥ⁿ:é]!
"╖"d#$±$─,C01I2W5╡586┐6Å8B:<╤<ä=Q>ìFHtIZKδLéMDN¿O╤Q?U╥V╞Z╛[Ö]_d`╘a÷b╥d{g√hj²k╨l(uúvUxg|╕}µ}Çâ≡âOàAå¢çêöêëÆëï╩ï-î=ÄσöπÖûÜXá9úñ-ªΓª▐¿¬<«]│^╢╖M║Æ╗╝╜ô╛d└ε└Ö├≤─I█