drew@cgou01.dec.com (Steve Drew) (05/04/87)
-> Well, I ran my decision to by a Pal Jr. past the wife today and she's still
-> speaking to me (civilly, to boot! :-) ), so I've been dragging out and
-> dusting off all those goodies that just don't fit in my current setup. I
-> got out the copy of the modified shell (V 2.05M), applied the one fix I
-> had seen come over the net (change _devtab[] to *_devtab) and "made" (maked?)
-> it. I'm using Manx 3.4a, got no compiler or link errors but when I run it,
-> all sorts of strange alternate character set stuff comes out on the screen
-> and I can't get it under control. I've spent no time at all trying to
-> investigate the problem, since I suspect that a message or two slipped by
-> me when I wasn't looking. Got any suggestions for a lazy guy? Thanks.
->
-> Mark
Adding a fflush(stdout); to main() just after the couple of lines that
set the stdout stream to buffered ( stdout->_buflen = STDBUF; ) in the
init() routine is the easiest way to fix this. Or you can comment out
the couple of places where I tamper with the stdout buffer. main.c &
Rawconsole.c. And just use the now featured console buffering in 3.4a.
(which is what I have done)
I've made a couple of other minor changes for 3.4a to handle the new
fexecv code. (which checks the amigados PATH but it forces the system
requester up as it searches each disk that's not inserted. This is unlike
how amigados handles this. So I turn of system requesters before calling
fexecv).
Steve Drew at ENET: CGFSV1::DREW
ARPA: drew%cfgsv1.dec.com@decwrl.dec.com
USENET: {decvax!decwrl}!cgfsv1.dec.com!drew RMF%ADMIN@UNCAEDU.BITnet (05/29/87)
From: RMF%ADMIN%UNCAEDU.BITNET@wiscvm.wisc.edu
I recently installed the Insider!(tm) in my machine and have come
across a weird qurk. If I have AmigaD*s Run command in RAM
and '$ run program' the program will start but I will be left
at a NewCLI. If I issue a EndCLI shell comes back. If I
leave Run on DF0: and '$ Run program' everything works fine.
This is really odd. Before I had extra ram, I always had
Run and Execute in ram. Does Run have a problem with fast
ram?
While I'm here, it seems odd to me that when you say help
under Shell it says run is a valid command, usally this means
its built into Shell, however Shell always requires the
AmigaD*s Run command, sigh.
/Russ
-----
Russell M Forster
DECnet: RMF @ { Admin | Comus | Stasis | Ins }
BITnet: RForster @ UncaEdu.BITnet
ARPA: Oc.Russ @ CU20B.Columbia.Edu
USEnet: siesmo!calgary!vaxa!forster
-------drew@cgou01.dec.com (Steve Drew) (06/01/87)
> RMF%ADMIN%UNCAEDU.BITNET@wiscvm.wisc.edu > > I recently installed the Insider!(tm) in my machine and have come > across a weird qurk. If I have AmigaD*s Run command in RAM > and '$ run program' the program will start but I will be left > at a NewCLI. If I issue a EndCLI shell comes back. If I > leave Run on DF0: and '$ Run program' everything works fine. > > This is really odd. Before I had extra ram, I always had > Run and Execute in ram. Does Run have a problem with fast > ram? > > While I'm here, it seems odd to me that when you say help > under Shell it says run is a valid command, usally this means > its built into Shell, however Shell always requires the > AmigaD*s Run command, sigh. > > /Russ Russ I don't know why you didnt mail me directly, (like usual). Anyway since I happen to know that since you got your extra memory, you are running VDK: software. First thing I would do is to try it with out that. I heard someone mention that with VDK: anything run under shell 2.05m causes what looks like a newcli. This could be something VDK: is doing or maybe problems with the old fexec (3.02a) code & VDK:. If all else fails just wait for shell 2.06M that I'll be sending out it a couple of days to .sources/binaries. Since the new fexec code under manx 3.40a works so much better. Re: shell run command: As documented Russ :-) the run command simple calls AmigaDos Run command after checking the shell $_path first and allowing redirection. /Steve.