The reason is to be able to read Pipedream files rather more
easily than using the DOS version of Pipedream, which I also
have.
The Pipedeam files are created under RISC OS 4.02, using
Pipedream 4.50/23. They contain primarily text, one box
copies another text box, there are some straightforward
calculations using +, - and * only, plus one not too complex
IF function.
There is frequent use of control codes to control printing
of these files on a dot-matrix printer.
When I start Fireworkz I am asked whether I want to create a
letter.fwt or sheet.fwt.
If I select letter.fwt, I can then drag a Pipedream file
into the window with no problem, although no regard is taken
of the Pipedream formatting. However, this is not terribly
useful, since all the formulas and calculations are treated
as text.
If I select sheet.fwt and again drag a Pipedream file into
the window, the file loads, but about a second later indows
throws up a fatal error message.
This is totally consistant, has happened so far on every
occasion, on both machines.
The same happens if I use the insert file option, or right
click on the Pipedream file icon and ask it to load the file
into Fireworkz.
Any ideas, plase?
--
Russell Hafter - Mailing Lists
rh.l...@phone.coop
Need a hotel? <http://www.hrs.com/?client=en__blue&customerId=416873103>
(NB This link needs Firefox to work)
It might help Stuart to identify where and what the problem was if you
posted the complete exact error message!
> > If I select sheet.fwt and again drag a Pipedream file
> > into the window, the file loads, but about a second
> > later indows throws up a fatal error message.
> It might help Stuart to identify where and what the
> problem was if you posted the complete exact error
> message!
"Fireworkz has encountered a problem and needs to close"
Following links on the error box I get
AppName Firewrkz.exe Ver1.34.0.1 Offset 000a35e1
A file with the following contents gets saved:
<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="firewrkz.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="firewrkz.exe" SIZE="1286144"
CHECKSUM="0xD7DB19A9" BIN_FILE_VERSION="1.34.0.1"
BIN_PRODUCT_VERSION="1.34.0.1" PRODUCT_VERSION="1, 34, 0, 1"
FILE_DESCRIPTION="Colton Fireworkz for Windows"
COMPANY_NAME="Colton Software" PRODUCT_NAME="Colton
Fireworkz for Windows" FILE_VERSION="1, 34, 0, 1"
ORIGINAL_FILENAME="firewrkz.exe" INTERNAL_NAME="firewrkz"
LEGAL_COPYRIGHT="Copyright � Colton Software 1992-2012"
VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004"
VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x144E79"
LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.34.0.1"
UPTO_BIN_PRODUCT_VERSION="1.34.0.1" LINK_DATE="03/20/2012
16:51:33" UPTO_LINK_DATE="03/20/2012 16:51:33"
VER_LANGUAGE="English (United Kingdom) [0x809]" />
<MATCHING_FILE NAME="unins000.exe" SIZE="1174979"
CHECKSUM="0x578C21CC" BIN_FILE_VERSION="51.1052.0.0"
BIN_PRODUCT_VERSION="0.0.0.0"
FILE_DESCRIPTION="Setup/Uninstall"
FILE_VERSION="51.1052.0.0" VERFILEDATEHI="0x0"
VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1"
MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="51.1052.0.0"
UPTO_BIN_PRODUCT_VERSION="0.0.0.0" LINK_DATE="12/20/2011
14:16:51" UPTO_LINK_DATE="12/20/2011 14:16:51"
VER_LANGUAGE="Language Neutral [0x0]" />
<MATCHING_FILE NAME="System\UK\DLL\DsAFF.dll"
SIZE="71168" CHECKSUM="0xAEF8F674" MODULE_TYPE="WIN32"
PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="02/14/1996
14:30:00" UPTO_LINK_DATE="02/14/1996 14:30:00" />
<MATCHING_FILE NAME="System\UK\DLL\DsFF9.dll"
SIZE="48640" CHECKSUM="0xCF89927B" MODULE_TYPE="WIN32"
PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="02/14/1996
14:31:53" UPTO_LINK_DATE="02/14/1996 14:31:53" />
<MATCHING_FILE NAME="System\UK\DLL\DsFntMap.dll"
SIZE="24064" CHECKSUM="0x2080884F" MODULE_TYPE="WIN32"
PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="02/14/1996
14:33:38" UPTO_LINK_DATE="02/14/1996 14:33:38" />
</EXE>
<EXE NAME="kernel32.dll"
FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="989696"
CHECKSUM="0x2D998938" BIN_FILE_VERSION="5.1.2600.5781"
BIN_PRODUCT_VERSION="5.1.2600.5781"
PRODUCT_VERSION="5.1.2600.5781" FILE_DESCRIPTION="Windows NT
BASE API Client DLL" COMPANY_NAME="Microsoft Corporation"
PRODUCT_NAME="Microsoft� Windows� Operating System"
FILE_VERSION="5.1.2600.5781 (xpsp_sp3_gdr.090321-1317)"
ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32"
LEGAL_COPYRIGHT="� Microsoft Corporation. All rights
reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0"
VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32"
PE_CHECKSUM="0xFE572" LINKER_VERSION="0x50001"
UPTO_BIN_FILE_VERSION="5.1.2600.5781"
UPTO_BIN_PRODUCT_VERSION="5.1.2600.5781"
LINK_DATE="03/21/2009 14:06:58" UPTO_LINK_DATE="03/21/2009
14:06:58" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>
There is also a load of technical info in the error window,
but I can find no way to copy and paste that into an e-mail.
When I start Fireworkz I am asked whether I want to create a
letter.fwt or sheet.fwt.
> I have no problem loading PipeDream spreadsheets into
> Fireworkz for Windows.
> Here is how I do it.
> Do NOT open a blank Fireworkz for Windows template.
> Click (or double click) on the PipeDream file to try to
> open it.
I think I had already tried that too and it crashed as
usual.
To be certain, I tried again and, yes, Fireworkz crashed.
> I have no problem loading PipeDream spreadsheets into
> Fireworkz for Windows.> Here is how I do it.> Do NOT open a blank Fireworkz for Windows template.> Click (or double click) on the PipeDream file to try to
> open it.I think I had already tried that too and it crashed as
usual.To be certain, I tried again and, yes, Fireworkz crashed.
> > > I have no problem loading PipeDream spreadsheets into
> > > Fireworkz for Windows.
> > > Here is how I do it.
> > > Do NOT open a blank Fireworkz for Windows template.
> > > Click (or double click) on the PipeDream file to try
> > > to open it.
> > I think I had already tried that too and it crashed as
> > usual.
> > To be certain, I tried again and, yes, Fireworkz
> > crashed.
> I wonder if the PipeDream file you have is suitable.
> From what you have said earlier, the version of PipeDream
> you are using is the version called 'PC PipeDream' which
> runs under DOS.
No, I said: "The Pipedeam files are created under RISC OS
4.02, using Pipedream 4.50/23."
I just mentioned that I also have the DOS version of PD,
which I have used in the past to read RISC OS PD files, but
it is not exactly user friendly.
> I do assure you that I have no trouble whatsoever loading
> PipeDream for RISC OS files into Fireworkz for Windows.
Nor do others. They told me so before I got Fireworkz for
Windows.
> > I have no problem loading PipeDream spreadsheets into
> > Fireworkz for Windows.
> > Here is how I do it.
> > Do NOT open a blank Fireworkz for Windows template.
> > Click (or double click) on the PipeDream file to try to
> > open it.
> I think I had already tried that too and it crashed as
> usual. To be certain, I tried again and, yes, Fireworkz crashed.
You've presumably got the (free) Fireworkz for RISC OS, so what
happens if you try to load a PipeDream file into that?
Would you care to compose a simple PD spreadsheet file and send it to
me (the address below is valid) and I'll see how it behaves on my
WindowsXP machine?
[ I haven't yet put FireworkzPC on my 64-bit W7 laptop, but I'm
willing to do so if you need such a test. Usually I use SA-VRPC OS
4.02 on a WXP machine. ]
Michael Harding
Rev. Preb. M.D. Harding ris...@mdharding.org.uk
> You've presumably got the (free) Fireworkz for RISC OS,
> so what happens if you try to load a PipeDream file into
> that?
No, I am only interested in being able to *read* the
original PD files when away from the office. PD does what I
want it to.
> Would you care to compose a simple PD spreadsheet file
> and send it to me (the address below is valid) and I'll
> see how it behaves on my WindowsXP machine?
I have sent you by private e-mail the template file from
which all the ones in question are derived. It does crash FW
under windows.
They load fine, as expected.
They *are* fireworkz files!
> > You've presumably got the (free) Fireworkz for RISC OS,
> > so what happens if you try to load a PipeDream file into
> > that?
> No, I am only interested in being able to *read* the
> original PD files when away from the office. PD does what I
> want it to.
> > Would you care to compose a simple PD spreadsheet file
> > and send it to me (the address below is valid) and I'll
> > see how it behaves on my WindowsXP machine?
> I have sent you by private e-mail the template file from
> which all the ones in question are derived. It does crash FW
> under windows.
I've just tried all the files of 'Lazybownz' [whose identity I can
easily surmise!] and also the template file that Russell Hafter sent
me privately and every one of them works for me under both PD and
Fireworkz in RISC OS and also in Fireworkz for Windows.
I am incompetent at managing to get the W-XP filing system to desist
from adding extra file-types and so I had to edit some of them,
deleting the 2nd extension. But I noticed that Russell's PD file
ended up in Windows XP as ,bdf. With no editing change to that,
Fireworkz for Windows read it without any qualms.
> I've just tried all the files of 'Lazybownz' [whose
> identity I can easily surmise!] and also the template
> file that Russell Hafter sent me privately and every one
> of them works for me under both PD and Fireworkz in RISC
> OS and also in Fireworkz for Windows.
> I am incompetent at managing to get the W-XP filing
> system to desist from adding extra file-types and so I
> had to edit some of them, deleting the 2nd extension. But
> I noticed that Russell's PD file ended up in Windows XP
> as ,bdf. With no editing change to that, Fireworkz for
> Windows read it without any qualms.
Interesting, particularly as by the time I got this, Gerald
had also asked for a file, and confirmed that it did crash
FW for windows. Even loading into FW (RISC OS), which
worked, then saving as a FW file and trying to load the RISC
OS FW file into FW (Windows) results in a crash.
But...
I hve just had another communication from Gerald -
apparantly Fireworkz for Windows 1.33/12 does not crash.
He hopes that Stuart may be able to pin down the problem
with that bit of info.
In the meantime, perhaps all I ned to do is find Fireworkz
for Windows 1.33/12 and downgrade to that.
[Snip]
> The reason is to be able to read Pipedream files rather
> more easily than using the DOS version of Pipedream,
> which I also have.
> The Pipedeam files are created under RISC OS 4.02, using
> Pipedream 4.50/23.
[Snip]
> If I select sheet.fwt and again drag a Pipedream file
> into the window, the file loads, but about a second later
> indows throws up a fatal error message.
The problem has been solved with a new version of Fireworkz
for Windows Ver 1.34/06.
The new version deals with the following, according to the
release note:
Formulas that referenced empty cells could crash Fireworkz.
A new convenient toolbar button, MAKE_CONSTANT, now performs
the Snapshot command as per the existing Edit -> Make ->
Make constant menu option.
Fixed line-of-best-fit in chart module (could erroneously
return out-of-memory error).
I imagine that the problem with my files was the first of
these, formulas referencing empty cells.
However, and sadly for me, now that I see the results of
loading my PD files into Fireworkz, it is not terribly
useful.
Loading the file as a letter keeps roughly the right page
layout, but does not do the calculations.
Loading it as a sheet does the calculations, but at the
expense of making a complete hash of the page layout, as
Fireworkz in sheet format does not sem to allow text to
overrun columns.
My documents are, basically, text documents that also do
calculations. I suspect that is not FW's forte.
It looks as though I shall still have to rely on PD for DOS
to display my RISC OS PD files under windows.
But, many thanks to both Gerald and Stuart, as well as to
Michael, for their effort and time solving this one!
Russell