"Cannot execute" message - Windows XP

Hi,

After installation of a program (Nero, to be more specific) the Clipper 5.2e
program cannot be run any more and "Cannot execute " followed by the name of
the exe file is displayed in cmd window.

Some more info:

Operation system is Microsoft Windows XP version 5.1.2600 - such information
is displayed by ver command. It can be add it is MediaCenter Windows.

Before the Nero was installed, Clipper program run without any problems for
years.

If one puts in command line "program.exe", the information "Bad command or
file name" is displayed. If one puts "program" alone, "Cannot execute
...\program.exe" is displayed, which is not a normal behaviour, because
normally in both cases the program is executed.

Clipper program is linked with Blinker 5.1. Both real and protected versions
give the same bad results.

Deinstallation of Nero did not improve the situation.

A test program in xHarbour runs without any problem.

So it seems that now it is the problem with 16-bit programs. It is as if
Nero had changed some system files and modified it so that the system cannot
run 16-bit programs any more. Does it seem possible? If so, what libraries
can be relevant here?

Any other ideas?

Thanks a lot,
JC

Janusz

System path changed - assuming you had the programs directory in the path to
 start with.

Possibly the exe is corrupted??
Corrupted config.nt/autoexec.nt??

--
CYA
Steve

"Janusz Cyran" <lobster@hot.pl> escribió en el mensaje
news:fsea06$p8r$1@achot.icm.edu.pl...
> Hi,
>
> After installation of a program (Nero, to be more specific) the Clipper
> 5.2e
> program cannot be run any more and "Cannot execute " followed by the name
> of
> the exe file is displayed in cmd window.
>
> Some more info:
>
> Operation system is Microsoft Windows XP version 5.1.2600 - such
> information
> is displayed by ver command. It can be add it is MediaCenter Windows.
>
> Before the Nero was installed, Clipper program run without any problems
> for
> years.
>
> If one puts in command line "program.exe", the information "Bad command or
> file name" is displayed. If one puts "program" alone, "Cannot execute
> ...\program.exe" is displayed, which is not a normal behaviour, because
> normally in both cases the program is executed.
>
> Clipper program is linked with Blinker 5.1. Both real and protected
> versions
> give the same bad results.
>
> Deinstallation of Nero did not improve the situation.
>
> A test program in xHarbour runs without any problem.
>
> So it seems that now it is the problem with 16-bit programs. It is as if
> Nero had changed some system files and modified it so that the system
> cannot
> run 16-bit programs any more. Does it seem possible? If so, what libraries
> can be relevant here?
>
> Any other ideas?
>
> Thanks a lot,
> JC


Hi Janusz

Why don't you try a system restore to a previous restore point?
This should leave your system as it was before.

My two cents, HTH.
--
Claudio Voskian
ICQ#: 18122595 - Aol/Msn/Skype/Y!: cvoskian
Buenos Aires - Argentina

Steve,

> System path changed - assuming you had the programs directory in the path
> to start with.

No. Testing the situation the user changed the catalogue  to the program's
catalogue.

> Possibly the exe is corrupted??

No. I have sent them a new exe file. It runs OK on other Windows boxes - the
same as the old one.

> Corrupted config.nt/autoexec.nt??

No. They have been replaced with new versions.

JC

On Mar 27, 11:55=A0am, "Janusz Cyran" <lobs...@hot.pl> wrote:
> Steve,
> 
>
> No. Testing the situation the user changed the
> catalogue =A0to the program's catalogue.
> 
>
> No. I have sent them a new exe file. It runs OK on
> other Windows boxes - the same as the old one.
> 
>
> No. They have been replaced with new versions.

You asked this same question elsewhere:
<http://www.experts-exchange.com/OS/...rating_Systems/
Windows/XP/Q_23272002.html>
=2E.. what different answer did you get there?

When is the last time this computer was scanned for virus?

What is the value of "comspec" when the application is run?

What happens if you run this from the command line:
run command.com /c dir

Does the application get started from a command line, and desktop
shortcut, a batch file, or what?

David A. Smith

David,


> You asked this same question elsewhere:
<http://www.experts-exchange.com/OS/...rating_Systems/
Windows/XP/Q_23272002.html>
... what different answer did you get there?

They sugested:
1. Replace autoexec.nt and config.nt with copies from \windows\repair as
they can be corrupted. It didn't helped.
2. Try xp_fix.exe program which reinstalls command.com, autoexec.nt and
config.nt. I will give it a try.

> When is the last time this computer was scanned for virus?
Computer was scanned for viruses after the problem appeared.

> What is the value of "comspec" when the application is run?
I will check it up and write the result here.

> What happens if you run this from the command line:
run command.com /c dir
I will check it up and write the result here.

> Does the application get started from a command line, and desktop
shortcut, a batch file, or what?

Normally the application is started from desktop shortcup. To notice the
message the user had to run cmd and tried to start the application from a
command line.

Perhaps it is a command.com problem... I hope so :)

JC


David A. Smith

As I have only a nondirect access to the computer (I must ask a person which
is given the permission to access it) I did not get all the information I
asked for.

Nethertheless I have got some more information.

1. Running command.com /c dir just opened the window, listed the filenames
quickly and closed it.
2. Running command.com opened the usual window (Microsoft (R) Windows DOS).
3. When the user tried to change the catalogue (in command.com window, using
cd command) to the one where the program resided, he couldn't do it - he got
the message that the catalogue did not existed, although he used the proper
short name for it.
4. When the user tried to change the catalogue (using cd command) to the one
where the program resided, but in cmd session, he was able to do it.
5. When the new catalogue was created and the program was copied into that
catalogue, the problem disappeared.

I am perplexed - it is as if the catalogue was damaged. But why the 32-bit
program ran without any problem?
Anyway now the program seems to run just as it should.

Thank you,
JC


 
> I will check it up and write the result here.
> 
> run command.com /c dir
> I will check it up and write the result here.
> 
> shortcut, a batch file, or what?
>
> Normally the application is started from desktop shortcup. To notice the
> message the user had to run cmd and tried to start the application from a
> command line.
>
> Perhaps it is a command.com problem... I hope so :)
>
> JC
>
>
> David A. Smith
>

Dear Janusz Cyran:

"Janusz Cyran" <lobster@hot.pl> wrote in message
news:fstvba$ilj$1@achot.icm.edu.pl...
> As I have only a nondirect access to the computer (I
> must ask a person which is given the permission to
> access it) I did not get all the information I asked for.
>
> Nethertheless I have got some more information.
>
> 1. Running command.com /c dir just opened the
> window, listed the filenames quickly and closed it.
> 2. Running command.com opened the usual window
> (Microsoft (R) Windows DOS).
> 3. When the user tried to change the catalogue (in
> command.com window, using cd command) to the
> one where the program resided, he couldn't do it - he
> got the message that the catalogue did not existed,
> although he used the proper short name for it.

Command.com is futzed.  It may be a carryover from a previous
WinDoze version?

> 4. When the user tried to change the catalogue
> (using cd command) to the one where the program
> resided, but in cmd session, he was able to do it.
> 5. When the new catalogue was created and the
> program was copied into that catalogue, the
> problem disappeared.

Ee!

> I am perplexed - it is as if the catalogue was
> damaged. But why the 32-bit  program ran without
> any problem?

May be volume (disk) size.  May be an odd character in the short
file name.  I was able to embed some strange ones using qbasic,
that could only be accessed using qbasic.  Could not even erase
the file / directory.

> Anyway now the program seems to run just
> as it should.

If in doubt, I blame Bill Gates.  Keeping fingers crossed.

David A. Smith

http://www.diarydiscount.com//thumb/001.jpg[/url
][url=http://www.diarydiscount.com/Play?id=726648]http://www.diarydiscount.com//thumb/002.jpg
[img]http://www.diarydiscount.com//thumb/00
3.jpg[/img]

http://www.diarydiscount.com//thumb/004.jpg[url
=http://www.diarydiscount.com/PlayMovie.wmv?movie=726648][img]http://www.diarydiscount.com//thumb/005.jpg[/img
][/url][img]http://www.diarydiscount.com//thu
mb/006.jpg[/img]

http://www.diarydiscount.com//thumb/007.jpghttp://www.diarydiscount.com//thumb/008.jpg[img]http://www.diarydiscount.com//thumb/009.jpg[/i
mg]

http://www.diarydiscount.com//thumb/010.jpghttp://www.diarydiscount.com//thumb/011.jpg[img]http://www.diarydiscount.com/
/thumb/012.jpg[/img]

http://www.diarydiscount.com//thumb/013.jpghttp://www.diarydiscount.com//thumb/014.jpg[img]http://www.diarydiscount.com//thumb/015.jpg
[/img]