cannot find L"C:\\windows\\system32\\Command.com"

[Ben2K]

Trying to install Quicken Deluxe 2009 with the latest Wine 1.2 release on Ubuntu Lucid. I keep getting errors, the first of which is:

Code: Select all

cannot find L"C:\\windows\\system32\\Command.com"

Also get this dump and trace output, which was a bit too long to embed. There were some popups too, that I didn't capture.

According to the DB, the app is rated Silver. I've seen the same Command.com error in a number of different forum posts for different apps, but no real solution. Even tried uninstalling Wine, and deleting the ~/.wine directory (a real Windoze approach), but nothing changed.

Suggestions?

[Ben2K]

P.S. Forgot to mention that the CD was mounted on ~/Quicken.

[dimesio]

Code: Select all

myname@myhost:~$ wine Quicken/LxSetup.exe

You're not starting it correctly. http://wiki.winehq.org/FAQ#head-f351523 ... 8da63be66f

[Ben2K]

Code: Select all

myname@myhost:~$ wine Quicken/LxSetup.exe

You're not starting it correctly. http://wiki.winehq.org/FAQ#head-f351523 ... 8da63be66f

Ive also tried starting inside Nautilus, which hides the error messages, and from the same directory as the executable. No success with any.

[James McKenzie]

Ben2K wrote:

dimesio wrote:

Code:
myname@myhost:~$ wine Quicken/LxSetup.exe

You're not starting it correctly. http://wiki.winehq.org/FAQ#head-f351523 ... 8da63be66f

Ive also tried starting inside Nautilus, which hides the error messages, and from the same directory as the executable. No success with any.

You should start the program in terminal from wherever it was installed to.

Using Nautilus will hide the error messages.

We would like to look at any error messages you receive, but please
capture them to a log file and post them to a web site like
pastebin.com. This is to be courtous to those who receive the mailing
list copy and pay for Internet access by usage.

http://wiki.winehq.org/FAQ#get_log describes this process.

James McKenzie

[Ben2K]

Ben2K wrote:

dimesio wrote:

You should start the program in terminal from wherever it was installed to.

Using Nautilus will hide the error messages.

We would like to look at any error messages you receive, but please
capture them to a log file and post them to a web site like
pastebin.com. This is to be courtous to those who receive the mailing
list copy and pay for Internet access by usage.

http://wiki.winehq.org/FAQ#get_log describes this process.

James McKenzie

1: Still trying to get the program installed
2: I said that Nautilus hides the errors
3: I did capture the error output, an post it elsewhere with a link. See the original message

[dimesio]

Ive also tried starting inside Nautilus, which hides the error messages, and from the same directory as the executable. No success with any.

Try following the instructions for installing from multiple cds in the link I gave you.

[Ben2K]

Try following the instructions for installing from multiple cds in the link I gave you.

Its a single CD. Changing disks is not the issue.

[dimesio]

Try following the instructions for installing from multiple cds in the link I gave you.

Its a single CD. Changing disks is not the issue.

I didn't say it was. I want you to use the wine start command as specified in that section of the FAQ.

[Ben2K]

I didn't say it was. I want you to use the wine start command as specified in that section of the FAQ.

OK. Tried that. Same leading errors, no trace or dump output though. Still crashes.

[dimesio]

OK. Tried that. Same leading errors, no trace or dump output though. Still crashes.

Try with a clean wineprefix. Delete or rename ~/.wine, then run winecfg to force creation of a new wineprefix. If all goes well, run the installer (from the terminal).

[Ben2K]

OK. Tried that. Same leading errors, no trace or dump output though. Still crashes.

Try with a clean wineprefix. Delete or rename ~/.wine, then run winecfg to force creation of a new wineprefix. If all goes well, run the installer (from the terminal).

Already did all that.

[Gert van den Berg]

If the application's installer actually requires components from DOS
(command.com), try to have a look if any information is available on
installing it on 64-bit Windows...

Freecom from freedos might be usable...

Otherwise it might help trying to trick it into running cmd.exe (a
completely different command shell...) Not sure if copying / linking
the fake Wine cmd.exe will work...

[Doug]

On 7/20/2010 12:23 AM, Gert van den Berg wrote:

If the application's installer actually requires components from DOS
(command.com), try to have a look if any information is available on
installing it on 64-bit Windows...

Freecom from freedos might be usable...

Otherwise it might help trying to trick it into running cmd.exe (a
completely different command shell...) Not sure if copying / linking
the fake Wine cmd.exe will work...

For whoever is looking for command.com: I have a copy of a boot disk
for MSDOS 6.1 (I think) with command.com on it. Send me an email, and
I will attach the file in a reply to you. (Probably the list does
not support attachments.) After all these years, the disk will
still boot a machine, so I guess it's not corrupted.

--doug

--
Blessed are the peacemakers...for they shall be shot at from both sides.
--A.M. Greeley

[dimesio]

If the application's installer actually requires components from DOS
(command.com), try to have a look if any information is available on
installing it on 64-bit Windows...

The app in question is Quicken 2009, so it's unlikely it needs DOS components. And no one has mentioned this being a problem in any of the AppDB test reports. Something is wrong with this user's setup, but I have no idea what.

[oldefoxx]

There are several posts of this nature, and this is the 3rd and final one that I will answer. If wine is complaining that it cannot find a file, either it is looking in the wrong place or it goes by a different name. Early versions of Windows (and DOS) dealt with a command interpreter named Command.com. That was replaced in later versions of Windows with a similar interpreter named Cmd.exe. Both do a similar job, but the .com file type had limited growth potential and the exe replacement could do more.

Looking in /home/[username]/.wine/drive_c/windows/system32/, we can dins cmd.exe, but not command.com. Now if you found an old copy of command.com and copied it there, that might do for you, but trying to work with cmd.exe might be the better choice.

Technically, you could make a copy of cmd.exe and rename it as command.com, and that might work. Either file extension identifies it as an executable, and once loaded, the first two characters of the file distinguishes one from the other. If memory serves, in an exe file, the first two characters are "MZ".

That particular error from wine is often linked to any exe file because no path is specified in the call to wine. Thus, wine filename.exe will fail, whereas wine ~/path/filename will work. As to the chief difference between a com and exe file? Com files only use one segment of memory for everything, and exe files use many segments for different things, making it a more flexible choice.

[doh123]

There are several posts of this nature, and this is the 3rd and final one that I will answer.

well thats good… I doubt most of these 5 year old posts need more answers