Hi again, > /config/boot > /floppy > /hdd ...
I assume you mean /config/boot/floppy and so on: In DOS, configuration is stored in config sys, in autoexec bat, and possibly in configuration files for the drivers you load, but that depends on which drivers you load and who made those drivers. You usually cannot change it in any other way than by using another driver for the same device instead. If you know something you want to configure in DOS but which you cannot configure yet (via kernel or driver config options), let me know. Note that there are almost no DOS drivers for wireless, scanners and cams at all, and only drivers for generic things (keyboard mouse storage) of USB. > /programs/Administrator > /group/user This is your choice, you can put programs where you want them :-). > /GUI Same. I hope you will find a nice GUI. OpenGEM is classic, but there are others with more eye candy. Those typically have fewer programs made for them. > /mount Drives get drive letters, not mount directories in DOS. Sometimes SUBST / ASSIGN / ... can help to map between directories and drive letters but the drive letters always exist. > /network If you access a network drive, it also gets a drive letter if you have a driver. If not, you may have something like a FTP client to access files. I think there is a DOS version of the Samba SMBCLIENT which belongs to this category. > /Personal Files/Administrator/Archives > /Documents ... As above, this is your choice. But avoid long file names unless you know that your DOS programs can work with tham or you accept that some names will show up as /perso~1/admini~1/whatever for those DOS programs which cannot use long names. > In config directory i suggest to be drivers for every device, You can do that if you want to, sure :-). Because drivers are no fixed part of the system, you can install any driver you want in any place you want. > in mount directory to be the mount point for the network See above - normally you use drive letters instead. > and in the network to be protocols ipx, tcp/ip and something > like eDirectory or ActiveDirectory. This is not handled by the operating system. If you have a DOS web browser, then it can for example support TCP/IP, but that does not mean that your other network related software would also support TCP/IP... For those programs which use the popular Wattcp networking framework, they all use one shared configuration file called wattcp.cfg :-). I do not think that any DOS software exists which can read data from eDirectory, ActiveDirectory, LDAP or similar. Eric ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
