I'm getting ready to install a Clipper 5.2E application on a Windows 2000 machine. It has been running for years on a W/98 machine. I am new to W2K and am not sure how to set up the DOS environment for the app.
I'm knew to W2000 also but I be glad to share what I can with you.
1) Set your file handles and environment in config.nt and autoexec.nt _not_ config.sys and autoexec.bat.
2) Printing can be a bear sometimes. W2000 does not support capturing printer output as was previously set in the details of the printer properties. If your app is used on a network you can "capture" you printing port by issuing a command like Net Use Lpt1 \\MySharedPath\MySharedPrinterersistent
This can be applied to whatever port being used--lpt1, lpt2, etc. Place this in your login script or wherever your administrator does the system configurations. Actually, you can just type that in from the DOS command prompt and it will work. Also, there was a very good tip given a few weeks ago about printer wait states--refer to that.
3) Be sure the printer software supports DOS printing! This one gives me more problems than anything else. Even if you have a local printer it still must support DOS printing. Remember the checkbox for the option "Will this printer be used for DOS applications?" or something to that effect. Be sure to say "Yes" or you won't have a DOS printing port. I haven't found a way around this yet, perhaps someone else has and will share it with us.
4) A simple test for DOS printing compatibility is to open a DOS box.(Run cmd or command.com) On the keyboard type DIR>LPT1 and if no errors are shown you will probably have to form feed the printer to see the output. Other simple tests include COPY SOME.BAT LPT1, etc.
5) Some environment adjustments can be made in the properties window of the shortcut or the PIF. The size of the window, to run in a window, etc. (See also FAQ on this)
Off hand, this is about all I can think of. Hope it is of assistance. If you have questions...you know the drill.
Everything David says is good.
Also look out for Clipper app hogging the CPU. I have a fix for this and I believ there is one on the Blinker site.
email me : pck@tokleyhiggs.freeserve.co.uk
Phil
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.