dbTalk Databases Forums  

PDOX 4.5 PRINT FILE LPT3 "not enough disk space"

comp.databases.paradox comp.databases.paradox


Discuss PDOX 4.5 PRINT FILE LPT3 "not enough disk space" in the comp.databases.paradox forum.



Reply
 
Thread Tools Display Modes
  #21  
Old   
psmart
 
Posts: n/a

Default Re: PDOX 4.5 PRINT FILE LPT3 "not enough disk space" - 12-13-2006 , 05:04 PM






Further developments - We've had another "incident", this time without
2GB fix, and with the revised implemention that uses PRINT FILE to a
buffer: When COPYing the buffer file to LPT3, only the first part of
the file goes to the (network) printer. The rest is lost, and the
print queue is empty.

At the time of the failure, I was able to duplicate this behavior from
a command line using COPY BufferFile LPT3 /B, with XP reporting "1 file
copied". However, COPYing the same file directly to the printer's UNC
name works fine! I've re-tested each way with 100% consistency.

So, the problem seems to be with the NET USE connection between the
local LPT3 port and the network printer. And whatever is causing that
file loss was presumably triggering the "Not Enough Memory" error with
the previous PRINT FILE LPT3 implementation.

Anyway, COPY to the unc seems to resolve the problem. Although the
(intermitent) NET USE failure mystery remains.


Reply With Quote
  #22  
Old   
Steven Green
 
Posts: n/a

Default Re: PDOX 4.5 PRINT FILE LPT3 "not enough disk space" - 12-13-2006 , 05:38 PM






Quote:
However, COPYing the same file directly to the printer's UNC name works
fine!
that's the only way I know of to do this on XP.. glad you finally came on
board (g)


--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards

"psmart" <psmart (AT) hydrocad (DOT) net> wrote

Quote:
Further developments - We've had another "incident", this time without
2GB fix, and with the revised implemention that uses PRINT FILE to a
buffer: When COPYing the buffer file to LPT3, only the first part of
the file goes to the (network) printer. The rest is lost, and the
print queue is empty.

At the time of the failure, I was able to duplicate this behavior from
a command line using COPY BufferFile LPT3 /B, with XP reporting "1 file
copied". However, COPYing the same file directly to the printer's UNC
name works fine! I've re-tested each way with 100% consistency.

So, the problem seems to be with the NET USE connection between the
local LPT3 port and the network printer. And whatever is causing that
file loss was presumably triggering the "Not Enough Memory" error with
the previous PRINT FILE LPT3 implementation.

Anyway, COPY to the unc seems to resolve the problem. Although the
(intermitent) NET USE failure mystery remains.




Reply With Quote
  #23  
Old   
psmart
 
Posts: n/a

Default Re: PDOX 4.5 PRINT FILE LPT3 "not enough disk space" - 12-13-2006 , 08:43 PM



Steve,

I think you missed my point: This problem and its resolution had
nothing to do with COPYing a buffer file vs a direct PRINT FILE.
Although one may be better than the other in some regards, they are
both functional.

The root problem here is that the virtual LPTx port created by NET USE
is buggy. The problem occurs if I COPY -or- PRINT FILE to the LPT
port, but not if I use the UNC name.

Peter


Reply With Quote
  #24  
Old   
Steven Green
 
Posts: n/a

Default Re: PDOX 4.5 PRINT FILE LPT3 "not enough disk space" - 12-13-2006 , 08:46 PM



Quote:
I think you missed my point: This problem and its resolution had nothing
to do with COPYing a buffer file vs a direct PRINT FILE.
we never said that PRINT FILE was your problem.. we suggested te
possibility, on XP, because it's not the way the rest of us do things,
because of related issues that we've found in XP.. "different" is always a
possible problem, until proven otherwise (g)


Quote:
The problem occurs if I COPY -or- PRINT FILE to the LPT port, but not if I
use the UNC name.
to which I replied "I absolutely agree".. on XP machines, I only use the
UNC..

--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards
"psmart" <psmart (AT) hydrocad (DOT) net> wrote

Quote:
Steve,

I think you missed my point: This problem and its resolution had
nothing to do with COPYing a buffer file vs a direct PRINT FILE.
Although one may be better than the other in some regards, they are
both functional.

The root problem here is that the virtual LPTx port created by NET USE
is buggy. The problem occurs if I COPY -or- PRINT FILE to the LPT
port, but not if I use the UNC name.

Peter




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.