General information
Title:
DOS Window running under W2K - should it work?
I have to keep an old Dos FP2.6a app running but want to move it to a W2K server. It is unattended and basically sits there doing calculations and then it spits out a printout. It is now rarely used (once a month) but the company wants it left running in case they want to reprint an old calculation from years ago. So it is basically an app that runs in a loop, with a display screen, and it searches for printjobs and processes them.
It used to run on a dos-only workstation but their server room is really getting full and I would like to take it off that and have it run as a DOS box on one of their other application servers (along with their newer Win apps that also run unattended but with a display form).
Can I do this as an unattended app and will the DOS box "behave" properly ie. will it share processor time properly with the other Win apps or if it comes forward, will it hog the CPU time. I ask this because in my testing, some of the users said they were not always getting their Windows printouts properly or they had an occasional error. I am wondering if maybe the DOS app came to the front and then it caused problems with CPU sharing for the Win apps that were then in the background.
If it is supposed to work, are there any settings I need to make to make sure that the DOS app shares the CPU properly?
Albert
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only