Re: Can't compile DOS program with long file name
- Posted by Vincent <darkvincentdude at yahoo.com> Apr 01, 2006
- 571 views
Robert Craig wrote: > What I could do is either: > 1. start using your DOS long file name routines > or > 2. have one translator for both DOS and Windows, > i.e. extend ecw.exe to handle DOS translations as well > > I'd prefer #2, since it would eliminate an executable that I have > to build, and it's probably quite easy to do. I'll look into it. > Rob wait just a second here. "ecw.exe" is a Windows NT executable right? Windows executables do not run in pure DOS environments. I use DOS Euphoria and the DOS translator in pure DOS 6.22 on my Pentium 133 MHz machine. Doing this would mean I can no longer use the translator in pure DOS. Extending "ec.exe" might work since DOS exectuables run with DOS emulation on Windows XP and older. However I dont know if Windows Vista will support DOS programs. I know for a fact that Microsoft will be removing the WOW 16 bit application subsystem in Windows Vista. What that means is you wont be able to run 16 bit programs in Vista. I believe ntvdm.exe is another piece of this and if they remove it we will not be able to run the DOS Euphoria interpreter, binder, backend, or translator as well. I can delete ntvdm.exe and Windows will recreate a copy automatically however I can make the DOS programs fail to run for a few moments. If its completely removed in Vista it wont ever work. So what I'm saying is *please* do not do this. Just make the two seperate translator executables like you always have. I think this is to big of a risk to chance. Regards, Vincent