bscott@nyx.UUCP (Ben Scott) (07/03/90)
In article <tracy.0021@taishan.cinnet.com> tracy@taishan.cinnet.com (Tracy S. Schuhwerk) writes: >Has anyone successfully used the latest version of UUCP (1.06) on the >3000 yet? I just tried and failed miserably. Seems like it wants to >Guru the machine on a write to the HD (THE GURU WILL NEVER DIE!). I >was running 1.03 with limited success (I had to run it under KS 1.3) >but 1.06 dies under both KS 2.0 and 1.3! My own UUCP node is having some severe problems as well. It started out perfect and was running fine for days, then it began to give error messages (in the logfile) and not transfer anything during sessions, and finally it's just not transmitting or receiving (though it does connect succesfully). All this happened very shortly after (but not right as) I switched to v1.06D from 1.05... I too had a HD crash during a UUCP session as well, but I'm not sure that was at all related. For a while I was using a hybrid, the uucico and uuname of v1.05 and the rest from 1.06 due to a warning from a friend, but neither a pure 1.06 nor (to date) reversion to 1.05 has been successful. I'm still trying a few more things (since it worked exactly once after my HD crash I'm going to re-restore it from the backup floppies and see if I can get it running again) and I hope to get it running again eventually. BTW: I'm running a 3 meg, KS1.3 A-500 with an A-590 and a super Agnus. . <<<<Infinite K>>>> -- .---------------------------------------------------------------------------. |Ben Scott, professional goof-off and consultant at The Raster Image, Denver| |Amiga UUCP node domain: bscott@vila.denver.co.us Else: bscott@nyx.cs.du.edu| |FIDO point address 1:104/421.2, or call the Arvada 68K BBS at (303)424-9831| |"Don't embarrass us..." "Have I ever?" - Buckaroo Banzai | *AMIGA POWER* | `---------------------------------------------------------------------------'
danny@whitwiz.lonestar.org (Danny White) (07/03/90)
>In article <1414@nyx.UUCP> bscott@nyx.UUCP (Ben Scott) writes: > >My own UUCP node is having some severe problems as well. It started out I have been running UUCP 1.06 for a couple of months now and have hadd no problems with it. (I am running it on an a500 with a 590 but no super Agnus.) I would suggest that you do restore from the backups and make sure that you have your stack size set to a large number (such as 15000) I had problems with 1.06 until I set my stack. (NOTE: this may not be a problem but I did get things to settle down by setting my stack) Also, you might want to check out your modem and phone lines. -- UUCP: ...!texbell!whitwiz!danny SNAIL:Danny White 1429 Glacier Dr. INTERNET: danny@whitwiz.lonestar.org Plano, TX 75023 ========================================================================== "In order to make an apple pie from scratch, you must first create the universe." -- Carl Sagan, Cosmos
caw@miroc.Chi.IL.US (Christopher A. Wichura) (07/04/90)
>In article <1414@nyx.UUCP> bscott@nyx.UUCP (Ben Scott) writes: >In article <tracy.0021@taishan.cinnet.com> tracy@taishan.cinnet.com (Tracy S. Schuhwerk) writes: >>Has anyone successfully used the latest version of UUCP (1.06) on the >>3000 yet? I just tried and failed miserably. Seems like it wants to >>Guru the machine on a write to the HD (THE GURU WILL NEVER DIE!). I >>was running 1.03 with limited success (I had to run it under KS 1.3) >>but 1.06 dies under both KS 2.0 and 1.3! > > >My own UUCP node is having some severe problems as well. It started out >perfect and was running fine for days, then it began to give error messages >(in the logfile) and not transfer anything during sessions, and finally >it's just not transmitting or receiving (though it does connect succesfully). >All this happened very shortly after (but not right as) I switched to v1.06D >from 1.05... I too had a HD crash during a UUCP session as well, but I'm not >sure that was at all related. UUCP v1.06D does, in fact, crash on the 3000. It is after it receives a file or when it is hanging up after a send only. However, I got uucico to work on my system by recompiling it with Lattice 5.05 and haven't had any problems since (guess Matt has a bug in DICE, eh?). -=> CAW /////////////////////////////////////\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ Christopher A. Wichura caw@miroc.chi.il.us (my amiga) u12401@uicvm.uic.edu (my school account) Please! Do not send mail to my school account unless mail to miroc bounces. I often do not check uicvm.uic.edu for periods in excess of a week. \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\//////////////////////////////////////
hclausen@adspdk.CBMNET (Henrik Clausen) (07/04/90)
>In article <tracy.0021@taishan.cinnet.com> tracy@taishan.cinnet.com (Tracy S. Schuhwerk) writes: >>Has anyone successfully used the latest version of UUCP (1.06) on the >>3000 yet? I just tried and failed miserably. Seems like it wants to >>Guru the machine on a write to the HD (THE GURU WILL NEVER DIE!). I >>was running 1.03 with limited success (I had to run it under KS 1.3) >>but 1.06 dies under both KS 2.0 and 1.3! Solution: run NoFastMem before running uucico (or uupoll). If you have only outgoing files, you can do it under 2.0, else do it under 1.3 - so do it under 1.3. I'm doing some banging on Matt to get him to find the bug. It's a Guru 00000006, a CHK instruction, seems uucico doesn't like the full 32 bit address space of the A3000. Perhaps a DICE problem? Dunno about the ram disk, that's trickier. This is hardly .tech stuff, btw. -Henrik -- | Henrik Clausen, Graffiti Data (Fido: 2:230/22.33) | | ...{pyramid|rutgers}!cbmvax!cbmehq!adspdk!hclausen | \_______________AmigaDOS: Amiga's Divine Operating System________________/
dillon@overload.UUCP (Matthew Dillon) (07/10/90)
>In article <danny.2035@whitwiz.lonestar.org> danny@whitwiz.lonestar.org (Danny White) writes: >>In article <1414@nyx.UUCP> bscott@nyx.UUCP (Ben Scott) writes: >> ... There are indeed problems running uucico on the A3000 (UUCP 1.06D). I am attempting to find the bug (several of you are helping me trace it, thanks!). Not having an A3000 (yet) makes it difficult, though. There are apparently two bugs. One Darrin Hyrup has traced to somewhere around the close-serial-device/open-serial-device calls used to terminate the call at the end. Another bug apparently occurs just after receiving a file. I suspect both bugs may be a manifestation of a memory mash somewhere. In anycase, those of you with A3000's should avoid using UUCP 1.06D until I can find the problem! Wish somebody had a debugger on his A3000 with UUCP 1.06D setup, the uucico executable does have symbols in it. The bugs *might* be due to a bug in DICE, but there is as much evidence for as against that so at the moment it is pure conjecture. As far as the CHK instruction goes, DICE never generates it. I've verified this by using Lattice's OMD on all the uucico object files. -Matt -- Matthew Dillon dillon@Overload.Berkeley.CA.US 891 Regal Rd. uunet.uu.net!overload!dillon Berkeley, Ca. 94708 USA