Hi Kurt,
kernel.sys is a program (like exe), not a config file.
It does open c:\fdconfig.sys and if it does not exist
then it opens c:\config.sys instead. If neither is
found, it just runs c:\command.com and the default
activity of command.com is to run c:\autoexec.bat
So if your fdauto.bat
Eric,
I again tried putting the fdconfig.sys in drive 'c', first with the
c-oriented version; then with the d-oriented version.
Also tried editing the autoexec.bat in 'd' drive to : cfg=c:\fdconfig.sys;
everytime I execute autoexec.bat in 'd',
exactly the same thing happens; action taken
Hi Kurt,
Please do the following:
- put c:\fdconfig.sys on what both Win98 and FreeDOS call C:
- edit the SHELL or SHELLHIGH line in c:\fdconfig.sys to use:
SHELL=D:\FDOS\bin\command.com D:\FDOS\bin /E:1024 /P=D:\fdauto.bat
- now you use d:\fdauto.bat as the autoexec.bat for FreeDOS
- Win98
Eric,
Tried what you said. Put echo tags at beginning and end of fdconfig.sys;
even put them in the bat. Both showed
in the bat, but the fdconfig never executed, not in 'c' , not in 'd' any
which way, so long as fdos was not initially
installed in 'c'. It is obvious that fdconfig does execute if
Eric,
I should clarify: when Georg (of DOSUSB) said dos assigns the drive letter
to dosusb, he was emphasising
that *dos does the assigning* , that is, there is not much,if any, manual
control over it. Also, to be specific,
when DOSUSB works with the cdrom (in drive 'c')the whole thing is
