Of course it would be a waste of time to complain to faculty.
Similarly, messing with the properties of "cmd" seems flawed (assuming you got the terminology right) since that's a 32-bit program. What you really want to change are the properties of NTVDM, as it applies to the particular 16-bit program you're trying to run (I've no idea, I lost interest in the details long ago).
Right-clicking on your Turbo C IDE icon might get you there.
Finding a machine which "does it right", and searching the registry for entries which may indicate how Turbo C is run (and comparing them with the same entries on your machine) again may offer clues.
> int gDriver=3,gMode=1; //650x350
Mmm - what does your manual say?
Are they?pathtodriver specifies the directory path where initgraph looks for graphics drivers. initgraph first looks in the path specified in pathtodriver, then (if they are not there) in the current directory. Accordingly, if pathtodriver is null, the driver files (*.BGI) must be in the current directory. This is also the path settextstyle searches for the stroked character font files (*.CHR).
Further, are they in a directory structure which conforms to 8.3 notation all the way to the files?
What about checking whether the driver was successfully loaded, rather than assuming all is well?