Thread View: borland.public.install.vdbase
3 messages
3 total messages
Started by fnbr
Mon, 07 Dec 1998 00:00
Print Capture
Author: fnbr
Date: Mon, 07 Dec 1998 00:00
Date: Mon, 07 Dec 1998 00:00
24 lines
1458 bytes
1458 bytes
We recently moved our NOS to Windows NT 4.0 (clients run Win 95). We have a very large library of dBASE IV 2.0 programs that we must continue to run. Many of the print jobs now need to start... "set prin to \\domain\printer=port" We are using HP DirectJet print servers, so there is no local port. When we issue this command, it creates a print capture. dBASE IV expects the job to end with "set prin to" command. This crashes the local computer. The only way to end the print job is "set prin to lpt1" as it is a valid, local device. Even if we end the print job as "set prin to nul", it crashes. Also, nothing seems to release the capture. The only way is to go thru the printer set-up under Win 95 (or run net use statement). The net use statement hangs quit often. Is there any work-around for dBASE IV 2.0 under Windows NT to end the print job without capturing yet another port, and, truly end the capture. Thx alot, Brian G. Florida New Business Report 1-800-635-2639 E-Mail: brian@fnbr.com
Re: Print Capture
Author: Romain Strieff [TeamB]
Date: Tue, 08 Dec 1998 00:00
Date: Tue, 08 Dec 1998 00:00
28 lines
1672 bytes
1672 bytes
In article <74hfcm$8f64@forums.borland.com>, fnbr politely paraphrased... > > We recently moved our NOS to Windows NT 4.0 (clients run Win 95). > We have a very large library of dBASE IV 2.0 programs that we must continue > to run. > > Many of the print jobs now need to start... > "set prin to \\domain\printer=port" > We are using HP DirectJet print servers, so there is no local port. When we > issue this command, it creates a print capture. dBASE IV expects the job to > end with "set prin to" command. This crashes the local computer. The only > way to end the print job is "set prin to lpt1" as it is a valid, local > device. Even if we end the print job as "set prin to nul", it crashes. > > Also, nothing seems to release the capture. The only way is to go thru the > printer set-up under Win 95 (or run net use statement). The net use > statement hangs quit often. > > Is there any work-around for dBASE IV 2.0 under Windows NT to end the print > job without capturing yet another port, and, truly end the capture. > Did you try CLOSE PRINTER? -- Romain Strieff [TeamB] Please read this newsgroup guide below before posting on the private Inprise newsgroups. http://www.inprise.com/newsgroups/guide.html --
Re: Print Capture
Author: fnbr
Date: Wed, 09 Dec 1998 00:00
Date: Wed, 09 Dec 1998 00:00
43 lines
2005 bytes
2005 bytes
Romain, Thanks for the idea -- however... Close Printer didn't work (it's only for "set printer to filename" commands). Any other ideas? Thx, Brian Romain Strieff [TeamB] wrote in message ... >In article <74hfcm$8f64@forums.borland.com>, fnbr politely paraphrased... >> >> We recently moved our NOS to Windows NT 4.0 (clients run Win 95). >> We have a very large library of dBASE IV 2.0 programs that we must continue >> to run. >> >> Many of the print jobs now need to start... >> "set prin to \\domain\printer=port" >> We are using HP DirectJet print servers, so there is no local port. When we >> issue this command, it creates a print capture. dBASE IV expects the job to >> end with "set prin to" command. This crashes the local computer. The only >> way to end the print job is "set prin to lpt1" as it is a valid, local >> device. Even if we end the print job as "set prin to nul", it crashes. >> >> Also, nothing seems to release the capture. The only way is to go thru the >> printer set-up under Win 95 (or run net use statement). The net use >> statement hangs quit often. >> >> Is there any work-around for dBASE IV 2.0 under Windows NT to end the print >> job without capturing yet another port, and, truly end the capture. >> >Did you try CLOSE PRINTER? >-- >Romain Strieff [TeamB] >Please read this newsgroup guide below before >posting on the private Inprise newsgroups. >http://www.inprise.com/newsgroups/guide.html >--
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads