UNSOLVED

ohdear

updated

23 years ago

O

ohdear

9 Posts

0

536

February 21st, 2004 14:00

run_time error R6009. config.sys and autoexec.bat

Help required please.

Dimension XPS T700r running Windows 98 SE

On shutdown get following error message;

run_time error R6009
-not enough space for environment
Press any key

Doesn't appear to be causing too much trouble but I don't know what may be
happening that I am not aware of.

Was told it may be due to the config.sys and autoexec.bat files.

Can anyone point me in the right direction to find out exactly what should be
in those files and what the order of priority should be.

I've found loads of information about how to edit those but not what to edit
them to.

Any help would be enormously appreciated.

I've been told to suppress some of the entries in those files and then see
whether the problem still occurs and so on until either it works or I kill my
machine completely, but surely there is a more reliable way of troubleshooting
other than trial and error.

Thanks for any takers on this one - and please don't get too technical
  • Denny Denham

    2 Intern

    •

    18798 Posts

    200

    0

    Posted February 21st, 2004 15:00

    ohdear,

    If you have a SoundBlaster audio card, see if this helps (taken from the long thread here):

    "How do I disable Sound Blaster 16 emulation for DOS?
    Go into your system properties in the Control Panel. Open the Device Manager tab, and scroll down to Creative Miscellaneous Devices. Click in the plus sign to display the list of devices. Click on Creative SBLive! SB16 Emulation, and click the Properties button at the bottom of the window. On the General tab, click in the check box labeled 'Disable in this hardware profile'. Then click OK. A red 'X' will appear next to the Creative SBLive! SB16 Emulation to indicate it is disabled. Early driver versions left odd drivers in the config.sys and autoexec.bat files that loaded into memory even if emulation was disabled. Make sure you have the latest drivers. Removing the device will only result in it being re-enabled on reboot. "

    Message Edited by Denny Denham on 02-21-2004 09:36 AM

  • ohdear

    9 Posts

    200

    0

    Posted February 21st, 2004 17:00

    Thanks Denny I understand what to do but I'm puzzled as to why this should occur at all. What would cause it to play up all of a sudden? Thanks.