Thursday, 15 November 2012

Songs for the LabVIEW Programmer (songs about LV and the dataflow experience) - NI Discussion Forums

Songs for the LabVIEW Programmer (songs about LV and the dataflow experience) - NI Discussion Forums:




Songs for the LabVIEW Programmer (songs about LV and the dataflow experience)

08-04-2010 11:17 AM

Last year at the LAVA BBQ here at NI Week, several users -- after a bit of drinking -- discussed the need for some LabVIEW drinking songs. Since NI tries to be responsive to user needs, I started creating songs to meet that need, and pulled on other R&D team members to help out. I already had a couple of children's songs for teaching LV to kids. So for the LAVA BBQ last night, I released Songs For The LabVIEW Programmer. There were only paper print outs available last night. Today I'm posting the songs for everyone to enjoy.

===================================
Songs For The LabVIEW Programmer
  • Drinking Songs: Songs for singing in groups, particularly while drunk, celebrating LabVIEW.
  • Teaching Songs: Songs for young children, just learning LabVIEW for the first time.
  • Emotional Songs: The angst, the joy, and all the other emotions that programming LabVIEW may raise within the soul.

The Debugging Tune*
(to the tune of The Itsy Bitsy Spider**)

The execution highlight
goes down the wire route.
All along the way,
probes may call the data out.
If it hits a breakpoint then
                there it will remain
until the Pause button
lets the highlight move again!

* because spiders are good at removing bugs
** feel free to adapt the original’s hand gestures!

There Was An Old Lady Who Wrote A VI
(to the tune of There Was An Old Lady Who Swallowed A Fly)

There was an old lady who wrote a VI.
I don’t know why she wrote the VI – it’s a blank VI!

There was an old lady who dropped “Simulate Signal.”
I don’t know why she needed the signal
– perhaps she just likes a noisy signal?
She needed the signal to start the VI.
I don’t know why she wrote the VI – perhaps she’s high?

There was an old lady who dropped “Power Spectrum.”
I don’t know why she needed the spectrum
– perhaps she just pulled it out of her rectum?
She needed the spectrum to filter the signal.
She needed the signal to start the VI.
I don’t know why she wrote the VI – it’s a trivial VI.

There was an old lady who dropped a graph.
I don’t know why she needed the graph
– perhaps she did it just for a laugh?
She needed the graph to display the spectrum.
She needed the spectrum to filter the signal.
She needed the signal to start the VI.
I don’t know why she wrote the VI – to impress a guy?

There was an old lady who dropped a while loop.
I don’t know why she needed a loop, why she needed a loop, why she needed a loop, why she – *SLAP*. (Oh, thanks…)
She needed the loop to repeat the graph.
She needed the graph to display the spectrum.
She needed the spectrum to filter the signal.
She needed the signal to start the VI.
I don’t know why she wrote the VI – it’s a broken VI.

There was an old lady who created a button.
I don’t know why she created the button
– I’d ask her but she told me not to butt in.
 She needed the button to stop the loop.
She needed the loop to repeat the graph.
She needed the graph to display the spectrum.
She needed the spectrum to filter the signal.
She needed the signal to start the VI.
I don’t know why she wrote the VI – it’s a familiar VI.

There was an old lady who wrote Acquire-Analyze-Present.
And now we know why she wrote the VI: She works for NI!



What Do You Do With A Broken Wire?
(to the tune of What Do You Do With A Drunken Sailor?)

CHORUS:
What do you do with a broken wire?
What do you do with a broken wire?
What do you do with a broken wire to fix a broken VI?

Verse 1:
Change one of its ends to an indicator!
Change one of its ends to an indicator!
Change one of its ends to an indicator!
That’ll fix the VI!

Verse 2:
Insert a node to convert the source type!
…
That’ll fix the VI!

Verse 3:
Check all ends connect to terminals!
…
That’ll fix the VI!

Verse 4:
Use control-B and just remove it!
…
That’ll fix the VI!

Verse 5:
Do whatever the Error Window tells ya!
…
That’ll fix the VI!

Message 1 of 10 (1,989 Views)
 
Reply
Trusted Enthusiast
Trusted Enthusiast
AristosQueue
Posts: 2,149

Re: Songs for the LabVIEW Programmer (songs about LV and the dataflow experience)

08-04-2010 11:18 AM
Mary Had A Block Diagram
(to the tune of Mary Had A Little Lamb)

Mary had a block diagram
                     block diagram
                     block diagram
Mary had a block diagram
     and she kept adding nodes.

It grew larger than the screen one day
                                         screen one day
                                         screen one day
It grew larger than the screen one day
     which was against the rule.

So Mary created subVIs
                              subVIs
                              subVIs
So Mary created subVIs
     with “Convert To SubVI” tool!


LabInterruptedVIEW
(to the tune of An Austrian Went Yodeling)

Ohhh, a programmer launched LabVIEW, a new project begun,
When along came a power spike, interrupting the fun.  L

Ohhhhhhhhh (lots of pounding on the table)
New Class! New V-I! Control+Space! Wire Click! Noooo! (howls)

Oh, a programmer launched LabVIEW, a new project begun,
When along came a manager, interrupting the fun.  L

Ohhhhhhhhh (lots of pounding on the table)
New Class! New V-I! Control+Space! Wire Click!
“That would be greaaaat.” Noooo!

Oh, a programmer launched LabVIEW, a new project begun,
When along came a forced reboot, interrupting the fun.  L

Ohhhhhhhhh (lots of pounding on the table)
New Class! New V-I! Control+Space! Wire Click!
Dum-du-du-du-duuum! (MS Windows launch sound)
“That would be greaaaat.” Noooo!

<and so on, each verse adding another sound or phrase>

LAST VERSE:
Oh, a programmer launched LabVIEW, a new project begun,
When along came some spare time, and now the VI does run!


The Event Structure
(to the tune of Pop Goes The Weasel)

All around the front panel
                the user clicked the mouse
And as it moved or clicked or dragged…
                POP went the events!



Unbreak My VIs by Akash Bhakta
(to the tune of Unbreak My Heart by Toni Braxton)

Un-break my VI
Say you can run it again
Undo this break that you caused
When I broke something else
That does not affect my VI
Un-open this error list
I scrolled so many times
Un-break my VI
My VI...



LabVIEW Rhapsody (by Stephen Mercer, Christina Rogers, & Jeff Boettcher)
(to the tune of Bohemian Rhapsody -- this song is loosely based on a new hire on the LV R&D team breaking LabVIEW.exe when he submits his first feature into the code base. There are a couple of internal terms you should know. "Bowling" is our term for submitting code to Perforce. The "trolls" are project managers who control which developers can submit to Perforce at what times -- they ask questions like, "Have you tested the code? Did you get someone to review it?" AppLibs is the build for the lvrt.dll and InTheDark is the build for LabVIEW RealTime.)

Is this my real job?
Is this just fantasy?
Working on LabVIEW,
Can’t believe they just hired me.
Open VIs
Look at diagrams in G…
We can do better, we need no C routine
Because it’s graphical, data flow,
Down the wires, into nodes,
Every way the code flows, that’s what really matters, in G, in G

Manager, just broke the build.
Used Perforce, synch’d to head,
Hit submit, and now it’s dead.
Manager, the test suite used to run,
But now I’ve gone and blown it all away.
Manager, oooo,
Didn’t mean to make you cry.
I’ll have it fixed again this time tomorrow!
Carry on, carry on, (as if deadlines really matter…)

Too late, release has come
Sends shivers down my spine
CAR list growing all the time.
OK, everybody, I’ve got to bowl,
Just can’t spend any more time to test the code.
Mama, oooo, (anyway the code bowls)
I don’t want to bowl…
I sometimes wish they’d ne’er filed this CAR at all…

The build machine syncs all the files that it can,
Incredibuild, Incredibuild – can you make it build faster?
InTheDark and Applibs – did you build the realtime?  No!
LabVIEW linking, LabVIEW linking,
LabVIEW linking, LabVIEW linking,
LabVIEW linking, here we go – log files show…

I’m just a newbie, nobody told me!
He’s just a new grad from college recently…
He’ll bring in donuts for this bowl travesty.
Easy bug, easy fix – will you let me bowl?
Broken Build! No, we will not let you bowl! Let him bowl!
Broken Build! We will not let you bowl! Let him bowl!
Broken Build! We will not let you bowl! Let me bowl!
We will not let you bowl! Let me bowl! Never!
Never let you bowl! Let me bowl!
Never let you bowl! Oooo
No, no, no, no, no, no, YES  -
Oh mama mia, mama mia, mama mia I can bowl!
The manager has given troll permission to me
yes me
yes me!

So you think you can submit without testing real time?
So you think you can bowl and then leave for a while?
Oh, baby – can’t do this to our baby.
Just back it all out, just back that change right outta here.

Ooh yeah, ooh yeah
LabVIEW really matters.
Anyone can see
LabVIEW really matters – LabVIEW really matters to me

In this way the code bowls…

Message 2 of 10 (1,988 Views)
 
Reply
Trusted Enthusiast
Trusted Enthusiast
aeastet
Posts: 2,174

Re: Songs for the LabVIEW Programmer (songs about LV and the dataflow experience)

08-04-2010 12:19 PM
We did this one in another thread Knight mares: Ben has one there too.

(John lenon Imagine)

Imagine there's no Visual Basic
It's easy if you try
Only Labview for coding
Around us only wires
Imagine all the people
Living for a day

Imagine there's only blockdiagrams
It isn't hard to do
Nothing to kill or die for
And event structures too
Imagine all the people
Living life in GUI

You may say that I'm a dreamer
But I'm not the only one
I hope someday you'll join us
And the world will program as one

Imagine written code
I wonder if you can
No need for probes
A brotherhood of man
Imagine all the people
Sharing all the code

You may say that I'm a dreamer
But I'm not the only one
I hope someday you'll join us
And the world will program as one
Tim
Johnson Controls
Holland Michigan
Message 3 of 10 (1,969 Views)
 
Reply
Trusted Enthusiast
Trusted Enthusiast
Jeff·Þ·Bohrer
Posts: 4,373

Re: Songs for the LabVIEW Programmer (songs about LV and the dataflow experience)

08-04-2010 02:06 PM
As originally presented here

(too, the tune of...."Mary Poppin's" song "Supercalifragilisitexpalidous" )

BE.. cause I was afraid to post when I was new to Lab(VIEW)
and Ben, he gave my code a tweak, and told me that I had,(Two)
used a local varible that made my VI bad.(oooh)
Then Ravens Fan explained to me what I really had(Whoo!)

Ohhhh...

Altenbach, smercurio and nugget for the week...
Altenbach, smercurio and nugget for the week...
Altenbach, smercurio and nugget for the week...
Super class of LVOOP and now my code's not weak!

Hummmm..LabVIEW.ini  Hummmmm ditty I  
Hummmm..LabVIEW.ini  Hummmmm ditty I 

SO.. as you'll see I'm soon to be an NI gifted Knight
And all my LabVIEW code will be just so completely right
I'll never miss a single trick my postings are all tight
And when I send an app to you it'll sing the bugs goodnight!

OHHHH

Altenbach, smercurio and nugget for the week...
Altenbach, smercurio and nugget for the week...
Altenbach, smercurio and nugget for the week...
Super class of LVOOP and now my code's not weak! ..

(Dick VanDyke- eat your heart out! )

 

"All shall be well and all shall be well and all manner of things shall be well" -Julian
Message 4 of 10 (1,951 Views)
 
Reply
Member RyanP
Member
RyanP
Posts: 11

Re: Songs for the LabVIEW Programmer (songs about LV and the dataflow experience)

08-09-2010 09:59 AM
aka ... "Songs in the Key of G"? :robotvery-happy:

Oh yes ... I went there :-)
Message 5 of 10 (1,768 Views)
 
Reply
Active Participant Henrik_Volkers
Active Participant
Henrik_Volkers
Posts: 1,608

Re: Songs for the LabVIEW Programmer (songs about LV and the dataflow experience)

