--------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: E5D00002 Date: 05/07/97 From: PETER BROWNWATER Time: 03:54pm \/To: SUE BLAKE (Read 0 times) Subj: Hello... am I here yet? Sue Blake wrote to All: SB> Phew, no wonder I found this tricky the first time round. SB> Then I blamed it on ignorance. Now I blame it on old age. SB> Did anyone ever come up with a less cramped event editor... I use OMAN 1.74 I find it works well with OPUS 1.79 in every area EXCEPT the MENU.... and I not sure about the menu either... waiting for Trev to answer on that. But it works for me on the events, User list, Nodelist and Outbound. Online help for any command is available, but it's all pretty simlpe. Regards, --- timEd/B8 * Origin: Pete's Place: 1-905-471-5229 (1:2424/204) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: E5D00003 Date: 05/08/97 From: TREV ROYDHOUSE Time: 2:35 am \/To: JOHN GIANNINI (Read 0 times) Subj: Re: Misc questions > *Grin* Let me be the first one to officially ask. > When will the next version of Opus be out? Will it be > soon? There is at least one further DOS release of Opus already under construction. The release date is to be advised. There may also be a Unix release and a Win32 release of Opus under construction "from scratch", provided sufficient people out there in MEADOW land pitch in and help. If you cannot program your way out of a paper bag, think about learning. If a dumb lawyer like me can do it, then anyone should be able to do it. Programming tools are not expensive -- and if you choose one of the *free* Unix operating systems like FreeBSD or Linux, the programming tools are also *free*. The only cost would be the Mix C Database Library, Linux version, for around $US 50. TREV. --- QM v1.30 * Origin: Sentry -- Sydney, New South Wales, Australia (3:711/401.0) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: E5D00004 Date: 05/08/97 From: TREV ROYDHOUSE Time: 3:03 am \/To: SUE BLAKE (Read 0 times) Subj: Re: Hello... am I here yet? > Phew, no wonder I found this tricky the first time > round. Then I blamed it on ignorance. Now I blame it > on old age. Hey, I'd blame it on old age too if I could remember how old I am :-) > Did anyone ever come up with a less cramped event > editor that doesn't require a printed command > reference to use? You could look at SPICE. > Well yes, if you can read this you'll know I'm back in > the meadow... crawling on all fours, but back. Was this a "new" install ... just curious as to how my installation program performed in the real world. TREV. --- QM v1.30 * Origin: Sentry -- Sydney, New South Wales, Australia (3:711/401.0) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: E5D00005 Date: 05/08/97 From: TREV ROYDHOUSE Time: 2:59 am \/To: STEIN-IVAR JOHNSEN (Read 0 times) Subj: Re: Misc questions > JG> then choking on that fragmented memory. I have 20 > JG> megs of RAM on this machine, but when you try to do > JG> something with 1.79.x, like abort an outbound call in > JG> progress, Opus can totally spaz out. > Strange, I run 1.79 on node2 with only 4 megs.. I don't believe Opus uses any of the memory beyond the 640k conventional memory barrier, so it does not matter whether you have 1mb or 64mb. The actual memory requirements for Opus 1.79, which are slightly greater than for Opus 1.73a, are detailed in the documentation. TREV. --- QM v1.30 * Origin: Sentry -- Sydney, New South Wales, Australia (3:711/401.0) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: E5D00006 Date: 05/08/97 From: STEIN-IVAR JOHNSEN Time: 09:26pm \/To: FRED BUSCH (Read 0 times) Subj: Misc questions In a message of <07 May 97>, Fred Busch (2:2464/205) writes : SJ> * Opus supports the following "baud" rates: 300, 1200, 2400, 4800, 7200, SJ> 9600, 12000, 14400, 16800, 19200, 38400, 57600. ... FB> Some here had asked to include 64000 and 115200 also (e. g. BINKLEY FB> does). I know, I'm using BT in front.. =-sijo-= --- OPMED 4.00.001/NDev.01 * Origin: El Beso Fatal (2:212/8) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: E5D00007 Date: 05/08/97 From: STEIN-IVAR JOHNSEN Time: 09:27pm \/To: FRED BUSCH (Read 0 times) Subj: General In a message of <07 May 97>, Fred Busch (2:2464/205) writes : FB> Cool. What value is added regarding the filebase of v1.79? Sorry, can't answer that since I'm not the one prog'in Opus.. But in the feature-list it says..: * The files database has been overhauled and made more bullet proof. FB> Btw: FLU '1.65' reports 'version 1.60' - bug or feature? Minor bug..;-) =-sijo-= --- OPMED 4.00.001/NDev.01 * Origin: El Beso Fatal (2:212/8) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: E5D00008 Date: 05/09/97 From: MICHAEL EPLER Time: 01:03am \/To: STEIN-IVAR JOHNSEN (Read 0 times) Subj: New version of OPUS CBCS released! SJ> Is it using shorter time to Norway and Zone2 than SJ> inside your zone? It's 1:18/14 who is hatching all SJ> files into SDSOPUS.. Looks that way...... as of today nada - zip - zilch has arrived here via SDSOPUS. So.....I guess I'll be using the internet to snag these.... --- Maximus 2.02 * Origin: DelaMarPenn MicroNet -+- Newark, Delaware (1:150/115) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: E5D00009 Date: 05/09/97 From: MICHAEL EPLER Time: 01:10am \/To: JOHN GIANNINI (Read 0 times) Subj: Misc questions JG> running 1.73a since 1990. But I *have* discovered the problem. it was JG> memory. See, most of the time 1.79.x works just fine JG> but sometimes - like denoted in the above log - Opus JG> spazzed out. Not only did it do weird stuff like the JG> I discovered if I rebooted when stuff like this happened, everything was JG> fine again. The problem apparently has to do with Opus JG> fragmenting memory, then choking on that fragmented JG> memory. I have 20 megs of RAM on this machine, but JG> when you try to do something with 1.79.x, like abort an JG> outbound call in progress, Opus can totally spaz out. Are you sure it is OPUS that is fragmenting your lower conventional memory (under 640 k) and not something else? It is almost 99.something that the problem doesn't care if you have 4, 8, 20 or 32 megs of ram on your machine. What kind of watchdog security program (if any) do you use with doors, including things like SX, BW or O'QWKer? If you don't use one, look for something else that is not properly releasing the memory. I'm not saying it couldn't be the new opus, but when I had a similar problem 3 or 4 years ago updating an SX door release, it was an old watchdog program used in the drop file, not opus or sx, that actually was causing the "fragmentation" problem. There was still enough total memory free, but alas the largest block was not big enough to load sx. SX worked in local mode. A reboot of course resolved the problem. So did killing the watchdog program. Sometimes when you have working sections of your bbs that have been around for awhile, a problem only appears when the new release nudges the system in a new way. --- Maximus 2.02 * Origin: DelaMarPenn MicroNet -+- Newark, Delaware (1:150/115) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: E5D00010 Date: 05/09/97 From: MICHAEL EPLER Time: 01:35am \/To: CHRISTOPHER BAKER (Read 0 times) Subj: Opus 1.79 files CB> have been hatched into SDSOPUS. CB> CB> i have a new link thru George Peace since the R18 route died. CB> please advise if they show up out there. CB> thanks. CB> I will check yet again with my net uplinks since it has been a week...... but as of right now, haven't seen any of them yet. --- Maximus 2.02 * Origin: DelaMarPenn MicroNet -+- Newark, Delaware (1:150/115) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: E5E00000 Date: 05/09/97 From: JAMES WALTON Time: 01:58am \/To: MARTIN FOSTER (Read 0 times) Subj: Re: The new Opus MF> Never having tried Opus before, I thought I'd have a look at the new MF> release. After what appeared to be a successfull installation, I have an MF> immediate problem ..... Opus can't get an "OK" from the modem. I've MF> obviously done something wrong but after numerous twiddles 'n tweeks, I MF> can't imagine what the problem is. Ideas anyone? Among others, make sure Opus knows which serial port you are using. Then check your fossil to make sure the send and receive buffers are set large enough. I run BNU and found that the faster the machine, the larger I had to make the buffers. (I've run Opus 1.73a on a 286, a 386 and a 486 and that was the only adjustment I had to make between machines.) You may also wish to activate the "Slow Modem" line in the control file. I will not bother sending you the init string for my modem since it probably won't work for you. (I found out the hard way that I can't swap various modems in and out without some work.) I haven't had the time to look at 1.79, but I hope it will be painless. I hope this helped a bit. --- Via Silver Xpress V4.00 SW12427 * Origin: Up In James' Attic (1:129/260)