#PageStream/Hotlinks
9 messages in this thread
Finally, HotLinks arrived at my place. It works very well except for
one little problem. I've digitized some pictures from several TV
stations in 24bit. I've loaded this pictures into BME and cut out the
Logo's of the stations. So I had some pictures in 24bit between 50×50
and 100×100. After that I've published them. Everything went good so
far. But trying either "Import Graphics" or using "Subscribe" in
PageStream 2.2 HL all I got was a "Error #8000 0005 Program failed"
with the buttons "Reboot" and "Suspend". Using 640×480 pictures in
24bit makes no problems. Are the other pictures to tiny?
My configuration: A2000, Rev. 6.2, 1MB Chip, PAL GVP 3001, 28Mhz, 8MB
GVP Series-II, 80MB Quantum,44MB SyQuest VLab 1.3 Realtime-Digitizer
ScanKing Card OS 2.04 (KS 37.175/WB 37.67) Any help will be
appreciated.
You can't import a published edition. It's not a normal graphic file.
You must use Subscribe as you say you also tried. (You can only use
Import on an unpublished picture.)
I suspect the problem is due to something incorrectly written by BME.
Please put the original picture (if it will fit) and the part you cut
out and published on a disk and mail it to: Soft-Logik Publishing,
attn: Mike, P.O. Box 510589, St. Louis, MO 63151-0589.
Alternatively, you can email me the cut out portion if it's fairly small.
Please include details of originating program and anything you think might
be relevant. I'll give it to the programmers to track down and will get
back to you on it.
Michael Soft-Logik Publishing
Ok, I'll do that.
Thanx. Mike
Michael I think I've found out something interesting for you. I made the
following steps: 1. Started BME 2. Open a 24bit File 3. Select the area
tool 4. Clone a part of the picture with the area tool 5. Save this part 6.
Publish this cloned part 7. Starting PageStream 8. Select NEW –> any size
9. Subscribe above cloned file
… ant Program failed Error 8000 0005 is displayed in a requester.
But, loading the cloned picture into AdPro and re-save it (after point 5)
and publishing after that… works! No problems with PageStream. Everything
works really great! I think you're right that something has been
incorrectly writte [D in BME (Clone –> Save).
Would you still like to get the pictures (Oversea mail needs about 1 – 2
weeks for reaching you).
Mike
Mike, we've already found the problem. The problem is the Clone command
creates a new picture with a DPI value of 0 sometimes. IFF files don't
normally have a DPI value, which makes them kind of difficult for DTP, so
we defined a DPI chunk for IFF ILBM. BME writes this out and any properly
written program which doesn't understand the chunk should ignore it. Any
DTP related program should definitely be modified to recognize it because
it is useful. Anyway, PageStream chokes on subscribing to edition files
with DPI values of 0 with the current module.
And/or chokes on loading saved IFF files with DPI values of 0. I forget
which is the case.
Anyway, the reason why loading the file into AdPro and saving it back out
creates a usable IFF files for PageStream is that AdPro doesn't recognize
the DPI chunk and ignores it. It then writes the file back out without the
DPI chunk. Thus it works with PageStream. AdPro should actually be modified
to recognize the chunk.
We Oops…. We'll make changes in the next version of BME to fix this, and
in the next version of PageStream's IFF module to ignore IFF values of 0.
Temporary workaround: create a blank picture with a DPI value and bitplane
setting and picture type identical to the original picture. Cut the area
out of the first and paste into the second. You can make the 2nd picture
any size you need. Basically, you'll be doing a manual clone area command.
Michael Soft-Logik Publishing
Oh No! Not another DPI problem. I thought AdPro DID use DPI, their program
"ZapDPI" adds and removes it from their files for compatability with
ProPage2.X, which would crash when you tried to import it. ProDraw 2.x
won't accept them either without removing the DPI chunk.
/ / / //ANDRE
I may be wrong about this, but I believe AdPro uses its own DPI chunk.
PageStream, BME and HotLinks use a DPI chunk which is registered with CBM
and which should be used by all programs wanting to use a DPI chunk.
Properly written IFF files should never crash a program which is IFF ILBM
compatible because the way IFF works, is, if you don't understand a part of
it, you just ignore it and go on. BME shouldn't write 0 dpi chunks, but
it's not really all that bad. PageStream is responsible since it should
recover from that sort of problem.
Michael Soft-Logik Publishing
I guess there was some simultaneous use of DPI by several people at around
the same time and everything got confused (DPI is a common term). It seems
to be getting straightened out slowly. Gold Disk has "fixed" PPage but
PDraw still crashes on AdPros DPI.
/ / / //ANDRE
PDraw 3.0 will not have a problem with DPI chuncks from Adpro or other
similar programs…but this also means that most Adpro images will import
at a smaller size because of the chunck. However, once you set the scale
factor it will always update at that new scale.
Philip Laitar
Supervisor