dos app stalls after some config change?

[Guest]

ok, so you hate dos.....

but this dos app runs fine until I install a certain Windows App or a
certain error occurs while I have a DOS box open ? This dos utility is only
30K long! All other dos utilities run fine! I can't blame a certain Windows
App because it will work fine on another windows computer. I have caused this
failure without installing any new apps too - by causing a build failure in a
DOS box. Once this error occurs, I can't recover.

- No Dos configuration change made.
- I tried running system restore - doesn't help.
- I tried reinstalling windows - doesn't help
- Failure occurs on all Windows versions
- Only way to cure problem is to wipeout hard disk and reinstall everything.

Any ideas? This utility is called udi.exe and was created by Intel to run
intel
programs in DOS environment. Seems like some enviroment variable must be set
that causes this failure?

 

[Guest]

Hi. You never actually said what the exact problem is, or I missed it. If the
..EXE opens and then stalls(freezes) and locks up the system, pressing Ctrl,
Alt and Delete keys, all at the same time will usually get you out of the
lockup. With the .EXE closed/inactive , you may have to fiddle with the
program's 'properties'. Right click on the progam line or icon to open the
'properties' window. I had this problem with DOS EXEs, and the only way to
cure it was to open the .EXE as a 'window'; not 'full screen'. There are all
sorts of things to reconfigure there, so take a look. Good luck, Paul

 

[Guest]

Thanks for replying to my email! As you know, Microsoft doesn't support DOS
questions anymore. Anyway, the answer to your question is that the program
effectively hangs waiting for some condition to be true. I have a program
called Sourcer that I used to convert the .exe file into an assembly file so
I could trace it. Using CodeView, I traced the execution of the failing DOS
app to one particular area...it gets in an infinite loop....but thats about
all I can determine. I would like to send you the DOS app to see if it
fails on your machine (only 30k). The APP works correctly if you just type
"UDI" and then displays " c> " ; The "c>" is a subshell where you can type
further commands. When the program hangs, you don't see that shell prompt
and must kill the command box using Ctrl-Alt_delete. I am particularly
interested to see if UDI.exe works or doesn't work on various Win machines
you may have...and if you can perform some magic to get it working again.

my real email address is (e-mail address removed)

Regards,
Kevin