Category : System Diagnostics for your computer
Archive   : DDARP120.ZIP
Filename : DDARP.DOC

 
Output of file : DDARP.DOC contained in archive : DDARP120.ZIP


DDARP v1.2

Driver Display And Rename Program

-----

Rob Stuntz
Mt. Prospect, IL.

6-28-92

Compuserve : 71043,117
GEnie : R.STUNTZ

Chicago Megaphile (Spitfire BBS)
312-283-4035 : Rob Stuntz

-----

DDARP is a program that can display the installed device
drivers in memory and/or rename a driver in memory. I wrote
this program because a game of mine would not run if it
detected my debugger's device driver in memory. I simply
renamed the device driver in memory and then the game did not
detect it anymore. Of course, when I was done playing, I
renamed the driver back to what it was originally. As I didn't
feel like manually editing memory every time I played the game,
a program was born, DDARP.

A quick explanation of the program's syntax.



Display drivers
---------------

C:>DDARP

If you want to display the name of the installed device
drivers, just run DDARP with no command line arguments. What
you will see is :

Address: this is the address of the driver's header.

Name: the name of the driver. If the driver is a block device,
this field will be the drive letter(s) associated with
this driver. Character drivers will have an eight
character name, which can include trailing spaces.

Type: will be either 'blk' or 'chr' depending on the
driver type (block or character).

Driver Attribute: this is a 16 bit value describing the
driver's capabilities.

Driver File: if the driver has it's own memory control block
(MCB), then the name of the file that it came from is
shown in this column.


The drivers are displayed in ascending order.

Alternately, you can include a command line argument to specify
the order in which to display the drivers.

/i Display in ascending order. This is the default
order. Included in case you're used to using
command line arguments.

/d Display in descending order.

/c Display in the order the drivers are arranged on
the driver chain.



Rename a driver
---------------

C:>DDARP

If you want to rename a driver, should be the name
of the driver you want to rename. is what you want
to rename it too. For example, to rename LPT1 to PRINTER1 :

C:>DDARP LPT1 PRINTER1

You will get a message about whether the rename was successful
or not. When renaming, DDARP starts at the beginning of the
driver chain and searches for . All driver name's are
in uppercase, however, you don't have to type your arguments in
uppercase. Only character type drivers can be renamed.

Also, if you want to rename a driver to all spaces, specify
=BLANKS= as . Since you can't specify a name of
eight spaces on the command line, =BLANKS= will change the
driver's name to all spaces (20h,20h,20h,20h,20h,20h,20h,20h).
=BLANKS= can also be used as .


Other Options
-------------

If you specify /A on the command line, a brief explanation
of the driver attribute word will be displayed. A good
programming book would probably describe these bits in greater
detail.

Specifying /?, ?, or /H on the command line will display a
small help screen on the program's syntax.


Comments
--------

This program was written on a 40Mhz 386dx running MS-DOS v5.0.
Also, make sure you can get out of any trouble you might cause
by renaming a driver. I wouldn't want you to blame me for loss
of data .... :).

And, I'm open to any comments or suggestions you might have
concerning this program.

Rob



Version History
---------------

v1.0 6-20-92 initial release
v1.1 6-22-92 added /i, /c, & /d command line arguments
v1.2 6-28-92 verify file name has valid chars if gotten from
MCB



  3 Responses to “Category : System Diagnostics for your computer
Archive   : DDARP120.ZIP
Filename : DDARP.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/