Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.msdos.batch    |    Fun with MS-DOS batch files    |    42,547 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 42,532 of 42,547    |
|    JJ to All    |
|    Re: So much Windows talk..    |
|    28 Oct 25 11:49:22    |
      From: jj4public@gmail.com              On Tue, 28 Oct 2025 01:22:17 +0100, Eirik Øverby wrote:       > JJ wrote:       >       >>Whatever happened here, this is still an MS-DOS group. You can still       >>ask/post about MS-DOS batch file. It's at least, why I'm still here for.       >       > Cool, then here's a question: I've been spending some (too much) time writing       > myself an "init"-type system of .bat files for my DOS machines. It's not as       > advanced as it might sound, but it allows me to keep config files for various       > NICs, sound cards and other hardware around, and then I copy the ones that       > apply to a given piece of hardware into the "active" directories for the       > hardware type, and it does its thing.       >       > Now having seen some of the samples I've learned from, it occurs to me       someone       > must have done something similar before, and re-inventing this particular       > wheel may not be the best use of my time.       >       > Has such a thing ever been done, and achieved any significant popularity? In       > other words, would there be such tools out there already, with a library of       > "driver wrappers" and such?       >       > If not, and if there is any interest, I'd be happy to publish what I've got       > (some of it can be downloaded from the museum URL below).       >       > Take care,       > /Eirik              I can't remember which, but I once used a DOS boot CD where its startup       script provides a menu to select which ATAPI/SCSI/USB CD-ROM driver to load.       But that's only for CD-ROM. Not for multiple type of devices. And I haven't       seen any boot media which include many type of devices and device models.              Driver configurations script would be useful as a reference when the driver       documentation is not available. It'll act as a hint on how to properly use a       specific driver, as some may require other driver to be loaded first. Aside       from how to properly configure it.              Though, it'd be more useful if all of the drivers are included in the       package, as sometime is a pain to find driver for a specific device. While       someone may already collected device drivers in one package, I doubt it       includes the script(s) to load each of them.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca