[SOLVED] "DOS support unavailable"

cwizardone · 01-11-2011, 02:02 PM

For years, and up to and including this morning, I've been running a old Windows program, The American Heritage Electronic Dictionary, in WINE.
This a.m. I installed the latest current changes and all was well. I then install all of Multilib changes and the 32compat packages and now when I try and fire up the above mentioned program I get the following error:

Code:

preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
winevdm: unable to exec 'C:\AHDW\AHD3.EXE': DOS support unavailable

Any ideas on how to fix this would be appreciated.
Thanks.

TheCrow33 · 01-11-2011, 02:44 PM

shot in the dark here, have you reinstalled wine since you did the multilib updates? I believe I had a problem with this a while ago.

cwizardone · 01-11-2011, 02:48 PM

Quote:

Originally Posted by TheCrow33

shot in the dark here, have you reinstalled wine since you did the multilib updates? I believe I had a problem with this a while ago.

Yes, I tried that, but thanks for the suggestion.

volkerdi · 01-11-2011, 03:25 PM

Quote:

Originally Posted by cwizardone

This a.m. I installed the latest current changes and all was well. I then install all of Multilib changes and the 32compat packages and now when I try and fire up the above mentioned program I get the following error:

Code:

preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
winevdm: unable to exec 'C:\AHDW\AHD3.EXE': DOS support unavailable

This is very likely due to an increase in the default CONFIG_MIN_MMAP_ADDR. Previously it was set to 4096, and possibly WINE had learned to work around that restriction.

It will probably work again (after a reboot) if you create or edit /etc/sysctl.conf with this contents:
vm.mmap_min_addr=0

To make the change from the command line as root: sysctl vm.mmap_min_addr=0

Note that this will open up a whole range of possible kernel attacks that can allow local users to root your machine.

cwizardone · 01-11-2011, 06:35 PM

Quote:

Originally Posted by volkerdi

This is very likely due to an increase in the default CONFIG_MIN_MMAP_ADDR. Previously it was set to 4096, and possibly WINE had learned to work around that restriction.

It will probably work again (after a reboot) if you create or edit /etc/sysctl.conf with this contents:
vm.mmap_min_addr=0

To make the change from the command line as root: sysctl vm.mmap_min_addr=0

Note that this will open up a whole range of possible kernel attacks that can allow local users to root your machine.

That worked.
Thank you very much, Mr. Volkerding!
Greatly appreciated!

masbroe · 05-20-2011, 02:55 AM

Quote:

Originally Posted by volkerdi

This is very likely due to an increase in the default CONFIG_MIN_MMAP_ADDR. Previously it was set to 4096, and possibly WINE had learned to work around that restriction.

It will probably work again (after a reboot) if you create or edit /etc/sysctl.conf with this contents:
vm.mmap_min_addr=0

To make the change from the command line as root: sysctl vm.mmap_min_addr=0

Note that this will open up a whole range of possible kernel attacks that can allow local users to root your machine.

Thanks Mr. Pat,
worked for me without reboot.

psionl0 · 05-20-2011, 04:57 AM

Quote:

Originally Posted by volkerdi

note that this will open up a whole range of possible kernel attacks that can allow local users to root your machine.

ewwwww!

cwizardone · 05-20-2011, 11:16 PM

Not a problem if it is a standalone box.

honeybadger · 05-21-2011, 12:28 AM

warning: compltetly off-topic.
Is it the real Pat Volkerding? Good Lord, it is mindblowing to know that you post in this forum. Really out of words to express my emotions. All I can really think of saying here is thankyou for slackware.

Nylex · 05-21-2011, 12:29 AM

Quote:

Originally Posted by SilverBack

warning: compltetly off-topic.
Is it the real Pat Volkerding? Good Lord, it is mindblowing to know that you post in this forum. Really out of words to express my emotions. All I can really think of saying here is thankyou for slackware.

It is indeed Pat. Several of the Slackware team are regular posters here.