Does anyone know how i can boot DOS and NWC3.0 from the harddrive.

So far I've done sys c:, which allows me to boot from harddrive.

But now I want to be able to start NWC OR Packet Driver/WWW from the command prompt.

I've made a www.bat file which basically allows me to setup my packet driver (ie. C:\driver\3c509 0x60)

but at times when I want to start NWC instead, I don't know how to do it (specifically, what I should do to activate ifshlp.sys from config.sys and HIMEM.SYS, etc)

If anyone knows how that would be great.

ALSO is it possible to have programs ran in Autoexec.bat style when I boot from Harddrive. (ie. CTMouse), can I somehow configure it so that the harddrive runs a .bat file on startup even though it is booting from Harddisk

Thanks a lot

Denton

I'm unfamiliar with Network Client 3.0 - but it seems as if it runs from DOS rather than instead of.

"is it possible to have programs ran in Autoexec.bat style when I boot from Harddrive"

Well, yes - you use autoexec.bat to load programs or even batchfiles - a batchfile can either be invoked using 'call' or you can just incorporate it into autoexec.bat

Device drivers are loaded by means of config.sys using the device= statement (or devicehigh). Himem.sys generally is loaded first - it's more of a memory manager than a driver, and certain conventions should be observed.

"even though it is booting from Harddisk"

Sure - these are odd questions, if you don't mind my saying so. Not much DOS experience?

Some DOS reading here and here

We have nothing against ideas. We're against people spreading them. - General Augusto Pinochet of Chile

Report Offensive Follow Up For Removal

Well, I don't have a lot of DOS experience, but i was relatively confused by your response what I want to know is:

Is there a way to run config.sys (ie. load device drivers) from the harddisk and encorporating it so that it will run before autoexec.bat.

What happens with NWC3 is that I insert floppy and it does everything for me, but when I execute autoexec.bat from C:\ it says that the device driver is missing and I just want to know how to load the device driver (from config.sys) before loading autoexec.bat.

Thanks again

Autoexec.bat executes automatically (hence the name) from the root directory of the boot drive. You don't need to (and probably shouldn't) run it from the command line

This is 'DOS 101' so to speak.

You refer to booting and running DOS from the hard drive as if it were an unusual practice. Booting from a diskette should only be necessary under certain circumstances, such as troubleshooting or as a method of installing an OS or booting multiple Operating Systems.

Device drivers are loaded from config.sys with the device= statement, as mentioned earlier - you need to be precise as to the name and location of the driver file, in accordance with DOS conventions.

Config.sys also runs automatically from the boot drive, prior to autoexec.bat

Much of this is covered in the links provided - possibly you could research DOS a bit more(?)

We have nothing against ideas. We're against people spreading them. - General Augusto Pinochet of Chile

Report Offensive Follow Up For Removal

No...i think i got it now

Thanks for the sites...it took me a while but i got it afterwards

Cheers

Sure - there's plenty of info out there on good ol' DOS - but you've got to have an understanding of the basics in order to configure your system to its best advantage.

Also of interest

Boot Process

We have nothing against ideas. We're against people spreading them. - General Augusto Pinochet of Chile

Report Offensive Follow Up For Removal

Good response JBoy, though NWC3 loads its base drivers thru CONFIG.SYS, and even unloading the drivers still leaves TSR's in memory hence it is difficult to run other software, due to lack of BASE 640K MEMORY.

NWC3 is covered at:

http://www.wown.com/j_helmig/dosclien.htm

Actually LANTASTIC is a better product than NWC3, but is not FREE!

Using Packet Drivers and associated software is the answer, but connecting to other O/Ses can be more difficult in a LAN, please look thru the following for lots of info...

http://www.mwpms.uklinux.net/index.htm

Yeah - I'm not that familiar with networking under DOS, but I keep hearing how 'hungry' those drivers etc. can be for low mem.

Just seemed that the OP was (more than) a bit unfamiliar with configuring the DOS startups.

Seems like he has a few options, but a bit of reading and experimentation is in order.

We have nothing against ideas. We're against people spreading them. - General Augusto Pinochet of Chile

Report Offensive Follow Up For Removal