* BETA VERSION 1.09b - PLEASE DO NOT DISTRIBUTE WITHOUT PERMISSION * It's not really secret stuff, but if people have trouble with this version but are not aware that it's only a beta..... The b in 1.09b stands for second beta edition of the upcoming 1.09 The distribution filename is HC2_109B.ZIP, and has my ZIP AV code! This is a FULL OS/2 edition of HydraCom so you can use HYDRACOM.DOC (still the 1.00 docs, I'm sorry) with for the following extra info: INSTALLATION ============ Copy/move GIO.DLL in a directory in your libpath. This is the communications library HydraCom/2 currently uses. May change in the (near) future. REMOVED OPTIONS =============== nofossil Use internal async routines even if FOSSIL present noinit Don't init/deinit FOSSIL driver upon entry/exit slowdisk Suspend async I/O during disk access com N=adr,irq Set PORTADR,IRQ for comport N (example: COM 1=3F8,4) fifo off|N 16550A rxFIFO trigger level: off, 1-14 (default=8) dcdmask N Carrier detect mask in decimal (default=128) biosvideo Use BIOS routines instead of direct video access These options are not used/needed in OS/2. You ARE allowed to set them in HydraCfg/2, they're just ignored by HydraCom/2 in .CFG and .CTL files. But if you put any of these on the COMMANDLINE of HydraCom/2, you WILL get an error report. ADDED OPTION ============ inherit N OS/2 SIO handle passed from parent process If you call HydraCom/2 from another comms program like Maximus/2 or TE/2, use INHERIT instead of PORT. In this case N is not the port number but the file handle that calling comms program got from OS/2 when opening the port. If PORT and INHERIT are both specified (which is NOT the way it should be!) no matter which order.... HydraCom/2 will only use INHERIT and ignores PORT. DSZLOG ====== The DSZLOG characters are lowercase 'h' for download, uppercase 'H' for upload. This is a change from HydraCom 1.00 !! (where the doc is based on) NOTES ===== Not much, really. As already noted, this is a complete OS/2 edition: 32-bit, windowed (no PM, sorry ;-), colours, chat mode, HydraCfg, etc. In short: just like the DOS version, but 32-bit native OS/2 compiled. Note the different filenames: DOS : HYDRACOM.EXE HYDRACFG.EXE OS/2: HYDRAOS2.EXE HYDCFG2.EXE This has one quite important implication: The OS/2 editions default to reading/writing HYDRAOS2.CFG while the DOS editions default to reading/writing HYDRACOM.CFG You CAN override the CFG file used by HydraCfg, but not in HydraCom. So you have two separate configurations for DOS and OS/2. I thought that was a smart thing to do, with possible different settings... SOURCES / COMPILER ================== The HydraCom source for DOS and OS/2 is almost identical, just some #ifdefs. It also uses the same windowing library (written by me). The OS/2 edition has been compiled with Borland C++ for OS/2 version 1.0 In principle only sources of major releases are made available, ie. HydraCom 1.10 be a source release, but not HydraCom 1.09 But if you REALLY need to have the latest source for a project, just ask; it's not a problem, I just don't want millions of source code versions floating around the world.... HYDRACOM/2 IN MAXIMUS/2 ======================= You should be able to plug him into Maximus/2 like this: (please note that the DownloadCmd and UploadCmd lines have been split here!) Protocol Hydra Type Batch Type Bi LogFile Hydra%K.Log ControlFile Hydra%K.Ctl ; Put in NOS (nostamp) to not have HydraCom retain date/time on rcvd files DownloadCmd HydraOS2.Exe inh %P spe %W lin %b use "%n" nor nob res %x:Hydra%K.Log rec %v sen @Hydra%K.Ctl UploadCmd HydraOS2.Exe inh %P spe %W lin %b use "%n" nor nob res %x:Hydra%K.Log rec %v get DownloadString %s UploadString DownloadKeyword h UploadKeyword H FilenameWord 10 DescriptWord 0 End Protocol FEEDBACK ======== Please report back as soon as possible if you have any comments? Arjen Lentz AINEX-BBS +31-33-633916 FidoNet 2:283/512 arjen_lentz@f512.n283.z2.fidonet.org I also read the OS2.... conferences on FidoNet. --- end of "hydraos2.doc" ---