Re: What is the reason for this?
- Posted by DB James <larch at adelphia.net> Aug 17, 2005
- 480 views
Elliott S. de Andrade wrote: > > >From: DB James <guest at RapidEuphoria.com> > >Reply-To: EUforum at topica.com > >To: EUforum at topica.com > >Subject: Re: What is the reason for this? > >Date: Tue, 16 Aug 2005 13:49:39 -0700 > > > >posted by: DB James <larch at adelphia.net> > > > >I have found a way to create long filenames from an Eu ".ex" file, but > >(there seems always to be a "but") it uses the double command of: > >system(cmd /c fsutil file createnew "&dQuote&longFullPath&dQuotes, 2) > > > > fsutil is its own program that exists in C:\Windows\System32 (or > C:\WinNT\System32); you do not need to call cmd. > > >This works and bypasses the emulated DOS restriction on long file names, > >but it insists on returning a message to stdout or stderr, anyway, to the > >screen. It doesn't help to use the quiet command to cmd.exe, which is /q. > > > > Try system("fsutil file createnew "&dQuote&longFullPath&dQuote&" 20 > nul", > 2) > > >Drat! I don't want that message from fsutil. Meanwhile I am wandering the > >corridors of Ralf Brown's list like a wraith lost in Colossal Cave, and > >trying other tricks.... > > > >--Quark > > > > ~[ WingZone ]~ > <a href="http://wingzone.tripod.com/">http://wingzone.tripod.com/</a> > Hi Elliot, Did you try that on your machine? You were right about skipping the cmd /q /c part, this worked to create the file: system("fsutil file createnew "&dQ&fullPath&dQ&" 0 > nul",2) However, it still proudly announced to the screen that it had done what it was asked to do. Thanks for the reply, it helped. --Quark