Re: [Freedos-user] problems with OpenWatcom debugger + FreeCOM + Win98

2005-07-09 Thread Brolin
Michael Devore wrote: WD is plain old goofy. It has had a slightly unstable reputation under DOS for over ten years. You could be seeing nothing more than the OS memory image having different byte values at a particular location(s), or slightly varied free memory values, or an internal

Re: [Freedos-user] problems with OpenWatcom debugger + FreeCOM + Win98

2005-07-09 Thread Michael Devore
At 03:29 PM 7/9/2005 -0800, Brolin wrote: Michael Devore wrote: WD is plain old goofy. It has had a slightly unstable reputation under DOS for over ten years. You could be seeing nothing more than the OS memory image having different byte values at a particular location(s), or slightly

Re: [Freedos-user] problems with OpenWatcom debugger + FreeCOM + Win98

2005-07-09 Thread Bernd Blaauw
Brolin schreef: I think maybe you misunderstood what I said. I can't test with and without HIMEM and EMM386 because the problems with WD only occur when using FreeCOM (not FreeDOS, i.e. the kernel) on Win98. There are no problems when using any of the following combinations: - Microsoft

Re: [Freedos-user] problems with OpenWatcom debugger + FreeCOM + Win98

2005-07-06 Thread Michael Devore
At 04:48 PM 7/5/2005 -0800, Brolin wrote: The DOS version of the OpenWatcom debugger (BINW\WD.EXE) behaves strangely when using FreeCOM on Win98. There are no problems with WD when using Win98's COMMAND.COM on Win98, nor are there problems when using FreeCOM on FreeDOS rather than Win98.

[Freedos-user] problems with OpenWatcom debugger + FreeCOM + Win98

2005-07-05 Thread Brolin
The DOS version of the OpenWatcom debugger (BINW\WD.EXE) behaves strangely when using FreeCOM on Win98. There are no problems with WD when using Win98's COMMAND.COM on Win98, nor are there problems when using FreeCOM on FreeDOS rather than Win98. The problem I'm experiencing is that WD will