mja@whuts.ATT.COM (AMMANN) (11/16/88)
More questions from the chap with the troublesome 6386. I've installed the MKS toolkit on my 6386. Unfortunately vi seems to be having some problems. If I try to delete a line the system hangs, complete with keyboard lockup. I'm booting this system off a floppy because my main hard disk is mounted as a Unix(tm) disk. I think maybe that has some thing to do with the problem. Like maybe it's trying to store the delete buffer in some strange place. so any assistance would be appreciated. please reply to troy newberry at att!whuts!troy
starr@shuxd.UUCP (Michael L. Starr) (11/16/88)
In article <5054@whuts.ATT.COM> mja@whuts.ATT.COM (AMMANN) writes: >I've installed the MKS toolkit on my 6386. Unfortunately vi seems >to be having some problems. If I try to delete a line the system >hangs, complete with keyboard lockup. >I'm booting this system off a floppy because my main hard disk >is mounted as a Unix(tm) disk. I think maybe that has some thing to >do with the problem. Like maybe it's trying to store the delete buffer >in some strange place. I run MKS toolkit on my 6386, too. I have most of my files on my C: drive and when I edit files on my C: drive, it works fine. I experenced problems when I would attempt to use vi on other drives, until I created a tmp directory at the root level on each drive. -- __/\__ ******************** __/\__ | starr@shuxd.att.com \ / * Michael L. Starr * \ / | att!shuxd!starr |/\| ******************** |/\| | starr%shuxd@att.arpa
jxh@cup.portal.com (Jim - Hickstein) (11/17/88)
I have trouble with MKS vi, too. I'm on a PS/2-80 under OS/2 1.05, in the DOS box (3x, but says version 10 to programs which ask!). It simply hangs when I try it. Thereafter, the DOS box is unusable until system reboot. Since the other problem mentioned is also a 386, I wonder if there's something related going on here. -Jim Hickstein jxh@cup.portal.com ...!sun!portal!cup.portal.com!jxh
rdo031@tijc02.UUCP (Rick Odle ) (11/18/88)
> I run MKS toolkit on my 6386, too. I have most of my files on my C: drive > and when I edit files on my C: drive, it works fine. I experenced > problems when I would attempt to use vi on other drives, until I created > a tmp directory at the root level on each drive. You need to do a "set tmpdir=c:/tmp" and a "set rootdir=c:/". rick -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- rick odle (615) 461-2371 texas instruments industrial systems division __ . _ /__, johnson city, tn 37601 ( ( (__ / ( uucp: mcnc!rti!tijc02!rdo031 faster uucp: mcnc!convex!smu!ti-csl!tijc02!rdo031 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
keithe@tekgvs.GVS.TEK.COM (Keith Ericson) (11/22/88)
In article <182@shuxd.UUCP> starr@shuxd.UUCP (Michael L. Starr) writes: > >I run MKS toolkit on my 6386, too. I have most of my files on my C: drive >and when I edit files on my C: drive, it works fine. I experenced >problems when I would attempt to use vi on other drives, until I created >a tmp directory at the root level on each drive. This isn't necessary. You can set an environment variable to point to the ONE temporary directory to use for temporary files. (I use a ramdisk.) c:/dos/join h: c:/tmp [join the ramdisk drive to C: as /tmp] set TMPDIR=c:tmp [let vi use it] keith