Currently attempting to run an old PC game on my Mac (Leopard). I've installed Wine using MacPorts, which worked flawlessly. Now when I attempt to install my PC Game the terminal responds with "16-Bit/DOS Support missing." Is there a way to fix this?
On Mon, Jul 12, 2010 at 4:10 PM, dwarfcricket <wineforum-user at winehq.org> wrote:> Currently attempting to run an old PC game on my Mac (Leopard). ?I've installed Wine using MacPorts, which worked flawlessly. ?Now when I attempt to install my PC Game the terminal responds with "16-Bit/DOS Support missing." > > Is there a way to fix this? >dosbox
On 7/12/10 2:10 PM, dwarfcricket wrote:> Currently attempting to run an old PC game on my Mac (Leopard). I've installed Wine using MacPorts, which worked flawlessly. Now when I attempt to install my PC Game the terminal responds with "16-Bit/DOS Support missing." > > Is there a way to fix this?Yeah. Run it in DOSBox. You're never going to run that under Wine on a Mac. That's because the Mac OS X kernel lacks Virtual-8086 mode support. And it's not trivial to add it, either--especially because most modern Macs run in 64-bit mode where v86 mode doesn't work. Chip
Well I thought so, too, but when I try to run it in DOS it says "This program requires Microsoft Windows." :| Am I doomed? Have all my efforts been futile?
On Mon, Jul 12, 2010 at 4:24 PM, dwarfcricket <wineforum-user at winehq.org> wrote:> Well I thought so, too, but when I try to run it in DOS it says "This program requires Microsoft Windows." ? ?:| > > Am I doomed? ?Have all my efforts been futile? >virtualbox/qemu emulation (not HW virtulization) mode + win9X John
John Drescher wrote:> On Mon, Jul 12, 2010 at 4:24 PM, dwarfcricket <wineforum-user at winehq.org> wrote: > > > Well I thought so, too, but when I try to run it in DOS it says "This program requires Microsoft Windows." ? ?:| > > > > Am I doomed? ?Have all my efforts been futile? > > > > > > virtualbox/qemu emulation (not HW virtulization) mode + win9X > > JohnNot to be a pain... but I'm new at this stuff - and that looks like gibberish... i know this is all pretty simple, but I'm just trying to get my footing. So... what should I do with that? [Embarassed]
Charles Davis wrote:> On 7/12/10 2:24 PM, dwarfcricket wrote: > > > Well I thought so, too, but when I try to run it in DOS it says "This program requires Microsoft Windows." :| > > > Oh, so it's a Win16 program. > > In that case, there are three things you can do: > - Run Windows in a VM, like John suggested. But that requires you to > have a Windows license. > - Upgrade to Snow Leopard. The reason MacPorts builds without Win16 > support is that Xcode 3.x has a linker that can't handle 16-bit code > very well. Xcode 3.2, which comes with SL, does not have this problem. > - Patch the linker. See bug 14920 > (http://bugs.winehq.org/show_bug.cgi?id=14920 ) for more info. > > If you pick one of the last two options, though, you'll then have to > change the Portfile to not pass --disable-win16 to Wine's configure script. > > ChipWell, I don't have a Windows license, unfortunately. SO, if I were to go about patching it - how would I change the Portfile?
Charles Davis wrote:> On 7/12/10 2:53 PM, dwarfcricket wrote: > > > Charles Davis wrote: > > > > > On 7/12/10 2:24 PM, dwarfcricket wrote: > > > > > > > > > > Well I thought so, too, but when I try to run it in DOS it says "This program requires Microsoft Windows." :| > > > > > > > > > > > Oh, so it's a Win16 program. > > > > > > In that case, there are three things you can do: > > > - Run Windows in a VM, like John suggested. But that requires you to > > > have a Windows license. > > > - Upgrade to Snow Leopard. The reason MacPorts builds without Win16 > > > support is that Xcode 3.x has a linker that can't handle 16-bit code > > > very well. Xcode 3.2, which comes with SL, does not have this problem. > > > - Patch the linker. See bug 14920 > > > (http://bugs.winehq.org/show_bug.cgi?id=14920 ) for more info. > > > > > > If you pick one of the last two options, though, you'll then have to > > > change the Portfile to not pass --disable-win16 to Wine's configure script. > > > > > > Chip > > > > > > > > > > > Well, I don't have a Windows license, unfortunately. > > > > SO, if I were to go about patching it - how would I change the Portfile? > > > The Portfile is in > /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/wine-devel. > There's a line that reads: > > configure.args-append --disable-win16 > > If you put a pound sign in front: > > # configure.args-append --disable-win16 > > then MacPorts won't disable Win16 support when it builds Wine. > > You only need to do this if you patch the linker, though. I just > realized that the Portfile is smart enough to realize when it's on SL. > There, it leaves Win16 support in. > > ChipWell, I attempted to change the Portfile, but it keeps telling me I don't have the appropriate access to do so - even though my account (I'm the admin) is allowed to Read & Write - is there another way for me to change the settings so that I may change and save the Portfile?
Charles Davis wrote:> On 7/12/10 3:18 PM, dwarfcricket wrote: > > > Charles Davis wrote: > > > > > On 7/12/10 2:53 PM, dwarfcricket wrote: > > > > > > > > > > Charles Davis wrote: > > > > > > > > > > > > > On 7/12/10 2:24 PM, dwarfcricket wrote: > > > > > > > > > > > > > > > > > > > > > Well I thought so, too, but when I try to run it in DOS it says "This program requires Microsoft Windows." > > > > > > > > > > > > > > > > > > > > > > > Oh, so it's a Win16 program. > > > > > > > > > > In that case, there are three things you can do: > > > > > - Run Windows in a VM, like John suggested. But that requires you to > > > > > have a Windows license. > > > > > - Upgrade to Snow Leopard. The reason MacPorts builds without Win16 > > > > > support is that Xcode 3.x has a linker that can't handle 16-bit code > > > > > very well. Xcode 3.2, which comes with SL, does not have this problem. > > > > > - Patch the linker. See bug 14920 > > > > > (http://bugs.winehq.org/show_bug.cgi?id=14920 ) for more info. > > > > > > > > > > If you pick one of the last two options, though, you'll then have to > > > > > change the Portfile to not pass --disable-win16 to Wine's configure script. > > > > > > > > > > Chip > > > > > > > > > > > > > > > > > > > > > > > > > > Well, I don't have a Windows license, unfortunately. > > > > > > > > SO, if I were to go about patching it - how would I change the Portfile? > > > > > > > > > > > The Portfile is in > > > /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/wine-devel. > > > There's a line that reads: > > > > > > configure.args-append --disable-win16 > > > > > > If you put a pound sign in front: > > > > > > # configure.args-append --disable-win16 > > > > > > then MacPorts won't disable Win16 support when it builds Wine. > > > > > > You only need to do this if you patch the linker, though. I just > > > realized that the Portfile is smart enough to realize when it's on SL. > > > There, it leaves Win16 support in. > > > > > > Chip > > > > > > > > > Well, I attempted to change the Portfile, but it keeps telling me I don't have the appropriate access to do so - even though my account (I'm the admin) is allowed to Read & Write - is there another way for me to change the settings so that I may change and save the Portfile? > > > You have to edit the Portfile as root. > > ChipI'm really sorry... what does that mean/how would I do that? [Embarassed]
Charles Davis wrote:> On 7/12/10 3:35 PM, dwarfcricket wrote: > > > Charles Davis wrote: > > > > > On 7/12/10 3:18 PM, dwarfcricket wrote: > > > > > > > > > > Charles Davis wrote: > > > > > > > > > > > > > On 7/12/10 2:53 PM, dwarfcricket wrote: > > > > > > > > > > > > > > > > > > > > > Charles Davis wrote: > > > > > > > > > > > > > > > > > > > > > > > > > On 7/12/10 2:24 PM, dwarfcricket wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Well I thought so, too, but when I try to run it in DOS it says "This program requires Microsoft Windows." > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Oh, so it's a Win16 program. > > > > > > > > > > > > > > In that case, there are three things you can do: > > > > > > > - Run Windows in a VM, like John suggested. But that requires you to > > > > > > > have a Windows license. > > > > > > > - Upgrade to Snow Leopard. The reason MacPorts builds without Win16 > > > > > > > support is that Xcode 3.x has a linker that can't handle 16-bit code > > > > > > > very well. Xcode 3.2, which comes with SL, does not have this problem. > > > > > > > - Patch the linker. See bug 14920 > > > > > > > (http://bugs.winehq.org/show_bug.cgi?id=14920 ) for more info. > > > > > > > > > > > > > > If you pick one of the last two options, though, you'll then have to > > > > > > > change the Portfile to not pass --disable-win16 to Wine's configure script. > > > > > > > > > > > > > > Chip > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Well, I don't have a Windows license, unfortunately. > > > > > > > > > > > > SO, if I were to go about patching it - how would I change the Portfile? > > > > > > > > > > > > > > > > > > > > > > > The Portfile is in > > > > > /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/wine-devel. > > > > > There's a line that reads: > > > > > > > > > > configure.args-append --disable-win16 > > > > > > > > > > If you put a pound sign in front: > > > > > > > > > > # configure.args-append --disable-win16 > > > > > > > > > > then MacPorts won't disable Win16 support when it builds Wine. > > > > > > > > > > You only need to do this if you patch the linker, though. I just > > > > > realized that the Portfile is smart enough to realize when it's on SL. > > > > > There, it leaves Win16 support in. > > > > > > > > > > Chip > > > > > > > > > > > > > > > > > > > > > > Well, I attempted to change the Portfile, but it keeps telling me I don't have the appropriate access to do so - even though my account (I'm the admin) is allowed to Read & Write - is there another way for me to change the settings so that I may change and save the Portfile? > > > > > > > > > > > You have to edit the Portfile as root. > > > > > > Chip > > > > > > > > > I'm really sorry... what does that mean/how would I do that? [Embarassed] > > > 'root' is the most powerful user on a Unix-type system. To become root > on Mac OS X, you use the 'sudo' command from the Terminal. (You've used > this command before; you needed it to install Wine from MacPorts in the > first place!) I'm not sure you can run any GUI programs as root, though, > and I definitely wouldn't recommend it, so I suggest using a text editor > like nano or vim or emacs that works in a Terminal. > > If you need more help, remember, Google is your friend. > > > > ChipAHH, gotcha! Thank you thank you thank you :) Sorry for all the questions - but thank you for all the responses!
Charles Davis <cdavis at mymail.mines.edu> wrote:>Sent: Jul 12, 2010 1:18 PM >To: wine-users at winehq.org >Subject: Re: [Wine] 16-Bit/DOS Suppor Missing? > >On 7/12/10 2:10 PM, dwarfcricket wrote: >> Currently attempting to run an old PC game on my Mac (Leopard). I've installed Wine >>using MacPorts, which worked flawlessly. Now when I attempt to install my PC Game the >>terminal responds with "16-Bit/DOS Support missing." >> >> Is there a way to fix this? >Yeah. Run it in DOSBox. You're never going to run that under Wine on a >Mac. That's because the Mac OS X kernel lacks Virtual-8086 mode support. >And it's not trivial to add it, either--especially because most modern >Macs run in 64-bit mode where v86 mode doesn't work.The problem is not 64 bitness, but a broken ld program that came with XCode 3.1. There is a patch to fix this on Wine's Bugzilla and you have to download the source for ld from opensource.apple.com. Also, there is very little truth to the fact that running X86 processors in 64 bit mode disables v86 mode. Maybe Apple disabled this in Snow Leopard, but Vista 64 supports running Win16 programs. James McKenzie
Charles Davis wrote:> On 7/12/10 3:52 PM, James Mckenzie wrote: > > > Charles Davis <cdavis at mymail.mines.edu> wrote: > > > > > Sent: Jul 12, 2010 1:18 PM > > > To: wine-users at winehq.org > > > Subject: Re: [Wine] 16-Bit/DOS Suppor Missing? > > > > > > On 7/12/10 2:10 PM, dwarfcricket wrote: > > > > > > > Currently attempting to run an old PC game on my Mac (Leopard). I've installed Wine > > > > using MacPorts, which worked flawlessly. Now when I attempt to install my PC Game the > > > > terminal responds with "16-Bit/DOS Support missing." > > > > > > > > Is there a way to fix this? > > > > > > > Yeah. Run it in DOSBox. You're never going to run that under Wine on a > > > Mac. That's because the Mac OS X kernel lacks Virtual-8086 mode support. > > > And it's not trivial to add it, either--especially because most modern > > > Macs run in 64-bit mode where v86 mode doesn't work. > > > > > > > The problem is not 64 bitness, but a broken ld program that came with XCode 3.1. There is a patch to fix this on Wine's Bugzilla and you have to download the source for ld from opensource.apple.com. > > > I told him about that. > > > Also, there is very little truth to the fact that running X86 processors in 64 bit mode disables v86 mode. > > > I could swear that you couldn't enter v86 mode when in 64-bit mode. I > seem to remember reading something about that in an early x64 manual I had. > > > Maybe Apple disabled this in Snow Leopard, but Vista 64 supports running Win16 programs. > > > That's because you don't need v86 to run most Win16 programs; they run > in 16-bit protected mode (which IS supported even in 64-bit mode). > > ChipAhem - told *her* about that, Chip :-P Thanks for the info., James. I'll try the patch and see if that fixes this up. It's so lame that I'm going through all of this for a silly old PC game [Laughing]
dwarfcricket ?rta:> Well I thought so, too, but when I try to run it in DOS it says "This program requires Microsoft Windows." :| > > Am I doomed? Have all my efforts been futile? >Install Windows 3.1 in Dosbox and run from there...
Charles Davis little technical fact v86 mode can work with x64 bit OS's but its a trip threw hell of the OS to implement. http://v86-64.sourceforge.net/ There are a few other ugly options that could be implemented including software visualization. Never is a very long time. If we got a few developers interesting in making wine dos support work without needing v86 it would become possible. But then again dosbox works quite we so no one is bothered at this stage.