Thread: running W98 DOS programs under NT/XP

carlosalbertomartinelli@hotmail.com wrote:
> Hi people. This is my first time... I owner a ansient comercial system
> that was developed to COBOL under W98 DOS environment without any
> problem. Now, with the massive migration of my clients to NT or XP
> systems, some programs of the system just doesnt work properly. The
> most of them stil works, but, suddenly, the system aborts with the
> message "unexpected goto to this momment".... What should I do to
> solver this problem? any environment variable to be set? Please help!!
> thx.
>
> IMPORTANT: The system stil works. I have observed that the most
> routines (or even all) that generate this error are external routines
> called with CALL statement.
>
It sounds like you've gotten nearly all the mileage you are going to get
out of that DOS mode application. You should expect the problems to
worsen as Microsoft distributes more and more NT/XP/Vista series
operating system licenses. You should SERIOUSLY evaluate producing a new
version with a Windows compatible development suite. Lots of other
developers have faced the same expensive choice.

carlosalbertomartinelli@hotmail.com <ca-martinelli@bol.com.br> wrote:
> Hi people. This is my first time... I owner a ansient comercial system
> that was developed to COBOL under W98 DOS environment without any
> problem. Now, with the massive migration of my clients to NT or XP
> systems, some programs of the system just doesnt work properly. The
> most of them stil works, but, suddenly, the system aborts with the
> message "unexpected goto to this momment".... What should I do to
> solver this problem? any environment variable to be set? Please help!!
> thx.
>
> IMPORTANT: The system stil works. I have observed that the most
> routines (or even all) that generate this error are external routines
> called with CALL statement.

Hi - you really need to have your software updated to something that will
work with contemporary operating systems. You may be able to get it to work
in XP by using "compatibility mode" (look at the properties of the
shortcut), but it's 2007 and time to get something new.

"carlosalbertomartinelli@hotmail.com" <ca-martinelli@bol.com.br>
wrote:

>IMPORTANT: The system stil works. I have observed that the most
>routines (or even all) that generate this error are external routines
>called with CALL statement.

This is 2007.

Not 1995.

Change is good.