RE: DIR not working right
- From: "Harry Binswanger" <hb@xxxxxxxxxxxx>
- To: <xywrite@xxxxxxxxxxxxx>
- Date: Fri, 30 May 2014 16:10:38 -0400
And what about under that alternate Cmd.Exe that RH recommended to us long
ago . . . or was that null and
void by the time of Vista / W7 ?
[HB:] kmd.exe? What about it?
Since you are the exponent of W7 32bit, I have one for you. I dragged
Editor.Exe onto my W7_x86 desktop,
where it stubbornly remains represented as a plain white sheet of paper.
Nothing I've tried so far has caused
*any* of the Xy icons available at Brian's site to "take." I don't seem to
have this problem with any other program
on that desktop, but then this is probably the only DOS program there, which
may well be the clue. If there is
some _other_ way to force this, do tell.
[HB:] I know a fair bit about that. If you run it directly as an .exe, you
cannot change the white sheet of paper into anything. BUT, you can change
the icon that shows on the task bar after has been launched, and which shows
on the upper left. However, that is done by using ResHacker on NTVDM.EXE, so
the price is that all DOS programs (e.g., cmd.exe) will show with the icon
you've chosen for Xy.
Alternatively, you can call Editor.exe from a .BAT file, in which case you
can get the icons you want through the normal Properties/Change Icon route.
The downside is that you won't see the right icon in the top left of the
window of Xy when launched, you will see instead the icon Win7 uses for
anonymous .exe files. I think there is some other downside to doing it that
way, because in the end I chose the first route. Give the .BAT file route a
try though.
Jordan
_____
From: Harry Binswanger <hb@xxxxxxxxxxxx>
To: xywrite@xxxxxxxxxxxxx
Sent: Thursday, May 29, 2014 7:09 AM
Subject: RE: DIR not working right
Win 7 32bit. No VM required.
From: xywrite-bounce@xxxxxxxxxxxxx [mailto:xywrite-bounce@xxxxxxxxxxxxx] On
Behalf Of Bill Troop
Sent: Wednesday, May 28, 2014 5:38 PM
To: xywrite@xxxxxxxxxxxxx
Subject: Re: DIR not working right
Harry, you don't say which platform, in this instance, you're running Xy4
from. I had a similar problem when I ran Xy4 under VirtualBox using either
W2K or XP as the intermediary. If it hadn't been for that, I would have
stayed with VirtualBox. The problem doesn't exist under VMware. I have not
yet filed a bug report with VirtualBox.
Other related posts:
