Re: [Freedos-devel] Rebooting without restarting the PC
You may have to take a page from the Win98 boot floppy, if possible. If you've ever watched it load, it cycles through several drivers trying to find the CD-ROM...especially in the SCSI territory. Date: Mon, 26 Mar 2007 12:35:38 +1000 From: adam-nos...@servfire.net To: freedos-devel@lists.sourceforge.net Subject: Re: [Freedos-devel] Rebooting without restarting the PC I'm not sure why devload causes problems, shouldn't be running out of memory (loading himem.exe and umbpci.sys), yeah, it's the MS Protocol Manager (protman.dos), a slightly modified dis_pkt.dos from the original boot disk, as well as whatever NDIS driver the card should use. All loaded with classic DEVICE(HIGH) lines in config.sys and Ghost picks it up. Do the same with DEVLOAD and it just doesn't detect them (can't pick network options, only gives local). I'll play around with it a bit more, as well as looking at the NWDSK to see how they're doing it. And yeah, I don't think METAKERN will do what I want, but looks to be an interesting program in itself, so I'll keep it in mind. Thanks Eric Auer wrote: 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.phpp=sourceforgeCID=DEVDEV ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel _ Rediscover Hotmail®: Get e-mail storage that grows with you. http://windowslive.com/RediscoverHotmail?ocid=TXT_TAGLM_WL_HM_Rediscover_Storage2_042009-- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Rebooting without restarting the PC
All packet drivers are executable, so devlçoad should not be used. All return errorlevel if not installed, All don't install if another is installed. So... you can simply try to load them all in sequence and only the good one will get installed. I have in fact tested this, give it a try :) Alain Adam Smith escreveu: Hey guys, Been puzzling over a few things for a boot disk image I'm making. Currently I've got the image booting, select your network card, loads ghost (or whatever I want), all fine. But, as I'm looking for this to be as automatic as possible, I've been wondering how I can auto detect the network card. Now, I could just have a separate disk image for each card and load whichever is necessary, but I figured there could be a cleaner way. I noticed when I installed FreeDOS that it does a sort of PCI ID detection on the network card drivers, but not all the network cards I'm using have free drivers that load as cleanly as crynwr drivers do. So I tried to use devload to load them up in my detection script, but for some reason devload doesn't quite load them the same way and whatever ghost does to initialize them, it doesn't detect them. So I've had another idea. Seeing as I'm already doing dynamic script rewrites with DJGPPs bash.exe, I could have the image boot up once (using pxe/isolinux + memdisk), do the PCI ID detection, write the appropriate config.sys out, then reload the system without hard rebooting it, keeping the memdisk hooks active and running, so that the kernel reloads and runs the dynamically modified config.sys loading everything cleanly. Anyway, my few attempts at writing a loader didn't go too well. All I was doing was attempting to load the boot sector off the floppy image and then jump to it, but I don't know enough about the various systems (or enough asm) to get this working well and so I was wondering if anyone had come across a program that did this, or if you're able to knock something up really quick (or are up for the challenge or whatever). I've seen similar things done like this before, most notably is the Linux Kernel Module that loads a new kernel image into memory and restarts the kernel without hard rebooting (was mentioned as handy for those servers with slow SCSI spinup times). If anyone can help me out, or point me in the right direction for writing my own, let me know, I'm subscribed so if you want to reply to the list as well. (If anyone has any other ideas for loading the network stack that ghost needs outside of config.sys I'd love to know as well, ghost version in particular is 8.2) Thanks - 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.phpp=sourceforgeCID=DEVDEV ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel - 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.phpp=sourceforgeCID=DEVDEV ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Rebooting without restarting the PC
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.phpp=sourceforgeCID=DEVDEV ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Rebooting without restarting the PC
I'm not sure why devload causes problems, shouldn't be running out of memory (loading himem.exe and umbpci.sys), yeah, it's the MS Protocol Manager (protman.dos), a slightly modified dis_pkt.dos from the original boot disk, as well as whatever NDIS driver the card should use. All loaded with classic DEVICE(HIGH) lines in config.sys and Ghost picks it up. Do the same with DEVLOAD and it just doesn't detect them (can't pick network options, only gives local). I'll play around with it a bit more, as well as looking at the NWDSK to see how they're doing it. And yeah, I don't think METAKERN will do what I want, but looks to be an interesting program in itself, so I'll keep it in mind. Thanks Eric Auer wrote: 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.phpp=sourceforgeCID=DEVDEV ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
