From: "John M. Aldrich" <fighteer AT cs DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Compile probs.... --ACK!! Long file name probl & win 95!!!
Date: Tue, 12 May 1998 21:29:49 -0400
Organization: Two pounds of chaos and a pinch of salt.
Lines: 31
Message-ID: <3558F78D.2D1D@cs.com>
References: <19980513011428 DOT AAB27360 AT ppp118 DOT cartsys DOT com>
NNTP-Posting-Host: ppp136.cs.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Nate Eldredge wrote:
> 
> >I may as well ask, is there any reason why DJGPP can't (in theory) include
> >its own long filename support in plain DOS?  The filenames are on the disk,
> >after all, and their format is publically known.
> 
> If this "plain DOS" is really DOS 7.0, the Windows 95 one, then LFNs will
> work from it as long as LFN=Y, and the previous poster is incorrect. Of
> course, LFN's still will not work with DOS <7, for obvious reasons.

If you Shut Down to MS-DOS through Windows 95's Start Menu, or if you
select Command Prompt Only from the Win95 boot menu, then you are
getting a no-frills version of DOS 7.0 which does not have LFN support
or any other features that Win95 tacks onto DOS.  If you type 'ver', you
still get the same "Windows 95. [Version 4.00.1111]" or whatever.

As I understand it, many of the extra "features" of DOS 7.0 are only
accessible when you are running in Windows 95 or in a Win95 DOS shell. 
If Windows is not loaded, those features are not available.

-- 
John M. Aldrich <fighteer AT cs DOT com> - ICQ UIN# 7406319

* Anything that happens, happens.
* Anything that, in happening, causes something else to happen,
  causes something else to happen.
* Anything that, in happening, causes itself to happen again, happens
  again.
* It doesn't necessarily do it in chronological order, though.
 
                                       --- Douglas Adams