Hi, On Mon, Nov 4, 2013 at 7:38 AM, Miguel Garza <garz...@gmail.com> wrote: > > I tried putting "INSTALL=c:\apps\lbacac~1\bin\LBACACHE.COM" in my config.sys > file and I get an error: > > STAK nest!? otherss = [a bunch of numbers and letters] [Repeats several > times]Bad or missing Command Interpreter: command.com /P /E:256 > Enter the full shell Command line: [blinking cursor] > > Which I don't know how to do so I just turned off the computer. On reboot > Windows ran an automatic chkdsk on my thumbdrive and fixed two files.
I never use INSTALL (in CONFIG.SYS). In fact, I'm not sure I even fully understand it. AFAIK, it's only for TSRs for saving a few precious bytes of environment (low) RAM, so I don't bother and just "install" manually in AUTOEXEC. I have no idea if you can still unload such TSRs later (by design or due to bugs). http://help.fdos.org/en/hhstndrd/cnfigsys/install.htm DEVICE is usually (IIRC) only for .SYS files. So here, you would use DEVICE=C:\FDOS\BIN\XMGR.SYS /N128 (since UIDE almost always requires it), DEVICE=C:\FDOS\BIN\UIDE.SYS /E /N2, and then (if you don't care what drive the RAM disk is, although Eric's FINDDISK.COM can help find it later) DEVICE=C:\FDOS\BIN\RDISK.COM /S20 (or whatever). Okay, so I don't remember proper parameters, lemme (partially) quote my CONFIG.SYS: DEVICE=C:\UTILS\XMGR.SYS /N128 DEVICEHIGH=C:\UTILS\UIDE.SYS /S127 /D:FDCD000 /H SHELL=C:\FDOS\COMMAND.COM C:\FDOS /E:1024 /P REM (this is from AUTOEXEC.BAT, I guess I specifically wanted G:\ here, heh) set RAMDRIVE=g lh rdisk /s150 /:%RAMDRIVE% md %RAMDRIVE%:\temp for %%a in (TEMP TMP TMPDIR) do set %%a=%RAMDRIVE%:\temp > I'm a bit confused by the Ramdrive thing. I mean, I get the basic concept. I > take it I would be running Zim "inside" the ramdisk. But would I be able to > access files on "C:" (my thumbdrive) and automatically save those same files > to C: when I choose to do so, without having to manually write weird > directory commands? If not, sounds like too much hassle. The RAM drive is just a normal (e.g. FAT16) drive that happens to be on (fast) RAM instead of (slow) hard drives or floppies. 99% of DOS utilities don't know (and don't need to know) the difference. Note that this almost always uses XMS (or similar), too, so again, you need XMGR (or HIMEMX or whatever) loaded. You don't have to install VIM nor run it from RAM disk at all. Indeed it won't automatically save anything permanently there as RAM is wiped upon reboot. The point is that anything you do run atop there is much much faster. So it's just a fast, but temporary, work directory. You do whatever you need to do, save the results, then copy (or move) that to more permanent storage (e.g. hard disk) later. > I will try the other cache programs...not sure if the Ramdrive thing is > worth it...I want to be able to use Vim like I would any other editor. Will > a Ramdrive let me do that? Yes, VIM should work fine as normal. It's just another drive to VIM, nothing special. > Don't want to use PuppyLinux...don't want to use a full-blown GUI... I suspected as much, just mentioning for completeness. It's probably more user friendly and does things that FreeDOS doesn't (or can't). And vice versa, of course. :-) BTW, IIRC there is a "nox" option to not load X11 if you don't want or need it for that particular session. > I tried deleting that other file from the Vim.exe directory...makes no > difference... Okay. So you're sure you're using CWSDPMI r7? > The built-in file browser in Vim that I'm referring to is netrw. It's a > plugin, but it ships with Vim 7, is their default browser for opening files, > deleting them, traversing directories, etc. If you want to get to netrw in > Vim, in Normal mode you type ":e ." without the quotes, for example. Okay, I just haven't used VIM (nor even VILE) enough to know every command and extension, plugin, etc. I know GNU Emacs has dired for things like this, but normally I don't need it. > The funny thing is other programs in FDOS on my thumbdrive have no problem > traversing directories quickly. Like if I want to open a file from within > EDIT, or Microsoft Word 5.5, or any number of other programs. Heck, if I run > Necromancer's DOS Navigator, it has no problem being a quick file browser... Dunno, but it shouldn't be slow without good reason, so it must be some configuration issue. > Yeah, the reason I settled on Vim is because I wanted something quick and > easy like EDIT but that could reflow text (e.g. wordwrap without carriage > return symbols) like Notepad or Microsoft Word 5.5. It should be fast, in theory, but apparently your setup is doing something weird. Well, it's definitely not DOS' fault. Believe it or not, even without modern features, it's still pretty quick. Maybe it's VIM's fault, but I doubt it. It's probably something really trivial (like what Eric hinted at). ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
