Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I need help in getting the right configuration for my config.sys and autoexec.bat files in Win3.1. I'm trying to get it to read my CD-Rom without having to use a boot disk to start-up. My files are currently configured as follows:
AUTOEXEC.BAT
@ECHO OFF
MSCDEX /D:BANANA /L:R
C:\DOS\SMARTDRV.exe
PATH=C:\DOS;C:\WINDOWS;
SET TEMP C:\WINDOWS\TEMP
SET IEPPP=C:\IEXPLORE
C:\WINDOWS\WINCONFIG.SYS
DEVICE=C:\WINDOWS\HIMEM.SYS
Can someone tell me what's missing??? I know there should be more included with the config.sys file, but not sure what it is.

You need a cd driver loaded in config.sys which is what the mscdex (in autoexec.bat) will control.
Similat to;
DEVICEhigh=e:\command\MTMCDAI.SYS /D:bananaYour path/driver will differ of course.

Yeah, what Dan said ;-)
That's a pretty empty config.sys - and it doesn't do much good *just* to load himem.sys
device=c:\dos\himem.sys
device=c:\dos\emm386.exe noems
DOS=HIGH,UMB.. is the basic memory management setup.
Of course, you'll need to load your CD driver in there as well - the devicehigh= statement only works *after* himem & emm386 are invoked in config.sys.Good luck.

Thanks for the suggestions! I tried something a little different, but it worked. I formatted the HDD, then used XCOPY from the boot disk to load the entire boot disk to the root directory. After that I loaded Win3.1 and edited the AUTOEXEC.BAT files to include the line: C:\WINDOWS\WIN. I removed the boot disk, restarted and everything came up fine. I did the above because I started to get impatient and wanted to get this thing up and running (it's for my sister). :-)

Well... ok, as long as it worked - although you could have used the 'sys' command - I'm somewhat surprised that you were able to successfully transfer the system with xcopy.
So, CD drive up & running too?

Hey jboy! (OK, so I snuck in here for a peek after I mailed you, but I am off to bed shortly.) ;>)
new_guy,
Yeah, I'm as well kinda surprised xcopying worked to get the HDD up. System files have to be in a certain place on the disk to make it bootable. Not to mention the paths etc would have to be edited in config.sys and autoexec.bat. You sure???

Yep, I'm sure. I couldn't believe it worked either, but I was trying different things until I got a response to the initial post. I first transferred the system using "A:\SYS C:". Then I used "A:\XCOPY A:\XCOPY.exe C:\". Then I used "A:\XCOPY A:\*.* C:\" to get the rest of the files transferred over. It asked if I wanted to overwrite the "COMMAND" file, which I answered "no" and it finished transferring everything else. After rebooting, it comes up just like you're using the boot disk. Of course, I had to edit the "autoexec.bat" file and add "win" to boot up Win3.1 automatically, but it's up and running now (reading the CD-Rom fine and everything).

Glad you got it going!
Yeah, well, since you transferred the system files *first*, sure no problem.
I have heard of folks successfully copying the system over (I think that they got lucky though), but DOS6xx versions of xcopy won't do files with the hidden or system attributes, afaik.
Myself, I've only used the DOS setup program once (back in '94), after that, just 'sys' and dump the external files to c:\DOS with a cable, then configure the startup files.
Whatever works :)

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |