Date:         Mon, 6 May 2002 21:53:41 -0700
Reply-To:     maxsfolks <maxsfolks@EMAIL.MSN.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         maxsfolks <maxsfolks@EMAIL.MSN.COM>
Organization: 24hoursupport.com
Subject:      Re: x commands on WinXP

John,

Having just moved to XP at work I'm getting reacquainted with all my
programs.  Quite a few use x commands to create lists of files to streamline
data processing.  So far so good.  The old programs that worked under NT
seem to run normally under XP Pro.

Bill McKirgan



"Lex jansen" <lex@lex-jansen.demon nl> wrote in message
news:ud5v8hpkg01pcc@corp.supernews.com...
> John,
>
> Although many commands in Win2K Command Prompt resemble the old DOS
> commands, it is in fact not DOS.
> It is a native Win2K command scripting language (also known as "Shell
> Scripting") which is part of the operating system.
> I have no WinXP here, but I would expect that the usual "DOS" commands
still
> work.
>
> There is however a tendency towards WSH (Windows Script Host) that starts
> replacing Windows Shell Scripting.
> So I think it is not a bad idea to start looking into WSH.
> You will find out that WSH gives you much more possibilities in scripting.
>
> Lex Jansen
>
> "John Gerstle" <JGerstle@SW.UA.EDU> wrote in message
> news:200205031830.NAA26888@bama.ua.edu...
> > Yeah, I've seen the DOS prompt shortcut too and indeed, it works.
> > The thing is that Win2K and WinXP are not dependent upon DOS
> > even being installed, unlike the older versions of Windows.  That's
> > why I'm wondering.  At some point, 16-bit programs (i.e. DOS-
> > based programs and commands) will not be supported by
> > Microsoft.  And I think that WinXP is the beginning of the phase-
> > out.  I would bet that the next generations of WinXP will not have
> > DOS installed, and so these DOS-based programs and commands
> > will not work.  And so, that's why I was asking the question.
> > Thanks,
> > John
> >
> > > Hi John,
> > >   I don't know about WinXP, but I've used the X command to run some
> > >   DOS
> > > commands on a Win2K machine, and it worked okay.  I don't know if DOS
> > > had to be installed separately, though- I've been able to get to a DOS
> > > window ("Command Prompt") since the machine was delivered, as it came
> > > with it already there.
> > >    Nancy
> > >
> > > Nancy Brucken
> > > Clinical/Regulatory Informatics
> > > Pfizer Global Research & Development, Ann Arbor
> > > (734) 622-5767
> > > E-mail address:  Nancy.Brucken@pfizer.com
> > >
> > >
> > > -----Original Message-----
> > > From: John Gerstle [mailto:JGerstle@SW.UA.EDU]
> > > Sent: Friday, May 03, 2002 12:29 PM
> > > To: SAS-L@LISTSERV.UGA.EDU
> > > Subject: x commands on WinXP
> > >
> > >
> > > I'm curious about this...
> > >
> > > We all know that WinXP (as was Win2K) was written without the
> > > use of the MS-DOS understructure to take care of a lot of those
> > > pecky Winodws problems (memory leaks, blue screen of death,
> > > etc).  Now, I've played with WinXP very briefly twice.  I know that
> > > MS-DOS can be installed on it, as a separate program, and that many
> > > DOS-based programs will work.  My question is this, for anyone useing
> > > SAS 8.* on WinXP, have you run into any problems using the x command
> > > to run operating system commands such as this one:
> > >
> > > x dir D:\DATA\ /b > d:\data\datalist.lst  ;
> > >
> > >
> > > This command reads in the filenames in D:\Data into a file to use to
> > > read in these files in a data step (using filename etc...).  I would
> > > like to know if this code will continue to work in the WinXP arena.
> > > Very soon we'll be getting new desktops and they will have WinXP on
> > > them.  We could alwyas try the dual bootup with Win2K, but I'd like to
> > > know if we need to do this.
> > >
> > > Thanks for any input and opinions,
> > > John Gerstle
> > >
> > >
> > >
> > >
> > >
> > > John Gerstle, M.S.
> > > Program Analyst, Sr.
> > > Applied Gerontology Program
> > > University of Alabama
>
>