Why do I get horrible resolution using Benchtop Function Generator.vi

At 200 Hz, the resolution on my Oscilloscope is horrible, I am running a sine wave, but it looks more like a square wave. What can I do to improve this so that I get good resolution at 1000 Hz

Hi John!
The infos you provide are very scanty.
Please tell me, what Hardware and Software you use. Are you measuring a real word signal or a simulated (Software)?
If you are measuring a real world signal - what device do use to accomplish this?
Please be aware of sampling theorem!
Stefan
Impossible is nothing - nothing is impossible

Similar Messages

I want to use the Function Generator VI to send command signals through the NI 7344 motion controller. This will be a closed loop servo valve system. I want to be able to change from say a square wave to a sine wave on the fly. Idea's?

I am going to run tests that require an actuator to move using various types of arbitrary waveforms such as sine or square. The NI 7344 is hooked to the UMI that is going through a driver for a servo valve. The loop is analog and it is closed. I have played with some of the examples but can't get it to work. I have used the function generator VI to generate a signal but I think I am using the wrong input VI to the motion control board. When I use what I have it moves the servo and then stops. It doesn't continually generate the signal.
I would love to use the controls on the function generator vi to control frequency and amplitude ect. Any help or pointer would be helpful. Thank you in advance.

Hello,
I'm not clear on exactly how you want to use the generated data but I'm assuming they will be used as your target points.
There's a built-in example for motion called 'One-Axis Contour Move.vi'. This example demonstrates how to provide your target points as 1-D array. All you need to do is to replace the input array with the output of the function generator. In order to have it run continuously, use a while loop. You can further program your application so that it'll change the waveform on the fly by monitoring the user interface but this might be little little tricky as you will need to reset the move and load the new generated points while keeping track of your current position.
I hope this helps. Let me know if you have further questions regarding this
application.
Best regards,
Yusuf C.
Applications Engineering
National Instruments

Elvis: Is It possible to use the Function Generator and the Oscilloscope simultaneously?

Hi,
We are using the NI Elvis to output a function or a sine wave at a certain frequency and using the oscilloscope on the same board/elvis to read a modified signal. Is this possible? Can we use both the Function Generator and the oscilloscope at the same time? Please help. The oscilloscope would be reading signal from an accelerometer. Thank you in advance. We have no VI as we do not know which to use and if they are possible.

Hi,
There is no problem using the Function Generator and Oscilloscope
at the same time with NI ELVIS. Using the NI ELVIS soft front panels (Start
>> Programs >> National Instruments >> NI ELVIS 3.0 >>
NI ELVIS – see picture attached –‘NI ELVIS soft front panels.JPG’), you can choose
to open more than one instrument at a time. We do this by opening one
instrument, allowing it to begin, and then opening another. We can also program
in LabVIEW using more than one instrument at a time by placing down multiple
Express VI’s taken from the NI ELVIS pallet on the block diagram (see picture
attached – ‘ELVIS Express VI's (LabVIEW).JPG’). One note when doing this,
please see KB 41ODPHX1
for an example of how to program in parallel. If you do not wire the ‘stop’
terminal of the express VI’s, you will get the error described.
David L.
Systems Engineering
National Instruments
Attachments:
ELVIS Express VI's (LabVIEW).JPG ‏74 KB
NI ELVIS soft front panels.JPG ‏56 KB

I am using the function generator example

i am using the function generator example to send sine, triangular, sawtooth waves to oscilloscope.
I would like to send not only the symmetric but also unsymmetric amplitude of each wave.for example the upper peak of the amplitude, i could adjust as 2 volts and the lower peak as 3 volts or vice versa.how it works in function genartor example.Please note the i am using data acquisition card AT- MIO-16XE-50 for this purpose.please tell me with some example.

To add a terminal to the connector pane, right click on vi icon and select show connector. Notice that the mouse pointer turns to a wiring tool when over the connector. Click on a small box inside the pane and then click on a front panel control or indicator to connect that box to the control/indicator. Then repeat for the next control/indicator. Do this until all the inputs (controls) and outputs (indicators) you need are defined. Normally, all inputs are on the left half and all outputs are on the right half, and Error In is connected to the bottom left box, and Error Out is connected to the bottom right box. You can change the terminal pattern by right clicking on the connector pane and pointing to pa
ttern and then selecting a pattern. To make the graph as an output, click on the top right box then click on the waveform graph.
As for continuous update, put the graph inside a loop where you generate your waveform and wire the output to the graph. As long as the loop is running, you will get a continuous update. The Y axis can be configured for amplitude and the X axis for time. Right click on the graph and select properties. Play with this to become familiar with all aspects.
- tbob
Inventor of the WORM Global

WHY THE IPHONE GETTING HOT WHEN USING 3G PLUS WITH DATa?, WHY THE IPHONE GETTING HOT WHEN USING 3G PLUS WITH DATA?

why my iphone 4s getting hot when using 3g plus with data?
then my phone left side speaker didnt work when i list songs?

It is normal for the phone to get hot when your using data such as YouTube videos, streaming music etc.. And as for the left speaker not working, the left speaker is a microphone, the right one is for sound. Don't worry, everything your iPhone is doing is normal.

Why my cellphone gets hot without using

Why my cellphone gets hot without using

Operate iOS devices where the temperature is between 0º and 35º C (32º to 95º F). Low- or high-temperature conditions might temporarily shorten battery life or cause the device to alter its behavior to regulate its temperature.
Store the device where the temperature is between -20º and 45º C (-4º to 113º F). Don’t leave the device in your car, because temperatures in parked cars can exceed this range.
When using the device or charging the battery, it is normal for it to get warm. The exterior of the device functions as a cooling surface that transfers heat from inside the device to the cooler air outside.
Conditions and activities that may cause the device to alter performance and behavior include:
Leaving the device in a car on a hot day.
Leaving the device in direct sunlight for an extended period of time.
Using certain features in hot conditions or direct sunlight for an extended period of time, such as GPS tracking or navigation in a car, or playing a graphics-intensive game.
If the interior temperature of the device exceeds the normal operating range, the device will protect its internal components by attempting to regulate its temperature. If this occurs, you may notice the following:
The device stops charging.
The display dims or goes black.
In navigation:The device will present an alert and turn off the display:
Navigation will continue to provide audible turn-by-turn directions. When approaching a turn, the display will illuminate to guide you through the turn.
To return the device to normal operation, press the Home Button and slide to unlock. If the device has cooled down enough, you can continue normal usage.
Drive and ride safely. Give full attention to driving or riding and to the road.
Cellular radios will enter a low-power state. The signal may weaken during this time.
The camera flash is temporarily disabled.
If the device exceeds a certain temperature threshold, it will present a temperature warning screen similar to this:
To resume use of your device as quickly as possible, turn it off, move it to a cooler environment, and allow it to cool down.
Note (iPhone only): When this message appears, the device may still be able to make emergency calls.

How get OBJECT_ID for using ARCHIV_BARCODE_GLOBAL function?

Hello experts:
Do you know how can I get the object_id that I must fill for using ARCHIV_BARCODE_GLOBAL function?
Please any help is very helpfull.
Best regards and thanks in advance for your time.
Miriam

I think you can get this in the interface. Ideally this gets populated in TOA01 or TOA02 or TOA03 table.
also check table
BDS_BAR_EX
BDS_BAR_IN
Thanks
Arghadip

JPG or PSD to PDF get horrible resolution degradation

Using Photoshop 9 / CS2 and Acrobat Pro 7, I make a nice cover page with
text and images at 300 dpi. Both the psd and jpg are very smooth.
I save to pdf, or print to pdf thru Acrobat driver and get CRUD, as if resolution is below 72dpi. Why? I have set "Adobe PDF" printer driver to max res, no compress.
Is there any other way of output to end up with GOOD pdf?

Actually, I have tried both "saving as PDF or printing to PDF" from PS-CS2.
I just did something that DID make good output.
Clicked JPG to open in file-manager's viewer, chose FILE/PRINT, chose Adobe-PDF driver, printed to PDF, seems full 300 dpi.
In PS-CS2, I had set all JPG to max-res and disabled down-sampling, still got those crud results. Using WordPerfect's publish to PDF got same crud results, again, supposedly without down-sampling.
I'd like to understand what's going on, but do now have usable PDF for ebook cover.

Why do I get -18001 Errors using Customised TestStand User Interface

Hi all
I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
If anyone
has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
Thanks
Dave

David,
I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
LabVIEW : VI is not executable.
An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
2) The same error will occur when
a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
Building The Operator Interface
The following are steps if you are using a LabVIEW operator interface.
1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
Creating a LabVIEW Run-time Server
If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
Assembling the Test VIs for Run-Time Distribution
This distribution process uses one of the shipping TS examples that calls LV VIs.
1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
3) Confirm that the sequence runs without problem.
4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
6) Set the target directory to be something distinct like C:\temp\AssblVIs.
7) If you are using TestStand 2.0 skip adding Dynamic VIs
8) Save with or without diagrams. Its your choice.
Change Search Directories
Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
1) In the sequence editor select Configure>>Search Directories.
2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
3) Close the Edit Search Directories dialog box.
4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
1) In the sequence editor select Configure>>Adpaters.
2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
Distributing Components
-To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
-To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
-You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
Hope this helps.
Regards,
Kitt
=========================================
Title:
Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
Components that need to be distributed:
TS engine
Operator interface
LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
LabVIEW run-time engine
LabVIEW test VIs
Test sequence files
Actions before distributing:
It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
Assemble the test VIs for distribution.
Update the TestStand search directories so that the sequences reference the assembled VIs.
Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
Test the distribution components on the development machine.
Enter section headings, separating each section with a line break:
TS Engine Component
Operator Interface Component
LabVIEW ActiveX Server
Configuring the LabVIEW Standard Prototype Adapter
LabVIEW Run-time Engine Component
Assembling your Test VIs for Distribution
Note
TS Engine Component
With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
Operator Interface Component
You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
LabVIEW ActiveX Server
You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
Configuring the LabVIEW Standard Prototype Adapter
When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
LabVIEW Run-time Engine Component
If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
Assembling your Test VIs for Distribution
After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
Links: See Distributing LabVIEW Test VIs below
Note
Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
==============================================

