Labview 6.0 Distribution disks
How do I create dictribution disks using labview 6.0 Application builder? The web site says "For LabVIEW 6i, the image files for your distribution disks will be in disks subdirectory within the destination directory that you specified in the initial Application Builder screen. You can copy them to 1.4 MB floppy disks by copying the Setup.exe file and the Data.001 file to the first disk, and then each Data.00x to a different disk, resulting in N setup disks for your application (where N is the number of data files generated during the build process)"
But I do not see any "disks" subdirectory at all! Instead a the following set of files are created in the destination directory:
application.exe
IndsMsi.exe
InstMsiW.exe
application.cab
application.msi
setup.exe
setup.ini
The other question I have is , if I ship it on a CD, what are the files I need copy to the CD?
Those files were created by the 6.1 application builder and not 6.0. For 6.1, NI switched to the Microsoft installer (the .msi files). To ship these on a CD, copy everything except for the application.exe file. Also, if you have 6.0 development but the 6.1 application builder, you might have some problems and I would recomend getting the versions in sync.
Similar Messages
-
Hello
I am using labview 7.0 to make a distribution disk.
I have followed the steps in the guides and I have created the installer and all its related files.
I can run the installer and create a single *.exe file, and a *.ini file in my Installation sub dir.
When I run the *.exe my PC just gets swamped with VI's, about 256 all opening up at the same time.
Can anyone explain what is happening, whether this is the norm - though I would say not. And most importantly what I need to do to get a sensible outcome
Thank You
ChrisHi Dennis
Thanks for the reply.
I had all my VI's as top level VI's, which may have been the cause of the problem.
The reason behind this selection was I don't really have one top level VI. The VI's are Labview versions of individual GPIB commands, all of which need to be visible to update and query the instrument configuration through Labview
I also have VI's that are designed to set up and take measurements, I built an "exe" for one of these and got a result that I was expecting, ie when I installed and ran the exe, only the one VI was opened, and was executable.
It would appear that I will have to create lots of "exe's", or I will have some redesigning to do to be able to distribute all the configuration commands.
Thank You -
LabVIEW 2013: Source distribution, destination path for post build VI changed?
Hi,
In a source distribution for an embedded target (Real-Time for instance) you specify both "Local destination directory" and "Target destination directory". Let's say the local directory is "C:\MyProject\MyModules\", and the target directory is "C:\" for instance. Then on my build machine my source distribution will end up in "C:\MyProject\MyModules\c\<source distrib files>", and I can then FTP everything from <source distrib files> to the root of my target's c-drive (or in some cases I can just deploy directly after the build, and LabVIEW will move the files to the target for me).
You can also specify a Post Build VI that can do stuff to your source distribution after the build has completed. Such a Post Build VI has an input named "Destination Path" for use inside your Post Build VI, so you can find your files to operate on :-)
In LabVIEW versions prior to 2013 this destination path would be "C:\MyProject\MyModules\c\", but in LabVIEW 2013 the destination path is only "C:\MyProject\MyModules\" thus missing the target destination directory part. Now my Post Build VI can no longer find my source distribution files, unless I inside that VI hardcode the target destination directory - and that isn't a good solution.
Is this changed by design in LabVIEW 2013, or is it a bug?
Cheers,
Steen
CLA, CTA, CLED & LabVIEW ChampionI don't do a lot of (actually any) source distributions of embedded files, but I can tell you that there was a bug in earlier versions where during an application build, the destination path was reported incorrectly. Perhaps this is related.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps -
Build installer LV2009, requires OLD distribution installation disks?
When building an Installer using LabVIEW 2009, and including additional distributions, why does the installer builder require the original distribution disks from the install DVD/CDs? Why are the version required not promoted to the LATEST update installed? This is a real PITA when I have to go find the disks from 1Q2009, no wait, it did not ask for that, it asked for Feb 2009 device drivers disk 2.
This is as bad as Microsoft for installing from original distributions.
It is not a good thing to expect that I have to maintain a library of DVDs/CDs for every distribution/update I have ever used. Especially when I am taking work home, and do not have access to this ENTIRE library, rather a copy of the lasest update ONLY.
to National Instruments, Thoughts on this?
Paul <--Always Learning!!!
sense and simplicity.
Browse my sample VIs?Thanks Craig... BUT, I only have LabVIEW 2009 Intalled. although I have upgraded components through the quartely updates. So while what you say is true... it does NOT necessarly mean that you have 'multiple' versions of the LabVIEW development environment installed
That said... I have been at this for a little while (more than a day, but less than the time since dinosaurs walked)... and app building is something that has become much more complicated over time... I want to know WHY NI does not promote the installers/distributions to the most current version on the update DVD/CD where applicable... but you bring up a good point... If it cannot promote the distribution, it should give you a warning and ASK you if you wish to 'cache' the obsolete distribution as it does when building the current distribution. This gives you an option to cache it WHILE the distribution is handy.
Failing that, in the project, there should be an option to have it display the currently required distributions as opposed to having to build the installer object, start the installer build, then wait for it to ask you.... by then it maybe too late.
I realize that you are trying to help/offer workarounds... I appreciate what you are trying to do... BUT, in this case, I want NI's people to justify what they are doing and why. This goes beyond wish list, this requires justification, as even Microsoft has addressed this issue.
Paul <--Always Learning!!!
sense and simplicity.
Browse my sample VIs? -
10.4.11 Installed -Safari Crashes, Disk Utility Won't Open
Installed 10.4.11 yesterday via software update on our 2.0GHz Core Duo Macbook Pro.
After installing Safari crashes seconds after opening (it freezes then crashes) and then I downloaded the 10.4.11 update from Apples website (using firefox) but Disk Utility won't open it. If I try and launch disk utility myself it just bounces in the dock once and closes. Please help!Same here - two identical iBook G4's, both updated to 10.4.11 - one is fine and everything works, the other one has the following problems: safari crashes 100% of the time, USB devices are failing to be recognised (mouse, storage key etc).
Looking in /var/log/system there is an error message saying a previous version of a kernel module is already loaded (cant get to the original error message text sorry!).
Looking on other forums looked like a simple 'trash the cache' fix - which I did - and hey presto the usb devices started working - but not safari. Messing around trying to flush out a safari cache failed after a few attempt, as did fixing file perms, zapping PRAM, booting from open firmware, and all the other usual things mentioned in the forums.
As it happens the iBook has nothing precious on it - so though to reinstall from the original installation disk. iBook G4 specific OSX Tiger distribution disk 1 inserted, but iBook now refuses to boot from it - holding down the c key on reboot just pops up a blue screen with a folder icon on it and an alternating finder and question mark logo - as in 'error I can't find a system on this installation disk' - the iBook then boots from the internal disk - getting nowhere fast.
Out come the Leopard install disks, and iBook quite happily boots from there and is right now doing a clean install from them (like I said nothing precious on there and thats why I cant get to the original error message...).
I've seen lots of posts about folks struggling to boot from the original install disks recently - wondering if patch 11 did something to knock the OSX version number on the machine greater than the version on the shipped G4 install disks??
And there is something very odd about patch 11 that seems to have hit this iBook and not my other one - they both installed fine, they have identical software apps on them and they are both the same spec.
Can't help more than this - but given I've seen these issues raised in several places worth adding to the thread. -
LabVIEW 2013 SP1 Compile Worker Fails
Hello,
after receiving the new DVDs with LabVIEW 2013 SP1 and successfull installation, I wanted to compile my FPGA.vi.
The Compile Worker does not start an I get the attached error Message. The additional Download of Xilinx Compilation tools 14.4 from the NI Website does not help.
When I choose the FPGA Compilation Tools via the Start menu, the Compile Worker does not start. When I try to start the FPGACompileServerConfiguration an Error occurs (see picture).
At the Moment I hav not Idea what to do. Perhaps someone can help.
What does I have to do to convert my system back to the Version 2013?
Attachments:
FehlermeldungCompileWorker.jpg 41 KB
ErrorwhenstartingFPGACompileServerConfiguration.jpg 15 KBdfschunk,
Thanks for your post. We are aware of an issue with the compile tools installed from the 2014 developer suite (2013 sp1) where the compile worker is installed with missing dependencies. We are taking immediate action to push out a fix for this and you will receive a notification through NI update service when the fix is available.
In the meantime, our recommendation is to downgrade to the 2013 installation of the Xilinx tools. No fixes were made between 2013 and 2013 sp1 in the compile worker or in the Xilinx tools so no worries there.
Go to Control Panel >> Programs and Features and select National Instruments Software.
This will launch a window where you have the option to select various NI software products and modify/repair/remove them.
Select NI LabVIEW FPGA Xilinx 14.4 Tools and select Remove.
After the software has been un-installed, go to the NI LabVIEW 2013 FPGA Module Xilinx Tools 14.4 donwloads page and install this version of the tools (released with 2013) or you may install the tools from your original LabVIEW 2013 developer suite disks.
Please post back or call support if you have any problems with this process, we want to make sure you are up and running until we push out a fix.
Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments -
Calling Matlab 7.1 from LabView 6.1
Hello,
I am using LabView 6.1 and I have recently installed Matlab 7.1 on the same machine.
When I try to call Matlab by a Matlab script node, I only get the error
message that the script could not be executed and that a failure
occured calling the script server. (This does not depend on what script
I implement.)
Earlier, I had Matlab 6.5 which worked well with the script nodes.
What can I do to get the script nodes running?Hello ffffff
I can pretty much assure you that LabVIEW 6.1 has not been tested with MATLAB 7.1, and "officially" I might go so far as to say it's not supported.
That said, you might try downloading the MATLAB Script.zip file attached to this KnowledgeBase entry:
http://digital.ni.com/public.nsf/allkb/4475BC3CEB062C9586256D750058F14B
Follow the directions in the KB to update the matscript.dll file in your LabVIEW 6.1 distribution, and this might resolve the issue. This addressed numerous issues with the MATLAB script node so that version 7.0 of MATLAB would work well with LabVIEW. I'm not sure if this version of the matscript.dll has been tested with LabVIEW 6.1 or not, but in theory it should work. Also, if the problems you are encountering are new to MATLAB 7.1 in specific, there may not yet be a solution for this; I don't know how new MATLAB 7.1 is.
Good luck!
Message Edited by Jeff B on 02-16-2006 07:44 AM -
Custom Control relies on a special font - Include it with distribution?
If you create a control that relies on a special font, does that font need to reside in the built application directory and/or <Windows/Fonts>?
I have a control that looks like a 7-segemt LED, and it relies on a "LCD" font.
Thanks,
Richard
RichardCOOL, I didn't know NI had a font. Thanks,
My original question concerns the need (or lack of) to include such a font on the distribution disk when you make an EXE?
Richard -
I need to reinstall Adobe Audition CS5.5 on a Windows 7-32 machine. The distribution disk doesn't work. Last time I was given a link by support to download an installable version. Need help to find!
http://prodesigntools.com/adobe-cs5-5-direct-download-links.html
Follow the Very Important Instructions before you try to download -
CD/DVD drives can't read Acrobat X Pro disk
My CD drive and DVD drive are unable to read my installation distribution disk. However, they can read an earlier version of Acrobat 7 Standard. Do I need to update my drives? I also have the same problem when trying to install FrameMaker 9. Please advise.
>Do I need to update my drives?
Possibly, but it stretches my mind a bit to think that TWO drives won't work
The easiest thing to do is go into Control Panel and remove the device(s) and then do a restart and let Windows "find" the drive(s) again and install the drivers
Only if that doesn't work should you go to the vendor site(s) to find a firmware update
Do you have problems reading any other discs? -
I have a problem with the installer build in 8.6.1. The short story - I build an executable and then an installer. In the installer I have the 8.6.1 Runtime checked on the Additional Installers page. Every thing is OK (except it prompts me for my disk for something in the 8.6.1 distribution, but that works OK and the build continues). I can modify the application, rebuild the exe, and then rebuild the installer - all OK so far. Now, I exit LabVIEW and install the application on my development machine - I do this to try and see if I have any obvious problems with the application or installer (like missing VIs for dynamic calls or config files) before I take it to the lab. This also works OK. Now, I see something that needs modification. I open LabVIEW, modify the VI that needs it, save, rebuild the application, and then try to rebuild the installer. Only now, the installer opens the Locate Distribution dialog and insists that "LabVIEW needs to copy a component installed or updated by the distribution" and it's pointing to the distribution (my installer) that I am trying to build. This circular dependency can't be resolved and the build fails. Here's some excerpts from the build log
Getting distribution information for NI LabVIEW Run-Time Engine 8.6.1
This product is cached. Skipping.
Getting distribution information for NI MetaUninstaller
This product is cached. Skipping.
Getting distribution information for MDF Support
This product is cached. Skipping.
Getting distribution information for NI Service Locator
This product is cached. Skipping.
Getting distribution information for Math Kernel Libraries
This product is cached. Skipping.
Getting distribution information for NI_Logos_5.0
Product is in volume 1 of distribution with id '{CB09ABD9-FCCC-43BC-B4E1-9DDA6EB98ADB}'
Product is in volume 1 of distribution with id '{FA21606E-6B91-43A2-83DE-199D5045AE5F}'
Adding distribution 'LabVIEW 8.6.1'
Path: D:\Distributions\LabVIEW\LabVIEW861\
Loading distribution information from path: D:\Distributions\LabVIEW\LabVIEW861\
Product is in volume 1 of distribution with id '{FDAAAF1C-1FFC-4C29-A472-27A929FC8489}'
Getting distribution information for NI TDM Streaming 1.2
This product is cached. Skipping.
Complete list of distributions and products to copy:
(0) LabVIEW 8.6.1, Disk 1
Id: {FA21606E-6B91-43A2-83DE-199D5045AE5F} Volume: 1
Path: D:\Distributions\LabVIEW\LabVIEW861\
Products:
(0) NI_Logos_5.0
Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936} Flavor: 'Full'
Path: Products\NI_Logos\
(1) MA231 Tester
Id: {CB09ABD9-FCCC-43BC-B4E1-9DDA6EB98ADB} Volume: 1
Path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
Products:
(0) NI_Logos_5.0
Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936} Flavor: 'Full'
Path: bin\p9\
(2) MA231 Tester
Id: {FDAAAF1C-1FFC-4C29-A472-27A929FC8489} Volume: 1
Path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
Products:
(0) NI_Logos_5.0
Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936} Flavor: 'Full'
Path: bin\p9\
And then,
> The source directory for "MA231 Tester" is invalid because it is at the same location as the deployment destination directory (source = "C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\", destination = "C:\MA231 Tester\Software\Builds\MA231 Tester Installer\").
<<<MDFDistCopyList_GetItemInfo>>> Returning info for distribution 1
Last known path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
Distribution title: MA231 Tester
I can only fix this by uninstalling my application AND going into the registry and deleting the first entry with the GUID under the NI_Logos_5.0 (which refer to my application) - these entries are in the registry under "HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer\Distributions\" - where there are also registry entries for every app I've ever built and installed with LabVIEW - all 300 something. Obviously, the uninstall doesn't do much in cleaning up these things.
So, anybody have any good ideas what to do? OR at least an explanation? I'm leaving soon today and won't have access to email again until Tuesday, 30 June, so if you post and I don't respond immediately please understand that I'm not ignoring the thread.
Thanks,
Mark
This has also been opened as Service Request 7249245I have a problem with the installer build in 8.6.1. The short story - I build an executable and then an installer. In the installer I have the 8.6.1 Runtime checked on the Additional Installers page. Every thing is OK (except it prompts me for my disk for something in the 8.6.1 distribution, but that works OK and the build continues). I can modify the application, rebuild the exe, and then rebuild the installer - all OK so far. Now, I exit LabVIEW and install the application on my development machine - I do this to try and see if I have any obvious problems with the application or installer (like missing VIs for dynamic calls or config files) before I take it to the lab. This also works OK. Now, I see something that needs modification. I open LabVIEW, modify the VI that needs it, save, rebuild the application, and then try to rebuild the installer. Only now, the installer opens the Locate Distribution dialog and insists that "LabVIEW needs to copy a component installed or updated by the distribution" and it's pointing to the distribution (my installer) that I am trying to build. This circular dependency can't be resolved and the build fails. Here's some excerpts from the build log
Getting distribution information for NI LabVIEW Run-Time Engine 8.6.1
This product is cached. Skipping.
Getting distribution information for NI MetaUninstaller
This product is cached. Skipping.
Getting distribution information for MDF Support
This product is cached. Skipping.
Getting distribution information for NI Service Locator
This product is cached. Skipping.
Getting distribution information for Math Kernel Libraries
This product is cached. Skipping.
Getting distribution information for NI_Logos_5.0
Product is in volume 1 of distribution with id '{CB09ABD9-FCCC-43BC-B4E1-9DDA6EB98ADB}'
Product is in volume 1 of distribution with id '{FA21606E-6B91-43A2-83DE-199D5045AE5F}'
Adding distribution 'LabVIEW 8.6.1'
Path: D:\Distributions\LabVIEW\LabVIEW861\
Loading distribution information from path: D:\Distributions\LabVIEW\LabVIEW861\
Product is in volume 1 of distribution with id '{FDAAAF1C-1FFC-4C29-A472-27A929FC8489}'
Getting distribution information for NI TDM Streaming 1.2
This product is cached. Skipping.
Complete list of distributions and products to copy:
(0) LabVIEW 8.6.1, Disk 1
Id: {FA21606E-6B91-43A2-83DE-199D5045AE5F} Volume: 1
Path: D:\Distributions\LabVIEW\LabVIEW861\
Products:
(0) NI_Logos_5.0
Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936} Flavor: 'Full'
Path: Products\NI_Logos\
(1) MA231 Tester
Id: {CB09ABD9-FCCC-43BC-B4E1-9DDA6EB98ADB} Volume: 1
Path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
Products:
(0) NI_Logos_5.0
Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936} Flavor: 'Full'
Path: bin\p9\
(2) MA231 Tester
Id: {FDAAAF1C-1FFC-4C29-A472-27A929FC8489} Volume: 1
Path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
Products:
(0) NI_Logos_5.0
Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936} Flavor: 'Full'
Path: bin\p9\
And then,
> The source directory for "MA231 Tester" is invalid because it is at the same location as the deployment destination directory (source = "C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\", destination = "C:\MA231 Tester\Software\Builds\MA231 Tester Installer\").
<<<MDFDistCopyList_GetItemInfo>>> Returning info for distribution 1
Last known path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
Distribution title: MA231 Tester
I can only fix this by uninstalling my application AND going into the registry and deleting the first entry with the GUID under the NI_Logos_5.0 (which refer to my application) - these entries are in the registry under "HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer\Distributions\" - where there are also registry entries for every app I've ever built and installed with LabVIEW - all 300 something. Obviously, the uninstall doesn't do much in cleaning up these things.
So, anybody have any good ideas what to do? OR at least an explanation? I'm leaving soon today and won't have access to email again until Tuesday, 30 June, so if you post and I don't respond immediately please understand that I'm not ignoring the thread.
Thanks,
Mark
This has also been opened as Service Request 7249245 -
LV5 serial write.vi vs hyperterminal difference?
I have a rs232c stepper motor controller connected to a PC running
NT4. I have
full control of the device (read and write) when using the
hyperterminal program (comes with NT4)
and everything work fine.
Without changing anything except running Labview<->Serial.vi from the
LV5 distribution
disk, I was only able to listen (serial read.vi ) to the device but
not controlling it. It appears
that ascii commands sent (serial write.vi) are ignore by the device,
while the same ascii commands sent via hyperterminal are accepted.
What are the likely reasons for this? The port parameters appears to
be OK because
I was able to read from it.
TIA.Thank you. That solved the problem.
> I think hyperterminal adds the EOL(end of line) itself, and in serial
> write vi YOU must add it, try putting a LF and/or a CR in the string
> you write, and everything should work.
> Hope this helps -
I am using Acrobat Professional version 8 on XP SP3. It had always worked in the past but now, after opening, I get a Runtime error when trying to make a new PDF.
Event Viewer gives:
"Faulting application acrobat.exe, version 8.1.0.137, faulting module adobeupdater.dll, version 5.0.0.316, fault address 0x000475a3."
I have run the Repair in the installer from the original distribution disk to no effect. This was after a system reboot and with nothing else started. The system runs Trend for security, which had not fully started either when I tried to re-run the program. I jave also run repair from the Help menu in the application itself, with a reboot afterward. There have been no significant changes made to the system, except possibly automatic updates, since it was working fine. It even crashes when I try to get the versionn number form the Help-About menu selection.I would suggest going to Help>Repair. Then doing Help>Update to get the updates current. Hopefully that will resolve the problem. When you do a repair from the original CD, you may lose updates.
-
I am trying to build an executible program that will be portable to machines which do not have CVI installed. It works fine on my CVI v9.1 system. However, whether or not I include "Full run-time support" in the build options, I get the error "The procedure entry point _UP_GetActiveTreeCell could not be located in the dynamic link library cvirte.dll" when I try to run it on a machine without CVI. Please help.
To run a CVI application on a system were the CVI IDE is not installed you need to have the CVI RunTime Engine installed. According to the error message at the bottom of this page you may have an older RTE installed in the target system.
To obtain it you can either download the RTE and install in the target system or better let the IDE build a distribution disk that installs all necessary software in it: this guide drives you in creating the appropriate installer for your application: you can find it also in CVI help function.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos? -
"Application Not Found" CS4 installation error
Problem: "Application Not Found" CS4 installation error
Some Adobe Creative Suite CS4 Production Premium distribution disks issue an "Application not found" error while loading Disk 2 due to an error in the Autorun.inf file.
Does your Autorun.inf for Disk 2, 3, or 4 contain
[autorun]
open=Autoplay.exe -auto
icon=\csppdvd.ico
Autorun.inf should instead only say
[autorun]
icon=\csppdvd.ico
There should not be the line
open=Autoplay.exe auto
Only Disk 1 should have this line.
On Disk 1, Adobe has a file called Autoplay.exe which starts the installation.
"open=Autoplay.exe auto" runs the Autoplay application.
Autoplay.exe is not on Disk 2, 3, or 4 so having the open line generates the error.
Since you cannot edit the DVD, the trick is to turn off autorun so Windows doesn't run Autorun.inf upon loading Disk 2. Look at the Wikipedia description of "Autorun" for details. Wikipedia describes how to disable Autorun using
Start -> Run -> gpedit.msc
You will need to do this for XP. Vista has a Control Panel which allows you to "Take no action" for "Software and games". If this does not work, use gpedit.msc instead. You will know Autorun is off if upon inserting Disk 1, no installation window appears.
Wikipedia notes that "AutoPlay is the name of a different feature in Microsoft Windows" not to be confused with Autorun starting the Autorun.inf file.
Now that Autorun is off, manually double click Autoplay.exe on Disk 1 to start the installation. Disk 2 should now load properly.
By the way, it appears you cannot teach an old dog new tricks. Some Adobe Creative Suite CS3 Production Premium distribution disks had the same problem. Obviously, Adobe did not learn from their past mistake.
You may want to call Adobe to obtain replacement disks which don't have this error.
(800) 642-3623 Adobe Technical Support
(800) 833-6687 Adobe Customer SupportPetrula,
Can you look at the DVDs and send me the numbers you find on the inner edge? Also, any numbers on the outer DVD sleeves. This can help us to identify which sets of media are affected and possibly resolve it, or at least more specifically target solution information.
Thank you!
Maybe you are looking for
-
Is there any way I can download 10.5 ?? from the apple site or somewhere online ?
-
Hi all, Just installed the trial of captivate 2, while checking the preview I noticed that the "frame timeline" is stuck on frame 2 (in my case), is this because of the trial or just a small bug? mcteam
-
Find and delete songs unable to locate
I have a lot of songs in my iTunes that I don't have on my computer anymore. Some are marked with the exclamation point, but others aren't because I haven't tried playing them yet. What is the easiest way to find which songs can't be located and dele
-
Hi, My Drag AP element web page works fine in Firefox, not at all in Opera, and quirkily in IE7. I can live without Opera, but I have to fix the quirks. Placing the cursor over the div will not allow me to drag it when the div is small (under about 2
-
Mail downloading phantom messages
Hi everybody. Something strange is happening from about 2/3/ days ago. When I open Mail, on the Mail activity box there are 6 messages downloading but then no new message show up in any of the mailboxes. This is happening every 10-15 minutes. I have