08-10-2010 03:17 AM
I remember that 'in the old days' the LabVIEW Zone had a Fun section with a song 'Write in G' (Org. 'Let it be', Beatles)....
Can't find it on the first try...
Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'
Message 6 of 10 (1,597 Views)
 
Reply
Proven Zealot
Proven Zealot
Ray.R
Posts: 9,455

to the music of Sound of Silence (Simon - Garfunkel)

08-16-2010 09:48 AM
Hello dark screen, my old friend
I've come to type to you again
Because algorithms are softly creeping
Written in my head while I was sleeping
And the code that was planted in my brain
Still remains
Within the sound of of typing

In front of my keyboard I code alone
Till I get distracted by my phone
'Neath the glow of my desk lamp
Fever's burning and I feel damp
When my eyes were stinging of dryness and constant light
both day and night
And touched the sound of coding

And in the diode light I saw
Ten thousand comments, maybe more
Code description without speaking
Commands executed without listening
Coders writing software that will never share
And no one dared
Disturb the sound of coding

"Fools", said I, "You do not know
coding, like a cancer grows
Hear my words that I might teach you
Take my diagrams that I might show you"
But my keys, like silent raindrops fell
And echoed
In the wells of coding

And the people reviewed my code
they were nasty and bold
And the code missed out on warning
In the code that was developing
And the note said, "The words of the Architect are written in the software specs
Just read the specs"
And whispered in the sounds of coding
===========  =========== * ===========  ==============
(starting to) See Life in a brand new way...

b* ^ )
Message 7 of 10 (1,472 Views)
 
Reply
Active Participant RobCole
Active Participant
RobCole
Posts: 568
0 Kudos

Re: to the music of Sound of Silence (Simon - Garfunkel)

08-16-2010 03:35 PM
A while ago, Enrique posted two songs that he recorded called I Code In LabVIEW and G Freak.

The link to the page in the forums is Here for the music.

Hmmm. I decided to test the links and found they're not working. I have them downloaded - I wonder if I can/should upload them.

     Rob
Message 8 of 10 (1,453 Views)
 
Reply
Trusted Enthusiast
Trusted Enthusiast
SteveChandler
Posts: 2,230

Re: Songs for the LabVIEW Programmer (songs about LV and the dataflow experience)

01-15-2011 09:25 AM
I already posted this already in it's own thread so sorry if you already seen it. But Jeff told me about this dedicated thread.

Capture.PNG
=====================
LabVIEW 2011

Certified LabVIEW Developer


'via Blog this'
Posted by at No comments:

32-bit and 64-bit Windows: frequently asked questions

32-bit and 64-bit Windows: frequently asked questions:


32-bit and 64-bit Windows: frequently asked questions

Here are answers to some common questions about the 32-bit and 64-bit versions of Windows.
Hide all

What is the difference between 32-bit and 64-bit versions of Windows?

The terms 32-bit and 64-bit refer to the way a computer's processor (also called a CPU), handles information. The 64-bit version of Windows handles large amounts of random access memory (RAM) more effectively than a 32-bit system.

How can I tell if my computer is running a 32-bit or a 64-bit version of Windows?

To find out if your computer is running a 32-bit or 64-bit version of Windows in Windows 7 or Windows Vista, do the following:
  1. Open System by clicking the Start button Picture of the Start button, right-clicking Computer, and then clicking Properties.
  2. Under System, you can view the system type.
If your computer is running Windows XP, do the following:
  1. Click Start.
  2. Right-click My Computer, and then click Properties.
    • If you don't see "x64 Edition" listed, then you're running the 32-bit version of Windows XP.
    • If "x64 Edition" is listed under System, you're running the 64-bit version of Windows XP.

Which version of Windows 7 should I install: the 32-bit version or the 64-bit version?

To install a 64-bit version of Windows 7, you need a CPU that's capable of running a 64-bit version of Windows. The benefits of using a 64-bit operating system are most apparent when you have a large amount of random access memory (RAM) installed on your computer, typically 4 GB of RAM or more. In such cases, because a 64-bit operating system can handle large amounts of memory more efficiently than a 32-bit operating system, a 64-bit system can be more responsive when running several programs at the same time and switching between them frequently. For more information, seeInstalling and reinstalling Windows 7‍.

How do I tell if my computer can run a 64-bit version of Windows?

To run a 64-bit version of Windows, your computer must have a 64-bit-capable processor. To find out if your processor is 64-bit-capable in Windows 7 or Windows Vista, do the following:
  1. Open Performance Information and Tools by clicking the Start button Picture of the Start button, and then clicking Control Panel. In the search box, type Performance Information and Tools, and then, in the list of results, click Performance Information and Tools.
  2. Do one of the following:
    • In Windows 7, click View and print detailed performance and system information.
    • In Windows Vista, click View and print details.
  3. In the System section, you can see what type of operating system you're currently running under System type, and whether or not you can run a 64-bit version of Windows under 64-bit capable. (If your computer is already running a 64-bit version of Windows, you won't see the 64-bit capable listing.)
To see whether a computer running Windows XP is capable of running a 64-bit version of Windows, do the following:
  1. Click Start.
  2. Right-click My Computer, and then click Properties.
    • If "x64 Edition" is listed under System, your processor is capable of running a 64-bit version of Windows.
    • If you don't see "x64 Edition" listed, your processor still might be capable of running a 64-bit version ofWindows. To find out for sure, download and run the free Windows 7 Upgrade Advisor from the Windows 7Upgrade Advisor webpage.

Can I upgrade from a 32-bit version of Windows to a 64-bit version of Windows 7 or from a 64-bit version of Windows 7 to a 32-bit version of Windows?

You can use the Upgrade option during Windows 7 installation, which preserves your files, settings, and programs, only if you're currently running a 32-bit version of Windows Vista and you want to upgrade to the 32-bit version of Windows 7. Similarly, if you are running a 64-bit version of Windows Vista, you can only perform an upgrade to a 64-bit version ofWindows 7. For more information, go to Upgrading to Windows 7: frequently asked questions on the Windowswebsite.
If you want to move from a 32-bit version of Windows to a 64-bit version of Windows 7 or vice versa, you'll need to back up your files and choose the Custom option during Windows 7 installation. Then, you'll need to restore your files and reinstall your programs. For more information about performing a custom installation, see Installing and reinstalling Windows 7‍.

Notes

  • To install a 64-bit version of Windows 7 on a computer running a 32-bit version of Windows, you'll need to start, or boot, your computer using a 64-bit Windows 7 installation disc or files.
  • If you start your computer using a 64-bit Windows 7 installation disc or files, but your computer isn't capable of running a 64-bit version of Windows, you'll see a Windows Boot Manager error. You'll need to use a 32-bit Windows 7installation disc or files instead.
  • Windows Easy Transfer can't transfer files from a 64-bit version of Windows to a 32-bit version of Windows. If you're running a 64-bit version of Windows Vista but you plan to install a 32-bit version of Windows 7, you can move your files to an external location manually or use Backup and Restore in Windows Vista. For more information, go to Back up your files and Restore a backup created on a previous version of Windows on the Windows website. (If you're running a 64-bit version of Windows XP, you'll need to move your files to an external location manually.)

Can I run 32-bit programs on a 64-bit computer?

Most programs designed for the 32-bit version of Windows will work on the 64-bit version of Windows. Notable exceptions are many antivirus programs.
Device drivers designed for the 32-bit version of Windows don't work on computers running a 64-bit version of Windows. If you're trying to install a printer or other device that only has 32-bit drivers available, it won't work correctly on a 64-bit version of Windows. To learn how to check for drivers, see Update a driver for hardware that isn't working properly or go to the device manufacturer's website. You can also get information about drivers by going to theWindows 7 Upgrade Advisor webpage.

Can I run 64-bit programs on a 32-bit computer?

If the program is specifically designed for the 64-bit version of Windows, it won't work on the 32-bit version of Windows. (However, most programs designed for the 32-bit version of Windows do work on the 64-bit version of Windows.)
Device drivers designed for the 64-bit version of Windows don't work on computers running a 32-bit version of Windows. To learn how to check for drivers, see Update a driver for hardware that isn't working properly or go to the device manufacturer's website. You can also get information about drivers by going to the Windows 7 Upgrade Advisor webpage.

