Posted on: Apr 15 2013, 09:40 AM | |
Forum Member Group: Members Posts: 11 Joined: 20-January 06 Member No.: 205 ![]() |
I have had a similar problem. I'm hoping you won't discount it since it is related to a user whose opinion you seem to value. I have extremely large directories under OS/2 and find that I must await PMView's reading of subdirectories before I can again use PMView. But, I need at least a little depth. Is it possible to set it to read a specifici number of directory levels? Too much work? I realize that it may be due to using an underpowered T30 that I'll be upgrading to a W400, or something similar. Also, I am shocked to hear you talking about stopping development of the OS/2-eCS version. I continue to use it for several hours daily despite the printer problems that you say are not yours to fix, despite my being unable to correct them by reverting to earlier driver revisions. Outside of these fora I only praise PMView. -- Mark |
Forum: PMView - OS/2 Technical Support · Post Preview: #1433 · Replies: 52 · Views: 5,511,379 |
Posted on: Jan 9 2012, 02:53 AM | |
Forum Member Group: Members Posts: 11 Joined: 20-January 06 Member No.: 205 ![]() |
If PMView crashes when a file is being batch converted and being replaced by the converted image, e.g., by a 'Quick Script' for cropping, it is destroyed. This has happened most often when insufficient space was available on the target disk as well as for other reasons involving either PMView or another application that freezes the desktop. The original file is irretrievable because, I believe, of PMView's otherwise excellent memory and INI file management that leaves no wasted space on the disk and no useless entries in INI files. I realize that I could always convert in a manner that does not overwrite the original. But, a prohibitive amount of effort would be required to delete the original files. Any other suggestions? Thanks for your thoughts. - Mark |
Forum: PMView - OS/2 Technical Support · Post Preview: #1376 · Replies: 1 · Views: 54,559 |
Posted on: Jul 19 2010, 05:09 PM | |
Forum Member Group: Members Posts: 11 Joined: 20-January 06 Member No.: 205 ![]() |
[quote name='Peter' date='Jul 16 2010, 04:50 PM' post='1348'] The maker of the printer driver is of course the first logical choice. If they won't help you, the next step is usenet news and use Google. I can guarantee no reply from HP for a printer this old, but, who knows... I'll give it a try. > The next step is to use IniMaint to clean up your OS/2 ini file. You could also try a clean install on a 2nd machine to see if it exhibits the same behavior. I use Unimaint regularly. And, this happens with brand new installations, every time. > If all else fails, you could look if there are alternate printer drivers available that do the work right... Well, I could try backleveling to omni drivers from the early 2000s. I'm not certain whether that might introduce other problems. But, nothing ventured, nothing gained. Thank you for your help. - Mark -- |
Forum: PMView - OS/2 Technical Support · Post Preview: #1350 · Replies: 8 · Views: 89,867 |
Posted on: Jul 16 2010, 04:49 PM | |
Forum Member Group: Members Posts: 11 Joined: 20-January 06 Member No.: 205 ![]() |
[quote name='Mark_Henigan' date='Jul 5 2010, 09:57 AM' post='1344'] > I'm not sure I understand if you have tried resetting the settings or not... I followed your instructions and reset the settings for both the 5L and 6L It made absolutely no difference. :-< I selected two pages from the FOC, then used Ctrl-P to bring up the print dialogue. Then I hit return. The printer produced six pages, only two of which were images, just as I described: 1. blank page 2. page with PJL string 3. image #1 4. blank page 5. page with PJL string 6. image #2 I'm sorry I can't report anything more hopeful. Where would be the most productive forum in which to discuss this, perhaps from the printer aspect? - Mark |
Forum: PMView - OS/2 Technical Support · Post Preview: #1347 · Replies: 8 · Views: 89,867 |
Posted on: Jul 5 2010, 11:57 AM | |
Forum Member Group: Members Posts: 11 Joined: 20-January 06 Member No.: 205 ![]() |
> I'm not sure I understand if you have tried resetting the settings or not... No, I hadn't, because I'm talking about fresh installs, as well as very old. > Please try to reset the settings. This brings in a CLEAN copy of settings from the printer driver. If I open the print dialogue and press setup, there is no reset option. There is a defaults option. Is that what you mean? > Resetting is REQUIRED if the driver is updated. If not reset, you may see problems just like the ones you're describing. I haven't updated this driver in a very long time. IBM hasn't issued an updated driver for a very long time. > Right click on "SETUP..." and select "RESET" Ahh! Right click! Got it! Sorry, not listening!! I never noticed that property of the Setup button. It made absolutely no difference. :-< I selected two pages from the FOC and wound up with six, only two of which were images, just as I described. I'm sorry I can't report anything more hopeful. - Mark |
Forum: PMView - OS/2 Technical Support · Post Preview: #1344 · Replies: 8 · Views: 89,867 |
Posted on: Jul 5 2010, 11:37 AM | |
Forum Member Group: Members Posts: 11 Joined: 20-January 06 Member No.: 205 ![]() |
I'm not sure I understand if you have tried resetting the settings or not... Please try to reset the settings. This brings in a CLEAN copy of settings from the printer driver. Resetting is REQUIRED if the driver is updated. If not reset, you may see problems just like the ones you're describing. Right click on "SETUP..." and select "RESET" Thanks, Peter |
Forum: PMView - OS/2 Technical Support · Post Preview: #1343 · Replies: 8 · Views: 89,867 |
Posted on: Jul 5 2010, 10:47 AM | |
Forum Member Group: Members Posts: 11 Joined: 20-January 06 Member No.: 205 ![]() |
[quote name='Peter' date='Jul 5 2010, 06:30 AM' post='1338'] > I'm not aware of a problem like this. > >Did the problem happen after upgrading PMView? If so, does reverting to the previous version solve the problem? No, the problem has existed for at least a couple of years. I had been hoping during the interval that upgrading to the most recent version would make a difference. The message printed is obviously the setup of the PCL parameters. The printers I'm using are older HPs. I'm not certain whether the newer one that doesn't have the problem uses PCL5 ("Enhanced" PCL5). It doesn't provide that information on its test page or in its manual. Clearly, it uses a different driver collection. Does anyone else use these older printers? They still provide a high quality 600 dpi output, although a little slow for really big jobs. >Have you tried to reset the printer settings in PMView? (Right click on the "Setup..." button in the printer dialog and select "Reset") I've made many adjustments to the settings on several different installations of OS/2, eCS, PMView, with HPLJ 5LXtra and HPLJ 6L with both 1MB (default) and 9MB (max) of memory. Nothing I've done has made a difference. It has been there all of the time for possibly several years. BTW, I'm having trouble figuring out how to quote previous posts in order to reply to them in context. Thank you for your reply. - Mark |
Forum: PMView - OS/2 Technical Support · Post Preview: #1341 · Replies: 8 · Views: 89,867 |
Posted on: Jun 27 2010, 08:37 PM | |
Forum Member Group: Members Posts: 11 Joined: 20-January 06 Member No.: 205 ![]() |
When printing multi-page docs (e.g., faxes0 or two or more pages selected from FOC, a blank page is inserted followed by a page with /// start of quoted material /// " @PJL SET COPIES=1 @PJL SET RESOLUTION=600 @PJL SET RET=MEDIUM @PJL SET ECONOMOD //// end of quoted material //// clearly referencing the HP Printer Job Language, after which the first page selected is printed, then repeating the pattern for each page selected, i.e., [blank] [PJL page] [page 1] [blank] [PJL page] [page 2] [blank] [PJL page] [page 3]...[last page]. This started happening at least a couple of years ago. I cannot pinpoint the date. It occurs with HPLJ 5L and HPLJ 6L but not with the HP Photosmart 8050 using the HPDJ 895C driver, all of which are from the LASERJET.HP and OMNI.HP drivers that come with eCS. I have several of these printers and depend on them. I do not select separator pages. Most of the images are TIFFs, but not all. This is important to me because I must either waste time selecting and printing each page separately, or paper and time printing as I would have previously, then removing the extra pages. Since I use PMView daily for a considerable amount of my work and need to be able to print directories of images, this change in behavior has created problems for me in work efficiency. So far as I am aware, there has been no substantial change in the drivers in many years leading me to wonder whether there has been an inadvertant change in PMView that has led to this problem. I just installed PMView v 3.61 and see no change. BTW, I am pleased to see the copy and move selection boxes being sizable, even if I still can't delete unused directories from their lists. [ Any thoughts? - Mark Mark Henigan |
Forum: PMView - OS/2 Technical Support · Post Preview: #1337 · Replies: 8 · Views: 89,867 |
Posted on: Apr 12 2007, 04:29 AM | |
Forum Member Group: Members Posts: 11 Joined: 20-January 06 Member No.: 205 ![]() |
[quote name='BSWAdmin1' date='Apr 10 2007, 08:15 AM' post='1121'] Hi Mark, There is a 'Time Stamp' option available from the pop up menu when right-clicking on an image in the File Open dialog. By selecting "Time Stamp -> Set to time in EXIF information" the time stamp is set to the time in the EXIF information of the file. Hello Brandon: Thank you for bringing this to my attention. I'll try this in the next couple of weeks. Does the EXIF data survive copying, or re-saving to compress the file, or cropping? Even if it works for photographs, this doesn't solve the more pressing problem for scans. Since scans don't contain EXIF information there is nothing to work with via the EXIF option for time stamping. And, my experience is that when I re-save an uncompressed TIFF scan of approx 1.6MB in order to shrink it to 25KB, for example, the creation date in the file system is updated to the date and time of re-saving. I did not realize how important this would be for me at the time it was being discussed. For example, there are many times when it is vital that I be able to sort a group of scanned images into the order in which they were originally acquired. However, since even the creation date of the file has been revised, there is no file attribute that conserves this datum. Thank you for your help. I will explore the use of the feature you mentioned. I think I was afraid that it would be updated in the same manner as the file system file attributes. Best Regards, - Mark -- |
Forum: PMView - OS/2 Technical Support · Post Preview: #1127 · Replies: 2 · Views: 61,175 |
Posted on: Apr 10 2007, 06:34 AM | |
Forum Member Group: Members Posts: 11 Joined: 20-January 06 Member No.: 205 ![]() |
I know this was hashed out at length on the PMView_beta_discuss mailing list when such things still existed. However, I find no reference to it now. (BTW, I find the forum approach an annoying substitute for the mailing list.) When I acquire an image from a camera memory or scan a new image, it is important for me to be able to retain the date the photograph was taken or the image scanned. Unfortunately, unless I retain an incredibly large uncompressed image, such as the 1.5MB 8.5 x 11 in 400dpi 1-bit TIFF bitmaps produced by SANE with my Canon LiDE scanners, I cannot keep the original image date. This is in conflict with my primary reason for choosing the TIFF format, lossless compression. When compressed with the CCITT Group 4 algorithm, even very detailed images of my smallest handwriting (a more primitive form of compression :->) may compress to an image of under 100KB files size. This image contains all of the information found in the original bitmap. The image is unaltered, although the file may be. However, this does not completely satisfy my _irrational_ needs. I would also like to know how to retain the date of the original image if I've made alterations such as manual deskewing. I have no objection to the idea that the date the image file was last written to should be shown so that something has been done to the file. I just want some means of preserving the file creation date, very much as occurs with text documents. In WordPerfect, this is the default behavior. I have many documents that show the original file date as that of the "template" that I started with. Is this already an option in PMView? If not, how do I go about requesting such a thing. Or, would I be wasting my time? TIA, - Mark Mark Henigan -- |
Forum: PMView - OS/2 Technical Support · Post Preview: #1118 · Replies: 2 · Views: 61,175 |
![]() ![]() ![]() ![]() |
![]() ![]() ![]() ![]() |
Lo-Fi Version | Time is now: 28th April 2024 - 08:36 PM |