>> to work. Sadly I was wrong, printing will still stop after say
after
>> half a page of graphics or a couple of pages of text. The
interesting
>> thing is: if I go to SBASIC and just enter the command OPEN#3,PAR
it's
>> enough to make printing resume and finish! I am completely unable
to
>> predict when the problem will occur, all I know is how to fix it.
>
>If its a QL problem it could be that your program needs to output a
FF
>instruction to the printer to flush its buffer. I havent bothered to
update
>all my printer drivers so I sometimes resort to a:
>
>_=FOPEN('par'):BPUT#_;12:CLOSE#_
>
>(Kept on a hotkey for convenience) It may do no better than what
youre doing
>already. But if this is the problem, try adjusting the printer
driver.
This is specific to QPC2v2final, the old QPC2 and QPC1 on the same PC
and none of my other systems do this. I could understand it if it was
a FLUSH requirement (the old Falkenberg hard disk system had a similar
problem when deleting files that you had to do a WIN_FLUSH to really
delete files). Most likely something Windows related I'd have thought
as it's inconsistent and the mere act of opening a channel to the
device causes a 'flush' of sorts.
Although the 'QPC2v2 again' thread is getting a bit long, the
discussion has been very interesting and shows that we need both an
emulator and a native hardware way forward. The emulator scene is very
well served at the moment. Let's hope that the future of
Q40/Goldfire/any other SGC successor is as good as the emulator scene.
--
Dilwyn Jones
[EMAIL PROTECTED]
http://www.soft.net.uk/dj/index.html
