In Windows XP when I print to the printer ( LPT1:), from DS, then my jobs
just sit in the print queue-they do not print.
Sometimes it helps when I change the print processor from 'Raw' to 'Text'.
But when I restart the computer, it no longer works.
I can get it to work sometimes, but when I restart the computer it no longer
works.
Any ideas that do not involve printing to a file and then printing from a
third party program.

"Sarah" wrote in message
In Windows XP when I print to the printer ( LPT1:), from DS, then my jobs
just sit in the print queue-they do not print.
Sometimes it helps when I change the print processor from 'Raw' to 'Text'.
But when I restart the computer, it no longer works.
I can get it to work sometimes, but when I restart the computer it no longer
works.
Any ideas that do not involve printing to a file and then printing from a
third party program.

You might check LPT1 status, to see if it's been re-routed or
otherwise reports problems:

mode lpt1 /status

As a workaround, you could try using NotePad (standard part of Windows,
not a third-party program) to print a file instead of redirection to LPT1. This
will operate through the usual Windows printer. Notepad should accept
a /p command line switch to print a textfile (usually has to be less
than 64Kbytes).

Typical command-line syntax (path to Notepad shouldn't be necessary):

start /min Notepad /p YourFile.txt

DS in XP? Where is it?
I don't got it & I wan't it
You mean a command prompt?

"William Allen" <_wa_@email.comwrote in message
news:42a8a53f$0$1711$ed2e19e4@ptn-nntp-reader04.plus.net
"Sarah" wrote in message
>In Windows XP when I print to the printer ( LPT1:), from DS, then my
>jobs
>just sit in the print queue-they do not print.
>Sometimes it helps when I change the print processor from 'Raw' to
>'Text'.
>But when I restart the computer, it no longer works.
>I can get it to work sometimes, but when I restart the computer it no
>longer
>works.
>Any ideas that do not involve printing to a file and then printing from a
>third party program.
>
You might check LPT1 status, to see if it's been re-routed or
otherwise reports problems:

mode lpt1 /status

As a workaround, you could try using NotePad (standard part of Windows,
not a third-party program) to print a file instead of redirection to LPT1.
This
will operate through the usual Windows printer. Notepad should accept
a /p command line switch to print a textfile (usually has to be less
than 64Kbytes).

Typical command-line syntax (path to Notepad shouldn't be necessary):

start /min Notepad /p YourFile.txt

"BruceM" wrote in message
DS in XP? Where is it?
I don't got it & I wan't it
You mean a command prompt?

No, I prefer the term MS-DS. "Command prompt" is less helpful (see below).

DS, or more properly MS-DS, is supported within parts of the software
normally supplied with Windows or MS-DS PCs, such as an old x86 running
MS-DS 1.0 - you can call it a "command prompt" if you wish. However,
that's not a particularly useful nomenclature since many items of software
present their interface as a command prompt, for example FTP or TelNet,
neither of which are sensibly called "MS-DS" and both of which can
be used in Windows XP as far as I am aware. The command-line way of
working is not unique to MS-DS, nor to Dos Virtual Machines in
Windows 95/98/ME (uses chip V86 mode), nor MS-DS windows in
Windows NT/2000/XP.

The presence of MS-DS software is why XP can interpret an INT 21 call.
And, of course, some call it an "emulation". However, MS-DS 1.0 on an
old x86 is only an "emulation" - or better, a metaphore - created in software
running on the chip hardware. do people suppose there's a tiny MS-DS
homunculus (perhaps reading from an ancient MS-DS manual), who lies
hidden inside each x86 chip obediently providing his handy (and sometimes
pejoratively termed) "same-day service" for MS-DS INT 21 calls?

Supported MS-DS syntax varies with version from MS-DS 1.0 all the
way through MS-DS 6.22, Windows 95/98/ME, to Windows NT/2000/XP.
Windows Longhorn will also support MS-DS syntax, much as Windows
XP does at present, since the intention is to retain CMD.EXE (and VBScript)
alongside the planned MSH (Microsoft SHell - code-named Monad) which
will add a C++ like syntax in a somewhat Unix-style shell-scripting language.

The later 32-bit systems (including Windows 95/98/ME in the GUI) need to
"thunk" or otherwise kludge the 16-bit address space that MS-DS programs
inhabit, but much MS-DS syntax remains surprisingly constant throughout
the S development. For example, as far as I can see at a quick glance, all the
MS-DS Batch syntax examples in The MS-DS Encyclopedia (see note)
are usable all the way through to Windows XP. You can construct examples
specific to a particular S if you wish, but that applies to all S development.

You have an answer you my question or you just like splitting hair over
terminology?

''
is a site or group?

LPT1 is not rerouted.
I am using your suggestion and printing to a file. Then I print the file
with NTEPAD/P. The problem is that there are chr$(12) in the file to tell
it to form feed-notepad is not interpreting these-it just prints the
character and does not form feed.

The net use did not help. The job goes into the print queue, but it never
prints. After a few minutes the data deletes itself. In the past I would try
changing the Print Processor to RAW, but in these case it does not help.

The net use did not help. The job goes into the print queue, but it never
prints. After a few minutes the data deletes itself. In the past I would try
changing the Print Processor to RAW, but in these case it does not help.