How can I find programs and devices that work with the 64-bit version of Windows 7?

To find programs and devices that work with Windows 7, look for products that display the "Compatible with Windows 7" logo. They've been tested to be compatible with both the 32-bit and 64-bit versions of Windows 7.
You can also go online to the Windows 7 Compatibility Center and check to see whether the program or device is compatible with the 64-bit version of Windows 7. Hardware and software manufacturers continue to update this information, so check back often.

If I'm running a 64-bit version of Windows, do I need 64-bit drivers for my devices?

Yes. All hardware devices need 64-bit drivers to work on a 64-bit version of Windows. Drivers designed for 32-bit versions of Windows don't work on computers running 64-bit versions of Windows.
To learn how to check for drivers, see Update a driver for hardware that isn't working properly or go to the device manufacturer's website. You can also get information about drivers by going to the Windows 7 Upgrade Advisor webpage.
Article ID: MSW700010





'via Blog this'
Posted by at No comments:

Wednesday, 14 November 2012

Enable or Disable UAC From the Windows 7 / Vista Command Line - How-To Geek

Enable or Disable UAC From the Windows 7 / Vista Command Line - How-To Geek:


Enable or Disable UAC From the Windows 7 / Vista Command Line

If you’ve used Windows Vista for more than 3.7 minutes, you know what UAC (User Account Control) is.. it’s the obnoxious, nagging popup window that will be your life for the next 3-5 years unless you switch back to XP in frustration, or to a better OS like… OS X, Suse, Ubuntu, or even XP.
Update: This should also work on Windows 7.
Note: Disabling UAC will lead to a less secure system, so be warned.
Windows needs your permission to annoy the crap out of you:
uac3.png
There’s a quick way you can enable or disable this annoying window from the command line:
Disable UAC
C:\Windows\System32\cmd.exe /k %windir%\System32\reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 0 /f
Enable UAC
C:\Windows\System32\cmd.exe /k %windir%\System32\reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 1 /f
After you enable or disable UAC, you will have to reboot your computer for the changes to take effect.
You can also enable or disable this from the Control Panel if you choose.



'via Blog this'
Posted by at No comments:

User Account Control, Digital Signing, and Manifests in LabVIEW Built Applications - National Instruments

User Account Control, Digital Signing, and Manifests in LabVIEW Built Applications - National Instruments:


User Account Control, Digital Signing, and Manifests in LabVIEW Built Applications

Primary Software: LabVIEW Development Systems>>LabVIEW Professional Development System
Primary Software Version: 8.2
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem: I need to make my LabVIEW applications and installers compatible with Windows Vista. Is there anything specific I need to do?

Solution:

User Account Control

Windows Vista from Microsoft introduces additional levels of security, including User Account Control. By prompting the user to enter an administrative password prior to installing applications or completing other tasks, User Account Control helps prevent users from inadvertently introducing viruses or other types of changes that might destabilize the system. Additionally, a user who logs into Windows Vista as a standard user can write only to specific locations on disk. Standard user is the default login for Windows Vista. Refer to the KnowledgeBase for more information about User Account Control on Windows Vista.
The security changes introduced by Windows Vista result in the following two issues to consider when using the LabVIEW Application Builder for Windows Vista:
  • LabVIEW embeds an application manifest in every LabVIEW built application and installer.
  • Built applications and installers for LabVIEW built applications are not signed.
LabVIEW 8.2.1 is the first version of LabVIEW to officially support Windows Vista.
In addition to this KnowledgeBase topic, you can refer to the following KnowledgeBase topic for more information about developing applications for Windows Vista:
  • KnowledgeBase— Contains links to several resources external to the National Instruments Web site, including Microsoft.

Application Manifests

