Re: [Freedos-user] How to unload a driver?
Hi, On Fri, Nov 4, 2022 at 2:48 PM dmccunney wrote: > > I did have utilities back when that I could use to optimize the > loading of TSRs. Most took memory when loading and initializing, but > that memory cuold be freed and only a small portion thaat was the > actual TSR needed to remain resident, so I got to play games h the > ortder in which TSRs loaded to leave space for the loading an > initialization of subsequent TSRs. That technique was not applicable > to drivers. For some TSRs, you can use these (mark / release) from TurboPower Software (Kim Kokkonen): * https://www.sac.sk/download/utilmisc/tsrcom35.zip * https://www.bttr-software.de/freesoft/system.htm#tsrcom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to unload a driver?
Some drivers might work DDL, DDU as well - https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/system/ddl/ On Fri, Nov 4, 2022 at 4:06 PM Robert Riebisch wrote: > Hi Michał, > > > I load drivers for SoundBlaster AWE64 by means of putting CTMM.SYS, > > CTSB16.SYS and CTCU.EXE in DEVICE= parameters in FDCONFIG.SYS. However, > > that leaves me with 570KB free. I know that I can free some of that > > memory if only I can unload the drivers once the card is configured. I > > need to have 600KB free in order to start some very strange games, like > > Wolf. No, not Wolfenstein. Wolf > > https://en.wikipedia.org/wiki/Wolf_(video_game) > > You could try UNISOUND instead. > > "UNISOUND can be launched without options, with optional command line > options and with/without a BLASTER/ULTRASND environment variable present > (before launch). It doesn't consume RAM. It is not a TSR, it doesn't > require mem extenders, XMS/EMS..." > > https://www.vogons.org/viewtopic.php?f=62=72553 > > (I never tried UNISOUND.) > > Cheers, > Robert > -- > BTTR Software https://www.bttr-software.de/ > DOS ain't dead https://www.bttr-software.de/forum/ > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to unload a driver?
Hi Michał, > I load drivers for SoundBlaster AWE64 by means of putting CTMM.SYS, > CTSB16.SYS and CTCU.EXE in DEVICE= parameters in FDCONFIG.SYS. However, > that leaves me with 570KB free. I know that I can free some of that > memory if only I can unload the drivers once the card is configured. I > need to have 600KB free in order to start some very strange games, like > Wolf. No, not Wolfenstein. Wolf > https://en.wikipedia.org/wiki/Wolf_(video_game) You could try UNISOUND instead. "UNISOUND can be launched without options, with optional command line options and with/without a BLASTER/ULTRASND environment variable present (before launch). It doesn't consume RAM. It is not a TSR, it doesn't require mem extenders, XMS/EMS..." https://www.vogons.org/viewtopic.php?f=62=72553 (I never tried UNISOUND.) Cheers, Robert -- BTTR Software https://www.bttr-software.de/ DOS ain't dead https://www.bttr-software.de/forum/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to unload a driver?
Hi! I load drivers for SoundBlaster AWE64 by means of putting CTMM.SYS, CTSB16.SYS and CTCU.EXE in DEVICE= parameters in FDCONFIG.SYS. However, that leaves me with 570KB free. I know that I can free some of that memory if only I can unload the drivers once the card is configured. I need to have 600KB free in order to start some very strange games, like Wolf. No, not Wolfenstein. Wolf https://en.wikipedia.org/wiki/Wolf_(video_game) A DOS forum thread discussing this online claims that some of those are only used for software mixing and concludes that you should get things working with only CTCM and AWEUTIL as well, so I guess you could test which of the 3 drivers mentioned in your setup are REALLY needed for your games. Also, you can use a boot menu to decide at boot time whether or not you want to load your AWE64 drivers. Then you can select the no-driver boot style for games such as Wolf which need more free DOS RAM :-) Also, it seems CTCU /S can be run in autoexec instead of config, which may be more convenient. CTCM = CreaTive Config Manager, AWEUTIL = relevant for MIDI emulation for real mode games etc., CTMM and CTSB16 might be components which are less necessary. Best regards, Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to unload a driver?
Hello, Alrighty, here's the entirety of my setup. I load drivers for SoundBlaster AWE64 by means of putting CTMM.SYS, CTSB16.SYS and CTCU.EXE in DEVICE= parameters in FDCONFIG.SYS. However, that leaves me with 570KB free. I know that I can free some of that memory if only I can unload the drivers once the card is configured. I need to have 600KB free in order to start some very strange games, like Wolf. No, not Wolfenstein. Wolf https://en.wikipedia.org/wiki/Wolf_(video_game) Best regards, Michał W dniu 4.11.2022 o 20:46, dmccunney pisze: n Fri, Nov 4, 2022 at 2:38 PM Michał Dec wrote: Hello, I'm loading a bunch of drivers during startup, but I'd like to try and unload them after all the setup is done. What \ command is for unloading drivers? I know LH and DEVLOAD are for loading. I don't offhand think there is such a command LH and DEVLOAD have the same purpose: load drivers and ?TSRs high to get them out of conventional memory. But in general, you wanted them present and available during your session, and didn't want to unload them. I do have a Unix machine which has an experimental capability to unload drivers, but it was experimental. Nowadays, the efforts are to have things loaded in user space, and unloadable if you no longer need what they do. What drivers are you loading in startup? A driver, by definition, provides access to hardware, and if you want to use the3 hardware you need the driver. I did have utilities back when that I could use to optimize the loading of TSRs. Most took memory when loading and initializing, but that memory cuold be freed and only a small portion thaat was the actual TSR needed to remain resident, so I got to play games h the ortder in which TSRs loaded to leave space for the loading an initialization of subsequent TSRs. That technique was not applicable to drivers. Tell us what you'reloading in startup? Maybe we can help optimize the process. Michał ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to unload a driver?
On Fri, 4 Nov 2022 15:46:44 -0400 dmccunney wrote: > I do have a Unix machine which has an experimental capability to > unload drivers, but it was experimental. Nowadays, the efforts are to > have things loaded in user space, and unloadable if you no longer need > what they do. Linux has been able to unload drivers (rmmod or modprobe -r) as far as I can remember (the 2.0.x days at least). Linux drivers are most definitely not in userspace unless it's a FUSE filesystem driver. There is even a system service that automatically unloads kernel modules that are unused after a while. FreeBSD also has a kldunload command. The drivers are not in userspace either. In DOS it's up to the driver to provide the unloading functionality. Ethernet packet drivers typically can. I know Realtek and 3com drivers can because I made myself a batch script to turn the network on and off in which I unload the packet drivers to free some RAM. I think mTCP drivers can be unloaded as well. --- WWW: https://metalpunks.info GPG: C90CAB7122AC1231 pgpb8nISKkqUE.pgp Description: OpenPGP digital signature ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to unload a driver?
n Fri, Nov 4, 2022 at 2:38 PM Michał Dec wrote: > > Hello, > > I'm loading a bunch of drivers during startup, but I'd like to try and unload > them after all the setup is done. What \ command is for unloading drivers? I know LH and DEVLOAD are for loading. I don't offhand think there is such a command LH and DEVLOAD have the same purpose: load drivers and ?TSRs high to get them out of conventional memory. But in general, you wanted them present and available during your session, and didn't want to unload them. I do have a Unix machine which has an experimental capability to unload drivers, but it was experimental. Nowadays, the efforts are to have things loaded in user space, and unloadable if you no longer need what they do. What drivers are you loading in startup? A driver, by definition, provides access to hardware, and if you want to use the3 hardware you need the driver. I did have utilities back when that I could use to optimize the loading of TSRs. Most took memory when loading and initializing, but that memory cuold be freed and only a small portion thaat was the actual TSR needed to remain resident, so I got to play games h the ortder in which TSRs loaded to leave space for the loading an initialization of subsequent TSRs. That technique was not applicable to drivers. Tell us what you'reloading in startup? Maybe we can help optimize the process. > Michał -- ___ Dennis ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
