Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!csc.anu.edu.au!manuel!ccadfa!prolix!dac From: dac@prolix.ccadfa.oz.au (Andrew Clayton) Newsgroups: comp.sys.amiga Subject: Re: AmigaUUCP 1.06D and V32 (9600bps) problems... Message-ID: <186e0fe4.ARN00775@prolix.ccadfa.oz.au> Date: 27 Dec 90 09:43:32 GMT References: <6502@crash.cts.com> <186a6051.ARN00669@prolix.ccadfa.oz.au> <186ab686.ARN08a7@easy.hiam><186cb910.ARN00704@prolix.ccadfa.oz.au> <186c4a0d.ARN0cc6@cbmami.UUCP> Reply-To: ccadfa.cc.adfa.oz.au!prolix!Dac Followup-To: comp.sys.amiga Organization: I'm not an Organization - I'm a person! Lines: 79 In article <186c4a0d.ARN0cc6@cbmami.UUCP>, Jason Goldberg writes: > In article <186cb910.ARN00704@prolix.ccadfa.oz.au>, Andrew Clayton writes: > (Sorry to post but he can't send/recieve mail...) > > > > On the seemingly silly suggestion that this 'problem' with UUCP > > was only recently being seen with 68030 owners, I reverted to > > 68000 (7.14Mhz) mode, and proceeded to get my mail to RAM:, at > > 9600, without a hitch. > I can't believe you thought my suggestion was silly ;-) Cruelty is my business. :^) > Actually I mentioned that all of us reporting the problem had > 68030's, only because people kept sending me mail saying maybe > our CPU's were too slow. I never thought that, the 68030 could > be the cause. I too was of the opinion that perhaps the 68000 could have been a tad slow for 9600, but I consider that there is no way that a 68030 at 1100% plain Jane Amy speeds can 'lose' data from the serial port. > So the next question is, do you run SetCPU? What version > and options do you use? It could be that we both have some type > of cache set up that UUCP doesn't like. Great minds think alike. I had a brainstorm whilst waiting for 7.00pm (+10GMT) to come around so that I could pick up my mail. I thought 'Hey, maybe the CACHE and BURST modes on my 68030 are doing something funny with uucico?' So I dutifully reverted my mail procedure to point the spool to HD, and to call SetCPU to turn off the Cache and Burst modes, and then call uucico. Worked like a charm! Perfmon running at the same time [who said multitasking wasn't useful] showed the the CPU resource was *almost* flatlined, prolly around 5-10% free CPU. There were a few 'sequence' errors in the transmission, but I got my mail packets without uucico crapping out, so I'm convinced that we have the solution to our problem. I hope that Matt gets the information [I would mail him, but I can't use mail :-(] and places a warning in his release of 1.07D, stating that CACHE and BURST mode *could* affect uucico operation on Amiga's that use 68030's. > Incedently, I have a 2091 controller with SCSI harddrives and have the > same problem of no 9600 V.32 UUCP transfers that you have. I can transfer > to the same site/modem via 9600 Z-Modem or 2400 via UUCP. So I don't think > your problem is related to the HardDrive, I have also tried putting the > uuspool: in ram to no avail. This makes sense if it's the 68030 cache problem. > I am thinking of getting UUCPPlus and seeing > if that works, also I have heard rumors that UUCP1.07 is due out in > January. I'm pretty limited in my ability to get new programs via the net. Only if they go through comp.binaries.amiga. Since that's been dead for months, it's not gonna happen soon, eh! :-/ > GoodLuck, I had my fair share of luck today. I hope this solution works for you too. > Jason Goldberg UUCP: ucsd!serene!cbmami!jason Dac -- _l _ _ // Andrew Clayton. Canberra, Australia. I Post . (_](_l(_ \X/ ccadfa.cc.adfa.oz.au!prolix!dac . . I am. -------- I cannot send or recieve mail to or from sites outside of Australia.