4.1.40 Update Released

[RamonS]

I eventually got around to download the update and I made three observations:
- the WinZIP self-extractor clearly states that there may be a delay while Windows configures the installation
- the size given in the dialog is 0.77 MB
- during the configuration the drive gets hammered quite well, so it isn't as that the installer doesn't do anything and just hangs around

Of course I got this error:
---------------------------
MadCap Flare V4.1
---------------------------
Failed to "Send File": The system cannot find the file specified
---------------------------
OK
---------------------------

because my default browser is not IE, but I've gotten used to the Microsoft-only approach and developer arrogance....or better to say ignorance here. What makes me wonder is why QA doesn't catch something obvious like this.

[helen]

because my default browser is not IE, but I've gotten used to the Microsoft-only approach and developer arrogance....or better to say ignorance here. What makes me wonder is why QA doesn't catch something obvious like this.

My default browser isn't IE either (I use both FF and Safari) but I have never seen that error. What does it mean?

[DocuWil]

I also run into the problem

Internal Error: Parameter is not valid

when building the PDF output. With the previous v4.1.19 it didn't.
The strange thing is that when running the Sample Book from Madcap, the PDF output will be generated without any problem.
I reported this bug together with my current project that run into the problem.

[RussGuill]

The only strange thing about this update is that the installer didn't tell me the patch install had completed - the installer window just disappeared. Something to notify the user the patch was successfully installed would be helpful in the future.

[RamonS]

because my default browser is not IE, but I've gotten used to the Microsoft-only approach and developer arrogance....or better to say ignorance here. What makes me wonder is why QA doesn't catch something obvious like this.

My default browser isn't IE either (I use both FF and Safari) but I have never seen that error. What does it mean?

My guess is that when Flare told Windows to go and pop-up the browser with a specified URL the DotNet runtime got confused since IE isn't the default browser. Windows itself figured it out alright since FF came up fine.

[KevinDAmery]

Just to confuse matters, my default browser is FF and I didn't get an error. I do have IE7 installed, but I only use it for our internal resources (which naturally are also M$ exclusive...

[Richard Ferrell]

If you need the update and behind a Firewall, or not able to download it see the following Knowledge base article.

http://kb.madcapsoftware.com/default_CSH.htm#PATF41SP1

[wijnand]

My intention was just to explain what the MSP was, aside from supporting flare I also support Windows Installer products. the reason why the entire MSP is so slow is because it does an integrity test on your source files stored in the C:\windows\installer folder. Once it has verified that everything is in order then it will start the setup and do a "reinstall"

It is not my intention for people to go clear that folder out, if you do you will enjoy the following benefits:

unable to uninstall your programs
unable to patch your programs

.NET isnt the problem with the FireFox, aslong as Firefox has the same hooks and entry points as IE it should work fine with it. The way you get a download link to your IE is something to this Effect: C:\Program Files\Microsoft\IE\Iexplorer.exe "www.madcapsoftware,com/downloadpatch.msp" and it will open the correct download link now i assume that FF has something along the same lines.

The problem with building ontop of .NEt Java is that unlike Windows 32 API you are relying on another platform where you have barely any control over. The upside however is your delegating a lot of complex things out of your hands. it took me 3 weeks to get a very proper Windows GUI with WIN32 and C and in C# and windows forms i was done in one evening. I have to add though my C knowledge is a bit muffy.

Just be patient when it is running the patch its pretty dependant on how fast your I/O is and how many programs you have installed.

[Richard Ferrell]

We are not using the MSP anymore, we have changed it an EXE, this is because older Image editing utilities such as Paintshop and Snag-IT change the file ext .MSP to thier programs thinking its a Microsoft Paint image.

[booey]

It would be very handy for Madcap to publish detailed release notes with updates and new versions. It seems that every release fixes broken stuff that we have had a workaround for and then the workaround doesnt work. Often we only find out by accident.

[GregStenhouse]

It would be very handy for Madcap to publish detailed release notes with updates and new versions. It seems that every release fixes broken stuff that we have had a workaround for and then the workaround doesnt work. Often we only find out by accident.

I agree, we rely heavily on import from FrameMaker, and part of this update said "Frame import fixes". I'd like to know what was fixed, or more importantly, what was broken with the old version.

[NorthEast]

Is anyone having problems with the project analysis in 4.1.40?

After installing the update Flare's project analysis reported thousands of broken links in a project which had no broken links. I deleted the project's database in the Analyzer folder and let it scan the files again, but it still says there are 3000 broken links and over 1600 database errors in the new database (I opened it in Analyzer afterwards to check the figures).

[NickC]

I also run into the problem

Internal Error: Parameter is not valid

when building the PDF output. With the previous v4.1.19 it didn't.
The strange thing is that when running the Sample Book from Madcap, the PDF output will be generated without any problem.
I reported this bug together with my current project that run into the problem.

I also have this problem. I have two PDF targets in one project and the first one in the list generates the second one does not. I've checked that all parameters are identical but still get the message. I've tried command line (madbuild) but the result is the same - the "Internal Error: Parameter is not valid" appears in the final part of the generation. Renaming target, cleaning output, deleting target which works, making target primary- no dice...

Please advise if there is a fix or workaround to this.

[DocuWil]

Right, and now have rolled back to 4.1.19.
I cannot stick with the 4.1.40.
I have to continue my job and not investigating what is going and what's not.

[Richard Ferrell]

If you are having this issue please open a support ticket

[DocuWil]

Sorry Richard,
I should have said that with my latest post.
I already did. One of the first I suppose.

[enricosavazzi]

I installed the update this morning, and have since not been able to build PDF output. I encounter the following error soon after the build initiates.

Internal Error: Parameter is not valid

This has been reproduced by one other writer on a different machine.
Has anyone else seen this?

Rolling back...

I have, and not only in 4.1.40 but since 4.0. In fact, I am simply unable to generate any PDF output from large projects (which is not a big problem, because anyway I prefer to generate Word output, tweak a few things by attaching a Word template, then generate PDF from there with Acrobat Pro). I found also that Word takes care automatically of a few things, like resizing images too wide to print on a page, that Flare does not to when directly generating PDF output.

[DocuWil]

Hi Enrico,

But the advantage of generating direct PDF is: Word is not needed any more.

I found also that Word takes care automatically of a few things, like resizing images too wide to print on a page, that Flare does not to when directly generating PDF output.

It is possible:
In your stylesheet: goto img, select Unclassified and set max-width.
Then, if you put an image into your topic select it and right-click to select Object (You can also use the shortcut CTRL+ALT+B). In the dialog Maximum Size set Height to Automatic.
That should do it and also should take the resolution into account.