Why do I get artifacts when using the adjustment brush to increase or decrease exposure?

When using the adjustment brush to darken a background I get white or light colored artifacts. When using the brush to lighten the eyes of a person I get brown artifacts that look like freckles in the area of adjustment. That didn't happen in LR 3.

Here are the screen shots with the original, with Auto Mask on and without Auto Mask.
Thanks to C. Frans W for the suggestion of it being an Auto Mask issue.
Dorin, if you have any other comments, I would welcome them.
If C. Frans W has additional comments those are welcome also.

Why do I get a ClassCastException using JNDI between ears?

This is an issue that has bothered me for almost a year. It comes up every once in a while and usually I can find a workaround, but I need to understand what is causing the failure.
Here is the problem description as an abstract example:
I have two WAR files deployed on WL (8.1 sp3), WarA and WarB.
In a servlet in WarA, I execute the following:
Context context = new InitialContext();
MyObject myObj = new MyObject();
context.bind("myObject", myObj);Then, in a servlet in WarB, I execute the following, receiving a ClassCaseException on the last line of code:
Context context = new InitialContext();
Object obj = context.lookup("myObject");
MyObject myObj = (MyObject)obj; //ClassCastException!!Of course I have deployed MyObject.class in a jar file inside the WEB-INF/lib of each WAR.
I understand that each WAR file uses a seperate ClassLoader, but I do not understand why the object's class is not recognized when it is retrieved. I have tried several debugging methods (obj.getClass().getName() or halting execution using a debugger and looking at the object's class signature). In every instance the classname looks correct, exactly as I would expect it to, but the ClassCastException is thrown anyways.
In the past I have "copped out" by creating an EAR, putting both WARs in the EAR, and adding the jar containing MyObject to the APP-INF/lib.
Unfortunately the most recent occurrence of this problem is more complex and I do not have the luxury of my standard workaround. Can someone please fill in the blanks of what elementary concept I am overlooking?
Thanks
JB

I don't think the classloader-structure tag is exactly what I am looking for. Based on the documentation I reviewed on the edocs site, that solution appears to make sense if you are manipulating numerous classloaders within a specific ear.
I suppose you could try to use the classloader-structure to reference a classloader from a seperate application, but the docs do not indicate that this is a possibility. Moreover, it seems dangerous and potentially very confusing.
Ultimately, I think this boils down to a lesson for me about classloaders. Unless someone can tell me otherwise, I am ready to concede that you cannot access/cast an object that you have bound to the JNDI tree in one application from within any other application. The notable exception to this rule is the scenario where the class type to which you are casting is a class that is loaded by the system classloader.
This makes some sense to me - each standalone war or ear is independent of other wars/ears deployed on the app server. But, it is also somewhat frustrating because you cannot share global services across a suite of applications via JNDI unless you bundle them all as a single ear.

Why am i getting redirected when using search engiens

when i use any search engine i get redirected, what can i do to correct this?

Do a malware check with some malware scanning programs.<br />
You need to scan with all programs because each program detects different malware.<br />
Make sure that you update each program to get the latest version of their databases before doing a scan.<br />
* http://www.malwarebytes.org/mbam.php - Malwarebytes' Anti-Malware
* http://www.superantispyware.com/ - SuperAntispyware
* http://www.microsoft.com/windows/products/winfamily/defender/default.mspx - Windows Defender: Home Page
* http://www.safer-networking.org/en/index.html - Spybot Search & Destroy
* http://www.lavasoft.com/products/ad_aware_free.php - Ad-Aware Free
See also:
* "Spyware on Windows": http://kb.mozillazine.org/Popups_not_blocked

Why am i getting hyperlinks without using a /a tags?

