Generally, if you have a mouse.com file, then that is put into the autoexec.bat. If you have a mouse.sys then that is put into the config.sys. You don't usually need a keyboard driver unless you have a non-standard keyboard; if you do, the procedure will be similar to that for the mouse.
And at the DOS prompt, try typing 'help', all the information on autoexec.bat and config.sys is available in the help files. Both are simply text files, Config.sys is loaded first and contains instructions to load resident device drivers and configure them, then 'autoexec.bat' is processed line by line exactly as though the lines had been typed at the keyboard.
To see if you have a mouse.com file, just type 'dir'. It will list all the files in the current directory as long as their hidden attribute isn't turned on.
yeah the software of a machine ..... its the software of a printing machine's A.R.C to control the registrations of the color ......... Kesai is the manufacturer of that software interface
yeah the software of a machine ..... its the software of a printing machine's A.R.C to control the registrations of the color ......... Kesai is the manufacturer of that software interface
as indicated in previous posts by other mebmers , check whether you have mouse driver already installed.
(it is in config.sys) file.
if already installed , then you might have connected mouse to com2 instead of com1 , i guess.
You didn't mention at all, which function you are exactly missing. You initially asked for mouse and keyboard driver, but I guess the keyboard is working?
the keyboard is not working at the software interface or for the software interface ...... but it does work when i exit the application (software) then a black screen comes up (i.e. DOS) and here you can use your keyboard & the keyboard works fine at DOS environment ............
This suggests, that your software uses a special keyboard driver or is expecting a particular hardware. I didn't came across this problem for keyboards, but I remember that early DOS applications have been interfacing the mouse directly though COM ports, relying on specific mouse products and a setup in the software.
In other words, the initial question "how to load drivers..." is probably missing the problem. Finding out the exact hard- and software requirements of your software is the necessary first step.