1. Re: FFFFFFFF Crash
- Posted by Robert Craig <rds at EMAIL.MSN.COM>
Jan 26, 1999
-
Last edited Jan 27, 1999
With the help of Pete Eberlein, Grape Vine and a few others who
sent me debug.log files, I think we may now have a solution.
On the vast majority of machines there is absolutely no problem
running exw.exe. However for a few people, their debug.log files clearly
showed that the first few hundred bytes of the code segment of
exw.exe was "garbage". This was true right away, before any
code was executed inside exw.exe. It's apparently an operating
system bug.
After I inserted some dummy code into those first few hundred
bytes, Pete reports that exw now works for him. I will leave this
filler code in there, even though most people don't need it.
Grape Vine has now corrected his system, and exw.exe is working
fine for him. After talking to Microsoft, he believes it has something
to do with an old update for the windows 95 kernel. He says:
"The updated kernel(95B.1) with the windows plus(95A) along with an original
install of 95B.0 causes a weird memory problem." I guess
you can ask him for the details.
The people experiencing a crash of exw should try:
http://members.wbs.net/homepages/f/i/l/fileseu/exw.zip (80K)
It's a new non-debug build of the PD exw.exe that should work around
this O/S problem. The fix will also be included in 2.1 beta in a few weeks.
You might also try to correct your system. I suspect exw will not be
the only program affected.
Regards,
Rob Craig
Rapid Deployment Software
http://members.aol.com/FilesEu/