Im using Dreamwever6 and im very new at this.
I have code showing up as a link when i preview it but there is no anchor tag set for a link. I've previewed in Safari, Fire Fox, and Chrome. I've included the html below. The lines that display incorectly are in bold.
<!doctype html>
<html>
          <head>
              <title>Project Title</title>
    <body>
                    <div id="top">
                              <div id="logo">
                      <img src="_img/ManchesterLogo.jpg" />
            </div>
            <div id="social-media">
                      <p>For Additional Info<br />Please call 555-555-0000</p>
                <ul>
                          <li><a href="http://www.facebook.com" /><img src="#" /></li>
                    <li><a href="http://www.twitter.com" /><img src="#" /></li>
                    <li><a href="#" /><img src="#" /></li>
                    <li><a href="http://www.linkedin.com" /><img src="#" /></li>
                    <li><a href="http://www.yelp.com" /><img src="#" /></li>
                    <li><a href="http://www.youtube.com" /><img src="#" /></li>
                </ul>
            </div>
                    </div>
        <div id="topnav">
                  <ul>
                      <li><a href="#" />Welcome</li>
                <li><a href="#" />About</li>
                <li><a href="#" />Products</li>
                <li><a href="#" />Services</li>
                <li><a href="#" />Gallery</li>
                <li><a href="#" />Contact</li>
            </ul>
        </div>
        <div id="banner">
                  <img src="#" />
        </div>
        <div id="content-wrapper">
                              <div id="content">
                              <h1>This is a level one heading that displays as a hyperlink.</h1>
                <p>This paragraph also showing as a hyperlink.</p>
            </div>
            <div id="rightside">
            </div>
                    </div>
        <div id="footer">
        </div>
          </body>
          </head>
</html>

You're about to have a palm to forehead, ah haaaaa moment.
You didn't close any of your menu anchor <a> tags.
Change this:
<ul>
                <li><a href="#" />Welcome</li>
                <li><a href="#" />About</li>
                <li><a href="#" />Products</li>
                <li><a href="#" />Services</li>
                <li><a href="#" />Gallery</li>
                <li><a href="#" />Contact</li>
</ul>
To this:
<ul>
                <li><a href="#" />Welcome</a></li>
                <li><a href="#" />About</a></li>
                <li><a href="#" />Products</a></li>
                <li><a href="#" />Services</a></li>
                <li><a href="#" />Gallery</a></li>
                <li><a href="#" />Contact</a></li>
</ul>
Nancy O.

Why do I get horrible Quality when I export!?!

I recently exported a movie (filmed with my Sony Hdr Fx7) from FCP5 and its very pixelated, especially when theres camera movement. Also at certain parts in the movie the audio does not match the video at all. I exported in all default settings. Whats my problem? HELP

Yeah guys its in quicktime and Kevin Brock, I already had those settings for quicktime like that, the quality is still ****. I took some snaps shots with apple shift 4 but I'm not sure theres any way I could show you guys them on the forum. Right now I'm just trying to get the quality figured out then I'll worry about the audio. Any suggestions?! I definitely think its something in final cut not quicktime
Message was edited by: Director93

ExtendScript Help - Why am I getting "prompt is not a function" error?

Hello RH friends,
I need to search through my 2200+ topic project, find any topics that use a certain image in the source and then open up that file in the wysiwyg editor to visually see what's happening to the conditional markings on those topics. I need to open them in chunks since I've determined there are some 600+ topics that has the image I'm looking for. Seems like something a script would be able to handle. Does anyone have a script that does something like this or something similar?
Anyway, I started messing around in the script editor with a test script to figure some of this out, but I get an error right off the bat when I try using the standard js prompt method to capture a text
string. I have these two lines of code in my script:
var strText = prompt ("Type a string to search for. Topics with that string will then open in the RH viewer.","i_chiclet.gif","String to Find");
alert (strText);
Running it directly from within the script editor, the prompt command works fine.
However, running the script from within RH--which is what I need to do for it to work on the current project to look at, I get a message that says:
"prompt is not a function."
What am I missing?
I'm using RH 9.02.271
Windows 7 64-Bit with adminstrator access

RH ExtendScript bug... Use Window.prompt() and it'll work. The same goes for confirm: Window.confirm() does work. Alert() does work however and prompt and confirm work in ExtendScript toolkit itself.
I've never tried opening a topic in the WYSIWYG and I don't think that RoboHelp supports this. You can open a file with ExtendScript, but that just launches the file in default viewer (probably your web browser). I'll look into opening a topic in the WYSIWYG, but I can't promise anything.
Greet,
Willam

Why do I get horrible resolution using Benchtop Function Generator.vi

Similar Messages

Maybe you are looking for