Sender: root AT delorie DOT com Message-ID: <389196AB.75F4F711@inti.gov.ar> Date: Fri, 28 Jan 2000 10:16:27 -0300 From: salvador Organization: INTI X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.38 i686) X-Accept-Language: es-AR, en, es MIME-Version: 1.0 To: djgpp AT delorie DOT com Subject: Re: Rhide, NT and LFN - some news References: <38909F3F DOT CA060487 AT mailbox DOT swipnet DOT se> <3891618F DOT 90CC4B18 AT mdh DOT se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp AT delorie DOT com Dan Levin wrote: > Dan Levin wrote: > > > > Hello ! > > > > I've been trying to run Rhide on NT together with Wojciech Galazka 's > > fix to enable LFN under NT. It works as far as LFN is concerned - but > > I ran into another problem.. (sigh !) When I create new source or > > project files in Rhide and then later save them, they seem to be saved > > with LFN all right - but the filenames appear in UPPER CASE !!! So > > when I try to open an already saved project, it does not appear in the > > "*.gpr" listbox ! And if I try to compile a source file with an > > upper-case-name, Rhide tells me: "I do not know how to create > > MYFILE.OBJ of MYFILE.C" ! > > I've been doing some continued work on this problem. I've found that > everything works great - IF YOU STICK TO LFN ALL THE TIME when you > create files. As soon as you name a file according to the classical DOS > 8.3 format in Rhide, you end up with a filename in UPPERCASE. > Consequently these files won't show up in the "Project-Open" file list > box, or in "File-Open" list box - and they won't be compiled either. It > would be wonderful if this restriction could be overcome, cause then > Rhide would work exactly as in Win9x !(with Wojciech Galazka's fix added > though) > > /Dan Levin, Eskilstuna, Sweden 1) What's that "fix"? a TSR or something like that? 2) I think the problem is in the "fix". RHIDE doesn't make any funky thing with names, just uses djgpp's libc. As djgpp's libc works very well under W9x I think this "fix" behaves different than W9x LFN API and that's the source of the problems. I know the Windows Explorer does some very stupid things when displaying file names, so perhaps Galazka's program is doing similar things. There are also some processing in libc and perhaps it generates the problem, but again: it only means the "fix" doesn't behave like Win9x. SET -- Salvador Eduardo Tropea (SET). (Electronics Engineer) Visit my home page: http://welcome.to/SetSoft or http://www.geocities.com/SiliconValley/Vista/6552/ Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org set AT ieee DOT org set-soft AT bigfoot DOT com Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013