Re: [Freedos-user] clarify dualboot 4.
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 would run while fdconfig.sys would be ignored, it would be a quite odd combination. You should also use F8 at boot to do things step by step so you can find out what is really going on. Eric 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 fdos installed to 'c'. I suppose this is the doing of 'kernel.sys', which does not show in plain text editor; I have a couple of hex editors, but that doesn't seem to work, either. Can windows sysedit be used? - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] clarify dualboot 3.
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 apmdos,bad command or filename,bad command or filename. Finally, I realized that if I completely remove 'fdconfig.sys from both 'c' and 'd' drives, that is, everywhere, and again execute the bat in 'd', there is no difference whatsoever! This means that the autoexec.bat completely ignores the fdconfig under these circumstances(fdos not in 'c') but the config in 'c' is empty, it being in w98. So, where does the bat get hijacked to, and why does it not happen when the fdos is installed in 'c'?! I mean for a fact, the bootup options are in the fdconfig! kurt-completely-puzzeled, [EMAIL PROTECTED]. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] clarify dualboot 3.
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 can keep using c:\config.sys and c:\autoexec.bat and c:\command.com for itself, they can be the Microsoft files :-) - all FreeDOS files *except* C:\fdconfig.sys can be in D:\FDOS\ now (depending on how you boot, kernel.sys can be on C:\ or D:\ here) - remember that BOTH fdconfig.sys and fdauto.bat can contain PATH setting commands, make sure to replace C:\FDOS\BIN\ etc into D:\FDOS\BIN\ and so on there ;-) 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 apmdos,bad command or filename,bad command or filename. You can also hit F8 at boot to do things step by step so you can watch what happens / in which directories things go wrong. Finally, I realized that if I completely remove 'fdconfig.sys from both 'c' and 'd' drives, that is, everywhere, Then FreeDOS will use c:config.sys which is the Microsoft one. and again execute the bat in 'd', there is no difference whatsoever! This means that the autoexec.bat completely ignores the fdconfig under these circumstances How do you execute it? By typing d:\autoexec.bat at the prompt? That is not the way you would normally run it... If it is not automatically run from (fd)config.sys then you might miss part of the configuration that it expects to be present, too... (fdos not in 'c') but the config in 'c' is empty, it being in w98. Empty? Not sure, but note that Win98 and FreeDOS use different syntax for some of the config.sys commands! If there is no SHELL line in (fd)config.sys then the default is to run C:\COMMAND.COM which should be the Microsoft version and that is not FreeDOS :-p So, where does the bat get hijacked to, and why does it not happen when the fdos is installed in 'c'?! I mean for a fact, the bootup options are in the fdconfig! See above... Note that /P=FILENAME is only one of at least two ways to tell FreeDOS command.com (FreeCOM) to use another file instead of c:\autoexec.bat, see command /? and the dos docs. Also note that Microsoft command.com ignores /P=FILE options(?) Eric - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] clarify dualboot 4.
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 fdos installed to 'c'. I suppose this is the doing of 'kernel.sys', which does not show in plain text editor; I have a couple of hex editors, but that doesn't seem to work, either. Can windows sysedit be used? kurt , [EMAIL PROTECTED]. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] clarify dualboot.
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 automatic; that is, the DOSUSB drive is assigned to 'd', and the cdrom gets bumped to 'e'. Finally, the neato flash driver was designed for w98, and it works better than the more common ones that have been mentioned; maybe it can be made to work in dos. If you are that interested, I will have to search for it's url(it's around here somewhere). kurt, [EMAIL PROTECTED]. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user