Program exectuted using FORCEDOS loses parameters in SP2

[TM-DDA]

I use Realia COBOL 4.217 (DOS based & ancient, but effective). After
updating to SP2, programs compiled using Realia and run using the FORCEDOS
utility run fine unless trying to use the REALDBUB debugging tool.

Basically, it seems like parameters that are passed between programs in the
..BAT files running the debugger are not passed properly, or are even
blocked.

Everything worked fine under XP SP1. Has anyone else run accross problems
with some programs not running in SP2?

We have tried adjusting the DEP settings, since the debug tool (like many
debuggers) does access memory, but have had no luck.

Any advice as to what to try, or how to properly adjust DEP settings, or
which of the many Software Deities to pay homage to would be greatly
appreciated.

[Mark Jacobs]

Roll back to SP1, then run Windows Update, but select Custom -> All the
Critical Security Updates, sidestepping SP2. This way, you retain SP1, but
gain the added security of many SP2 patches. Afterwards, you can see them in
the Add/Remove Programs list. Works for me!
--
Mark Jacobs
DK Computing
http://www.dkcomputing.co.uk

"TM-DDA" <tmiller-dda-001(((scrap this > wrote in message
news:1096644035.nczR05YAHv7kw9/n28ZeCg@teranews...
| I use Realia COBOL 4.217 (DOS based & ancient, but effective). After
| updating to SP2, programs compiled using Realia and run using the FORCEDOS
| utility run fine unless trying to use the REALDBUB debugging tool.
|
| Basically, it seems like parameters that are passed between programs in the
| .BAT files running the debugger are not passed properly, or are even
| blocked.
|
| Everything worked fine under XP SP1. Has anyone else run accross problems
| with some programs not running in SP2?
|
| We have tried adjusting the DEP settings, since the debug tool (like many
| debuggers) does access memory, but have had no luck.
|
| Any advice as to what to try, or how to properly adjust DEP settings, or
| which of the many Software Deities to pay homage to would be greatly
| appreciated.

[TM-DDA]

Thank you for the reply.

Luckily we found the problem on test machines, and had not installed SP2 on
all PCs, so no rollback is needed.



"Mark Jacobs" <http://www.jacobsm.com/mjmsg?Microsoft%20Newsgroup> wrote in
message ...
> Roll back to SP1, then run Windows Update, but select Custom -> All the
> Critical Security Updates, sidestepping SP2. This way, you retain SP1, but
> gain the added security of many SP2 patches. Afterwards, you can see them
in
> the Add/Remove Programs list. Works for me!
> --
> Mark Jacobs
> DK Computing
> http://www.dkcomputing.co.uk
>
> "TM-DDA" <tmiller-dda-001(((scrap this > wrote in
message
> news:1096644035.nczR05YAHv7kw9/n28ZeCg@teranews...
> | I use Realia COBOL 4.217 (DOS based & ancient, but effective). After
> | updating to SP2, programs compiled using Realia and run using the
FORCEDOS
> | utility run fine unless trying to use the REALDBUB debugging tool.
> |
> | Basically, it seems like parameters that are passed between programs in
the
> | .BAT files running the debugger are not passed properly, or are even
> | blocked.
> |
> | Everything worked fine under XP SP1. Has anyone else run accross
problems
> | with some programs not running in SP2?
> |
> | We have tried adjusting the DEP settings, since the debug tool (like
many
> | debuggers) does access memory, but have had no luck.
> |
> | Any advice as to what to try, or how to properly adjust DEP settings, or
> | which of the many Software Deities to pay homage to would be greatly
> | appreciated.
>
>