Try as I might, I cannot get FastEcho 4.31 DPMI files
to work. All it does is hang, and will not close. I
have the RTM environment set, and have the
DPMI16bi.ovl and rtm.exe in the same directory as the
fastec16.exe (and the other) files.
I am using Windows XP on a PII/400Mhz machine with 256M of memory.
I am calling fastecho from a batch file (at least THAT is working)
Any help would be appreciated.
DPMI problems with WIN XP are reported and have been the subject of a fair amount of discussion and frustration with PowerBASIC users in a number of threads in the PowerBASIC support forums. I realize this is not a programming issue. But you might be able to learn a lot about WIN XP compatibility issues about DMPI and many other aggravations when using WIN XP from visiting the PB site at www.powerbasic.com and looking into the forums there. A search engine at the site can cover the whole current and all the archives there pretty quickly to assist you. Bob Zale and crew have done an outstanding job at offering really wonderful tools for programming in the WIN world for years now.
Perhaps what some of the programming folks have found and cussed and discussed
about WIN XP will help you here.
That said ....
I realize that you aren't running OS/2 or a DOS_VDM under OS/2 as I do. I also
have no experience at all at running WIN XP at all.
But I wonder about something. In OS/2 we have a utility called THESEUS which is a system and memory use analysis tool from IBM. If you run it you are able to see a horrific amount of information on the OS/2 operating system as it is being used, together with a rather complete analysis of every task and process.
Our world is sorta complicated too. My main box typically has at least 35 tasks open concurrently and typically has over seven hundred (700) file handles
open simultaneously on it 24X7 forever, the way I use it... The point being that as WIN grows better and better, it, too, has the same kind of organizational depth and complexity. It takes very good tools, sometimes, to find things like you are searching for.
One of the analysis subsets of THESEUS we can use is a complete review of every
file handle, all the paths and so on, which a given task has opened for use and
the parameters about them. In the world of OS/2, that means one can look into the whole FastEcho operation during execution and tell immediately what handle is being used for the log file(s), where they are, and so on. I might have to put a hold flag of some kind in the batch file to let me get a crack at this in
THESEUS, or something like that, but if I could suspend the process for long enough to get a look at it this way, there would be no question about what path, where, the name and so on, over this issue of any 'missing' log file here.
Again, I know nothing about WIN XP at all. But does the same kind of system analysis tool for it exist like THESEUS does for OS/2? Surely it must. And if
it does, it very likely will not be something you can just open from the WIN XP
normal operations, or at least it would be confusing to me to learn that this might be true.
I've been following this thread here silently for the duration of it. I actually use FE here at 1:117/100 as part of the Net 117 hub operation. It is run in a DOS-VDM here. The current log is over 27 Megabytes in size and is directed to a common log subdirectory in the InterMail master operation which is the focus of 1:117/100.
Just thinking out loud here and trying to help. That's all.
Sleep well; OS/2's still awake! ;)
Mike @ 1:117/3001
--- Maximus/2 3.01
* Origin: Ziplog Public Port (1:117/3001)