LabVIEW 8.2.1 embeds an application manifest in every LabVIEW built application and installer. Because the manifest is embedded in the application, you must retrieve the manifest before it appears in the directory with the application. The manifest is an XML file with the extension .manifest. The manifest contains information that describes the application properties to Windows. While manifests are not new to Windows, the security section of the manifest is a new feature. You can now specify the requested execution level in the manifest for an application you deploy on Windows Vista.
Specifying the execution level of the application determines the required security privileges you need to launch an application. The execution level of the application determines if the application displays a dialog box prompting the user to give administrator consent or to enter an administrator password before launching the application. Applications that require administrator privileges have a security shield overlay on the application icon. Whether the application runs as an administrator or standard user then determines several properties of the application, including the directories to which the application can write. If you launch an application as a standard user, the application cannot write to protected directories and registries. The Program Files directory is an example of a protected directory on Windows Vista.
Microsoft recommends that applications run without requiring administrator privileges. Therefore you should design applications so they do not attempt to access protected areas of the operating system. Running without administrator privileges gives all users the opportunity to run the application as intended.
The following code is an example manifest for a LabVIEW built application.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0>
<assemblyIdentity version="1.0.0.0"
processorArchitecture="X86"
name="National Instruments.LabVIEW.LabVIEW"
type="win32"/></assemblyIdentity>
<description>LabVIEW Development System</description>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel
level="asInvoker"
uiAccess="false"/>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>The requested execution level of a built application can be any of the following values:
  • asInvoker—(Default) The built application executes with the same access privileges as the user, either standard or administrator. The application does not display a dialog box prompting the user for consent before it runs. If the application runs as standard user, the application cannot write to protected directories. If the application runs as administrator, the application can write to protected directories.
  • highestAvailable—The built application executes with the highest access privileges possible. If the user has only standard user privileges, the application does not display a dialog box prompting the user for consent, but the application cannot write to protected directories. If the user has administrative privileges, the application displays a dialog box prompting the user to either consent or to enter the administrator password and can write to protected directories.
  • requireAdministrator—The built application executes at the administrator level. If the user has only standard privileges, the application displays a dialog box prompting the user to enter the administrator password and can write to protected directories. If the user has administrator privileges, the application displays a dialog box prompting the user for consent before it runs. The application can write to protected directories.
If you develop a LabVIEW built application in LabVIEW 8.2.1 or later and deploy the application on Windows 2000/XP or earlier, a built application that includes a manifest and has the requested execution level specified does not exhibit the Windows Vista behavior. Windows 2000/XP ignores the security section of the manifest.
The setup.exe in LabVIEW built installers also contains a manifest. The default requested execution level is requireAdministrator. Because the setup.exe updates system-level files, settings, and configurations, avoid changing the requested execution level of setup.exe. Changing the requested execution level of setup.exe might cause the installer to function incorrectly.
Note: Versions of LabVIEW prior to 8.2.1 also embed a manifest; however, the security section of the manifest is new to LabVIEW 8.2.1. The security section of the manifest is particularly important for applications you deploy to a Windows Vista system.
Refer to the KnowledgeBase for more information about application manifests.

Editing the Application Manifest

Microsoft highly recommends that the requested execution level of an application be asInvoker. Therefore, asInvoker is the default requested execution level for all LabVIEW 8.2.1 built applications. However, there might be occasions where you cannot adhere to this recommendation. Complete the following steps to edit the manifest.
  1. You must verify that you have installed mt.exe on the computer before you can edit the manifest. Use mt.exe to interact with the manifest using command-line arguments. If mt.exeis not on the computer, download the Software Development Kit from the Microsoft Web site. The Windows Software Development Kit for Windows Vista and .NET Framework 3.0 Runtime Components contains mt.exe. Refer to the KnowledgeBase for information about downloading this SDK.
  2. To edit the manifest, you must first retrieve it. Complete the following steps to retrieve the manifest.
    1. Open the command line window.

      Note  On most Windows operating systems, you can access the command line window by selecting Start»Run, entering cmd in the Open text box and clicking the OKbutton.
    2. Enter the following command to retrieve the manifest: mt.exe -inputresource:directory path\Application Name.exe -out:Application Name.manifest in the command line window where directory path is the path to the built application and Application Nameis the name of the application.

      Note  If mt.exe is not in the same directory as the application whose manifest you want to retrieve, you must specify the path to mt.exe in the previous command.
    3. Press the <Enter> key to run the command. The application manifest with the file extension .manifest appears in the same directory as the application.
  3. Complete the following steps to edit the manifest.
    1. Right-click the manifest in the destination folder and open the file in a text editor or an XML editor.
    2. Locate the code <requestedExecutionLevel level="asInvoker" uiAccess="false"/>. Change the value asInvoker to requireAdministrator or highestAvailable depending on the execution level you want the built application to have.
    3. Save the manifest file.

