| delorie.com/archives/browse.cgi | search |
| Xref: | news-dnh.mv.net comp.os.msdos.djgpp:2811 |
| Path: | news-dnh.mv.net!mv!news.sprintlink.net!nwnews.wa.com!uw-coco!uw-beaver!newsfeed.rice.edu!rice!news!sandmann |
| From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Re: Long filenames? |
| Date: | Tue, 24 Oct 1995 23:20:57 CDT |
| Organization: | Rice University, Houston, Texas |
| Lines: | 6 |
| References: | <46dkvv$79o AT dante DOT linknet DOT it> <46h354$1cpq AT thebes DOT waikato DOT ac DOT nz> <DGxB95 DOT JBw AT argo DOT net> <308c6e35 DOT sandmann AT clio DOT rice DOT edu> <DGz3q7 DOT MD0 AT cfanews DOT harvard DOT edu> |
| Reply-To: | sandmann AT clio DOT rice DOT edu |
| Nntp-Posting-Host: | clio.rice.edu |
| To: | djgpp AT sun DOT soe DOT clarkson DOT edu |
| Dj-Gateway: | from newsgroup comp.os.msdos.djgpp |
> What about OS/2 (HPFS) long file names? Can a DOS program get at those? I don't know of any way to do this. If someone wrote a device driver for OS/2 DOS sessions which would handle the LFN API, it would work work with the V2 LFN support code. I have considered writting a DOS TSR which would provide this in the absence of Win95, but don't hold your breath.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |