Windows7 Compatible for filePro

[Nancy Palmquist]

Mark,

Sorry for the top post, I have done that ever since John mentioned it 
was easier for him to follow with his reader.

I hate these words "compatible" or "certified" or "compliant", when they 
do not define what standard it meets.

I fight this all the time with the Medical stuff.  They want "electronic 
medical records", I have yet to find any definition for that anywhere.  
Each software developer defines it themselves.

I can help a customer make "electronic medical records" by having them 
scan documents, save them on an electronic drive, use adobe to attach a 
password (complying with the true chart standard for secure and 
unchanging.) I have done just this, which meets the "electronic medical 
records" basic definition.  I do not think it is entirely workable 
without some exchange mechanism for the Providers.

Currently I have embedded the filePro runtime into my installation which 
is built with Setup Factory.  (Tried Install Shield but found it too 
expensive and too complex to be useful.  Got my money back.)

My install is currently installing 5.0 - that was the last version I 
could install without getting a license file and all kinds of data from 
the customer to attach it to their system.

I have actually purchased 5.6 for almost all of my customers, but I have 
only installed a few on new clients.

Finally see my notes below.

On 3/31/2010 1:46 PM, Fairlight wrote:
> Simon--er, no...it was Nancy Palmquist--said:
>    
>> Guys,
>>
>> I am wondering if anyone would suggest that filePro 5.6 is Windows 7
>> compatible.  I can certainly install it and make it work on my Windows7
>> computer.  I had to license it to the Drive ID, but it works.
>>      
> Then technically, I'd say it's compatible.
>
> The reality is that I can't think of anything that fP does that's not
> compatible, unless Windows entirely stripped out the "DOS" type console, or
> changed the API to it.  If fP runs, the rest is pretty generic.  I've not
> seen the internals, but just by looking at what it does and doesn't do,
> there's nothing magical there that seems to rely on specific versions of
> any given OS, barring shared library version issues on linux.
>
>    
>> My hesitation is in the area of printing.  I am seeing a real disconnect
>> with the ability to print from filePro to the new printers available for
>> new machines with Win7.
>>
>> The newer printers seem to have PCL6 instead of PCL5.
>>      
> Try using PrintWizard from Rasmussen Software?
>
> PCL6 is not a Windows 7 thing, it's a printer industry thing.  Blame HP.
>
>    
>> If filepro would provide, out of the box, a proper way to handle
>> printing on Windows, I think I would feel better about suggesting that
>> my software - built under filepro - is windows 7 compatible.
>>      
> Luck on that.  :/  If it hasn't happened in the last half decade, I don't
> see it happening anytime soon, if ever.
>
>    
>> Also, I have no good way to provide an installation CD for my MOS
>> software that will properly install both the filePro runtime and my
>> application.  I am still hung up on that licensing requirement that they
>> download a file, instead of an interface that allows them to enter an
>> activation code on the screen.  My customers are stuck on 5.0 for this
>> application, because there is no way I can distribute an application and
>> have the end user get a license file, supply a license file on a
>> "diskette?" .
>>      
> -Assuming- that you don't mind an installer just copying files to their
> proper location, rather than doing a full, official "finish" each time,
> what about making an actual setup installer with something like InnoSetup,
> or NSIS?  You could make that install everything, both fP and the custom
> system you have.  Actually, you could have InnoSetup run "finish",
> technically speaking, but that seems like a Bad Idea[tm] to give the power
> to screw that up to a customer.
>
> As for the license...it just depends how you do it.  Do you get the license
> for them anyway and install it yourself, or do you have them go through the
> actual licensing step on the way?  Because if it's the latter, there's
> quite possibly a way to programmatically grab the required information and
> post it to the fP-Tech web site, then download the file.  It would involve
> writing an application to do so, however, and then having the installer run
> that program.  You'd just bundle it into the installer and have the
> installer run it as part of the install process--just like lots of programs
> run sub-installers for the Microsoft Visual C++ 2005 Runtime Executable
> Libraries, or DirectX.  Same principle, except this program needs to get
> data from the system and then grab the right stuff from fP-Tech.
>
> If you get the license for them yourself anyway, you could just copy the
> license file to the right spot in the distribution and recompile a new
> installer for each client.  That's the dead easy way of doing it.
>
>    
How is cutting a unique distribution for each customer "dead easy"?  I 
want to generate one installation CD, with the runtimes I need and my 
software.  During installation, I want a screen to popup that can ask 
for an Activation KEY for FilePro.   I want to be able to have a 
customer download the installation, and install it without trying to 
figure out the license file stuff they do now.  They keep telling me it 
is possible, but never get around to the function of it.  I really still 
think the license manager they added to control installations, has been 
the item that has most killed their business.  It has most radically 
affected the windows side of their business and driven many of my 
customer to other stuff, or to just sit at 5.0 until they die.

I have NEVER had an installation on Windows or Unix that worked right 
the first time.  If I am unable to install filePro, without problems, 
how can I expect a customer to do it?
So to tell Microsoft that I have tested my application and it is Windows

>> 7 compatible has left me cold.  I don't think filePro has the features
>> that would meet that level of functionality on Windows7.
>>      
> You're actually wanting to bother with Windows 7 certification?  I
> wouldn't.  I mean...let's face reality...  If the software works on the
> platform, it works on the platform.  Certification logos look great on a
> website that sells heavily consumer-oriented, commodity software (WinZip,
> Carbonite, Acronis, etc.).  Your software doesn't really fall into that
> category, though.  It's specialised.  So what's the point of certification,
> in reality?
>    
Tom told Microsoft he was testing it.  I am stuck dealing with the 
issue.  I am going to ignore them.


Nancy

-- 
Nancy Palmquist         MOS&  filePro Training Available
Virtual Software Systems    Web Based Training and Consulting
PHONE: (412) 835-9417           Web site:  http://www.vss3.com