Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!kepler.Berkeley.EDU!me128-aw From: me128-aw@kepler.Berkeley.EDU (me128 student) Newsgroups: comp.sys.amiga Subject: Re: Microbotics Stardrive startup query Message-ID: <27023@ucbvax.BERKELEY.EDU> Date: 5 Dec 88 19:14:12 GMT References:Sender: usenet@ucbvax.BERKELEY.EDU Reply-To: me128-aw@kepler.Berkeley.EDU (me128 student) Organization: University of California, Berkeley Lines: 29 In article mp1u+@andrew.cmu.edu (Michael Portuesi) writes: >Anyhow, I'm having a small problem with my startup-sequence. The >startup-sequence on my boot disk currently looks like the following: > >the first two lines of dh0:s/startup-sequence are: > >Fastmode dh0: >Fastmode dh1: > >which put the Microbotics controller into "fastmode". Trouble is, >the Fastmode commands fail with error code 31 when executed from the >startup-sequence. They work just fine when I type them at a CLI >prompt, however. > I have a stardrive hooked up to my st225n. I use fastmode with no problems. My call is: FastMode dh0: read write Are the read and write parameters necessary? Maybe that's your problem. Or maybe you should just set Fault 32 I set the fail limit up for another reason, but I dont recall if its before or after the fastmode call. I'm not on Amy now, (sounds funny, don't it) so I can't see. I seem to recall having a similar problem. Vincent H. Lee "Demented and sad, but social" - The breakfast club (^ Yeah, I show my age by what quotes I choose, don't I)