Hi, you should have a look at how NWDSK does the network card detection and driver loading :-).
One FreeDOS way to do it would be to use PCISLEEP to list all PCI devices of the "network" category and use the new SET /E (or so) feature to put the first output line of PCISLEEP into an environment variable. Then you would indeed use DEVLOAD... You did not say why devload caused problems. Do things work with classic DEVICE lines in config sys or does GHOST load things in a completely other way? To boot a kernel of your choice, you can have a look at METAKERN. You could modify it to make the choice depending on some PCI scan results. But I doubt that this is what you want. You always want the same kernel, just different config sys lines. As said, it should even be possible to figure out how to do all loading later with DEVLOAD. Do make sure that enough memory is free - it might be the case that using BASH for your "which driver?" decision takes too much memory, so DEVLOAD cannot give the driver enough memory to load properly. Eric ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