Validating the Manifest

The tags within the manifest are case sensitive. It is good practice to validate the changes you make to the manifest after you edit it. However, validating the manifest does not find spelling errors. Complete the following steps to validate the manifest.
  1. In the command line window, enter the following command to validate the manifest: mt.exe -manifest Application Name.manifest -validate_manifest in the command line window whereApplication Name is the name of the application.
  2. Press the <Enter> key to run the command.

Applying the Manifest

After you edit and validate the manifest, you must apply the changes. Complete the following steps to apply the manifest.
  1. In the command line window, enter the following command to apply the manifest: mt.exe -manifest Application Name.manifest -outputresource:directory path\Application Name.exe;#1in the command line window where directory path is the path to the built application andApplication Name is the name of the application.
  2. Press the <Enter> key to run the command.

Digital Signing

Digital signing lets users verify who created an application and decide whether the application is safe to install or run. Because Windows Vista offers additional levels of security, users might encounter additional dialog boxes warning them about the risks of installing or running unsigned applications. By default, LabVIEW does not sign built applications so you can customize the digital signature for an application. To reduce the amount of dialog boxes a user encounters, sign LabVIEW built applications and installers.
Note: You cannot sign applications or installers in versions of LabVIEW prior to 8.0.
You need the following tools to sign an application or installer:
  • Signing certificate—You can purchase signing certificates from a number of vendors, including Verisign. You can purchase signing certificates only for companies or organizations. Individuals cannot purchase signing certificates.
  • Signing tool—The Windows Driver Kit includes the signing tool. You use the signing tool to apply the digital signature. Refer to the KnowledgeBase for more information about downloading the Windows Driver Kit.
To sign a LabVIEW built application, you need to sign only the .exe file. To sign a LabVIEW built installer, you need to sign only the setup.exe. You do not need to sign any other files for LabVIEW built applications and installers. Digital signing involves procuring third-party providers for digital certificates, and no single procedure for signing code exists. Refer to the KnowledgeBase for more detailed information about digitally signing applications or installers for deployment on Windows Vista.

Examples

When you edit manifests and sign applications or installers, you must do so in the correct order to avoid overwriting the manifest or voiding the digital signature. You must always edit and apply the manifest before signing the application or installer. The following examples suggest the order you should follow for editing manifests and applying digital signatures.

LabVIEW Built Applications

  1. Build the application.
  2. Edit the application manifest, if necessary.
  3. Sign the application .exe file.
  4. Build the installer.

LabVIEW Built Installers

  1. Build the installer.
  2. Sign the setup.exe file.
Rebuilding a LabVIEW built application or a LabVIEW built installer results in setting the manifest back to the default settings. If you make changes in the manifest and then rebuild the application or installer, you must change the manifest again. Additionally, if you rebuild an application or installer that you signed, you must sign the application or installer again.

'via Blog this'
Posted by at No comments:

Saturday, 10 November 2012

Big kitchen or tiny kitchen and utility room - Home Improvement in Ripley - Zoopla

Big kitchen or tiny kitchen and utility room - Home Improvement in Ripley - Zoopla: "It is a detached family home so kitchen facilities are important, 'the heart of the house' as they say. So a good size kitchen space would probably be best, but as Mark said be mindful of costs in the current market. If when on the market it proves a repeated problem maybe thats the time to consider it."



Photo of garethb1
garethb1
It is a detached family home so kitchen facilities are important, 'the heart of the house' as they say. So a good size kitchen space would probably be best, but as Mark said be mindful of costs in the current market. If when on the market it proves a repeated problem maybe thats the time to consider it.




'via Blog this'
Posted by at No comments:
Subscribe to: Posts (Atom)