RE: Small boot problem.

True. But only AFTER Windows is loaded.

If you want to boot to the Command Prompt and use the CD ROM ( say to run Windows Setup ) you will not be able to do it without the config,sys and Autoexec.bat. A boot from a power off does not use the DOSSTART.bat.

If you have the Windows setup files on the HD then you are OK.

I myself do not do it that way but I know users that do.

The Autoexec.bat also may have DOS audio settings in it.

This is why I mentioned in the other thread about being sure that you do not use DOS.

BillyBob

 

You have to set a separate DOS environment for DOSSTART.pif
No Win OS loaded.
regards

 

The DOSSTART.bat does not come into play until Windows is restarted in the MSDOS MODE.

It is not loaded at boot up.

The MSDOS Mode is actually a Dual Boot. It may switch the Config.sys and Autoexec.bat and loads the DOSSTART.bat. Then when you EXIT the MSDOS Mode it switches every thing back. And anything in the DOSSTART.bat is out of the picture again.

I just checked to make sure but, on my Wifes' machine there are two config and autoexec files. One with .sys and .bat and one each with .DOS extention. The ones with the .DOS ext are the ones used when you restart Windows in the MSDOS Mode. NOT THE COMMAND PROMPT at boot up

Yes you can set up a different enviroment. But is involves the Config.sys. the Autoexec..bat and the DOSSTART.bat.

And that new enviriment had better be RIGHT/CORRECT or you may be re-installing Windows to get things back. I have been that route

And if you do happen to be running some DOS programs they may require;

HIMEN.SYS,
EMM386.exe
FILES = 50

And these can ONLY be loaded via the CONFIG.SYS.

I still have couple of older DOS programs that I run in XP Pro.

They WILL NOT run if I wipe out the CONFIG.SYS.

I also installed a SB Live Audio card yesterday. It put the DOS settings into the Autoexec.bat

DOS IS NOT as dead as Microsoft would like us to believe.

It relates strictlly to how the machine is set up and/or used.

As an experiment I renamed the Config.sys on my Wifes' machine ( 98SE ) and three of her DOS programs DID NOT run.

But one thing about this XP Pro machine that may make a difference. I put XP Pro overtop of 98SE.

Again. If you do not use DOS programs or switch to the MSDOS Mode then forget the two files.

But if you do do either of the above the files are needed.

BillyBob

 

Do not understand that BillyBob. I can boot from an ERU floppy
and run dosstart from it.
So where does Windows OS come into the equation ?
regards

 

merlin, BillyBob,

I generally agree with you both, but I think you are talking past (not to) each other.

But I don't wish to interfere. I would just like to know what an ERU floppy is, and what is the point of running dosstart if you are already in dos?

I costomize my startup disks, adding scsi drivers (2) and favorite utilities (2-3), so don't reboot to dos on hdd except for VERY simple jobs.

 

I think we are going in different directions here.

The ERU ( startup disk ), the Config,sys and Autoexec.bat and the DOSStart.bat are used in three different places.

The startup disk is just that. A bootable floppy. Cabable of loading what ever one wishes it too. ( DOSwise )

The config.sys and Autoexec.bat are used on a normal boot of the machine.

THe DOSStart.bat is only used when restarting Windows into the MSDOS Mode.

In your case there should be no need.

But if you are in Windows and restart to the MSDOS Mode it may be needed to load that ( or some of that ) stuff.

THe DOSStart.bat is only meant to load DOS items when restarting Windows into the MS DOSMode. And unloads same when exiting back to Windows.

It comes into play when you are running Windows and restart into the MSDOS Mode.

BTW. I mis-configured DOSStart.bat will stop Windows from restarting in the MS DOS Mode. Or it will cause errors messages just like the Autoexec.bat can.

BillyBob