Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: Sean W. Smith who wrote (4184)	12/13/1998 2:56:00 PM
From: Nazbuster	Respond to of 14778

Sean, COMSPEC usually takes care of itself, but you are right about the SHELL command. Most people have so much stuff in their AUTOEXEC.BAT that they exceed the ENVIRONMENT space for storing the values of the SET variable=value statements. Putting a SHELL statement in is the only way I know of enlarging the environment: SHELL c:\dos\command.com /e:2048 /p This defines the pathway to the command interpreter, changes the environment size to 2048 and makes the pathway permanent (/p). I like to keep a copy of command.com in the DOS directory for the rare times when I stupidly type DEL . thinking I'm in some subdirectory! I also make a directory called "root" where I copy EVERYTHING (including sytem files with the exception of the windows swap file) sitting at C:\ so I can recover easliy. I use a DOS utility called LIST from Vernon Buerg (http://www.buerg.com) which is one of those handy file manager shells. It permits easy changing of attributes for system/read-only files, copies and deletes sets of things easily as well (if you purchase the non-shareware version which I did).

To: Sean W. Smith who wrote (4184)	12/13/1998 3:03:00 PM
From: Spots	Respond to of 14778

>>Something I have done since the OS2 days is install a minimal NT Setup about 100M on the second physical and use OS/2 BM to boot off it then you have true NTFS support for recovery. Yes, I also maintain a second NT system, for exactly that reason (among others). I don't use a boot manager, though. Nothing wrong with a boot manager, but I have just never wanted to introduce the added layer of dependence. No particular reason except caution. The immediate issue at hand is having a DOS environment for those things which can't be done from NT, though, not disaster recovery. Board diagnostics and bios flashing, for instance. For disaster recovery, the second NT is by far the preferable way to go. But I do keep DOS bootable too (belt AND suspenders<g>). Spots