Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!motcsd!mcdcup!mcdchg!ddsw1!indep1!pete From: pete@indep1.UUCP (Peter Franks) Newsgroups: comp.windows.ms Subject: Re: .cshrc for MSWINDOWS? Summary: Windows runs on TOP of DOS Message-ID: <1372@indep1.UUCP> Date: 30 Nov 90 15:07:41 GMT References: Reply-To: pete@indep1.MCS.COM (Peter Franks) Followup-To: comp.windows.ms Organization: /usr/lib/news/organization Lines: 38 In article deen@romulus.rutgers.edu (Cinnamon Raisin) writes: -> -> Greetings, -> -> I have an XT, and as you might guess, very limited -> experience with windows. -> -> At a friends house, though I had a chance to play -> with it for a while on his 386. One thing I noticed -> is that when you open a DOS session in a window, it doesn't -> go through the usual new shell stuff you might expect -> as an X user. -> -> It doesn't load config.sys or autoexec.bat when you -> start a new shell the way X loads .cshrc and .login. -> -> Is this a normal thing, or did my friend set his -> windows up wrong? If this is noraml then, how -> do you run things that require drivers (eg scanner) -> in a dos window? Yes, it is normal. MS Windows is NOT an operating system (although it does do some things that operating systems do). If you recall, when your friend turned on his machine, it booted DOS - right? When it did so, it loaded config.sys and autoexec.bat. After all that was done, he typed in 'win'. That loaded MS Windows. When you invoke a DOS shell from MS Windows, all you do is run command.com. DOS is already resident, so it won't look for config.sys and/or autoexec.bat. If you want to run things (like a scanner) that require drivers, you must load the driver BEFORE you run MS Windows. -- +------------------------------------------------------------------------------+ | Peter Franks | pete@indep1.mcs.com OR pete@indep1.uucp | | NI9D | Use whichever one works | +------------------------------------------------------------------------------+