Enabling 16bit DOS on MAC?
Enabling 16bit DOS on MAC?
I've been reading around, so I found this solution (on another topic here) for enabling DOS support on Macs with wine, something having to do with "patching the linker". Can anybody either explain this in simple terms, or point me towards a guide for doing this?
Enabling 16bit DOS on MAC?
On 3/29/11 6:25 PM, bigmac909 wrote:
the bug. It only lets you run Win16 programs (and not DOS programs) anyway.
Are you on Leopard?
You only need it on Leopard (10.5). On Snow Leopard (10.6), they fixedI've been reading around, so I found this solution (on another topic here) for enabling DOS support on Macs with wine, something having to do with "patching the linker". Can anybody either explain this in simple terms, or point me towards a guide for doing this?
the bug. It only lets you run Win16 programs (and not DOS programs) anyway.
Are you on Leopard?
Enabling 16bit DOS on MAC?
On 3/29/11 7:07 PM, bigmac909 wrote:
(http://bugs.winehq.org/show_bug.cgi?id=14920) for details.
But still, you'll only be able to run Win16 programs (i.e. 16-bit
programs that need Windows) and not DOS programs. DOS programs need
virtual-8086 mode, which Mac OS X will never ever support on its own.
Chip
Then take a look at bug 14920Yes, 10.5.8
(http://bugs.winehq.org/show_bug.cgi?id=14920) for details.
But still, you'll only be able to run Win16 programs (i.e. 16-bit
programs that need Windows) and not DOS programs. DOS programs need
virtual-8086 mode, which Mac OS X will never ever support on its own.
Chip
Enabling 16bit DOS on MAC?
On 3/29/11, doh123 <[email protected]> wrote:
How about it? Some programs look like they need DOS, but really are
command line Windows16, and will need a specially built version of
Wine if you are using Leopard.
James McKenzie
You know, the OP never told us what program was needed.DOSBox is the best way to run DOS programs... on Macs or many other OSes.
How about it? Some programs look like they need DOS, but really are
command line Windows16, and will need a specially built version of
Wine if you are using Leopard.
James McKenzie
Enabling 16bit DOS on MAC?
On 3/29/11 7:59 PM, James McKenzie wrote:
That's why the Windows version of ipconfig (winipcfg) was a graphical
program, and not a command-line one. (Raymond Chen explained it in his
blog, "The Old New Thing".)
Chip
There's no such thing. In 16-bit Windows, DOS *was* the command line.On 3/29/11, doh123 <[email protected]> wrote:You know, the OP never told us what program was needed.DOSBox is the best way to run DOS programs... on Macs or many other OSes.
How about it? Some programs look like they need DOS, but really are
command line Windows16,
That's why the Windows version of ipconfig (winipcfg) was a graphical
program, and not a command-line one. (Raymond Chen explained it in his
blog, "The Old New Thing".)
Or, you could just apply the linker patch I made.and will need a specially built version of
Wine if you are using Leopard.
Chip
Enabling 16bit DOS on MAC?
On 3/30/11 4:19 PM, bigmac909 wrote:
linker patch.
Chip
I told you, go read bug 14920. It will tell you exactly how to apply theThe game is Zelda Classic, if it matters. It's rated Gold on the AppDB.
And this linker patch is exactly the on I was talking about, I saw you post in an old topic. I just have no idea how to do it.
linker patch.
Chip
That's my problem, I'm not sure what I'm supposed to be looking for on that page.
I'll assume I should follow the directions in the attached configure log. My problem there is that I don't know where Wine is. Yeah, I know, sad. I followed this tutorial to get it on my computer:
http://davidbaumgold.com/tutorials/wine-mac/
Thanks again for your patience.
I'll assume I should follow the directions in the attached configure log. My problem there is that I don't know where Wine is. Yeah, I know, sad. I followed this tutorial to get it on my computer:
http://davidbaumgold.com/tutorials/wine-mac/
Thanks again for your patience.
Enabling 16bit DOS on MAC?
On 3/30/11 4:47 PM, bigmac909 wrote:
Chip
My posts.That's my problem, I'm not sure what I'm supposed to be looking for on that page.
Chip
Enabling 16bit DOS on MAC?
On 3/30/11 6:03 PM, bigmac909 wrote:
sudo port -n upgrade --force wine
or
sudo port -n upgrade --force wine-devel
if you installed the development version.
Chip
No. Just do:Nice thanks. Now I'm only confused at the final step:
So do I have to uninstall, and then reinstall wine? From scratch?5. Build and install Wine from source as usual.
However, I used MacPorts to do that. Do I have to figure out how to manually assemble Wine now, after all of this?
sudo port -n upgrade --force wine
or
sudo port -n upgrade --force wine-devel
if you installed the development version.
Chip
Enabling 16bit DOS on MAC?
On 3/30/11 6:35 PM, bigmac909 wrote:
sudo port edit wine
or
sudo port edit wine-devel
if you installed the development version.
Where it says '--disable-win16', take that out. They put that in
precisely because of the linker bug.
Chip
Oh yeah, I forgot to mention. You have to edit the Portfile:That's odd... everything worked just fine, but I'm STILL getting the "missing 16bit support/DOS" message upon trying to run the program!
sudo port edit wine
or
sudo port edit wine-devel
if you installed the development version.
Where it says '--disable-win16', take that out. They put that in
precisely because of the linker bug.
Chip
Enabling 16bit DOS on MAC?
On 4/3/11 11:31 AM, bigmac909 wrote:
responsibility.
Oh, and you should never ever run Wine under sudo. Editing and
installing ports should be done as root (i.e. under sudo, unless your
MacPorts prefix, usually /opt/local, isn't owned by root).
Chip
That's right.Alright, I think I've done it. So just to make sure, I just highlight and delete the "--disable-win16" right out of the terminal? And then just press enter?
It is, if you use it improperly. Remember, with great power comes greatSorry I'm being so cautious, I was told that SUDO was dangerous, even though I doubt it will do anything besides mess up wine for me.
responsibility.
Oh, and you should never ever run Wine under sudo. Editing and
installing ports should be done as root (i.e. under sudo, unless your
MacPorts prefix, usually /opt/local, isn't owned by root).
Chip
Ugh, I must be stupid or something. It still won't work. And now, when I go back to try and edit, I get all of these warning messages, to which I respond RECOVER (r). My edit is still there too, so is there something else I need to be doing? Do I need to do more within the platform?
platform darwin 9 {
# Fix "Xcode 3.x cannot build 16-bit code correctly. Use --disable-win16 if you don't need 16-bit support."
# Only affects Xcode 3.0.x and 3.1.x, not 3.2.x.
# See http://bugs.winehq.org/show_bug.cgi?id=14920
configure.args-append --disable-win16 [/b]
Where the bold is what I remover earlier.
platform darwin 9 {
# Fix "Xcode 3.x cannot build 16-bit code correctly. Use --disable-win16 if you don't need 16-bit support."
# Only affects Xcode 3.0.x and 3.1.x, not 3.2.x.
# See http://bugs.winehq.org/show_bug.cgi?id=14920
configure.args-append --disable-win16 [/b]
Where the bold is what I remover earlier.
Enabling 16bit DOS on MAC?
On 4/3/11 11:55 AM, bigmac909 wrote:
Chip
Delete the entire 'configure.args-append' line. That should fix it.Ugh, I must be stupid or something. It still won't work. And now, when I go back to try and edit, I get all of these warning messages, to which I respond RECOVER (r). My edit is still there too, so is there something else I need to be doing? Do I need to do more within the platform?
platform darwin 9 {
# Fix "Xcode 3.x cannot build 16-bit code correctly. Use --disable-win16 if you don't need 16-bit support."
# Only affects Xcode 3.0.x and 3.1.x, not 3.2.x.
# See http://bugs.winehq.org/show_bug.cgi?id=14920
configure.args-append --disable-win16 [/b]
Where the bold is what I remover earlier.
Chip