How can Labview 7.1 deploy an application to run on Win95?

[WayTreader]

I know the requirements for the run-time engine for 7.1 don't include the Win9x OS.   And for LV 7.0 it includes Win98 but not Win95.   But am I missing something?  It doesn't seem like it should be such a problem.   If an addon can facilitate deploying applications to any embedded processor running any OS,  then why not to an intel pentium running Win95?

[Chaos]

The different operating systems are dropped depending if or not Microsoft supports it.  A while back Microsoft did a press release stating Win98 would not be supported and LabVIEW was developed accordingly. Some time after the fact Microsoft backpeddled and decided to extend support but by this time it was too late to add this back into LabVIEW.  Windows 95 is the same story.  Its impossible to get support from Microsoft for Windows 95 so LabVIEW doesnt support it as NI has no way to test if something is buggy on a non-supported platform.

BTW, if you are refering to LabVIEW embedded this is different beast altogether.  This "addon" allows you to directly target embedded processors (kinda like FPGA) but your comparison is faulty.  The pentium chip boots into Windows 95 from hard disk so whats on the chip is the *BIOS* and loaders, not Windows.  If you *could* run LabVIEW embedded and target this chip it would no longer have this bios (or anything else) and it would only do what you programmed it to do and certainly no longer boot up as you are accustomed to seeing it...

[WayTreader]

Thank you Chaos. I see what they did with the "support" issue. But I don't think the analogy is faulty at all. The LabVIEW Embedded Development Module implements development in two steps. The first step involves the integration of a third party toolchain and OS into the build process by using the Embedded Project Manager. This is a one-time operation for the target toolchain, OS, and processor combination. This is very much like the run time engine idea. If new features aren't supported on the target system, of course they can't be used, but like the quote above say's "its a one time operation for a target system." Of course the "unsupported OS" is not appropriate for an upgraded development environment, but there is no reason it should be prohibited as a target system. (I know there are ways to keep using the old development environments, but...) Even Microsoft doesn't prohibit using the old system just because they won't "support it".