[Freedos-user] PRINT command
Hi, Eric! Your changes to the Print command did increase printing dramatically and placed it on par with ms print! - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] PRINT command
Okay, I tried print and printq with freedos and neither of them work like ms print. So, I'll use ms print until any freedos updates for print come around. I may try other dos flavors in the meantime but freedos does a fine job! - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PRINT command
Hi Chris, I'll give printq a try and see what happens Hmmm I only found a 6/2000 version on the page, which is described as being from Dr Dobbs and being a user interface for PRINT. It tries to highly portable (various DOS compilers) and seems to be 1991 by Robert Mashlan, Public Domain. Most files are from 5/2000. There is no built-in help, but the following commands are okay: printq /t -- cancels all queued printjobs printq /c filenames -- cancels all selected printjobs printq /p filenames -- adds all selected files to the queue The main code is in prnspool.c, no wildcards supported. Install check is: int 2f.100 - if return al=-1 print found Enqueue file is: int 2f.101 pack=ds:dx - carry, ax on error pack has fields level=0 and pathname=(char far *)string (pack is 1 + 4 bytes) (RBIL: if no carry, 01=added 9e=printing) Unqueue file is: int 2f.102 stringpointer=ds:ds - ... Cancel all is: int 2f.103 - carry, ax on error List queue is: int 2f.104 returns ds:si, carry, ax on error pointer is to array of strings, each padded to 64 bytes (RBIL: also returns error count since last read in DX...) (first empty string marks end of list) List queue ack is: int 2f.105 (needed to continue printing after getting the pointer to the live list queue array) Get status is: int 2f.104 - carry, ax on error, and always in dx the count of printing errors (since when?) Error codes are: 0 okay 1 invalid func 2 file not found 3 path not found 4 too many files open 5 access denied 8 queue full 9 spooler busy c name too long f drive invalid RBIL also tells that int 2f.106 returns carry, ax=8, ds:si= pointer to device driver if printing, no carry, ax=0 else (useful to know which device PRINT is using at the moment) (useful to avoid concurrent printing to the same device) So... PRINTQ is just a user interface for PRINT :-) It should also work for MS PRINT, but of course MS PRINT has those options built-in anyway. FreeDOS PRINT is ancient, from 1999... It does not support ANY command line option beyond a name of a file to be printed. The first time you run it, it goes resident, and all other times, it expects a file name as command line option. Simplistic utility. Yet the source code is ca 1000 lines of Assembly... FreeDOS PRINT hooks int 5 (prtscr), 8 (timer), 13 (disk), 24 (error), 28 (idle), 2f (print api). It also checks for dos critical sections. RUN_CNT is initially TIME_TOGO (18 ticks, 1 sec). There is a byte marked with SETONIT where you can set the printer number to be used, manually. You can queue at most 10 files. What FreeDOS PRINT does is, basically, try to send data to the printer once per second, but only if neither DOS nor the disk are active at that moment. Both the timer and the idle int are used to check the moment. The int 5 hook is simply suppress print screen while a queued file is printing. The level thing is read by FreeDOS PRINT as if 0, then send form feed, and if 1, do not send form feed. PRINT takes a lot of effort to avoid collisions with other DOS activities. For example it uses its own PSP, DTA and crit err handler. It fully implements the interface used by MS PRINT and PRINTQ apart from the get device one. At most 256 chars are printed at a time (fixed buffer size: BUFFER DB 258 DUP..., followed by 192 bytes of local stack, quite small?). You could *tune* the print speed by patching the bytes at file offsets (add 0x100 if you are in debug) here: - 0x348 reduce from 0x12 but maybe better not to 2 - 0x395 reduce from 0x12 ... To change the chunk size, you would have to recompile. For comparison, MS PRINT has the /T /C /P and filename options handled by the free PRINTQ, plus also: /d:device (for example LPT1, default PRN, as with ours) /b:chunksize (512-16384 default 512, twice of ours) /u:ticks (to wait till ready) /m:ticks (max wait per 1 char, uses printer default in our print) /s:ticks (how often to try to send, half of ours) /q:queuesize (1-32, default 10, as ours). So FreeDOS PRINT has default queue size 10, chunk size 256, printer PRN, poll delay 18, per char timeout as set by MODE, unknown ready timeout. All unconfigurable. MS PRINT has default queue size 10, chunk size 256, printer PRN, poll delay 8, per char timeout unknown, ready timeout unknown. So default is to print 4x faster. You said you wanted PRINT /B:1024 /Q:4 /S:1 /D:PRN which would be chunk size 1024, queue size 4, poll delay 1, printer PRN. This is 32x faster than the MS PRINT default and 128x faster than FreeDOS PRINT. You can make FreeDOS PRINT 9x faster as described above, though :-). More only with recompiling. Note that every PRINT takes a filename as input, not the actual data to be printed, so it should be easy to write a FAKE PRINT tool which only grabs the file and copies it to another file instead of actually printing it :-). I hope you find one on WWW. Eric - This SF.net email is
Re: [Freedos-user] PRINT command
Thanks Alain! I've downloaded it and will give it a try! Alain M. wrote: I was used to printq because it was far better then print, you should give it a try. I found it at ibiblio (in Freedos, he he...) http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/print/ Alain Chris Ruhl escreveu: I will certainly give the NEWDOS a whirl when I can. I've downloaded it, just need to get time to play! I will, no doubt, enjoy comparing the ms print with freedos print!! You guys are great at fixing things up right and I seem to have the perfect difficult hardware and applications for testing it! Eric Auer wrote: Hi Chris, I agree that MS PRINT is no long term option. Did you also try the shareware NEWDOS PRINT? Newdos is a German shareware collection of replacements for MS DOS commands, trying to be both user friendly and modern. See: www.newdos.de Another useful point in running MS PRINT in FreeDOS is that you can compare various settings and can compare how the various PRINTs behave. Maybe we can just fix some internal settings in FreeDOS PRINT or PRINTQ to get you going :-). Eric - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PRINT command
I got the MS Print to load in FreeDOS by using CALLVER but couldn't do a test print from a nasty paper jam that I'll clear tomorrow. I'll let you know. My only concern is the license issue ... I'm using this in a commercial environment. Nobody would probably know that we're using a non-FreeDOS version of print but still... I can understand you not thinking that anybody would actually use print -- I rarely did, if ever, fifteen years ago when DOS was on every IBM desktop. Bernd Blaauw wrote: Chris Ruhl schreef: Any way I can pass this on to the PRINT side of the project?? Anybody have any suggestions?? Again, can't re-code the application. No idea, never expected anyone to actually use PRINT application anymore, maybe you're unique :) Does MS print program work on FreeDOS? we got CALLVER and you can change dos version reported in config.sys as well if MS print works on FreeDOS but slower than on MSDOS, then we got an issue. I agree it's best though to get FD print program up to the standard of the MS program, but if MS program works on Freedos, by all means use it :) Bernd - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PRINT command
I will certainly give the NEWDOS a whirl when I can. I've downloaded it, just need to get time to play! I will, no doubt, enjoy comparing the ms print with freedos print!! You guys are great at fixing things up right and I seem to have the perfect difficult hardware and applications for testing it! Eric Auer wrote: Hi Chris, I agree that MS PRINT is no long term option. Did you also try the shareware NEWDOS PRINT? Newdos is a German shareware collection of replacements for MS DOS commands, trying to be both user friendly and modern. See: www.newdos.de Another useful point in running MS PRINT in FreeDOS is that you can compare various settings and can compare how the various PRINTs behave. Maybe we can just fix some internal settings in FreeDOS PRINT or PRINTQ to get you going :-). Eric - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PRINT command
I was used to printq because it was far better then print, you should give it a try. I found it at ibiblio (in Freedos, he he...) http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/print/ Alain Chris Ruhl escreveu: I will certainly give the NEWDOS a whirl when I can. I've downloaded it, just need to get time to play! I will, no doubt, enjoy comparing the ms print with freedos print!! You guys are great at fixing things up right and I seem to have the perfect difficult hardware and applications for testing it! Eric Auer wrote: Hi Chris, I agree that MS PRINT is no long term option. Did you also try the shareware NEWDOS PRINT? Newdos is a German shareware collection of replacements for MS DOS commands, trying to be both user friendly and modern. See: www.newdos.de Another useful point in running MS PRINT in FreeDOS is that you can compare various settings and can compare how the various PRINTs behave. Maybe we can just fix some internal settings in FreeDOS PRINT or PRINTQ to get you going :-). Eric - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] PRINT command
Hi all! First off, the recent improvements to JEMM386.EXE have made this memory manager workable for my hardware. I could not run with previous versions or the plain FreeDOS version! Excellent job! No more boot issues or system locks so far. The same is true with the DOSFSCK version 2.11c! Very good. The added counter for surface scans is a nice touch! I'm thankful for the updates. My only remaining hurdle is with the PRINT command. The FreeDOS version doesn't want to work like the MS equivalent and is very, very slow in comparison when I use my Lexmark parallel port printers. The details: I have a software application that uses the PRINT command as its spooler for reports. Some of these reports are long, 30+ pages. I have to load PRINT resident in AUTOEXEC.BAT something like this: C:\DOS\PRINT /B:1024 /Q:4 /S:1 /D:PRN In other words, PRINT with some command line options. This is what the application wants per the software authors. The authors are long gone and I can't change it. I have to live with it. Failure to run this command line before launching the application brings can't spool to printer error message. Now, the following command line results in nothing going to the printer. The application thinks that all is okay because it sent the print job to the spooler and got no errors. The dianostics confirm this. C:\FDOS\BIN\PRINT /B:1024 ... The only way that I can print is if I use the above command line with no options, specifically: C:\FDOS\BIN\PRINT It prints but ever so slowly compared to MS PRINT and so slow that I really can't use it for anything but the shortest of reports. It can take two minutes to print a three to five page report compared to a minute or so with MS-DOS PRINT. Any way I can pass this on to the PRINT side of the project?? Anybody have any suggestions?? Again, can't re-code the application. Thanks! - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PRINT command
Chris Ruhl schreef: Any way I can pass this on to the PRINT side of the project?? Anybody have any suggestions?? Again, can't re-code the application. No idea, never expected anyone to actually use PRINT application anymore, maybe you're unique :) Does MS print program work on FreeDOS? we got CALLVER and you can change dos version reported in config.sys as well if MS print works on FreeDOS but slower than on MSDOS, then we got an issue. I agree it's best though to get FD print program up to the standard of the MS program, but if MS program works on Freedos, by all means use it :) Bernd - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PRINT command
I will test and let you know! Bernd Blaauw wrote: Chris Ruhl schreef: Any way I can pass this on to the PRINT side of the project?? Anybody have any suggestions?? Again, can't re-code the application. No idea, never expected anyone to actually use PRINT application anymore, maybe you're unique :) Does MS print program work on FreeDOS? we got CALLVER and you can change dos version reported in config.sys as well if MS print works on FreeDOS but slower than on MSDOS, then we got an issue. I agree it's best though to get FD print program up to the standard of the MS program, but if MS program works on Freedos, by all means use it :) Bernd - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] print command
Hi all, I have my freedos obtained with dosemu ver 1.2.0-1 and I can't find the print commnad. What I'm wrong?? --- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562alloc_id=6184op=click ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
